Hi,
Thanks Caty for the proposal. Here are my comments on it and on the
application that I think we should target:
- The progress bar is nice. We could also use a "step" mechanism since we
have 3 or 4 steps. I am not sure a pourcentage is relevant.
- Since we are in a wizard I think standard buttons "Preview", "Save
&
Continue" ... etc should be replaced by "<< Previous" and
"Next >>"
- ColorTheme application example is not a very good example IMO.
Basically, users will want to use Application Within Minutes every time they
want to manage "entries", à la Excel. So it can be events, products, tasks,
people, ... See example given here :
http://www.xwiki.com/xwiki/bin/view/Blog/ContentStructuration . You can
also check how IWA could have used Application Within Minutes to create this
space :
http://www.iwawaterwiki.org/xwiki/bin/view/EventsExtra/ (When
loggued in, you can contribute material)
- I don't see the page / area that lists all applications. Is this
located in the administration? It would be cool not to have them in the
administration.
- Application Within Minutes is for end users. Developers already have
access to XWiki ability to create applications. Therefore, we should not
have any line of code in the default (simple) view.
- The first thing that we have to target is the simple view
- Here are the items that users in simple view should have access to (and
only):
- Application Name
- Application Key
- Application Description
- A page that allows user describe the data he/she wants to manage
- Property name
- Property type
- Application home page options
- Welcome message
- Does users want to list entries on the home page
- Fields to be displayed in that list
- Rights settings (maybe not in this version)
- Other options?
- => Therefore we should not mention class, sheet, template, etc.
All this should be transparent for those user (at least in simple view)
- I beleive we can use a default XWiki page, no need to have a dedicated
environment. If we want to display extra tips we can either use the
administration layout or panels.
Thanks
--
Thibaut
On Mon, Apr 25, 2011 at 10:03 PM, Ludovic Dubost <ludovic(a)xwiki.com> wrote:
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 :
Hi,
--
Ludovic Dubost
Blog:
http://blog.ludovic.org/
XWiki:
http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs