webgen users - Sep 2008 - horizontal submenus no longer separate unordered list?

I originally generated my website with the andreas09 template under
webgen 0.4 (or earlier).

Under webgen 0.4, my horizontal submenus were separate line unordered lists.

Under webgen 0.5, they are in the same unordered list as the main menu
level, with this class webgen-menu-submenu.  This messes up the layout
of my menus.

Do you have any examples of CSS which will correctly format horizontal
submenus, or a switch/flag to make them be in a separate unordered
list?

Thanks,
-- Chad

Am Sat, 20 Sep 2008 22:41:17 -0700
schrieb "Chad Woolley" <thewoolleyman at gmail.com>:
> I originally generated my website with the andreas09 template under
> webgen 0.4 (or earlier).
> 
> Under webgen 0.4, my horizontal submenus were separate line unordered
> lists.
> 
> Under webgen 0.5, they are in the same unordered list as the main menu
> level, with this class webgen-menu-submenu.  This messes up the layout
> of my menus.
> 
> Do you have any examples of CSS which will correctly format horizontal
> submenus, or a switch/flag to make them be in a separate unordered
> list?
The menu tag currently only generates nested lists. I will add an
option for generating non-nested lists which would do the following:

tag.menu.nested = true:

    ul 1
      li 11
      li 12
      li 13
        ul 2
          li 21
          li 22
      li 14

tag.menu.nested = false:

     ul 1
       li 11
       li 12
       li 13
       li 14
     ul 2
       li 21
       li 22

Would that be okay?

Note: for such a menu to work correctly, the
tag.menu.show_current_subtree_only option has to be set to true.
Otherwise the display would be a little confusing.

-- Thomas

On Tue, Sep 23, 2008 at 7:28 AM, Thomas Leitner <t_leitner at gmx.at>
wrote:
> tag.menu.nested = false:
>
>     ul 1
>       li 11
>       li 12
>       li 13
>       li 14
>     ul 2
>       li 21
>       li 22
>
> Would that be okay?
>
> Note: for such a menu to work correctly, the
> tag.menu.show_current_subtree_only option has to be set to true.
> Otherwise the display would be a little confusing.
Yes, I think that would be fine, and the sensible thing (default?) for
horizontal menus.  Otherwise, it is a pain to style - I''m not even
sure how you would get the submenu in a different block.

By the way, do you have your github project configured to
automatically generate beta gems?  That would be nice, then I could
use this as soon as you code it and not wait for the release or have
to build it myself.

Thanks,
-- Chad

Am Tue, 23 Sep 2008 10:44:41 -0700
schrieb "Chad Woolley" <thewoolleyman at
gmail.com>:
> On Tue, Sep 23, 2008 at 7:28 AM, Thomas Leitner <t_leitner at gmx.at>
> wrote:
> > tag.menu.nested = false:
> >
> >     ul 1
> >       li 11
> >       li 12
> >       li 13
> >       li 14
> >     ul 2
> >       li 21
> >       li 22
> >
> > Would that be okay?
> >
> > Note: for such a menu to work correctly, the
> > tag.menu.show_current_subtree_only option has to be set to true.
> > Otherwise the display would be a little confusing.
> 
> Yes, I think that would be fine, and the sensible thing (default?) for
> horizontal menus.  Otherwise, it is a pain to style - I''m not even
> sure how you would get the submenu in a different block.
> 
> By the way, do you have your github project configured to
> automatically generate beta gems?  That would be nice, then I could
> use this as soon as you code it and not wait for the release or have
> to build it myself.
Will look into that if it is possible to do that in a DRY way. Note
that the official releases will be done on Rubyforge, not on Github. So
there may be a chance that a gettalong-webgen-0.5.5 is not the same as
webgen-0.5.5.

Are there any downsides to using github as gem server, apart from a
different gem naming scheme?

-- Thomas

On Thu, Sep 25, 2008 at 5:07 AM, Thomas Leitner <t_leitner at gmx.at>
wrote:
> Will look into that if it is possible to do that in a DRY way. Note
> that the official releases will be done on Rubyforge, not on Github. So
> there may be a chance that a gettalong-webgen-0.5.5 is not the same as
> webgen-0.5.5.
>
> Are there any downsides to using github as gem server, apart from a
> different gem naming scheme?
>
Well, it publishes with every commit, so that means you have multiple gems
published which have the same version, but are really different.  But, if
you bump your version in master after every deploy, and add a fourth-level
component, I think this is not a big deal though.  So, if you just published
0.5.5 to rubyforge, you would immediately bump the version in master to
0.5.6.1.  The existence of a fourth-level component could indicate by
convention that it is a github, beta gem which will be modified without
incrementing the version.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/webgen-users/attachments/20080925/a699b1fa/attachment-0001.html>

Am Thu, 25 Sep 2008 11:00:55 -0700
schrieb "Chad Woolley" <thewoolleyman at
gmail.com>:
> Well, it publishes with every commit, so that means you have multiple
> gems published which have the same version, but are really
> different.  But, if you bump your version in master after every
> deploy, and add a fourth-level component, I think this is not a big
> deal though.  So, if you just published 0.5.5 to rubyforge, you would
> immediately bump the version in master to 0.5.6.1.  The existence of
> a fourth-level component could indicate by convention that it is a
> github, beta gem which will be modified without incrementing the
> version.
I have pushed the changes regarding the webgen.gemspec to the Github
repository and the gettalong-webgen gem is now available from
gem.github.com.

The github gem contains the push date as last part of the version
number, for example 0.5.4.20080929. Note that when running `webgen
version` webgen will still identify itself with 0.5.4.

Also note that the github gem is always considered a BETA gem so it may
still contain some unfixed bugs. However, I try to only push useable
versions to github but that is not guaranteed!

-- Thomas

On Tue, Sep 23, 2008 at 7:28 AM, Thomas Leitner <t_leitner at gmx.at>
wrote:
> The menu tag currently only generates nested lists. I will add an
> option for generating non-nested lists which would do the following:
>
> tag.menu.nested = false:
>
> Note: for such a menu to work correctly, the
> tag.menu.show_current_subtree_only option has to be set to true.
>
Finally tried this out - it seems to work fine.  Thanks!

-- Chad
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/webgen-users/attachments/20081017/2434ed61/attachment-0001.html>

On Tue, Sep 23, 2008 at 7:28 AM, Thomas Leitner <t_leitner at gmx.at>
wrote:
> The menu tag currently only generates nested lists. I will add an
> option for generating non-nested lists which would do the following:
>
> tag.menu.nested = false:
>
> Note: for such a menu to work correctly, the
> tag.menu.show_current_subtree_only option has to be set to true.
>
Finally tried this out - it seems to work fine.  Thanks!

-- Chad
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/webgen-users/attachments/20081017/fe2e0010/attachment.html>