- themes - lists.drupal.org

Drupal Main Theme page - A Suggestion for Improvements
by Trae McCombs 20 Dec '05

20 Dec '05

* resending this as it wasn't in the archives ** archives should now be fixed. fwiw. Hi all, If you go to this page: http://drupal.org/support You will see a variety of information for someone looking for support. However, if you go to the main Drupal Themes page, you are simply confronted with a bunch of themes to download. I suggest we create a Launching page for the Main Themes page too. We should have at least the following: 1. Prominent Large Image pointing to the Themes Gallery (Think Drupal News Letter "Ad" on the front page of Drupal.org) Perhaps links to themes hosted elsewhere. (offsite from drupal.org) 2. Themes Help area that lists the following links: - Basic Themes Help: http://drupal.org/node/39451 - Manage inconsistancy in themes: http://drupal.org/node/37156 3. IRC Channel This should simply mention the #drupal-themes irc channel on irc.freenode.net. 4. Mailing list info Info about this mailing list. 5. Other stuff... ... I'm not sure who is the person that would or does have the permissions to do this. I would not mind doing it if Dries gave me access to the site to do it. Thanks for your time, Trae -- Trae "occy" McCombs || http://occy.net/ Founder - Themes.org // Linux.com CivicSpaceLabs - http://civicspacelabs.org/

2 2

Re: [themes] usability and accessibility improvement
by Michelle Cox 19 Dec '05

19 Dec '05

There is a module to add a block for changing the font size. I'm with Ber, though, and ended up uninstalling it because it made more sense to just let the user set it in their browser. Michelle On 12/19/2005 3:50:26 AM, Egon Bianchet (egon.bianchet(a)gmail.com) wrote: > Hello, > I'm wondering if there is a plan regarding usability and accessibility > of standard Drupal themes. > > I'd > like to know if somebody already thought about implementing: > > - skip-navigation, return-to-top links > - change-font-size, high-contrast-css links > - internal, external and mailto links differentiation > > -- > Egon Bianchet <egon.bianchet(a)gmail.com> > > _______________________________________________ > themes mailing list > themes(a)drupal.org > http://lists.drupal.org/mailman/listinfo/themes

4 3

usability and accessibility improvement
by Egon Bianchet 19 Dec '05

19 Dec '05

Hello, I'm wondering if there is a plan regarding usability and accessibility of standard Drupal themes. I'd like to know if somebody already thought about implementing: - skip-navigation, return-to-top links - change-font-size, high-contrast-css links - internal, external and mailto links differentiation -- Egon Bianchet <egon.bianchet(a)gmail.com>

4 4

Fwd: [General inquiry (other)] Contributing Themes
by Dries Buytaert 19 Dec '05

19 Dec '05

Can someone on this list help Ken? :) Begin forwarded message: > From: ken(a)metaskills.net > Date: Mon 19 Dec 2005 01:02:53 GMT+01:00 > Subject: [General inquiry (other)] Contributing Themes > Reply-To: ken(a)metaskills.net > > Ken Collins sent a message using the contact form at > http://drupal.org/contact: > > I've been using Drupal for almost a year now and I am very > interested in > submitting my theme to the community. See metaskills.net for a > preview. I > am testing with 4.7 now too. Whom do I submit these two, I would > love to > share and help drupal become a more user-centric blogging app. > > TIA, Ken -- Dries Buytaert :: http://www.buytaert.net/

1 0

comments in $links --> move it elsewhere
by david hodgkins 16 Dec '05

16 Dec '05

I want to move the number of comments 'indicator' (i.e. 3 Comments) elsewhere. (Yet keep the original $links intact.) I want something like this in my node.tpl.php: Comments in this Entry: # (where # is any number, 0 on up, and the # linked to the comments.) I've tried a few things (like comment_num_replies<http://drupaldocs.org/api/head/function/comment_num_replies> ($pid) and others from drupaldocs, but I usually got an "array" or a total of all comments on my site. Has anyone figured this out? Any way to do this? (drupal 4.6). silverwing

2 1

Re: Please. Hold on for a second. (was Re: [development] proposal for theming nodes)
by Liza Sabater 16 Dec '05

16 Dec '05

Chris, I am not a developer, so I'd be the worst person to ask to start DIV TAGGING inside modules. Just to explain my previous comments, what I am suggesting is more than just themers asking for a favor from module developers. I believe there is a need for the development group to agree to a standard for 'div tagging' inside modules already in existence and then enforcing it. Again, not everybody is going to move to 4.7. The costs are going to be great to many groups, especially here in the US the political and culture activist groups that have embraced Drupal over Scoop. I guess, I'd have to ask, what does it take for something like this to be happen in Drupal? I am cross-posting to the themes list --we've been remiss in keeping this conversation on both lists. / liza On Dec 15 2005, at 01:31 PM, Chris Johnson wrote: > Liza Sabater wrote: > >> upgraded to 4.7? Is there a way to go back to what is ALREADY >> created and ask module developers to clean what is there based on >> theme parameters that y'all can agree on? Why can't we ask of >> developers to do something as simple as going back to their >> modules and setting DIV TAGS SPECIFIC TO THEIR MODULES? > > Why yes, you can ask module developers to enhance their previous > release (4.6, 4.5, etc.) modules. And if you and some others do > the same, then it would be "we" and it might or might not happen, > depending on the time available to the developer and his or her > inclinations. > > So, by all means, ask! > > No promises, though. :-) > > ..chrisxj > >

2 1

Re: style date differently
by david hodgkins 14 Dec '05

14 Dec '05

While four letter words were used a lot in trying to figure this out, echo wasn't one of them! It worked! Thanks! david (silverwing) Because of the all-important "echo". This should work in node.tpl.php: > > <?php echo format_date($node->created, 'custom', 'D M d Y'); ?> > > -- > David Carrington > > > > > End of themes Digest, Vol 1, Issue 11 > ************************************* >

2 1

Re: style date differently
by david hodgkins 14 Dec '05

14 Dec '05

Just adding that didn't work anywhere. I'm still open to any other suggestions.... > > Message: 1 > Date: Wed, 14 Dec 2005 03:04:35 -0500 > From: erik hopp <drupal(a)mediamutiny.org> > Subject: Re: [themes] style date differently > To: A list for theme developers <themes(a)drupal.org> > Message-ID: <439FD213.8030107(a)mediamutiny.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > try something like this: > > put this at the top of the node.tpl.php or wherever you need it... > > <?php format_date($node->created, 'custom', 'D M d Y') ?> > > hope it helps... i actually have almost no idea what i'm talking about > and its 3am!!!!! > > erik. > > > > > david hodgkins wrote: > > (I've spent a couple hours trying this on my own, but to no avail.) > > > > On my theme Connections, I need to have the date styled differently. It > > should be: > > day date month year, > > Wed Dec 14 2005 or > > D M d(or j) Y > > > > I have no idea what to change, or how to change it. (I have a funny > > feeling that template.php plays a roll in this.) > > > > While I would have loved to come up with an answer on my own, I don't > > think I can. The documentation in the handbook is poor. > > > > The function in the api is at > > http://drupaldocs.org/api/4.6/function/format_date > > > > I'd appreciate it if someone could help me with this. > > > > ~silverwing > > >

2 1

Re: [development] proposal for theming nodes
by Robin Monks 14 Dec '05

14 Dec '05

Mabey we should offer free "learn PHP ultra-quick" ebooks for themers? It's a shame there isn't a way to query variables and other php bits and knowledge from drupaldocs, as well as functions. Robin On 12/14/05, Trae McCombs <occy(a)occy.net> wrote: > > too bad I don't know PHP, as it would be nice for me to comprehend these > theme changes you guys are discussing. I think this is the disconnect > we typically have between themers and developers. > > People will carry on a conversation about something and perhaps it'll > seem like a good idea at the time, until someone finally codes it, and > then we go... "huh"? heh > > I'm simply saying to keep us non-hackers in mind while having all these > discussions. > > Thank you, drive through. > Trae > > > Jose A. Reyero wrote: > > Bèr Kessels wrote: > > > > > >>Hi, > >> > >>way too often i have to hack modules or even core (upload) to make it > *not* > >>append HTML to $node->body. > >> > >>I think this practice of appending stuff to the body is very bad, since > it > >>makes it impossible to add thatdata elsewhere, without duplication. > >> > >> > >> > > > > Yep, I agree, same problem here > > > > > >>I think that teh best option is an additional variable in $node > >>$node->extra > >>containing structured data added by all the modules. > >>$node->extra->upload could, for example contain that uplaod/attachement > table, > >>that is now hardcoded to the body. > >> > >> > >> > >> > > > > First I would like to insist in that *all html* produced should be > > themeable. > > > > About this specific issue, I think we could > > a) Just use themeable functions, that can be overridden, like a > > 'theme_upload_node_body' but, anyway, don't store it into node->body, > > but in node->output or similar > > b) Use that $node->extra->upload you propose but maybe better make it an > > array, $node->extra['upload'] so we can use a simple 'implode' at the > > end. Maybe weights could be useful here too > > > > The ideal would be using both, themeable functions that produce > > structured data, but any of them used separately would just fix the > > problem. However, the way to go, thinking big, would be kind of > > 'generalized form API' that could be useful to build any object -page, > > block, node..- as structured data and then render it to HTML. > > > > > >>Waht do others think > >>Bèr > >> > >>PS: Im not to sure about tis crossposting thing, but there are loads of > theme > >>and developers issues; is it safe to assume that interested parties at > least > >>read development? (so that we can keep this on development) > >> > >> > > > > > > -- > Trae "occy" McCombs || http://occy.net/ > Founder - Themes.org // Linux.com > CivicSpaceLabs - http://civicspacelabs.org/ > -- Robin Monks, CSL Web Administrator robin(a)civicspacelabs.org

1 0

proposal for theming nodes
by Bèr Kessels 14 Dec '05

14 Dec '05

Hi, way too often i have to hack modules or even core (upload) to make it *not* append HTML to $node->body. I think this practice of appending stuff to the body is very bad, since it makes it impossible to add thatdata elsewhere, without duplication. I think that teh best option is an additional variable in $node $node->extra containing structured data added by all the modules. $node->extra->upload could, for example contain that uplaod/attachement table, that is now hardcoded to the body. In the very very end, the theme_node will iterate over all these ->extra 's and append them to teh body. Now, the code, the patch, should not be too hard to make, its just a few lines to the theme_node functions The hard part, imho is to convert **all** core modules to use this. and with All i mean all :). Taxononomy, for example, should add its terms in there, while book module should add its navigation. The other thing is, that while this annoys me a huge lot, i just don't have time to get a patch going, untill at least end of Januari. Waht do others think Bèr PS: Im not to sure about tis crossposting thing, but there are loads of theme and developers issues; is it safe to assume that interested parties at least read development? (so that we can keep this on development) -- PGP ber(a)webschuur.com http://www.webschuur.com/sites/webschuur.com/files/ber_webschuur.asc PGP berkessels(a)gmx.net http://www.webschuur.com/sites/webschuur.com/files/ber_gmx.asc

1 0