Following swiftly along with this, here's a couple of tweaks (btw those
are Ubuntu's system default buttons, I'm building a collection :), shut
up Michael, I can hear you snigger).
I've included for a continue button. It's not that bad to be honest. I
think it's all pretty clear.
Once a phase is done, it's opaqued out and we get a funky little
message, just to keep a smile on your phase while you're sorting things
out.
I'll do an error message and where that can go in the next batch.
.. perhaps it could be rendered using CSS (which has the side effect of
looking the same across
several browser and OS platforms).
> I've included for a continue button. It's not that bad to be honest. I
> think it's all pretty clear.
>
> Once a phase is done, it's opaqued out and we get a funky little
> message, just to keep a smile on your phase while you're sorting things
> out.
>
> I'll do an error message and where that can go in the next batch.
>
>
>
>
>
>
> >
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
--
Cheers,
Brendan | ya...@angrymonkeys.net | http://www.smackfoo.com
I think that upon loading the installer, the Habari requirements(php
version, database, etc) should be checked and if not met, there should
be "already" a message on the first panel alerting the user about that.
I don't think that making the user having to click on continue to check
if the requirements have been met or not is that..hmm..useful(?).
Actually, i think it would also be nice to have also a message when the
requirements have been met(this is after launching the installer for
the first time), something in the lines of "Congratulations, our
hamsters have verified that your server is ready to begin the Habari
installation, please press continue to begin." (ok, you can skip the
hamsters part ;) )
Anyway, just some ideas for Khaled & Michael (and whoever else is
working on this) to think about :)
Khaled,
I'm writing a *big* memo right now that puts all my cards on the table
as far as the 'states' the installer might end up at, I'm a bit uneasy
about all this very detailed design iteration that's going on without
taking into account that there are lots of things that'll need to be
taken care of designwise in terms of how the installer will behave.
Looking forward to your thoughts.
The installer can't display thumbnails?! That's a rather awful
limitation. Who coded that? ;)
An idea that intrigues me is allowing developers to add additional,
custom pages to the installer for setting plugin or theme options
directly at that time. Seems completely plausible in this scenario.
Owen
Other than that I quite like the simplicity of the latest mockups,
probably just needs a bit of colour.
Will there be some sort of visual unity between this installer section
and the admin section?
Because they both look pretty different so far.
On Jan 19, 12:12 pm, "Michael Heilemann" <heilem...@gmail.com> wrote:
> Selecting any kind of theme in the installer seems unnecessary to me, I must
> say.
>
> On 1/19/07, Owen Winkler <epit...@gmail.com> wrote:
>
>
>
>
>
> > On 1/18/07, khaled Abou Alfa <brokenk...@gmail.com> wrote:
>
> > > Like you if anyone's got some major requirements for other form areas
> > happy
> > > to see them, I think Owen wants you to choose the theme to be used from
> > the
> > > installer. Shouldn't be too difficult to do, although I really don't
> > think
> > > it's a necessary thing, especially as the theme chooser in the admin
> > panel
> > > gives you a thumbnail preview etc, which is a lot more useful than
> > having a
> > > name to choose from.
>
> > The installer can't display thumbnails?! That's a rather awful
> > limitation. Who coded that? ;)
>
> > An idea that intrigues me is allowing developers to add additional,
> > custom pages to the installer for setting plugin or theme options
> > directly at that time. Seems completely plausible in this scenario.
>
> > Owen--
> Aloha,
> Michael Heilemannhttp://binarybonsai.com
> The installer can't display thumbnails?! That's a rather awful
> limitation. Who coded that? ;)
>
> An idea that intrigues me is allowing developers to add additional,
> custom pages to the installer for setting plugin or theme options
> directly at that time. Seems completely plausible in this scenario.
>
> Owen
Owen,
I think this is worth additional discussion... I'm very heavily biased
towards making the installation a 'I can't believe it happened so
quickly'/'wow that was very few questions' type of experience. I
really think we should keep whittling it until it's the barebones
necessities to get the 'darn thing running'.
Maybe a compromise would be something like Khaled's thinking about, a
post-install 'welcome' section that'll give you a quick overview and
maybe let you switch between current themes and so on.
The reason it'd be different is that the installation process is like
holding your breath--you're just not sure what's going to fall apart.
Tinkering around with themes and a nice short intro *after* you've
installed means that you're sure at this point nothing's going to fall
apart.
I realize the difference is superficial, but I think this 'psychology
of perception' thing is really important for a first step/stage. The
installer is the very very very first thing people deal with when
deciding to go with habari.
There's no reason we can't transparently provide automation hooks for
meta-install scripts without messing up the GUI for the manual
installers.
--
Firas Durri | http://firasd.org
I think this ties nicely to issue #55
http://code.google.com/p/habari/issues/detail?id=55&can=2&q=
We could include a theme and plugin activation section in the "First
Time" welcome message, and possibly links to it in the "Beginner" section.
Can we please roll with one of these mockups! I soooo want to start moving Habari ahead not only in code, but design. These last mockups are pretty amazing Mike.