LiveKit Changes, and Reconstructing

MingcongBai commented 9 years ago

What is Decided

We are gonna switch plan.
AOSC OS3 will be releases in a single ISO, with a (VERY) lightweight environment, running several programs like LiveKit Installer itself, GParted, axel, and basic programs for installation.
What is NOT Decided
Should AOSC OS for Server be installed in the same way? Or should we bundle a headless version of environment, running a CLI based installer (@Arthur2e5)?
How to adapt the installer (and probably system packages as well), in order to make AOSC OS able to install onto Portable medias (HDD and flashes et al), and run right after installation?
Should we try to walk on the fire of Kexec (that means we can run the system right after the installation without even restarting)?
Discuss Time!

I'll be attaching design graphs and sketches... so be ready to bang me with criticism.

MingcongBai commented 9 years ago

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 1

Page 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.

348s

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 2

Page 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 3

The "Work in Progress" page, having a simple progress bar and checklist. As shown below.

Page 4

Page 4 is basically the "Work done" page, just telling the user that the installation is completed. And user will have some choices:

Reboot and jump right into AOSC OS;
Kexec (should we do it?) into AOSC OS, in case GRUB did not install properly, or they need some emergent changes...;
Install another copy of the system, loop to the first page of the installer.

Basically that's all... but for the actual design, I've got no idea for now. It's coming soon I know...

MingcongBai commented 9 years ago

The main focus of this change is just to give users more choices. @Arthur2e5 had clearly stated that before...

Artoria2e5 commented 9 years ago

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.

MingcongBai commented 9 years ago

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.

-----原始邮件----- 发件人: "Mingye Wang" notifications@github.com 发送时间: ‎2014/‎11/‎24 17:28 收件人: "AOSC-Dev/AOSC-LiveKit" AOSC-LiveKit@noreply.github.com 抄送: "Jeff Bai" jeffbaichina@members.fsf.org 主题: Re: [AOSC-LiveKit] LiveKit Changes, and Reconstructing (#6)

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. — Reply to this email directly or view it on GitHub.=

m13253 commented 9 years ago

I suggest three pages:

Welcome and locale choosing and accessibility options for the visual challenged
Partitioning
Component configuration (Locale & IME, Timezone, DE, Root password, APT mirror) and the installation procss happens immediately in the background without waiting for all the informations are gained
Chroot or kexec into the new system, without user noticing the change at UI
Directly boot into the desktop

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?

m13253 commented 9 years ago

Some typos:

Step 3: s/locale \& // since locale is already configured at step 1.

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.

MingcongBai commented 9 years ago

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...

在 2014年11月24日，下午9:46，Star Brilliant notifications@github.com 写道：

I suggest three pages:

Welcome and locale choosing and accessibility options for the visual challenged

Partitioning

Component configuration (Locale & IME, Timezone, DE, Root password, APT mirror) and the installation procss happens immediately in the background without waiting for all the informations are gained

Chroot or kexec into the new system, without user noticing the change at UI

Directly boot into the desktop

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?

— Reply to this email directly or view it on GitHub.

MingcongBai commented 9 years ago

Kexec is like taking the brain out and insert another one... Sounds grouse huh? Well that's basically how it looks to me... Haha.

在 2014年11月24日，下午9:51，Star Brilliant notifications@github.com 写道：

Some typos:

Step 3: s/locale & // since locale is already configured at step 1.

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.

— Reply to this email directly or view it on GitHub.

jyhi commented 9 years ago

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?)

MingcongBai commented 9 years ago

@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?). As of paging, not sure, I'm trying my best in putting together a mockup right now, and tell me what you think by then, alright?

MingcongBai commented 9 years ago

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.)

mock_intro

jyhi commented 9 years ago

@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)

MingcongBai commented 9 years ago

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?

在 2014年12月2日，上午2:30，Junde Yi notifications@github.com 写道：

@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)

— Reply to this email directly or view it on GitHub.

Trickness commented 9 years ago

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 已傳送： 2014年12月2日下午10:10 收件者： "AOSC-Dev/AOSC-LiveKit" AOSC-LiveKit@noreply.github.com 副本： "张峻锋" SternWZhang@outlook.com 主旨： Re: [AOSC-LiveKit] LiveKit Changes, and Reconstructing (#6)

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?

在 2014年12月2日，上午2:30，Junde Yi notifications@github.com 写道：

@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)

— Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub: https://github.com/AOSC-Dev/AOSC-LiveKit/issues/6#issuecomment-65235455

MingcongBai commented 9 years ago

By putting/not putting them is not acceptable?

-----原始邮件----- 发件人: "张峻锋" notifications@github.com 发送时间: ‎2014/‎12/‎3 0:18 收件人: "AOSC-Dev/AOSC-LiveKit" AOSC-LiveKit@noreply.github.com 抄送: "Jeff Bai" jeffbaichina@members.fsf.org 主题: Re: [AOSC-LiveKit] LiveKit Changes, and Reconstructing (#6)

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 已傳送： 2014年12月2日下午10:10 收件者： "AOSC-Dev/AOSC-LiveKit" AOSC-LiveKit@noreply.github.com 副本： "张峻锋" SternWZhang@outlook.com 主旨： Re: [AOSC-LiveKit] LiveKit Changes, and Reconstructing (#6)

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?

在 2014年12月2日，上午2:30，Junde Yi notifications@github.com 写道：

@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)

— Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub: https://github.com/AOSC-Dev/AOSC-LiveKit/issues/6#issuecomment-65235455 — Reply to this email directly or view it on GitHub.

Artoria2e5 commented 9 years ago

Just start GParted.

Screen 0 Welcome Screen 1 License Screen 2: (Visual 'Order' Header Part?) GParted, Partition, Boot Method BUG: Mount Points? Username, password and computer name (End Header) (Package Manager) (DE) (Extra) (End Screen 2) Screen 3: YO, REBOOT!

MingcongBai commented 9 years ago

Is a License "clicker" (if you know what I mean) really necessary?

在 2014年12月3日，下午5:36，Mingye Wang notifications@github.com 写道：

Just start GParted.

Screen 0 Welcome Screen 1 License Screen 2: (Visual 'Order' Header Part?) GParted, Partition, Boot Method BUG: Mount Points? Username, password and computer name (End Header) (Package Manager) (DE) (Extra) (End Screen 2) Screen 3: YO, REBOOT! — Reply to this email directly or view it on GitHub.

MingcongBai commented 9 years ago

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).

@Trickness @Arthur2e5

在 2014年12月3日，上午12:18，张峻锋 notifications@github.com 写道：

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 已傳送： 2014年12月2日下午10:10 收件者： "AOSC-Dev/AOSC-LiveKit" AOSC-LiveKit@noreply.github.com 副本： "张峻锋" SternWZhang@outlook.com 主旨： Re: [AOSC-LiveKit] LiveKit Changes, and Reconstructing (#6)

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?

在 2014年12月2日，上午2:30，Junde Yi notifications@github.com 写道：

@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)

— Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub: https://github.com/AOSC-Dev/AOSC-LiveKit/issues/6#issuecomment-65235455 — Reply to this email directly or view it on GitHub.

Artoria2e5 commented 8 years ago

dig(grave).

AOSC-Archive / AOSC-LiveKit