-
Notifications
You must be signed in to change notification settings - Fork 1
LiveKit Changes, and Reconstructing #6
Comments
Alright... just got some pictures done... Let me explain the basic design here, the installer is going to have only 4 pages. Let's jump right into it right now... Page 1Page 1 is basically a "warm yet fast" welcome for user. With a "recipe" style design (I got the inspiration from Which Wich, a sandwich restaurant around my neighborhood), if you are not sure what it is... just look at the picture below. So... a recipe like the one above. So we would use this design for the first page, letting user choose what they want, including stuff shown below. (God I'm hungry) The list above shows the basic contents of the stuff in the first page. Design-wise, in my design I want to try my best in getting rid of all drop down menus, and make most of them into radio buttons, and the rest being input boxes. Page 2Page 2 is basically an overview of the PM, DE and optional features, partition settings set by the user, here we need a clear list of what the user had chosen. User will read through this list (as the confirmation/reject button is at the very bottom), content as shown below. Page 3The "Work in Progress" page, having a simple progress bar and checklist. As shown below. Page 4Page 4 is basically the "Work done" page, just telling the user that the installation is completed. And user will have some choices:
Basically that's all... but for the actual design, I've got no idea for now. It's coming soon I know... |
The main focus of this change is just to give users more choices. @Arthur2e5 had clearly stated that before... |
I don't think we are going to have a very lightweight one, honestly. We are using a LIVE environment, and we should make sure that it has a user experience that is close to an installed system. |
Maybe we are unclear on this thing... We need a installation environment that actually installs the system fast and without problem even on older machines. You know, AOSC OS2 is almost impossible to install even on Core 2 class system, as it was HUGE, and xz compressed. You may compare this plan to openSUSE's DVD installer and Fedora, as well. -----原始邮件----- I don't think we are going to have a very lightweight one, honestly. |
I suggest three pages:
Thus, since step 3, the user could leave the computer and have a rest. However an option could be set at step 3 to delay some of the configurations to step 5, which is useful for OEM preinstalled machines. A installation script may be used for OEM preinstallation or mass installation of server in productivity environment. P.S. @MingcongBai why were you "assigning" me instead of "at"ing me? |
Some typos: Step 3: Step 4: Chroot or kexec into the new system and continue the installation process (GRUB configuring, etc), without user noticing the change on the screen. |
Hmm... That would certainly be easier. Actually what do You think of the "Which Wich" style design? It just came to my mind as a brain hole... Not sure if we would be able to fill it in properly... As of Kexec, do you believe that it's stable enough for it to be the only choice? The reason why I thought of it as an option is came out of the worry of this issue. Well... As of assigning folks... Sorry...
|
Kexec is like taking the brain out and insert another one... Sounds grouse huh? Well that's basically how it looks to me... Haha.
|
Big plus. But I suggest the Page 1 should be divided into several steps, or some users may don't know what to do at first. As for the kexec problem, I think it will be okay. (We've tried this in OS1, haven't we?) |
@lmy441900 True, but we never tried it in X11, and kexec from there... We'll see very soon. @m13253 Finally got the time to think about this thing. Yes, we should try making it compatible to people that are visually challenged, and talked to @Trickness about trying GTK+ combined with ATK (probably better than implementing it with Qt yes?). |
Got the mockup for Intro page done... The picture represents the actual 100% size of the LiveKit Installer window. Haven't considered much of HiDPI for now, just to get you guys an idea... Please tell me what you think. @lmy441900 @Arthur2e5 @m13253 @butangmucat @Icenowy @liushuyu @JoyNeop (If even you guys can't understand what's it about in this page... I should probably redo it.) |
@MingcongBai Nice design ,and some of the members in our school club think this is okay. I still don't know if you will put such a long menu (or window??) on the screen? Personally speaking, cut each "Stop" into several "steps" can be better. P.S. Very admire our options of DE... (Big project) |
The window is designed for at least a XGA resolution in mind, and it scrolls. Maybe we need a scroll stopper so it flips like pages?
|
I think theres some other options should set like disk parted. Do we locate these in the front page?I think its unacceptable. --- 原始郵件 --- 寄件者: "Jeff Bai" notifications@github.com The window is designed for at least a XGA resolution in mind, and it scrolls. Maybe we need a scroll stopper so it flips like pages?
Reply to this email directly or view it on GitHub: |
By putting/not putting them is not acceptable? -----原始邮件----- I think theres some other options should set like disk parted. Do we locate these in the front page?I think its unacceptable. --- 原始郵件 --- 寄件者: "Jeff Bai" notifications@github.com The window is designed for at least a XGA resolution in mind, and it scrolls. Maybe we need a scroll stopper so it flips like pages?
Reply to this email directly or view it on GitHub: |
Just start GParted. Screen 0 Welcome |
Is a License "clicker" (if you know what I mean) really necessary?
|
When recipe indicates GNOME/Cinnamon/Unity as desktop, we need to specify Input Method to IBus instead of Fcitx. Just some package changing... And imchooser needs to be run as well (AOSC-Dev/imchooser).
|
dig(grave). |
What is Decided
What is NOT Decided
Discuss Time!
I'll be attaching design graphs and sketches... so be ready to bang me with criticism.
The text was updated successfully, but these errors were encountered: