The easy Weblog and Wiki Software
[ start | index | login ]
start > Calendar Requirements
UI
The look of the calendar is for me correct: nice size, character, previous/next month navigation.

The only thing to say is that the start day of the week could be configured (start on Monday or start on Sunday)

Events
The calendar shows for the moment the days where there are blog snips, with a link to them.

I would suggest a separation between calendar and events and work with "layers" of events. I explain: on the calendar, which is a "fix" presentation of dates, we could present various "events": the days for which there are snips, the days where wiki snips were created, the days where you edited snips, maybe also true calendaring events (meetings, conferences). We don't know in advance what the calendar usage can be.

I suggest that we could pass to the calendar representation a list of "layers" (an hashmap with subjects, like "Blog entries", "Snips created", "Conferences", "Birthdays") and for each map, a list of dates and links to entries. We could have a parameter like "layer=" and the title or id of the layer to show.

Navigation
The main request of SnipSnap can receive a caldate parameter with a chosen date. Depending on the space url, current user context and maybe choices in the macro displaying the items, the behaviour can be different: showing an object for that date, showing the list of objects for that date (preferred default value), showing the x first elements of the list of objects for the date.

A tag like {weblog} could have additional parameters like startdate, enddate, count, span, with usages like

  • {weblog:startdate=2004-01-16} list of blogs du jour
  • {weblog:startdate=2004-01-16|span=week} list of blogs for the week (or month) starting at that date
  • {weblog:startdate=2004-01-16|span=week|count=10} first ten blogs
The same behaviour could be applied to a {snips} or an {events} macro.

(An event, a birthday, etc. could be simply snips with a snip-type label: {snips:snip-type=birthday})

Pagination
If the number of snips exceeds the count per page, hyperlinks back and forth should help us to go to the rest of the list.

Other hyperlinks could help us navigate to the previous or next "time-span" of the blog (next day, next week, next month) even if clicking on the calendar can help navigate directly to a particular day.

Summary
Same presentation as today. Default behaviour: layer is "blogs", click on calendar shows list of all blogs of the day. entries per page (count)(with a maximum count of 100 for example), time-span (day,week, month, year) could be set in the user context (preferences). Additional layers (creation date or edition date or date label) of any snip-type could be added (can be subject to different calendars, or the same calendar with option buttons or combo box for layer)

Sorry to be so long. I hope I'm not too unrealistic (don't know yet the technical implications), and I'm hoping also that I am in the philosophy of the tool (don't hesitate to brutalise me if I'm not in synch) (and of course, I want to help)

Icon-Comment phobia, 4 years and 218 days ago. Icon-Permalink

How are "layers" different than snip streams?

I like your approach for consistent date range specifications. For the purposes of example, I think weblog macro calls would typically specify no startdate and use some sort of "enddate=today", though.

Icon-Comment damaspi, 4 years and 217 days ago. Icon-Permalink

Not different, probably a subset: to add on your snip stream definition, I would say "a layer would be a snip stream keyed by label"

And the label would define the layer name.

As in picture edition, you could make layers visible or invisible, filtering your snip streams.

Of course, snips are sorted by date descending, so enddate makes more sense than startdate, well seen.

In implementations, I would maybe check that every date operation can also handle date+time ("2004-01-16 23:02") because extensions of usage of calendar and calendar views different than "monthly" may have a need for time information.

Icon-Comment pmode, 4 years and 217 days ago. Icon-Permalink

@phobia: Maybe you should take a look at the >>Lifestreams idea from David Gelernter (now working at mirrorworlds). I think funzel tries to implement the idea of substreams based upon attributes (label values) of snips in a given context (namespace) sorted by a date.
Please login to post a comment.

What is SnipSnap?
SnipSnap is a free and easy to install weblog and wiki tool written in Java.

SnipSnap download
Current version: 1.0b3-uttoxeter
Try our >>Web Start Demo!

Resources

5567 Users and 13713 Snips. Installed 6 years and 41 days ago

Logged in Users: (1)
… and 13 Guests.

snipsnap-changed for older changes.

< August 2008 > (Calendar Requirem...)
SunMonTueWedThuFriSat
12
3456789
10111213141516
17181920212223
24252627282930
31

snipsnap
Listed on BlogShares
XHTML 1.0 validated
CSS validated
RSS 2.0 validated
RSS Feed

pico-powered

Powered by SnipSnap 1.0b3-uttoxeter
YourKit >>Java Profiler

Fraunhofer FIRST

snipsnap.org | Copyright 2000-2006 Fraunhofer FIRST