Yeh, I use queries a lot. I updated the code as you suggested and it doesn't
look that bad on the query pages:
http://www.techpresentations.org/w/index.php?title=Conferences&action=purge
Sergey
On Dec 11, 2007 3:16 AM, Markus Krötzsch <[EMAIL PROTECTED]> wrote:
> On Dienstag, 11. Dezember 2007, Sergey Chernyshev wrote:
> > Yep, I thought about adding time within template - the problem with it
> is
> > that it gets displayed as full date/time which is not really my
> intention.
>
> I think in my design below it doesn't (unless time is explicitly specified
> by
> the user), since I use the plain date as an alt label. In query results
> you
> will o course always get the full result right now (since incomplete
> values
> are not supported yet).
>
> Markus
>
> >
> > Sergey
> >
> > On Dec 10, 2007 3:02 AM, Markus Krötzsch <[EMAIL PROTECTED]>
> wrote:
> > > On Donnerstag, 6. Dezember 2007, Sergey Chernyshev wrote:
> > > > It looks like timeline's logic is somehow flawed - my users at
> > > > TechPresentations.org age complaining that date ranges (for
> > > > conferences) don't show the last day of the range correctly -
> Timeline
> > > > assumes 00:00
> > >
> > > of
> > >
> > > > the last day of the range to be the end of timeline item, but it's
> more
> > > > logical to assume 23:59 to be the end of the range.
> > > >
> > > > For example of the problem see the timeline of conference page:
> > > > http://www.techpresentations.org/Conferences
> > >
> > > The reason is that values of Type:Date represent a single precise
> point
> > > in time. If you just enter a date, then the associated time of the day
> > > must be "guessed" and currently we just guess 00:00. We could also
> guess
> > > 9:00 or
> > > 16:00, but no choice seems to be really suitable to represent start-
> and
> > > end-times alike. A simple workaround is to specify more concrete times
> > > when
> > > giving start and end of an event. Note that this could also be done in
> a
> > > template: use two parameters, date and daytime, annotate the date with
> > > either
> > > the time added or a default time, and print the extra time only if
> > > specified,
> > > e.g.:
> > >
> > > [[start date::{{{startdate}}} {{{starttime|09:00}}}|{{{startdate}}}]]
> > > {{{starttime}}}
> > >
> > > The time-datatype needs improvements in the future, and maybe we can
> > > incorporate imprecision into it (so instead of creating a default
> time,
> > > one
> > > would really leave the exact time unspecified and timelines could then
> > > default interval endings to 23:59 and starts to 00:00).
> > >
> > > Markus
> > >
> > >
> > > --
> > > Markus Krötzsch
> > > Institut AIFB, Universät Karlsruhe (TH), 76128 Karlsruhe
> > > phone +49 (0)721 608 7362 fax +49 (0)721 608 5998
> > > [EMAIL PROTECTED] www http://korrekt.org
>
>
>
> --
> Markus Krötzsch
> Institut AIFB, Universät Karlsruhe (TH), 76128 Karlsruhe
> phone +49 (0)721 608 7362 fax +49 (0)721 608 5998
> [EMAIL PROTECTED] www http://korrekt.org
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Semediawiki-devel mailing list
> Semediawiki-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
