Possible Anaconda GUI re-work?

[Dan]

Hello?!? Hmmmm. No, you should well able to see them. But .. let's experiment. Reload the page, and post if you can see them now.

If anyone else can't see them please post.

[Flounder]

That's odd. I can see it in Firefox, but I can't see it using Chrome. That is very interesting.

I do like the design you have though, but I don't see how the red cylinder on the hard drive helps.

[Dan]

In your mind's eye, take the illustration from DBelton's post, and place it where the red one is now. Understand that this is a fast and dirty work-up, so everything may not be to scale, or perfectly accurate. It's the ideas that are being represented that are important.

That drive which is now red, would be the visual representation of what your configuring efforts will bring to pass when you "Complete the install."

[Demz3]

yeah i get the same problem, i cant see your images in Chrome 27 but i can see them in Firefox 22

---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------

try with rekonq and Epiphany, me wonders if its just a webkit based browser problem

[bob]

OTOH, Chrome 25 works fine for me.

[Demz3]

Originally Posted by bob

OTOH, Chrome 25 works fine for me.

i'll disable Adblock an see

---------- Post added at 01:12 PM ---------- Previous post was at 01:09 PM ----------

update, makes no difference

[Dan]

Sounds like Chrome be broken.

[Demz3]

Originally Posted by Dan

Sounds like Chrome be broken.

possibly. 27 is Alpha so yeah

[AdamW]

So this is a single spoke for partitioning and repository selection? Or it's meant to do a complete install process? If the latter, what would be on the Hub you can return to, and where's the networking config? If the former, why the 'localize install' option?

How would LVM and RAID be handled?

How do you handle the case where there are six disks? Ten? Twenty? Do the lists of disks scroll horizontally?

Drag and drop for selecting a partition type seems a bit of an obscure mechanism, and it seems like using the exact same base graphic for 'disk' and 'partition' could lead to confusion.

"Seriously, how much alteration does the boot loader need?"

You don't want to talk like that, you know. You'll wake up with a copy of lilo bleeding all over your sheets, courtesy of the Multiboot Mafia.

How do you indicate whether an existing partition is to be reformatted or not? How is this illustrated on the 'what you will get' bit? Mouseover again?

It's great you came up with something constructive, thanks a lot. My overall concern here though is that you're hitting much like what the anaconda+design folks hit on their first few iterations: they tried quite hard to fit everything into a single screen with no pop-up child dialogs etc, and concluded it's just not feasible. There's too much stuff. I worry your mockup will look (even more) overstuffed once we add in all the extra bits (see above).

[Dan]

Originally Posted by AdamW

So this is a single spoke for partitioning and repository selection? Or it's meant to do a complete install process? If the latter, what would be on the Hub you can return to, and where's the networking config? If the former, why the 'localize install' option?

No. The tabs on the right are the "call-out" pages. I've only listed a few here for illustration purposes. The tabs and content don't need (and shouldn't be) this huge. It's a "first-look" type mock up for working in the idea.

How would LVM and RAID be handled?

Probably best done on an "advanced" tab. Selecting the "RAID etc." layout blank would automagically flip you to that tab.

How do you handle the case where there are six disks? Ten? Twenty? Do the lists of disks scroll horizontally?

Ayup. Scroll them is good. But if they are all going to be the same, a "Clone this set-up" button would be good too.

Drag and drop for selecting a partition type seems a bit of an obscure mechanism, and it seems like using the exact same base graphic for 'disk' and 'partition' could lead to confusion.

Ok. Then clicking the drive parks it in the working boxes. (The big graphic in each "L".) A simple color square assigned to each partition type would be better than the drives graphic, indeed. But I already had those made, so I plunked them in.

"Seriously, how much alteration does the boot loader need?"

You don't want to talk like that, you know. You'll wake up with a copy of lilo bleeding all over your sheets, courtesy of the Multiboot Mafia.

Meh. I'll give them your address on IRC and tell 'em it was your idea. <....>

How do you indicate whether an existing partition is to be reformatted or not? How is this illustrated on the 'what you will get' bit? Mouseover again?

When you return to the "hub" page, it updates the "What you will get" graphic. That's a poor compromise to be sure, but it seemed the better idea than trying to have it live-update.

It's great you came up with something constructive, thanks a lot. My overall concern here though is that you're hitting much like what the anaconda+design folks hit on their first few iterations: they tried quite hard to fit everything into a single screen with no pop-up child dialogs etc, and concluded it's just not feasible. There's too much stuff. I worry your mockup will look (even more) overstuffed once we add in all the extra bits (see above).

Ok. Use more "call-out" tabs to handle the work. It takes lots of spokes to make a cool looking sports car wheel! <....>

Once again, it's just another idea to float. Seems like it's better to light a single candle ... and all that rot.

<....>