From: Dan A. <da...@co...> - 2004-04-14 12:32:32
|
Hello, I've been thinking about changing the daemon's default behavior to print its help screen when it doesn't receive any pparameters instead of trying to run Linux. It would help people to notice that the daemon in fact accepts parameters. If you have any objections about this, please tell me. -- Dan Aloni da...@co... |
From: <ch...@to...> - 2004-04-14 12:56:47
|
Better put a getch() or something after the printing of defautlt parameters or something otherwise the typical windows user will never see it. ;) Speaking of the typical windows user the current behavior does make it easy to start with a click. So on second thought it may be better to leave the default alone and just have it accept -h --help or /? to get usage. If you do decide to change it then it would probably be a good idea to include a runcolinux.bat file that will use the default config file. (or a shortcut with the apropriate parameters ) Even as a mainly linux user I still revert to just clicking on stuff when in windows. chris > Hello, > > I've been thinking about changing the daemon's default behavior to > print its help screen when it doesn't receive any pparameters instead > of trying to run Linux. It would help people to notice that the daemon > in fact accepts parameters. > > If you have any objections about this, please tell me. > > -- > Dan Aloni > da...@co... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Dan A. <da...@co...> - 2004-04-14 13:17:11
|
On Wed, Apr 14, 2004 at 02:56:38PM +0200, ch...@to... wrote: > Better put a getch() or something after the printing of defautlt > parameters or something otherwise the typical windows user will never see > it. ;) > > Speaking of the typical windows user the current behavior does make it > easy to start with a click. So on second thought it may be better to leave > the default alone and just have it accept -h --help or /? to get usage. It already has a '-h'. Hopefully, when the GUI configurator/manager/whatever is done, people won't even have to know about the daemon executable, and coLinux's execution would be handled from that GUI. > If you do decide to change it then it would probably be a good idea to > include a runcolinux.bat file that will use the default config file. (or a > shortcut with the apropriate parameters ) > > Even as a mainly linux user I still revert to just clicking on stuff when > in windows. BTW, coLinux's behavior/design is completely open to debate. Anyone can feel free to suggest any change to the way coLinux works and interracts with the user. -- Dan Aloni da...@co... |
From: <ch...@to...> - 2004-04-14 13:37:49
|
>> the default alone and just have it accept -h --help or /? to get usage. > > It already has a '-h'. > I meant "and" /? not "or" so the dos heads would be able to figure it out quick. If I can't keep and & or strait from my head to my fingers so much for a programing career for me ;) Actually the default behavior is probably a non issue because of the future gui configuration those of us using it before 1.0 should be able to adapt to whatever. chris |
From: Digital I. Inc. <ok...@di...> - 2004-04-14 15:37:31
|
Yeah, I agree. as a future plan, I would do like this on conoppix: clicking .elf file (or .daemon) -> run colinux with this configuration. clickinc .distribution (or .linux) -> same as clicking .elf. clicking .cbd(or ubd or cow or cloop or ...) -> shows a pop up that tells you to click related .elf/distribution/linux.... file. clicking .kernel -> same as clicking cbd. clicking colinux.exe -> appears a window similar to VMWare initial window. you can select settings in that window. (colinux.exe is colinux-daemon.exe of current zip file.) type $ colinux -> same as clicking it. type $ colinux -h -> show command line syntax. type $ colinux -c xxx -> run colinux with this configutation. clicking other exe -> dont do it. .xml file -> I think all .xml files must be disappeared. Why you use this extention, with risk of confusing? use .elf or other exetention which is easily understood as a Linux binary. default.colinux.xml -> renamed to default.colinux.xml.elf. so your proposal, which eliminate default.xml, would be right. --- Okajima. >Hello, > >I've been thinking about changing the daemon's default behavior to >print its help screen when it doesn't receive any pparameters instead >of trying to run Linux. It would help people to notice that the daemon >in fact accepts parameters. > >If you have any objections about this, please tell me. > >-- >Dan Aloni >da...@co... > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: tei <42...@in...> - 2004-04-14 21:24:26
|
http://telejano.berlios.de/option/colinuxutopi1.png thats idea depict a "baby tux with windows feather (may eventually ^fly^" work in progress. :D |
From: tei <42...@in...> - 2004-04-14 22:27:08
|
sorry for the double post, icon conversion done: normal http://telejano.berlios.de/option/colinuxutopi1.ico with a "is a file" background (cob images?) http://telejano.berlios.de/option/colinuxiso1.ico work in progress Can a baby tux en windows feather actually fly? yes http://telejano.berlios.de/option/colinux1.swf (that is a joke) |