7 Apr
2011
7 Apr
'11
11:21 a.m.
Actually, as I was starting to implement this, I realized that dashboard
pages need to be edited in WYSIWYG mode as well, to modify the
parameters of the dashboard (such as the style of the dashboard).
Now, what we could do to fix that is to store the whole dashboard
definition in an object as well (attached to the page) and use the
dashboard macro only to pinpoint the position in the page. Then, we
could provide UI in the dashboard visual editor for these parameters
(change the style and / or layout).
However, there is one parameter, source, which should still be a macro
parameter since it tells where to read these objects from.
Even so, is it OK that the simple users will only be able to edit a page
that contains a dashboard in inline mode? e.g. if they have additional
text on the page they'll need to become advanced users to be able to
choose wysiwyg editing for that text, or if they want to change the
parameters of the dashboard macro.
I would like to have your opinion on this potential mixed editing need.
Thanks,
Anca
On Tue, 2011-03-22 at 17:26 +0100, Luca Anca wrote:
Hi all,
I've got some suggestions that the current way of editing the dashboard
is not really intuitive (Edit -> Inline Form), and mainly because users
wouldn't necessarily look under "Edit" for a method to change the
dashboard. Also, other users that I've observed, forgot that they need
to go in some edit mode before changing things.
I also agree that without documentation no user would figure out that
editing a dashboard is under Edit -> Inline Form. While editing will
still remain "in inline mode", from the technical pov, we need to
provide a easier way for users to discover this.
Let's look at the following options:
1/ Add a "Customize" menu entry under edit, in the page menu, as
proposed in the mockups from Cati, a long time ago:
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/GadgetsDashboard .
2/ Add a "Customize this dashboard" button in the dashboard in view
mode, in the top right corner, something like
http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/oldDashboa…
but styled better to integrate with the current dashboard.
3/ Define and implement a mechanism to allow the inline form edit to be
triggered for a document without that document having to include a
document which has an object in it. E.g. as Vincent proposed at one
point, trigger inline mode when an object is present in the current
document.
I should note that solutions 1 and 3 still assume that the user will go
to "Edit" to try to customize the dashboard, which can also be
problematic (I cannot figure it out for sure right now, we need fresh
users or proper UX expertise which I don't have).
WDYT?
Thanks,
Anca
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
