In the early days, it never occurred to me to use inline css lists. Didn't even know you could do it. So just did what seemed natural (you'll find many things in BoltWire are quite literal).
It's perfectly configurable of course. But I didn't change the core, not sure how it would affect existing sites. I admit though we should change the core. That's probably another good candidate for 3.xx. Just added to the roadmap. Cheers, Dan On Thu, Feb 19, 2009 at 9:03 PM, Linly <[email protected]> wrote: > > There is a solution from Marcos can change the site action list into a > real XHTML list: > > http://www.boltwire.com/index.php?p=solutions.css.siteactions > > Cheers, > linly > > On 2月20日, 上午8時31分, Hans <[email protected]> wrote: >> I notice that all links on page site.actions are strung up on one >> line, making it difficult to edit, and also difficult to create nice >> css menus. And it makes it impossible to create action menus with >> several levels, like for instance used as drop down menus. >> >> I suppose I am used to work with menus which are built from unordered >> lists, where the items are all list items, and can have second and >> third level items. There are many good css menu list examples >> onhttp://www.alistapart.com/, and I have used some in my skins. >> >> But for this I need to use unordered lists of links, and a single line >> of links wil not work. >> >> Any thoughts on this? Why has BoltWire adopted a single line of links? >> >> cheers, Hans > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
