| 1 |
Taras Glek wrote: |
| 2 |
|
| 3 |
>Why is a gui needed to do an installer? One could do a ncurses based |
| 4 |
>console "gui" that would be just as useful, but wouldn't depend on shaky |
| 5 |
>things like framebuffer(not all cards do vesa, some do it better/worse |
| 6 |
>than others), imho using a console interface, sort of like the one in |
| 7 |
>dos borland ides would be more than sufficient. |
| 8 |
> |
| 9 |
>On Sun, 2002-01-06 at 14:54, Geert Bevin wrote: |
| 10 |
> |
| 11 |
>>Hi all, |
| 12 |
>> |
| 13 |
>>I post a log of what Hallski and I have been talking about on irc, |
| 14 |
>>please add you comments. |
| 15 |
>> |
| 16 |
>><Bevin> what did you already imagine in terms of GUI tools for gentoo? |
| 17 |
>>installer, package manager, admin tools, ... ? |
| 18 |
>><Hallski> not much really, the problem for packagemanager and admin |
| 19 |
>>tools would be which toolkit (or mulitple) |
| 20 |
>><Hallski> about the installer I would really like to have it so that |
| 21 |
>>users see what happends and take an active part in it |
| 22 |
>><Hallski> since it's very educating |
| 23 |
>><Hallski> *puh* |
| 24 |
>><Bevin> that's also how I see the installer, more like a guide with |
| 25 |
>>blanks to fill in and commandlines to choose from, not something that |
| 26 |
>>tries to detect and do everything automatically |
| 27 |
>><Hallski> yes |
| 28 |
>><Hallski> well, some kind of hardware detection would be nice though |
| 29 |
>><Bevin> I saw this kinda like a frame based approach, left frame with |
| 30 |
>>details about the current step and required data with links to |
| 31 |
>>alternative paths |
| 32 |
>><Hallski> that takes you through setting the different parts up |
| 33 |
>><Bevin> right frame almost exactly as a normal shell, but i which |
| 34 |
>>commands get auto-pasted from the left frame |
| 35 |
>><Bevin> didn't the new developer was going to work on auto-detection |
| 36 |
>>of hadrware |
| 37 |
>><Hallski> yes, I think it would be rather nice to have that, so it can |
| 38 |
>>autoinsert commands |
| 39 |
>><Hallski> oh, nice |
| 40 |
>><Bevin> so it's a kinda like an interactive and guiding documentation |
| 41 |
>><Hallski> yes |
| 42 |
>><Bevin> with no need to print out the installation manual before |
| 43 |
>>installing |
| 44 |
>><Hallski> it could even be so easy to just have a html-browser that |
| 45 |
>>shows the installation |
| 46 |
>><Hallski> but it would be nicer to have some more interactive aproach |
| 47 |
>><Hallski> like, when you excecute the command in the shell-prompt it |
| 48 |
>>takes you to the next step in the guide-part |
| 49 |
>><Hallski> wonder if that would be easy to do :) |
| 50 |
>><Bevin> exactly my thoughts :-) |
| 51 |
>><Hallski> you can have like Next-button |
| 52 |
>><Bevin> or even a real website-like navigation with possible |
| 53 |
>>installation actions tat still have to be done |
| 54 |
>><Bevin> the most important part will in fact be to write a good |
| 55 |
>>'story-board' |
| 56 |
>><Hallski> agree |
| 57 |
>><Bevin> where every step in clear explanantions and all 'follow-ups' |
| 58 |
>>needed |
| 59 |
>><Hallski> yes |
| 60 |
>><Bevin> guess I'll get onto that storyboard first then |
| 61 |
>><Bevin> and post it to the mailinglist as soon I have a first draft |
| 62 |
>><Hallski> yes, that would be great |
| 63 |
>><Bevin> about the toolkit, I like to use qt for it for several reasons |
| 64 |
>><Hallski> ok |
| 65 |
>><Bevin> 1. everything possibly needed is available in 1 lib |
| 66 |
>><Hallski> I don't want to hack QT but it's ok if you do it :) |
| 67 |
>><Bevin> 2. it officially supports operating without X |
| 68 |
>><Bevin> first however I'd like to try to make a boot cd that contains |
| 69 |
>>the qt-embedded lib and an example app, as a proff of concept |
| 70 |
>><Bevin> do you know if drobbins has 'portagified' his build cd |
| 71 |
>>creation scripts already? |
| 72 |
>><Hallski> well, I think I can look a little at QT, but I'd rather not |
| 73 |
>>spend to much time learning about it |
| 74 |
>><Hallski> dunno |
| 75 |
>><Bevin> helping out with the storyboard will be most of the work |
| 76 |
>><Hallski> yes |
| 77 |
>> |
| 78 |
>> |
| 79 |
>>_______________________________________________ |
| 80 |
>>gentoo-dev mailing list |
| 81 |
>>gentoo-dev@g.o |
| 82 |
>>http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 83 |
>> |
| 84 |
> |
| 85 |
> |
| 86 |
>_______________________________________________ |
| 87 |
>gentoo-dev mailing list |
| 88 |
>gentoo-dev@g.o |
| 89 |
>http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 90 |
> |
| 91 |
For me, without any doubt, grafical installers can only cause trouble |
| 92 |
and compatibility problems.. has you said. |
| 93 |
A ncurses aproach would be preferable, like the instalers of : |
| 94 |
freebsd |
| 95 |
slackware |
| 96 |
debian |
| 97 |
redhat v5 (the one i liked most) |
| 98 |
|
| 99 |
It should be, in order of priority: functional/pratical, stable, safe, |
| 100 |
fast, pretty. |
| 101 |
|
| 102 |
Regards, and happy new year! |
| 103 |
|
| 104 |
Miguel Sousa Filipe |
| 105 |
debian and gentoo user |
| 106 |
m3thos@×××××××.pt (PORTUGAL) |
Archives