Installer HTML Mockup
Owen Winkler
http://habari.owenw.com/system/install/index.php
I put in the stuff I liked, took out the stuff I didn't like, turned
it all into HTML with a little DHTML and CSS, and baked it for three
hours. Discuss.
Owen
Doug Stewart
Interesting stuff, but putting the DB stuff second rubs me the wrong way - it's not the way the system views it (not that that should constrain the users, mind you) and seems just, well, _backwards_ from what has gone before (and what has been proven to work).
--
-Doug
http://literalbarrage.org/blog/
BlueSaze
1. Database Info should come first. No use collecting the username
Password if the user is not able to configure the database to install.
2. Where is the Next button.
3. Do we really need Theme selection. We need to minimize the number of
steps for installation.
4. Apply Setting = Finish (Sounds less complicated)
5. Color scheme need a little more work. (I like Khaled Design)
Owen Winkler
>
> 1. Database Info should come first. No use collecting the username
> Password if the user is not able to configure the database to install.
Maybe. I was thinking that it would be nice if the user got the
feeling that they weren't going to have to fill out 4 pages of
technical info to get the job done, but perhaps a page or two that
they actually care about.
> 2. Where is the Next button.
There is no next button. The slides open as they are completed by the
user and validated via javascript/Ajax. Yes, there will be a noscript
fallback, I'm tired of people asking, file a bug when you see it being
untrue, it is a goal of the project to be non-js-capable, yatta yatta
ad-infinitum.
> 3. Do we really need Theme selection. We need to minimize the number of
> steps for installation.
No, we need to minimize the interaction with the admin for a user who
just wants to get to blogging. The very first thing they do after
they write their first post (perhaps even before that) is say, "Dear
God, this is butt-ugly." Let's address that at the start. I'm
inclined to let them pick packed-in plugins to enable, too.
And don't forget the guy doing the install for another user. If he
can upload all of the bits before he runs the install, and then set
those values during the install instead of goofing around in the
admin, we've made his job much, much easier. Think "unattented",
folks.
> 4. Apply Setting = Finish (Sounds less complicated)
Tomato, Tomato, Potato, Potato... Let's call the whole thing off.
> 5. Color scheme need a little more work. (I like Khaled Design)
You guys keep working on that. I've got software to get to a
dev-preview state by the end of the month. I'll take a minute or two
to nitpick over colors later if I need to.
Owen
chrisjdavis
might not know that we are shooting for a Jan 31st Developer Preview
Release.
We (being Owen, Scott, Rich and I) really want to hit this first
release deadline hard. Thankfully all the work you guys have been
doing since you came on board has made it possible for us to make this
deadline.
So thanks! Now get back to work!
Chris
Jay Pipes
The InstallHandler is coded up and (at least on my system) correctly
analyzes the system for the requirements and also writes the config.php
file to the local HABARI_PATH directory (this is much easier than
telling the user copy the file...). The requirements page checks that
the HABARI_PATH is writeable, checks the PHP version, and the PDO
extension, and if any of those fails, displays a requirements screen via
the installer theme. The requirements template even has switches to
display Windows or *nix instructions depending on the analyzed operating
system.
Would be great if someone could work on the installer template files
(they are Smarty templates, but for all practical purposes, they're
simply XHTML pages) and make 'em pretty!
I'll do a commit if someone is willing to work on the 070110 branch in
the themes/installer/ directory. Note that the *only* directory you'll
need to touch is the /themes/installer/ directory. Due to the new
theming engines, no PHP coding will be required.
Note that checking out that branch will install Smarty into your local
web directory.
Jay
Chris J. Davis
trunk.
Chris
Root
with a new app just to do a bit of CSS.
Scott Merrill
> As to smarty - it is a big ask for folk unfamiliar with it to grapple
> with a new app just to do a bit of CSS.
I'm sorry, I'm having a devil of a time following your responses, Root.
There's no quoted context to this message, so I've long since forgotten
which message in this thread dealt with smarty.
As for grappling with Smarty, no one is required to do so. People who
want to use Smarty for templating should be able to do so. People who
want to use plain ol' PHP for templating should be able to do so.
Our goal is to have a variety of "theme engines" which allow folks to
use the templating system of their preference.
--
GPG 9CFA4B35 | ski...@skippy.net | http://skippy.net/
vkaryl
actually pretty easy to learn and use; there's an active support group
and forum at http://www.phpinsider.com/smarty-forum/ with the overview
and links at http://www.smarty.net/. It didn't take me long to figure
it out while using esyndicat (http://esyndicat.com) and though I've
gone on to a different directory script which is "straight" php, I do
still think smarty's a great engine.
Root
@Vkaryl - learning another set of tags pace txp is what I am trying to
avoid :)
Chris J. Davis
themeable, and he mentioned smarty as the language that was used. I
am not a fan of using a 3rd party bit for core files, but I am
prepared to relent if screamed at with sane arguments loud enough.
Chris
vkaryl
assuming that a majority decision will no doubt prevail. I pick up
templating/template tags really quick, so I'll be okay with whatever in
this instance.
I wouldn't think a 3rd party system would be at all logical for core
files really; but then is a templating engine going to be part of core,
or an adjunct to same?
Root
James Lao
I just wanted to say I'm not a big fan of theme engines like smarty
and what not; mostly because they can slow a site way down. If a
smarty (or some other theme engine) is integrated into Habari, I would
still like to see the option to code template in PHP.--
James Lao
jameslao.com
Scott Merrill
> Hi, I'm new here.
Welcome!
> I just wanted to say I'm not a big fan of theme engines like smarty
> and what not; mostly because they can slow a site way down. If a
> smarty (or some other theme engine) is integrated into Habari, I would
> still like to see the option to code template in PHP.
Our goal is to support multiple theme engines, to provide as much
flexibility as possible. Our use of "theme engines" permits us to use
Smarty templates _in addition to_ plain ol' PHP. If you prefer PHP
templating, you've got it!
Jay Pipes
> James Lao wrote:
>> Hi, I'm new here.
>
> Welcome!
>
>> I just wanted to say I'm not a big fan of theme engines like smarty
>> and what not; mostly because they can slow a site way down. If a
>> smarty (or some other theme engine) is integrated into Habari, I would
>> still like to see the option to code template in PHP.
FUD. I should point out that Smarty compiles to optimized PHP code
itself, and has been shown to be as fast or faster than straight PHP
files in productoin systems due to its compilation and caching.
> Our goal is to support multiple theme engines, to provide as much
> flexibility as possible. Our use of "theme engines" permits us to use
> Smarty templates _in addition to_ plain ol' PHP. If you prefer PHP
> templating, you've got it!
Indeed.
The point of doing the installer in Smarty was not to force it on
anyone, just to show that the template engine supports anything, not
just straight PHP code...
Jay