Also, it'd be nice to see some of the format functions revamped. Right now more() allows you to create text links after a cutoff with text specified by the theme class. It'd be nice to be able to specify a string, and have a keyword in that string replaced like in printf. This would allow for a lot more design freedom.
- Matthew On Jun 14, 1:25 am, Realpolitik <cav...@gmail.com> wrote: > The theming functions theme_prev_page_link, theme_next_page_link, and > theme_page_selector should allow themers to specify their own classes > for current-page, next-page, and prev-page. It's likely that designers > will want different pagination on home, page.multiple, entry.multiple, > or search. It is possible to achieve these different themes by placing > the output of these selectors in different <div> classes and > specifying the subclasses .current-page .next page and .prev-page, but > this seems a little backwards. > > I would propose just passing the class variables to the given > function, and if no variable was passed, use a theme-defined variable > that can be overwritten by child themes. > > Furthermore, It would be nice if theme_page_selector could return an > array so that designers aren't stuck with <a href="#">1</ > a> <a href="#">2</a> <a href="#">3</a> and can instead put > each of those links in it's own div or li which would reduce the > limitations on design. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to habari-dev@googlegroups.com To unsubscribe from this group, send email to habari-dev-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
