Ticket #1202 (new enhancement)
UserBootscript etc. missing from $HOME/config/boot
| Reported by: | humdinger | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | - General | Version: | R1 development |
| Cc: | Blocked By: | ||
| Platform: | All | Blocking: |
Description
The folder $HOME/config/boot with all user scripts is yet missing from the image.
I attached an archive with UserBootscript, UserSetupEnvironment, UserShutdownFinishScript and UserShutdownScript to this ticket you may want to use or modify.
The contents is very much inspired by the R5 scripts, esp. the UserSetupEnvironment, that I pretty much took as supplied and just altered the first paragraph a bit and applied StyledEdit niceties.
The UserBootscript includes an Autostart folder that would also have to be created in $HOME/config/boot/ . You may want to discuss the Autostart idea first. Personally I think it's great for endusers that don't want to mess with scripts and having certain apps always start on startup is quite essential. Also, a link to the folder in the Deskbar wouldn't be too bad. There were some more sophisticated solutions around that took startup priority into account. I always considered those a bit over the top. If you need to have apps started in a particular order, most of the time they are interdependent and just a proiority won't have one app waiting until another is completely started. For that kind of thing, you'll need to dig a bit deeper and get involved with the UserBootscript and stuff like sleep and waitfor. IMO.
I'm also not sure if we need to provide these scripts as "*.sample" that have to be renamed before use. Empty as they come they won't hurt and if someone adds commands they just work.
I'm sorry for this long ticket. It just got more and more... :)
