Devil's Advocate: should we make the directionality dependant on
locale/language, since some read right-to-left?

:-D

On 2/14/06, David M Johnson <[EMAIL PROTECTED]> wrote:
> I see what you're saying. I have this:
>     <<  next |  current  | prev  >>
>
> And you say that instead it should be this:
>     <<  prev |  current  | next  >>
>
> I think you are correct.
>
> - Dave
>
>
>
> On Feb 14, 2006, at 10:10 AM, Matt Raible wrote:
>
> > I think the problem is you have >> meaning "back" - but I'm used to <<
> > meaning back.  The way it's currently implemented seems backwards to
> > me - especially since the calendar uses << to indicate the previous
> > month.
> >
> > Matt
> >
> > On 2/14/06, David M Johnson <[EMAIL PROTECTED]> wrote:
> >>
> >> On Feb 14, 2006, at 1:28 AM, Matt Raible wrote:
> >>> This sounds like great stuff Dave.
> >>>
> >>> One thing - on your main entry there's a link to previous entries.
> >>>
> >>> CANCELLED: Talking R... ยป
> >>>
> >>> This looks backwards to me, shouldn't it be:
> >>>
> >>> << CANCELLED: Talking R...
> >>
> >> No, the arrows are correct. They're just as shown on all other pages.
> >> I just added back the link to the current day, that should make the
> >> correctness more obvious.
> >>
> >> And I forgot something: since I fixed the in-line search results too
> >> there is actually a fifth type of page:
> >>
> >>      Search page
> >>           /page/<handle>?q=<search terms>
> >>      If there are search results, then this macro will show them
> >> using the
> >>      current weblog's day template.
> >>
> >> BTW, this stuff is commented in the #showWeblogEntriesInCategory()
> >> macro, since that's where the logic is.
> >>
> >> - Dave
> >>
> >>
> >>
> >>>
> >>> On 2/13/06, Dave Johnson <[EMAIL PROTECTED]> wrote:
> >>>> ROL-473: Page view for specific date should show all entries for
> >>>> datehttp://opensource2.atlassian.com/projects/roller/browse/ROL-473
> >>>>
> >>>> This fix is a pretty significant change, so I'm looking for
> >>>> feedback.
> >>>> To fix this old bug I had to introduce the idea of current day,
> >>>> day,
> >>>> month and entry pages. That sounds drastic, but all old permalinks
> >>>> still work (even the old /page/<handle>/YYYYMMDD#<anchor> ones).
> >>>>
> >>>> Here's how the four types of Roller blog URLs work:
> >>>>
> >>>> Current day page
> >>>>       /page/<handle>/
> >>>> On the current day page, Roller will show the most recent N blog
> >>>> entries (not just those for the day).
> >>>> At the end of the page, a previous link points to day page of
> >>>> entries
> >>>> before the ones shown (and the link is displayed as the day's
> >>>> date).
> >>>> This works exactly as before.
> >>>>
> >>>> Day page
> >>>>       /page/<handle>/YYYYMMDD
> >>>> On a day page, Roller will show all of the entries for a specific
> >>>> day. At the end of the page, a next/previous link allows navigation
> >>>> to next and previous day of entries (and the links are displayed as
> >>>> the day's dates). Before, day pages always showed N entries (where
> >>>> usually N=15), but now they'll show only a day's worth (e.g. 1-3
> >>>> entries).
> >>>>
> >>>> Month page
> >>>>       /page/<handle>/YYYYMM
> >>>> On a month page, Roller will show the most recent N blog entries in
> >>>> the month. At the end of the page, a previous link points to day
> >>>> page
> >>>> of entries before the ones shown. This is new; we didn't have month
> >>>> pages before.
> >>>>
> >>>> Entry page
> >>>>      /page/<handle>?entry=<anchor>
> >>>> On an entry page, one entry is shown. The next/prev links link
> >>>> to the
> >>>> next and previous entries (and the links are displayed as the entry
> >>>> titles, nicely truncated). This one also works exactly as before.
> >>>>
> >>>> I also changed the calendar macro/JSP tag, so that the next/
> >>>> previous
> >>>> month links point to next/previos month links.
> >>>>
> >>>> I've got this deployed on my blog now, in case you want to
> >>>> experiment
> >>>> with permalinks, the next/prev stuff and the calendar links.
> >>>>
> >>>> - Dave
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
>
>

Reply via email to