21 Mar
2014
21 Mar
'14
8:35 a.m.
On Thu, Mar 20, 2014 at 2:37 PM, Clemens Klein-Robbenhaar <
c.robbenhaar(a)espresto.com> wrote:
Hi,
Not sure if it's possible or not, but could the paging also be 'date
related'. For example: instead of just saying 'Past Events' could say
'Past
Events 10-16 March, 2014' and use the .fc-button-prev and .fc-button-next
to navigate. But even so, the example fits in the week timeframe, so maybe
an additional paging will be needed.
Hi,
One of the objectives of 6.0 is to review the existing applications on
extensions.xwiki.org, improve them and see how they would integrate in
the
new Flamingo skin (while also making improvements
suggestions).
This mail covers the Flamingo integration for the MoccaCalendar
application.
You can see the proposal at:
http://design.xwiki.org/xwiki/bin/view/Proposal/CalendarApplicationDesign
Any feedback is welcomed (especially from Denis and Clemens :) ).
Thanks for the proposal. It seems by and large the MoccaCal might fit ok
into the new skin, and would look much better with the improvements.
Some bits of feedback from me, mostly things I maybe misunderstood:
- I see the "past events" list needs paging after a while of usage :)
- should have thought about that in the first place.
- showing events in a dialog instead of a page by itself: this is
actually on the top of the todo list for me, it is just that I did
not get around to work it.
The new details view looks good; however I wonder what the "View"
button does. Is this an alternative to "Edit", e.g. depending on the
view/edit mode one sees a button to switch to the other one?
I've mentioned what the buttons are suppose to do in
http://jira.xwiki.org/browse/MOCCACAL-13?focusedCommentId=80201&page=co…
'View' should direct to the event page, in view mode, allowing viewing of
comments, attachments, etc.
The functionality is similar to our 'Quick Jump' (Ctrl + G), but I've
changed the order of importance for Edit and View.
For the Panels:
- if there are many calendars (e.g. if every user creates ones own
calendar)
then the panel for filtering the calendars one wants to see will not
scale well, if it lists all calenders available. (However it will be
more needed then ever, of course :)
However as I have no good idea how to handle the case of very many
calendars,
I am happy to get this panel working first.
We could list a fix number of calendar (5-10) and have a 'More' that lists
more calendars. We have a similar effect in Solr Search facets.
- This panel also needs a way to store some kind of "User Preferences"
for the Calendar. I think this is a good idea, but I am not sure how
to implement this. (Is adding a "MoccaCalendarPreferences" object to
the
user profile acceptable? I am not sure if this makes the users profile
unusable if someone uninstalls the application that has defined the
prefs.)
IMO this is acceptable. We have done it in the past for Dashboard,
Watchlist, Workspaces, etc. and let the user have his preferences defined
in his User Profile. In Flamingo's proposal, I've clearly separated the
Application's preferences in a special section in the vertical-menu
http://design.xwiki.org/xwiki/bin/download/Improvements/Skin4xProfile/profi…
- What does the "little calendar" panel in the lower right do?
I guess it is just to show it on the same page as the other calendar
related panels, because it would be good to have this panel elsewhere
to be able to jump to the calendar, but that might be of not much use
inside the calendar app itself?
Or maybe I am misunderstanding what it is good for.
The Calendar proposal is very similar to Google Calendar.
The nice thing about the panels is that they could be reused also in other
applications (spaces). It just displayed the current month and day. Having
it for navigation could be interesting, but complicated from implementation
point of view.
About view order:
- Why is "Day, Week, Month, Agenda" better than "Month, Week, Day,
Agenda" ?
(just asking, I do not understand the rationale)
Btw, the "Month, Week, Day" order just happen to be the default for full
calendar, that is the rationale why it is the way it is now. ;)
'Day', 'Week', 'Month', 'Agenda' is the order also defined
in Google
Calendar, Yahoo Calendar, Apple Calendar, etc. Having the same layout and
pattern throughout calendar applications is good.
I feel the best order depends on how many events are in the calendar.
For example if there are only a few, say, it contains milestones
for a software release, the "month view" is the one that will be
used most.
Well, I guess I am asking for making this configurable. I have a
vague feeling that this will come back to me :D
Calendars:
- the reasons that the view to add calendars is now on the main page
is that users do not miss that they can add their own calendars.
However I understand that this is not the best way to get a high
usability/area ratio, as one only rarely adds new calendars
The proposal is to move that to a separate page, which I agree,
and to show a "settings" button to get to that page. Where
I am not sure is if "Settings" is a good label - I would not expect
to find the ability to add new calendars in "Settings".
I would have preferred something like "Manage Calendars".
(However I have to admit that this makes the label quite long ...)
At first can be called 'Manage Calendars' if you prefer. In my mind, the
'Settings' should be extended in the future with the ability to adjust the
timezone, starting day of the week, export calendars, etc.
- for every calendar there are "add / edit / actions" in the screens.
I guess that is just the default that XWiki offers for every page?
Sometimes I wonder if allowing an application to hide some of the
menu options would be good. (E.g. exporting a calendar to PDF
is possible, but the result looks nowhere like what the user might
expect;
it is mostly a blank page.)
I've tough about that. The problem is that currently our menus do not have
extensions points. In the future menus could be personalized per
application, or incorporate the application's custom buttons inside (like
being able to Add - Event from the content Add). I know it's not perfect,
but for the current layout and implementation both content and applications
actions should be visible (in order to be able to add pages, export, etc.)
Thanks :)
Caty
Clemens
Thanks,
Caty
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs