[idea] [structure] actions in queue #100

New issue

Closed

opened 2017-03-10 19:10:22 +00:00 by papajoke · 4 comments

papajoke commented

2017-03-10 19:10:22 +00:00

(Migrated from gitlab2.manjaro.org)

Currently the menus must follow a strictly technical way (not possible to do one step if the other one has not been made)
For more flexibility in the menu, for a few actions only

A solution that could precisely make it possible to have a menu for users and not technical would be to put some actions on hold.

make a table of type

Declare -A INSTALL = (
     [Mounted] = 0
     [Mirroelist] = 0
     [Pacmankeys] = 0
     [Fstab] = 0
     [Hostname] = 0
     [Local] = 0
     [Keymap] = 0
     [Root] = 0
     [User] = 0
     [Gpudriver] = 0
     [Networkdriver] = 0
     [Linux] = 0
     [Dm] = 0
     [De] = 0
     [Init] = 0
)

0 = not selected by user
1 = selected but waiting
2 = installed

For example (not the best ;) ), you can choose the init (openrc) before mounting the partition, the value goes to 1. After mounting, we find values "1" and if technically possible they are installed (and increases to 2 )

Currently the menus must follow a strictly technical way (not possible to do one step if the other one has not been made) For more flexibility in the menu, for a few actions only A solution that could precisely make it possible to have a menu for users and not technical would be to put some actions on hold. make a table of type ``` Declare -A INSTALL = ( [Mounted] = 0 [Mirroelist] = 0 [Pacmankeys] = 0 [Fstab] = 0 [Hostname] = 0 [Local] = 0 [Keymap] = 0 [Root] = 0 [User] = 0 [Gpudriver] = 0 [Networkdriver] = 0 [Linux] = 0 [Dm] = 0 [De] = 0 [Init] = 0 ) ``` 0 = not selected by user 1 = selected but waiting 2 = installed For example (not the best ;) ), you can choose the init (openrc) before mounting the partition, the value goes to 1. After mounting, we find values "1" and if technically possible they are installed (and increases to 2 )

oberon commented

2017-03-10 20:15:21 +00:00

(Migrated from gitlab2.manjaro.org)

In the end you could just boil it down to in fact what Calamares does:
Collect all the information about what the user wants first and then just do everything needed in the right order.
It's kind of the outline of m-a 2.0 but it's a really nice approach.

In the end you could just boil it down to in fact what Calamares does: Collect all the information about what the user wants first and then just do everything needed in the right order. It's kind of the outline of **m-a 2.0** but it's a really nice approach.

Chrysostomus commented

2017-03-11 00:43:35 +00:00

(Migrated from gitlab2.manjaro.org)

That would be useful

Chrysostomus commented

2017-03-17 01:21:45 +00:00

(Migrated from gitlab2.manjaro.org)

This could theoretically also be used to doing multiple installation tasks simultaneously like thus did. For example, create user accounts when desktop is installing

yochananmarqos1 commented

2024-05-05 19:28:57 +00:00

(Migrated from gitlab2.manjaro.org)

changed the description

yochananmarqos1 (Migrated from gitlab2.manjaro.org) closed this issue

2024-05-05 19:28:57 +00:00