22 Jun
2011
22 Jun
'11
3:59 p.m.
Dear All,
I'm working on the Calendar Application and I would like a few opinions on
how to structure it.
Details about the application can be found here:
http://incubator.myxwiki.org/xwiki/bin/view/Drafts/CalendarApplication and
my main problem is choosing between the presented alternatives.
A few important pieces of information about the application:
- every event is a document with an object of EventClass attached
- every calendar is a document with an object of CalendarClass attached
- whenever a calendar is added, a space is also created. This space will
store the calendar doc and the events associated with the calendar
The functionality can be found on incubator.
The alternatives are:
*Calendar aggregator*
The WebHome of the application is an aggregated calendar which displays the
events from all the calendars of a user.
The user creates several calendars (e.g. Personal, Work) which can be
visualized both individually and together, on the main page of the
application.
This is very similar to Google Calendar, following the same approach. The
main advantage of this is the ease of interaction between users' calendars
(e.g. sharing a calendar with another user means displaying the specific
calendar among his own calendars, inside the WebHome).
*Individual calendars with categories*
The users creates calendars which are individual entities and each event is
assigned a category when added.
When the user is invited to other events he can choose to view those events
in one or more of his calendars while when another user shares a calendar
with him he can only view that calendar, on a separate page.
As far as I see it, the first choice means easier interaction between users
but considering the number of events that must be selected every time,
performance might not be that good.
Please let me know which of the two you consider to be better or, if you
have another solution, which might that be.
Thanks,
Vlad
22 Jun
22 Jun
8:50 p.m.
Hi Vlad,
In my opinion one user should have one calendar. I think having more than
one calendar per user will bring unnecessary complexity. I can see the value
of this approach in Google Calendar, but since XWiki is an enterprise wiki,
most of the user's activity on the wiki, calendar included, will be around
the work he does.
Having one calendar with several categories I think should suffice. By
changing the privacy settings the user will be able to specify which of
these categories he wants to:
* share with everyone
* share with certain users he selects
* keep completely private
Silvia
On Wed, Jun 22, 2011 at 4:59 PM, Vlad Merticariu <vmerticariu(a)xwiki.com>wrote;wrote:
Dear All,
I'm working on the Calendar Application and I would like a few opinions on
how to structure it.
Details about the application can be found here:
http://incubator.myxwiki.org/xwiki/bin/view/Drafts/CalendarApplication and
my main problem is choosing between the presented alternatives.
A few important pieces of information about the application:
- every event is a document with an object of EventClass attached
- every calendar is a document with an object of CalendarClass attached
- whenever a calendar is added, a space is also created. This space will
store the calendar doc and the events associated with the calendar
The functionality can be found on incubator.
The alternatives are:
*Calendar aggregator*
The WebHome of the application is an aggregated calendar which displays the
events from all the calendars of a user.
The user creates several calendars (e.g. Personal, Work) which can be
visualized both individually and together, on the main page of the
application.
This is very similar to Google Calendar, following the same approach. The
main advantage of this is the ease of interaction between users' calendars
(e.g. sharing a calendar with another user means displaying the specific
calendar among his own calendars, inside the WebHome).
*Individual calendars with categories*
The users creates calendars which are individual entities and each event is
assigned a category when added.
When the user is invited to other events he can choose to view those events
in one or more of his calendars while when another user shares a calendar
with him he can only view that calendar, on a separate page.
As far as I see it, the first choice means easier interaction between
users
but considering the number of events that must be selected every time,
performance might not be that good.
Please let me know which of the two you consider to be better or, if you
have another solution, which might that be.
Thanks,
Vlad
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
23 Jun
23 Jun
noon
Hi,
Both approaches are very similar regarding the logic: either you have
multiples calendars, either you have categories; you will use them to manage
your events in the same way.
The problem is technical and we don't know what version would be more simple
to be implemented on top of XWiki.
- having multiple calendars store in spaces - needs an aggregator for them
(and a place to store it).
- having categories means you need to do queries (could be slower) on top of
the events properties in order to determine the relationship.
The main use case for Calendar is the sharing of events. You create an event
and you want to share it with multiple participants. How do you mark the
external event in a participant's calendar? Do you just link it? Do you
create copies of the event in the participant's calendar? How do you
synchronize it if changes appear?
The spaces multiplication is gonna be bigger in the multiple calendars
version. Each user will have n spaces for each calendars. But this way we
can also have specific spaces that contain specific content. For example you
can assign a calendar in the "Marketing" space and this space will contains
the event pages, but also content pages.
You be very nice to have a technical advice regarding this aspect.
Thanks,
Caty
On Wed, Jun 22, 2011 at 21:50, Silvia Rusu <silvia.rusu(a)xwiki.com> wrote:
Hi Vlad,
In my opinion one user should have one calendar. I think having more than
one calendar per user will bring unnecessary complexity. I can see the
value
of this approach in Google Calendar, but since XWiki is an enterprise wiki,
most of the user's activity on the wiki, calendar included, will be around
the work he does.
Having one calendar with several categories I think should suffice. By
changing the privacy settings the user will be able to specify which of
these categories he wants to:
* share with everyone
* share with certain users he selects
* keep completely private
Silvia
On Wed, Jun 22, 2011 at 4:59 PM, Vlad Merticariu <vmerticariu(a)xwiki.com
wrote:
Dear All,
I'm working on the Calendar Application and I would like a few opinions
on
how to structure it.
Details about the application can be found here:
http://incubator.myxwiki.org/xwiki/bin/view/Drafts/CalendarApplicationand
my main problem is choosing between the presented alternatives.
A few important pieces of information about the application:
- every event is a document with an object of EventClass attached
- every calendar is a document with an object of CalendarClass attached
- whenever a calendar is added, a space is also created. This space
will
store the calendar doc and the events
associated with the calendar
The functionality can be found on incubator.
The alternatives are:
*Calendar aggregator*
The WebHome of the application is an aggregated calendar which displays
the
events from all the calendars of a user.
The user creates several calendars (e.g. Personal, Work) which can be
visualized both individually and together, on the main page of the
application.
This is very similar to Google Calendar, following the same approach. The
main advantage of this is the ease of interaction between users'
calendars
(e.g. sharing a calendar with another user means
displaying the specific
calendar among his own calendars, inside the WebHome).
*Individual calendars with categories*
The users creates calendars which are individual entities and each event
is
assigned a category when added.
When the user is invited to other events he can choose to view those
events
in one or more of his calendars while when
another user shares a calendar
with him he can only view that calendar, on a separate page.
As far as I see it, the first choice means easier interaction between
users
but considering the number of events that must be selected every time,
performance might not be that good.
Please let me know which of the two you consider to be better or, if you
have another solution, which might that be.
Thanks,
Vlad
_______________________________________________
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
4:34 p.m.
Hi,
A third option is to have all the calendars and events inside the Calendar
Application space.
This is nice because the application is isolated in its space and no noise
is created, but it requires much care and custom UI to handle everything.
Plus, some people might like to have a calendar in their existing spaces
instead of having their work 'fragmented' (calendar in a different location
than the work's location).
It's not very clear which option is best, we need to pick one that 'hurts'
the least and go with it.
Thanks,
Eduard
On Thu, Jun 23, 2011 at 1:00 PM, Ecaterina Moraru (Valica) <
valicac(a)gmail.com> wrote:
Hi,
Both approaches are very similar regarding the logic: either you have
multiples calendars, either you have categories; you will use them to
manage
your events in the same way.
The problem is technical and we don't know what version would be more
simple
to be implemented on top of XWiki.
- having multiple calendars store in spaces - needs an aggregator for them
(and a place to store it).
- having categories means you need to do queries (could be slower) on top
of
the events properties in order to determine the relationship.
The main use case for Calendar is the sharing of events. You create an
event
and you want to share it with multiple participants. How do you mark the
external event in a participant's calendar? Do you just link it? Do you
create copies of the event in the participant's calendar? How do you
synchronize it if changes appear?
The spaces multiplication is gonna be bigger in the multiple calendars
version. Each user will have n spaces for each calendars. But this way we
can also have specific spaces that contain specific content. For example
you
can assign a calendar in the "Marketing" space and this space will contains
the event pages, but also content pages.
You be very nice to have a technical advice regarding this aspect.
Thanks,
Caty
On Wed, Jun 22, 2011 at 21:50, Silvia Rusu <silvia.rusu(a)xwiki.com> wrote:
The
specific
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi Vlad,
In my opinion one user should have one calendar. I think having more than
one calendar per user will bring unnecessary complexity. I can see the
value
of this approach in Google Calendar, but since XWiki is an enterprise
wiki,
most of the user's activity on the wiki,
calendar included, will be
around
the work he does.
Having one calendar with several categories I think should suffice. By
changing the privacy settings the user will be able to specify which of
these categories he wants to:
* share with everyone
* share with certain users he selects
* keep completely private
Silvia
On Wed, Jun 22, 2011 at 4:59 PM, Vlad Merticariu <vmerticariu(a)xwiki.com
http://incubator.myxwiki.org/xwiki/bin/view/Drafts/CalendarApplicationand
wrote:
Dear All,
I'm working on the Calendar Application and I would like a few opinions
on
> how to structure it.
>
> Details about the application can be found here:
> > my main problem is choosing between the
presented alternatives.
>
> A few important pieces of information about the application:
>
> - every event is a document with an object of EventClass attached
> - every calendar is a document with an object of CalendarClass
attached
-
whenever a calendar is added, a space is also created. This space
will
store the calendar doc and the events
associated with the calendar
The functionality can be found on incubator.
The alternatives are:
*Calendar aggregator*
The WebHome of the application is an aggregated calendar which displays
the
> events from all the calendars of a user.
> The user creates several calendars (e.g. Personal, Work) which can be
> visualized both individually and together, on the main page of the
> application.
> This is very similar to Google Calendar, following the same approach. main
advantage of this is the ease of interaction between users'
calendars
> (e.g. sharing a calendar with another user means displaying the > calendar among his own calendars, inside the
WebHome).
>
>
> *Individual calendars with categories*
>
> The users creates calendars which are individual entities and each
event
is
calendar
assigned a category when added.
When the user is invited to other events he can choose to view those
events
> in one or more of his calendars while when another user shares a > with him he can only view that calendar, on
a separate page.
>
>
> As far as I see it, the first choice means easier interaction between
> users
> but considering the number of events that must be selected every time,
> performance might not be that good.
>
>
> Please let me know which of the two you consider to be better or, if
you
have
another solution, which might that be.
Thanks,
Vlad
_______________________________________________
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
4834
days inactive
4835
days old
3 comments
4 participants
participants (4)
-
Ecaterina Moraru (Valica) -
Eduard Moraru -
Silvia Rusu -
Vlad Merticariu