Hi,
Here is some feedback about the proposal.
Generally I like the proposal which covers mostly what we need.
I see some ntegration issue however:
- the structure of the page is different than a normal "xwiki" page.
This is a problem I think. I'm not sure how this will integrate in the
rest of XWiki. This probably means there should be some way to customize
the "home page" look.
- it's not clear where the application resides, wether it is in the
"prefs" or somewhere in the wiki and how we access it.
Some comments about the UI itself:
Main Screen:
- "Add New Entry" should not have a page name. One of the objectives of
the project is to get rid of this requirement. It should only be an
"Add" button.
Structure Screen:
- I'm not sure about the left vertical zone with the different page
types. Your proposal is kind of "IDE view". For an "IDE view" I would
prefer a tree. But I think we first need an "simple view", so I believe
we should propose 2 views: Simple / Advanced.
- Simple View:
- Show only the minimun actions: Class, Templates, Translations
- We don't need "Sheet" in the simple view as it should be the
default script. In "simple" mode no script should be necessary.
- IDE View:
- Show a tree with all the different page types.
Each page type should have some more advanced proposals to help edit.
The most important one is the "Class Editor". We need a simpler
proposal. We should look at applications on the web (google forms or so)
which propose some simple ways to add and edit fields. This could mean
merging "class editor" and "sheet editor" but I'm not sure we are
ready
for that yet.
For "Sheets" we need a way to associate "Sheets" with edit modes (view
/
edit / search / changes / home), but that's advanced mode too.
For Translations initially it would be the usual wiki editing, but then
we should propose an editor.
The main priority I see for the next steps are:
- propose a "simple view"
- propose a simpler class editor
- clarify/fix integration issues for the home page / define entry point
of the App Within Minutes app
- propose an edit view for translations
In general it's ok that we think "long term" (IDE style in advanced
mode, more advanced editors), but we can already deliver something
compelling with all the "default options" used instead of providing too
many features.
Let's make sure we have a clear definition of the "minimum" so that
developers know what to start with.
Looking forward for the next cycle.
Ludovic
Le 22/04/11 18:54, Ecaterina Moraru (Valica) a écrit :
--
Ludovic Dubost
Blog:
http://blog.ludovic.org/
XWiki:
http://www.xwiki.com
Skype: ldubost GTalk: ldubost