- Development - lists.drupal.org

update on the theme
by Farsheed 06 Oct '06

06 Oct '06

Hi, The Delicious Zen theme has been updated. Please, let's avoid getting into another long thread about design issues on this list. Posting to the issue queue is probably better: http://drupal.org/node/81217 ----------------------- Update: - only search/login forms are themed, color contrast improved on buttons - should work in 4.7 now (explicitly includes "Markup free clearing" for this purpose. redundant in CVS though...) - mission statement themed - simplified footer - replaced comment icon with homemade generic double arrow icon -cleaned up, organized and commented CSS files a bit better Demo site: http://www.drupalart.org/drupal48 Cross-browser compatibility seems to be very good according to BrowserCam tests and feedback by testers...IE 5.0 may need further testing however, if we care about it. If you have any questions or comments regarding this themes accessibility, xhtml, or W3 validation, please post to the issue queue. I think it is pretty stable now. -Farsheed __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Drupal 4.7.3 + CK-ERP 0.20.1 demo
by C K Wu 06 Oct '06

06 Oct '06

Hi, folks, I have produced a preliminary version of a drupal connector for use within CK-ERP and a demo of CK-ERP 0.20.1 operating within Drupal 4.7.3 is now available (along with other demos) at, http://ck-erp.net/ckerp/sitemgr/sitemgr-site/?page_name=DemoSites Please send your comments and feedbacks to, CK-ERP-en [at] googlegroups.com or CK-ERP-zh_CN [at] googlegroups.com Cheers, CK

1 0

Aggregator to nodes
by Drupal 05 Oct '06

05 Oct '06

The feed_node module at https://svn.bryght.com/dev/browser/feed_node is just a rough sketch... but functionally evolving in the right direction. Since it's existence has now been revealed i will get a cleaner version up later today. d

1 0

4.7 maintenance: Change in policy
by Gerhard Killesreiter 05 Oct '06

05 Oct '06

Hi there, up to fairly recently I have reviewed all patches that were applied to HEAD if they might be needed for 4.7 too. Due to the large number of patches being committed to HEAD that are mostly HEAD specific I won't do this anymore. If you supplied a patch that was applied to HEAD and you think it should be committed to 4.7 as well, please recategorize the patch as "ready to be committed" for the 4.7 version after it was committed to HEAD. If you submit a patch for a bug found in 4.7 and HEAD, please file it against CVS instead of 4.7. This will ensure it gets more attention. Finally, there are a number of pending patches, it would be nice if people could review/ work on them: http://drupal.org/project/issues?projects=3060&states=8,13,14&versions=1069… Cheers, Gerhard

4 4

collectigng i18n use cases, and systems to learn from
by Gabor Hojtsy 05 Oct '06

05 Oct '06

Hello World, It is now official that I am going to attempt to write my diploma about Drupal Internationalization. I have confirmation from my university and my consultant there that I will work on Drupal i18n as my DIY project in this semester (10-17 weeks) and then the semester coming after that, preparing my diploma. To make this diploma worthy, I need to do this *right* (and I also need to be somewhat self-focused, so that I can show that *I* have done significant work in the project, not just showing off with what the community produced). That said, I plan to go through 1.) deep evaluation of how some of the other systems do i18n, 2.) collecting use cases in which Drupal i18n could be used, and abstracting some common stuff out of these 3.) look into how the relevant parts of Drupal are built up (dirty details of parts possibly affected by i18n, without care about how an actual implementation would affect them) 4.) study of previous Drupal i18n efforts, including all modules providing such functionality and previous approaches of them 5.) higher level suggestions about possible implementation strategies 6.) once there is consensus, coordinate implementation of the actual approach Once again, note that since I aim at this being my diploma topic, I need to do it according to the "school book" (which should help the Drupal i18n project be as throuroughly thought out and discussed as possible, but would take more time to get to the actual implementation). Also my need to produce results *myself* does not mean I should not work closely with the community. The above plan has several connections to the community, starting from collecting a list of i18n capable systems to study to getting use cases and discussing implementation strategies. I itend to do this 'in the open', so everyone can see what is going on, and can benefit from the progress. I am also not starting this with a disconnect to existing work done (namely Jose and others contributing to the i18n.module), but since there were a lot of debate around the approach taken there, I would like to take a step back, and provide a solid base for the soon to be core code with actual use cases and existing system comparisions. It could turn out that the current i18n implementation stands still, or it could result in a better implementation. Time will tell. I will have weekly meetings with my consultant at the university, who demands that I show up with some work done, so I'd better start and do what I can :) What you can do to help bring this forward first is to join the i18n group at groups.drupal.org and second to take part in any of the two community feedback requests I have put up. I would like to start with collecting your input in two areas. First if you know of a system which is possible to set up 'at home' (ie. on a usual Windows or Linux server) and you already know of its good i18n capabilities (mostly content translation related features), please tell us about it. Second if you have some use case you already tried to use Drupal i18n in (or any other software with i18n capabilities for that matter), you could provide a use case. Suggest a system: http://groups.drupal.org/node/1544 Provide a use case: http://groups.drupal.org/node/1545 What's i18n? http://groups.drupal.org/node/1543 The i18n group: http://groups.drupal.org/i18n I think it is better to comment on these nodes or add new nodes there in case of use case collection, but if you have anything pressing you need to ask/discuss/say here, just do so. Gabor

