Zitat des anonymen Erschaffers
weitere Ideen....This is how I am thinking:
Neutrino Startup:
if installer_already_run = 1 then
>> dont run installer again
else
run_installer (installer_step1)
And then you have seperate files for each category/page:
install_step1.cpp
A menu asking user to IP address for the image
Click "next" option to display install_step2.cpp
install_step2.cpp
A menu asking user netid/scan settings etc
Click "next option to display install_step3.cpp
etc etc, until we get to final stage:
install_final.cpp
A menu displaying all settings chosen. The user clicks "Finish" to apply
the settings, and the box reboots itself. It sets a flag to say that the
installer has been run. Then when neutrino restarts, it will continue
as normal..
Ich werde die Diff Dateien spaeter hier anhaengen ;-)... whilst not amazing attractive, this is only the foundations.
I used CMenuForwarderNonLocalized functions to draw the
menu so I didnt have to mess around with locale files...
This would be changed before it would be released.
Neutrino starts, loads neutrino.conf and checks the installer_run
value. If "true", neutrino carries on as normal. If false, this means
the image hasnt been run before, and you then get the wizard.
Files for above menu attached - compiled and diffs.
The compiled version you can just stick in /bin on any JFFS2 image and reboot.
This will bring up the screenshot you see above. Note that neither the "start"
nor "skip" options actually work at this point. You should simply press the HOME
button to exit out of the menu.
The diffs are very messy. I've commented nearly everything, and the way the
code is written is kinda lazy. But hey it works for now. Everything can be tidied
up at a later stage.
To apply diffs, go into your CVS base directory (not CDK!!) and type:
patch < installer_welcome.diff
(obviously the installer_welcome.diff file must be in the CVS base dir too!)
The diffs affect the following files:
system/settings.h, src/neutrino.h, src/neutrino.cpp
I am starting to code the first step and phaized is going to have a go at using that template to code the extra steps. I'll be using an actionkey on each menu to save the values for each step into a temporary file. The final stage will concatonate all the steps into one big value list; and then write these values into neutrino.conf using coding based on the SaveSetup() routine.
At first the whole thing will be written using Non Locale-Dependant entries, and when its complete it will then be made into LOCALE_WIZARD_XXX entries and editable via english.locale and deutsch.locale