FreeEMS-Tuner Development Diary - Comments

[Fred]

Best you design an interface to control which block of flash to retrieve via a drop down menu for retrieve flash type blocks :-)

More details to come. I'll be tidying up tomorrow and releasing either then or sunday night.

Fred.

[jharvey]

I think I buggered my ini file or perhaps I need a reboot. Here is what I currently get. I'll try a reboot in a bit, but can't do it right now. I'm willing to bet it's the standard windows fix here.

C:\Documents and Settings\Owner>cd C:\Documents and Settings\Owner\Desktop\freee
ms-tuner.git

C:\Documents and Settings\Owner\Desktop\freeems-tuner.git>main.py
Traceback (most recent call last):
File "C:\Documents and Settings\Owner\Desktop\freeems-tuner.git\main.py", line
34, in <module>
logger.setup()
File "\\10.10.10.100\mythtv\freeEMS\FreeEMS-Tuner\github.com\srynot4sale\freee
ms-tuner.git\logger.py", line 39, in setup
config_level = config.load('Logging', 'verboseness')
File "\\10.10.10.100\mythtv\freeEMS\FreeEMS-Tuner\github.com\srynot4sale\freee
ms-tuner.git\config.py", line 40, in load
return parser.get(section, option)
File "C:\Python26\lib\ConfigParser.py", line 311, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'Logging'

C:\Documents and Settings\Owner\Desktop\freeems-tuner.git>

[sry_not4sale]

That error sounds like you have removed the [Logging] section by accident. Restart the app to re-read the config, and reboot isn't required.

Replace config.default.ini with the original, and then start adding things to data/my_config.ini until you hit trouble

To change to the Fake comms plugin, use the code in one of my earlier posts.

[jharvey]

I haven't rebooted quite yet. Attached should be my config files, and some snap shots of my directory structure. Hmmm. Perhaps the spaces in the file name... I originally had it on a network drive with no spaces, then I moved it to my desktop so I could see the shell commands, that

Zip file is because it only allows 3 attachments.

[sry_not4sale]

That should work providing config.default.ini is in the root directory (same as README, INSTALL, main.py ...) and my_config.ini is in the data/ directory.

[jharvey]

That should work providing config.default.ini is in the root directory (same as README, INSTALL, main.py ...) and my_config.ini is in the data/ directory.

Well that seems to be the start of my problem.

To copy the ini file, I copied it to another dir, then renamed it, then copied it back. I appear to have gotten myself messed up, because they are both in the comms dir. Hmmm, not that I do it again on a fresh one, I see the copy and cut are next to each other. Perhaps I wondered a little bit with the mouse click.

I copied the files back to where they should be and it works tip top now. Also works fine in the Desktop with the spaces in the name, so good news there as well.

[sry_not4sale]

Glad ya got it sorted

If there are any improvements I can make to the install process, be sure to let me know.

[jharvey]

Some things to add to the list.

-- A connected vs not connected indicator in the bottom of the dialog.
-- GUI error detector, seems to toss up some messages if you don't remember to connect. Perhaps it could remind me I need to connect.
-- Help pops up an error message, perhaps is should thank you for your interest in helping out with the project
-- on the fly comm port settings vs config file, perhaps on the fly overrides

Hmmm, how about a windows installer, that offers to either install python, or notes it needs to be installed, ect if not detected.

Once upon a time, I played with an installer for a PSoC project. I was doing. The PSoC project can be found here.

http://www.psocdeveloper.com/forums/viewtopic.php?t=964

I seem to recall the installer was open source, however I don't appear to have left any bread crumbs, so I can't remember the installer I was using.

I can come up with more to add to the list, but don't want to sound to negative. Keep up the great work.

[Fred]

Some things to add to the list.

-- A connected vs not connected indicator in the bottom of the dialog.
[+1 good idea]
-- GUI error detector, seems to toss up some messages if you don't remember to connect. Perhaps it could remind me I need to connect.
[+1 I already didn't notice the console messages also]
-- Help pops up an error message, perhaps is should thank you for your interest in helping out with the project :P
[good idea, but don't care at the moment]
-- on the fly comm port settings vs config file, perhaps on the fly overrides
[I asked for this too ;-)]

I can come up with more to add to the list, but don't want to sound to negative. Keep up the great work.

I'd suggest that you spit them out, but we should make sure Aaron isn't a moisturiser wearing JAFA panzy before being too critical ;-) I doubt you'll offend him with "i'd prefer this" or "it would be nice if it worked this way" or "this seems broken, is it meant to work like this" etc :-)

[Fred]

-- on the fly comm port settings vs config file, perhaps on the fly overrides
[I asked for this too ;-)]

I was thinking about this and realised that we'll be getting fresh installs of this regularly (hopefully LOL) that may change config style and options etc. It could be useful for that reason although as discussed it's a initial start up /setup thing only most of the time. I don't think it's that important right now. Ironing out comms and getting the data displayed and editable are top priority IMO.

On another note, what I would like to see is a parallel release of this and the firmware each time, or perhaps a few days lag. I think we are on track to do that with the forum discussions and msn chats and sharing code back and forward between releases. If we work together closely while adding new stuff and design it together first then we can probably implement it at a similar time and get some brief testing in at my end pre a parallel release. I guess to take the load off of you in the medium/long term the dynamic config thing will need to be present and working well so that I can add and remove and change gui and comm components fairly easily. That may be too hard though. I'm just rambling really, take what you will from it or ignore it entirely, you are doing a great job! :-)

Fred.