0000042: Tuner title text - version, etc

Notes
(0000063) Fred (administrator) 2008-11-09 20:44	Looking above this box I see that firefox has the page title to the left and it's own name to the right. In release version the build won't be present so I'd be looking for that to be integrated with the name and version at the moment. If that's the case then it makes sense to me to display the firmware version in the title bar next to the tuner version. As mentioned in the forum, the configuration and code should be labeled around the interface stuff. IE, if you follow your name/version structure for the next release it will be : basedir/IFreeEMS\ Vanilla/0.0.1.py or whatever The version of the firmware should be for display purposes and linking bugs only. The interface should define the interaction between the tuner and firmware. So in the info box from the menu, put interface and build and so forth and on public display put tuner name/version - firmware name/version If you think the build is more than just a build tag for dev use then I'm concerned because it implies that you may have more than one 0.0.1 available at any given time which would seriously confuse users IMO. builds for dev, releases for release? These are my thoughts.

(0000074) Fred (administrator) 2008-11-16 14:18	New thoughts : Whatever is displayed should probably indicate what type of device it is talking to at the time. MegaSquirt2 SerialMonitor FreeEMS VEMS etc :-) Fred.

(0000107) sry_not4sale (administrator) 2008-11-28 08:05	Build for commits, versions for packaged/tagged releases. Can you confirm a title scheme and status bar scheme that you would like?

(0000110) Fred (administrator) 2008-11-28 14:25	Well, I think these should be obvious at all times while running : * Tuner exact name and version (regardless of release status, always want to know that even if it's ugly) * Firmware Name and Version (display, not interface) * The type of firmware connected (covered by the last one probably) I'd probably go with just the title bar (use other space for actual tuning) : <tuner name/version> - <firmware name/version> Which for your first release will probably be something like : FreeEMS-Tuner (0.0.1) - "FreeEMS Vanilla v0.0.18 pre-alpha" Or something. I don't want to be too fussy about this but I do want those two name/versions to be displayed obviously such that no one can be confused about what they are using.

(0000154) sry_not4sale (administrator) 2009-02-20 20:44	Had issues with importing modules starting with a integer, so renamed 0_0_1 folder to v0_0_1 e.g comms/protocols/IFreeEMS_Vanilla/v0_0_1/*

(0000162) sry_not4sale (administrator) 2009-03-31 20:56	Is this ok for an interface version?: IFreeEMS.Vanilla (v0.0.1)

(0000163) sry_not4sale (administrator) 2009-08-31 21:32	Example..: Titlebar: FreeEMS-Tuner (version) - FreeEMS Vanialla v0.0.18 pre-alpha Statusbar: Protocol: IFreeEMS.Vanilla (v0.0.1) \| Comms: Serial (/dev/tty1)

(0000164) sry_not4sale (administrator) 2009-09-02 08:32	All done bar interrogation to get firmware version

Issue History
Date Modified	Username	Field	Change
2008-11-09 05:43	sry_not4sale	New Issue
2008-11-09 05:43	sry_not4sale	Status	new => assigned
2008-11-09 05:43	sry_not4sale	Assigned To	=> sry_not4sale
2008-11-09 05:43	sry_not4sale	Issue Type	=> Improvement
2008-11-09 20:44	Fred	Note Added: 0000063
2008-11-16 14:17	Fred	Relationship added	related to 0000059
2008-11-16 14:18	Fred	Note Added: 0000074
2008-11-28 08:05	sry_not4sale	Note Added: 0000107
2008-11-28 14:25	Fred	Note Added: 0000110
2009-02-20 20:44	sry_not4sale	Note Added: 0000154
2009-03-31 20:56	sry_not4sale	Note Added: 0000162
2009-08-31 21:32	sry_not4sale	Note Added: 0000163
2009-09-02 08:32	sry_not4sale	Note Added: 0000164