[En-Nut-Discussion] RE: Nutconf /s option

[Harald Kipp]

At 23:01 15.01.2006 +0100, you wrote:

>Man, you were NOT a popular person at that moment, Harald !

You are thousands of miles away and Sweden is not the ultimate choice
right now for a holiday trip. Hope you calmed down until summer. :-)



>Now, I've finally heard that you can use the /S parameter, but that's just 
>not the right way. First of all, the nutconf is a nice little icon that is 
>clickable, I don't want to fuddle around with an undocumented command line 
>option everytime I need to use the configurator.
>Secondly, as this is apparently necessary for using NutConf properly, why 
>is this not documented ?
>PLEASE move ALL settings to the CONF file, so opening a conf will pull in 
>all the settings for a project.
>I'm quite sure many have been extremely frustrated over how Nutconf 
>handles settings.

You can create several icons, which use different options.
nutconf /h is the only document, which I agree is insufficient.

I've been frustrated by changing the settings over and over
again for the bunch of versions and target platforms I've
installed. Once I had been in a hurry and decided to stop
this by adding this tiny command line hack.

OK, OK, no good excuse.

As I explained earlier, the .conf file is for the target
specific settings only. It's intention was, to allow other
board manufacturers or hobbyists to add their own hardware
configuration to the distribution. Unfortunately the
AVR_GCC = ""
entry should be in there. But it turned out to be difficult
to get the build tree created correctly otherwise.
Under no circumstances the path information should be
included here, because this is a local configuration.

I spent a few hours to browse through the code once again,
but still didn't get the right idea. May be the Configurator
should use an .ini file, like it does on Linux. And this
ini file may then contain the registry settings plus the
name of the .conf file. When it opens up and finds one .ini
only, everything settles up automatically. If more than one
.ini file is found, then the user has to select the correct
one.

Somehow like this...however, the wxWidgets library may not
support this out of the box.

One important thing to note too: The .conf file and the
.nut files are Lua Scripts and parsed by the Lua interpreter.
Right now they look like simple config files, but they
have a lot of potential. Values, which are now constants,
will be calculated on the fly in later versions. In
opposite, the settings in the registry are simple strings.

Creating the application tree is part of the Configurator,
because there's nothing else available. I plan to move this
into a new tool, something like an application wizard.

Harald