• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Item3559: The newbies experience in Configure is .... challenging

Item Form Data

AppliesTo: Component: Priority: CurrentState: WaitingFor: TargetRelease ReleasedIn
Engine ConfigureScript Normal Closed   patch 4.1.2

Edit Form Data

Reported By:
Applies To:
Current State:
Waiting For:
Target Release:
Released In:


Apparently configure presents too much info for a noob, if LocalSite.cfg isn't there.

First reaction; it's not an installer script, it's a configuration interface.

Second reaction; need to cut it down to the essentials if LSC is missing.

-- TWiki:Main/CrawfordCurrie - 04 Feb 2007

What I have done probably needs polishing, but it's not too shabby for 20mins work, IMHO


I was planning to give this more thought. On 12 Dec 2006 I had this conversation on IRC:

ArthurClemenspossible for a lot of twikis, but bloggers might think otherwise. Ah well, they use BlogPlugin.
Lavr: I am working on an interaction design for configure. Perhaps you can give some feedback (Lynnwood as well)
LavrAny time [20:33]
Lynnwood_my one big request is separating out General Paths. [20:33]
ArthurClemensMy idea is to show as first step only 2 fields: for the site url and for the path_to_twiki [20:33]
ArthurClemensthen enter password and save
and return to the main screen
with feedback at the top about customizing
I will come to step 2
Lynnwood_sounds good [20:34]
ArthurClemensso far? [20:34]
LavrVery good. [20:34]
step 2: main interface
the twisties do not work well
often settings are hidden (people don't know where they are)
so I figured at least a page find should be possible
that is: show everything on the page
and provide a left menu with anchor links
that let the main content jump to the correct position
(kind of back to basics)
(while a search function a la Spotlight would be nice, but not feasible)
the left menu also has a checkbox "hide expert settings"
Lynnwood_there's always the browser search... which will work if everything is visible. [20:38]
ArthurClemensyes, that I mean
the left menu also contains the "Save changes" button
and that button is repeated at the very bottom
LavrIf we hide the expert settings - then we also need to review what is expert. Many are wrongly marked today. [20:39]
ArthurClemensI haven't looked at these in detail
meaning that some expert settings are not?
LavrBut I like the idea of the hide expert button.
Just look at the Store settings.
{RCS}{FgrepCmd} is not marked at expert.
But I shit my pants just by looking at the value /bin/fgrep %CS{|-i}% %DET{|-l}% -H -- %TOKEN|U% %FILES|F%
ArthurClemensit worse if non-expert settings are marked as expert and got hidden [20:42]
LavrSo it is more adding more "expert settings" then the opposite [20:42]
ArthurClemensbut yes, we need to review these [20:42]
LavrThere are a few I would revert the other way. But very few. Maybe 2 [20:42]
ArthurClemenswe also need to look at "Find more extensions"
it should detect if contribs are installed
I even had the impression this was a technical limitation of contribs, but InstalledPlugins does list them
clv_guyLavr thanks [20:45]
LavrInstead of showing all an alternative is an expand all button which you can hit and then search. [20:47]
***clv_guy has quit IRC ("Leaving") [20:47]
ArthurClemenswe have that now, but its not visible enough [20:48]
LavrHa. No clearly not. I do not see it until now that you tell me. [20:49]
ArthurClemensits a possibility if the button is more visible, near the menu
but I think with the menu that hiding/showing does not add that much
Lynnwood_i agree. [20:51]

I think this can be the global outline, but it would be handy if I can jot it in a design.


It is the right thing you do Crawford.

I have suggested this change a long time ago.

However you should have tested it more before checking it in. It doesn't work at all!

It does not store anything else than the paths and it does not store the password when you save the first time.

Then you return to configure and you see everything yes.

And you can change fields. But when you hit next it says the password was not saved. And no matter if you provide the old password or a new password nothing is saved.

Configure is totally broken now.

-- TWiki:Main.KennethLavrsen - 04 Feb 2007

Lowering to normal. Not blocking 4.1.1. In fact I will be releasing now.

-- KennethLavrsen - 04 Feb 2007

OK, thanks for testing it! I did say it was only 20mins work, and I guess it shows. I never really expected you to release it in 4.1.1, I just wanted to show what we could do instead of ignoring important and useful checkers.

I'll get back to you with an imnproved version; though the password setting issue is a PITA. I had intended it not to prompt for the password on the first save (the install step) but obviously didn't get that right frown

If Arthur can help, I'm sure we can get something pretty crisp in time for 4.1.2.

-- CrawfordCurrie - 05 Feb 2007

I addressed the issues with the functionality, it should now save etc.

That's all I'm doing on this; if anyone wants to improve the L&F, they should open a new issue.

Merged to Patch04x01


Closed with release of 4.1.2


Summary The newbies experience in Configure is .... challenging
ReportedBy TWiki:Main.CrawfordCurrie

SVN Range TWiki-4.1.1, Fri, 02 Feb 2007, build 12717
AppliesTo Engine
Component ConfigureScript
Priority Normal
CurrentState Closed

Checkins 12756 12759 12772 12794 12795
TargetRelease patch
ReleasedIn 4.1.2
Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r13 - 2007-03-04 - KennethLavrsen
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback