[Fwd: Re: Ready for a 3.1.1 release candidate?]

[Ryan de Laplante <ry...@ijws.com>]

Hi,

I'm curious if these requests made it into 3.1.1?  They are not terribly 
important requests.


Thanks,
Ryan

Re: [Fwd: Re: Ready for a 3.1.1 release candidate?]

[Ryan de Laplante <ry...@ijws.com>]

Awesome, thank you so much!


Ryan


Dave wrote:
> I just applied #1 and #3 in the Roller 3.1 and trunk branches.
>
> - Dave
>
>
>
> On 7/7/07, Ryan de Laplante <ry...@ijws.com> wrote:
>> I'm curious if these requests made it into 3.1.1?  They are not terribly
>> important requests.
>>
>> ---------- Forwarded message ----------
>> From: Ryan de Laplante <ry...@ijws.com>
>> To: user@roller.apache.org
>> Date: Sun, 01 Jul 2007 01:40:42 -0400
>> Subject: Re: Ready for a 3.1.1 release candidate?
>> Hi Dave,
>>
>> A while back I asked for a few small changes to enable to to make better
>> templates, but forgot to create a tickets for them.  If it is not too
>> difficult, I would really appreciate the following enhancements (from a
>> May 30 2007 message):
>>
>> > I've been working on creating a new Roller theme based on a sharp
>> > template from styleshoot.  It's almost finished.  There is a button
>> > effect that I can't do 100% accurately to the theme (even after
>> > fiddling with the CSS for hours) because of the very few tags in that
>> > menu bar.  It would be most helpful to theme developers if at least
>> > one of these two things could be added to Roller's default output:
>> > (not just on my installation)
>> >
>> > 1) Change the menu bar list items from:
>> >
>> >   <li class="rNavItem">
>> >       <a href="$url.site/">$config.siteShortName</a>
>> >   </li>
>> >
>> > to have a span inside of the a link:
>> >
>> >   <li class="rNavItem">
>> >      <a href="$url.site/"><span>$config.siteShortName</span></a>
>> >   </li>
>> >
>> >
>> > 2) If Roller knows that one of these list items is currently being
>> > displayed (such as Front Page or Weblog), then add either an id or
>> > class of "current" to the list item.
>> >
>> > 3) On the comments form, the buttons have a class of "button" which is
>> > very helpful.  On the search form, the button does not have a class of
>> > "button" so it gets styled differently.
>

Re: [Fwd: Re: Ready for a 3.1.1 release candidate?]

[Dave <sn...@gmail.com>]

I just applied #1 and #3 in the Roller 3.1 and trunk branches.

- Dave



On 7/7/07, Ryan de Laplante <ry...@ijws.com> wrote:
> I'm curious if these requests made it into 3.1.1?  They are not terribly
> important requests.
>
> ---------- Forwarded message ----------
> From: Ryan de Laplante <ry...@ijws.com>
> To: user@roller.apache.org
> Date: Sun, 01 Jul 2007 01:40:42 -0400
> Subject: Re: Ready for a 3.1.1 release candidate?
> Hi Dave,
>
> A while back I asked for a few small changes to enable to to make better
> templates, but forgot to create a tickets for them.  If it is not too
> difficult, I would really appreciate the following enhancements (from a
> May 30 2007 message):
>
> > I've been working on creating a new Roller theme based on a sharp
> > template from styleshoot.  It's almost finished.  There is a button
> > effect that I can't do 100% accurately to the theme (even after
> > fiddling with the CSS for hours) because of the very few tags in that
> > menu bar.  It would be most helpful to theme developers if at least
> > one of these two things could be added to Roller's default output:
> > (not just on my installation)
> >
> > 1) Change the menu bar list items from:
> >
> >   <li class="rNavItem">
> >       <a href="$url.site/">$config.siteShortName</a>
> >   </li>
> >
> > to have a span inside of the a link:
> >
> >   <li class="rNavItem">
> >      <a href="$url.site/"><span>$config.siteShortName</span></a>
> >   </li>
> >
> >
> > 2) If Roller knows that one of these list items is currently being
> > displayed (such as Front Page or Weblog), then add either an id or
> > class of "current" to the list item.
> >
> > 3) On the comments form, the buttons have a class of "button" which is
> > very helpful.  On the search form, the button does not have a class of
> > "button" so it gets styled differently.