4 3

Themes - Trying to do too much in one theme?
by Michelle Cox 05 Oct '06

05 Oct '06

I've been reading these theming threads with much interest and it seems to me that part of the problem is trying to make the default theme work for different kinds of users. With respect to theming, I think we have three main types: 1) The out-of-the-boxer. This user just wants to set up a site and use the theme that's there. Maybe change the colours, but that's it. For this user, a very pretty eye-candy theme is great. Everything should be styled and it should just work with all browsers. 2) The power user that can't theme their way out of a wet paper bag. This user doesn't care a lot what the default theme looks like but wants one that's easy to modify with very little CSS/HTML/PHP knowledge. This theme needs very little markup and should focus heavily on changeability. 3) The theming guru. I don't know what this class wants. Maybe they don't even care what theme comes with Drupal as they always make their own? I think a big problem is that 1 and 2 are at odds with each other. Having a Wow! theme that's easy to change is difficult, maybe impossible. What I think, and this is totally IMO, is that the default theme (and maybe a couple others for variety) are made totally Wow! to address user type 1. Don't worry too much about making these easy to change. Make them work and make them pretty. Maybe put something for changing the colours at the top for a little tweak but, beyond that, expect them to be used as is. To address user type 2's needs, what we really need is a set of wire frames with minimal styling and lots of comments. Take the basic shapes that most websites used (that is, 1 2 or 3 columns, header, footer, stuff like that) and code them really well so the layout holds up to whatever contribs throw at it. Then put in all the various elements that can be styled, but leave them empty or with something fairly neutral. Put lots of comments on them so someone with just a little CSS knowledge can look at it and know what a change there will do. By doing this, the novice CSSer won't have to fight the browser quirk layout issues and all that mess but will be able to easily tweak the theme to look how they want it without having to unstyle a bunch of eye candy. Just my $0.02 US ;) Michelle (type 2)

10 15

Re: [development] new CVS branch/tag conventions (was Re: tagadelic 'backport' for 4.7)
by Chad Phillips -- Apartment Lines 05 Oct '06

05 Oct '06

