Interesting approach, Timer.
Looking at your code, your DFT looks a lot more like 3x 1 LY tanks then a 1x 3 LY fueltank to me.
Was this your intention ?
P.S. your code is well structured, but i suggest you to read https://bb.oolite.space/viewtopic.php?f=4&t=12149 .
[WIP] Duplex Fuel Tank v0.5
Moderators: winston, another_commander
Re: [WIP] Duplex Fuel Tank v0.5
OS : Arch Linux 64-bit - rolling release
OXPs : My user page
Retired, reachable at [email protected]
OXPs : My user page
Retired, reachable at [email protected]
- timer
- ---- E L I T E ----
- Posts: 336
- Joined: Sat Mar 17, 2012 8:26 pm
- Location: Laenin spiv club
- Contact:
Re: [WIP] Duplex Fuel Tank v0.5
Hi!Lone_Wolf wrote:Interesting approach, Timer.
Looking at your code, your DFT looks a lot more like 3x 1 LY tanks then a 1x 3 LY fueltank to me.
Was this your intention ?
P.S. your code is well structured, but i suggest you to read https://bb.oolite.space/viewtopic.php?f=4&t=12149 .
thank for feedback )
I think my external tank can be full or not )
and it has discrete I/O portions.
hmm... what wrong in OXP code or pack?
Cobra MK III owner since 1994
Re: [WIP] Duplex Fuel Tank v0.5
suppose the dft is empty, and i buy 1 refill only and launch. At that point the dft is 1/3 full .timer wrote:I think my external tank can be full or not )
and it has discrete I/O portions.
I do like the idea of being able to finetune fuel use a bit, and a design with discrete I/O portions does feel like a good choice for rocketfuel.
There's nothing really wrong with your code/pack, but it could be improved.timer wrote:hmm... what wrong in OXP code or pack?
- you don't include a readme file and/or change log in the oxz
- you could add some more comments for documentation purpose
example :this.info = function(cs)
no description what kind of input values cs can have
(in a small oxp like this it's not hard to figure that out, but in larger oxps it matters a lot) - naming
- oolite core functions start with lowercase or uppercase (mainly Constructors) letters.
if oxp functions use those also it could lead to confusion / clashes.
preceding oxp functions with _ (my personal preference) or $ prevents that. - using unique names in oxps helps a lot with troubleshooting.
prepending names with a few letters specific to the oxp makes this easy. - ex:
this.get_current_state
could becomethis._dft_get_current_state
- oolite core functions start with lowercase or uppercase (mainly Constructors) letters.
OS : Arch Linux 64-bit - rolling release
OXPs : My user page
Retired, reachable at [email protected]
OXPs : My user page
Retired, reachable at [email protected]
- timer
- ---- E L I T E ----
- Posts: 336
- Joined: Sat Mar 17, 2012 8:26 pm
- Location: Laenin spiv club
- Contact:
Re: [WIP] Duplex Fuel Tank v0.5
Ok, I understood. I agree with all points.Lone_Wolf wrote:There's nothing really wrong with your code/pack, but it could be improved.
When I'll get a bit free time from coding on main job - I try to do tiny refactor
Thanks!
Cobra MK III owner since 1994
- timer
- ---- E L I T E ----
- Posts: 336
- Joined: Sat Mar 17, 2012 8:26 pm
- Location: Laenin spiv club
- Contact:
Re: [WIP] Duplex Fuel Tank v0.5
real life is time machine from nightmare...
there was a "tiny" delay with the update
uploaded v0.52
there was a "tiny" delay with the update
uploaded v0.52
Cobra MK III owner since 1994