<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">What is Chipin?<DIV><BR class="khtml-block-placeholder"></DIV><DIV>As for the spec I am not quite sure as to what you mean. Is it retaining to the theming or the extension?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR><DIV><DIV>On Aug 15, 2007, at 12:10 PM, Kieran Lal wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">Peter, my suggestion would be to go with ChipIn as it's a tool that's worked successfully on <A href="http://Groups.drupal.org">Groups.drupal.org</A>.<BR><BR>Also, I think we need to do more work on spec so people know what the would be supporting and we need to get more feedback on a spec that people would be willing to pay for it. <BR><BR>Cheers,<BR>Kieran<BR><BR><DIV><SPAN class="gmail_quote">On 8/14/07, <B class="gmail_sendername">Peter Apokotos</B> <<A href="mailto:drupal@apokotos.com">drupal@apokotos.com</A>> wrote:</SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> If anyone would like to donate to this project please go here <http://<BR><A href="http://donorge.org/d_donate/basket_add/0/1/1014">donorge.org/d_donate/basket_add/0/1/1014</A>><BR><BR><BR>Thank you for your support on making this project a reality. <BR><BR>Peter Apokotos<BR><BR><BR>On Aug 10, 2007, at 9:52 PM, Steven Peck wrote:<BR><BR>> Any theme can make all the others go away. However, that is really an<BR>> advance theme issue.<BR>><BR>> By far the vast majority of the Drupal admin population needs the help <BR>> of the included starter css. As such, those advanced enough merely<BR>> exclude print $styles in their theme and accept they will need to<BR>> build everything from scratch. The rest of us can leverage the <BR>> existing helper css quite nicely.<BR>><BR>> Drupal 6 theming takes this much further.<BR>><BR>> -sp<BR>><BR>> On 8/10/07, Peter Apokotos <<A href="mailto:drupal@apokotos.com">drupal@apokotos.com </A>> wrote:<BR>>> Pre-existing modules? If they have defined divs, classes and so on<BR>>> then you could just adjust or add the settings to your new C.S.S.<BR>>> with your new templates. Of course I also think that the Drupal.css<BR>>> file should go away and have only one style sheet for the majority of<BR>>> items. But I would leave the amount of style sheets to each theme<BR>>> developer because not everyone works the same way. I personally use <BR>>> just one and use shorthand and compress the sheet as much as I can.<BR>>> But I would still like to see all of the module developers use XHTML<BR>>> 1.0 Strict, CSS 2.0 (3.0 possibly) and I won't pick on them only. <BR>>> Drupal needs it too. Another issue I have is either create a module<BR>>> for the <HEAD>So that I don't have to dig down in the core of Drupal<BR>>> to add or change items</HEAD> Or just leave the head to be changed <BR>>> independently for each page, article, book, node and so on.<BR>>><BR>>> Peter<BR>>><BR>>> On Aug 10, 2007, at 4:04 PM, Farsheed wrote:<BR>>><BR>>>> How would such an extension deal with pre-existing CSS <BR>>>> and HTML generated by core/other modules?<BR>>>><BR>>>><BR>>>> Farsheed<BR>>>><BR>>>><BR>>>><BR>>>><BR>>>><BR>>>> --- Peter Apokotos < <A href="mailto:drupal@apokotos.com">drupal@apokotos.com</A>> wrote:<BR>>>><BR>>>>><BR>>>>> On Aug 10, 2007, at 10:59 AM, sime wrote:<BR>>>>><BR>>>>>> Hi<BR>>>>>> <BR>>>>>> Since I'm getting value out of reading this<BR>>>>> thread, my conscience<BR>>>>>> says I<BR>>>>>> should mention my current project, even though<BR>>>>> I've only used dw for a <BR>>>>>> sum total of 3 days in my life.<BR>>>>>><BR>>>>>> I plan to let dw users edit some individual page<BR>>>>> elements with<BR>>>>>> Dreamweaver, individual files for things like <BR>>>>> "blocks", "left<BR>>>>>> sidebar",<BR>>>>>> complete with dummy content. I'm going to mark up<BR>>>>> these files with<BR>>>>>> locked tags. Then another process will do the <BR>>>>> conversion into a real<BR>>>>>> theme using these tags (the designer won't see<BR>>>>> that). The designer<BR>>>>>> will<BR>>>>>> need to follow instructions to make sure things <BR>>>>> are done right (eg.<BR>>>>>> css<BR>>>>>> files are correctly linked etc).<BR>>>>>><BR>>>>>> It won't be a purist solution, but then again my <BR>>>>> goals are not lofty.<BR>>>>>> Simply allow dw designers to mess with a theme a<BR>>>>> little, and in a<BR>>>>>> controlled way.<BR>>>>>><BR>>>>>> In the meantime, I'll keep reading this thread :) <BR>>>>>><BR>>>>>> Simon<BR>>>>><BR>>>>> One of the key features of this extension would be<BR>>>>> the comments for<BR>>>>> each of the template files. In the comments you <BR>>>>> would read what php<BR>>>>> functions you can use or what should be used. Also<BR>>>>> the standard CSS<BR>>>>> things like how to wrap the text around a picture in <BR>>>>> the content. Or<BR>>>>> how to assign a common photo or icon to distinguish<BR>>>>> what category<BR>>>>> this content falls under. Like you would find in<BR>>>>> the CMS Geeklog. <BR>>>>> And that is just the beginning. For example I use<BR>>>>> the Well Rounded<BR>>>>> DW extension. Why? Is it because I am too<BR>>>>> lazy...no it's because<BR> >>>> there is a tool that is drag and drop and saves me<BR>>>>> time.<BR>>>>><BR>>>>> Peter<BR>>>>> _______________________________________________<BR>>>>> themes mailing list <BR>>>>> <A href="mailto:themes@drupal.org">themes@drupal.org</A><BR>>>>> <A href="http://lists.drupal.org/mailman/listinfo/themes">http://lists.drupal.org/mailman/listinfo/themes</A><BR>>>>> <BR>>>><BR>>>><BR>>>><BR>>>><BR>>>> ____________________________________________________________________<BR>>>> __<BR>>>> ______________Ready for the edge of your seat? <BR>>>> Check out tonight's top picks on Yahoo! TV.<BR>>>> <A href="http://tv.yahoo.com/">http://tv.yahoo.com/</A><BR>>>> _______________________________________________<BR>>>> themes mailing list <BR>>>> <A href="mailto:themes@drupal.org">themes@drupal.org</A><BR>>>> <A href="http://lists.drupal.org/mailman/listinfo/themes">http://lists.drupal.org/mailman/listinfo/themes</A><BR>>><BR>>> _______________________________________________ <BR>>> themes mailing list<BR>>> <A href="mailto:themes@drupal.org">themes@drupal.org</A><BR>>> <A href="http://lists.drupal.org/mailman/listinfo/themes">http://lists.drupal.org/mailman/listinfo/themes</A> <BR>>><BR>> _______________________________________________<BR>> themes mailing list<BR>> <A href="mailto:themes@drupal.org">themes@drupal.org</A><BR>> <A href="http://lists.drupal.org/mailman/listinfo/themes"> http://lists.drupal.org/mailman/listinfo/themes</A><BR><BR>_______________________________________________<BR>themes mailing list<BR><A href="mailto:themes@drupal.org">themes@drupal.org</A><BR><A href="http://lists.drupal.org/mailman/listinfo/themes"> http://lists.drupal.org/mailman/listinfo/themes</A><BR></BLOCKQUOTE></DIV><BR><BR clear="all"><BR>-- <BR>To strive, to seek, to find, and not to yield.<BR><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">themes mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:themes@drupal.org">themes@drupal.org</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="http://lists.drupal.org/mailman/listinfo/themes">http://lists.drupal.org/mailman/listinfo/themes</A></DIV> </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>