On Oct 4, 2006, at 4:26 PM, Khalid B wrote: > >> 1) "DRUPAL-4-7--1" and "DRUPAL-4-7--1-0" >> >> 2) "DRUPAL-4-7-V-1" and "DRUPAL-4-7-V-1-0" >> >> 3) "DRUPAL-4-7-R-1" and "DRUPAL-4-7-R-1-0" >> >> 4) "DRUPAL-4-7-REV-1" and "DRUPAL-4-7-REV-1-0" >> >> 5) "DRUPAL-4-7_1" and "DRUPAL-4-7_1-0" (just for comparison, this >> isn't >> a contender) > > I think #4 is the least ambiguous. the -- is the most concise, but > I am afraid > it would not be obvious to new Drupal users, or non-technical users. i second this opinion -- it adds three more characters to the name, but makes it totally obvious to any developer--even those with no drupal experience. +1 to #4 :)

1 0

Any way to get a poll? Drupal 5.0 Default theme.
by Trae McCombs 04 Oct '06

04 Oct '06

It would be nice if we could figure out which way we are currently wanting to go with things. While the theme @ http://themes.net/ isn't finished yet [Waiting to find out if Dries thinks we are on the right track], I would like to find out what people think about the current direction of the two themes: http://istyledthis.nl vs. http://themes.net/ I've posted a poll on themes.net, but I wonder if it would be good to have an "official" poll somewhere. This isn't meant to be a divisive thing, but more to see where people are. I'm sure Steef will post his comments on the state of his theme, so please allow for that feedback. [Steef, If you create an account on themes.net I can give you admin access if there is something you need to post] Currently, the Deliciously Zen theme is only set to work @ a fixed position, but of course the fluid one will be fixed along with other details. Farsheed and I (and others) will work to make sure it's something we can hopefully mostly all be proud of. :) Let the voting begin! -- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com

11 20

Re: [development] Any way to get a poll? Drupal 5.0 Default theme.
by Nathaniel Catchpole 04 Oct '06

04 Oct '06

Jeff Eaton said: >Ultimately, I think we would be better served by settling >on a much-improved base XHTML layout (zen's is MUCH better than any >previous Drupal default) and promote it as a base for pure-css themes by >designers who lacked the programming experince to put together a Drupal >theme from scratch. This is the main thing for me as a non-coder (although I understand CSS and html reasonably well). Bluemarine isn't pretty without any alterations, but I can be pretty certain that it will display output from contributed modules readably and is likely to be upgraded for the next release of Drupal. It doesn't contain any structural images (backgrounds, block corners etc.), so it's easy to swap css colours/spacing around without being concerned about changing those additional elements to see what it'll look like roughly. So with that knowledge, I can: *use it as a base to develop another theme from - i.e. change css and page.tpl.php a bit at a time instead of starting from scratch or spending hours looking through the themes index. *take code from page.tpl.php and styles.css and plug it into other themes if I'm having trouble reproducing, say, primary links displayed inline in the header. In both cases, if there's an upgrade, it's going to be relatively easy to apply any changes to Bluemarine again, or compare the old and new versions to upgrade my own modified version. With this in mind, for any user who's going to do more than just install it and leave it as it is, it makes sense to have a transparent structure clean and clear coding (ideally with code comments in there as well). Then medium-experience spare time admins like me can see what the various elements are making it work and begin to understand how they're related - this can then be applied to contrib. themes or building from scratch later. The javascript rounded corners and/or multiple divs sounded like moves in the opposite direction to that. If there's going to be a move towards more themes in a drupal installation, then it makes sense to have the more "boxed in"/complex ones as options - so someone who just wants to pick a theme and stick with it has easy access to some choices. Also, it does matter what the core theme looks like. The first time I used drupal was when I did a fantastico install alongside another CMS (iirc geeklog, and I'd tried postnuke before that). Drupal.org looks good - some other CMS sites are really ugly. I looked at things in fantastico before I'd ever seen the homepage of a CMS though, and I'd imagine that's the way a lot of people come across them - or at least start using them. You've also got opensourcecms.com where people will be flicking through various options at speed, and will be thinking about usability more than customisation when they know it's not 'their' site and any theme changes will be wiped in a matter of minutes. Regards, Nathaniel Catchpole (catch) -- Confidentiality: This email and its attachments are intended for the addressee only and may be confidential or the subject of legal privilege. If this email and its attachments have come to you in error you must take no action based on them, nor must you copy them, distribute them or show them to anyone. Please contact the sender to notify them of the error. Security: Security Warning: Please note that this e-mail has been created in the knowledge that e-mail is not a 100% secure communications medium. We advise that you understand and observe this lack of security when e-mailing us. Viruses: This email and any attached files have been scanned for the presence of computer viruses. However, you are advised that you open any attachments at your own risk. Please note that electronic mail may be monitored in accordance with the Telecommunications (Lawful Business Practices) (Interception of Communications) Regulations 2000. Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of B6 Sixth Form unless explicitly stated otherwise ----------------------------------------------------------------------- This message has been inspected by DynaComm i:mail -----------------------------------------------------------------------

1 0

Re: [development] Any way to get a poll? Drupal 5.0 Default theme.
by Michelle Cox 04 Oct '06

04 Oct '06

On 10/3/2006 9:39:33 PM, Walt Daniels (wdlists(a)optonline.net) wrote: >The contrib themes are a good start but they need a uniform classification >scheme so one can tell at a glance the basic properties (fixed/fluid), >(css/tables/mixed), n-col, etc. >Perhaps the secret, at least for me, is themes which can be easily >specialized a bit to look unique by someone with a poor graphic eye for >beauty. This means getting all the little things right, like margins, >alignment and especially browser agnostic. This is where I am. I find theming the most difficult part of Drupal. Some day, I'd like to get paid for doing Drupal sites for small businesses in the area. My target market likely won't pay enough for a site for me to be able to subcontract out the theme part. So the easier Drupal can make it for a non graphic designer to come up with a decent looking theme, the better. I realize the truly outstanding themes will always take someone who really knows how to design, but non-designers should at least be able to come up with something usable by changing colours and graphics and not having to worry about all the browser quirks and whatnot. Michelle

1 0