On 8/15/07, Peter Apokotos <drupal@apokotos.com> wrote:
What is Chipin?

It's been used successfully here: http://groups.drupal.org/node/3484 . You can google chipin to get the information you need.

As for the spec I am not quite sure as to what you mean.  Is it retaining to the theming or the extension?

The spec would be to describe what the extension to Dreamweaver could do.

Cheers,
Kieran
 

On Aug 15, 2007, at 12:10 PM, Kieran Lal wrote:

Peter, my suggestion would be to go with ChipIn as it's a tool that's worked successfully on Groups.drupal.org.

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.

Cheers,
Kieran

On 8/14/07, Peter Apokotos < drupal@apokotos.com> wrote:
If anyone would like to donate to this project please go here <http://
donorge.org/d_donate/basket_add/0/1/1014>


Thank you for your support on making this project a reality.

Peter Apokotos


On Aug 10, 2007, at 9:52 PM, Steven Peck wrote:

> Any theme can make all the others go away.  However, that is really an
> advance theme issue.
>
> By far the vast majority of the Drupal admin population needs the help
> of the included starter css.  As such, those advanced enough merely
> exclude print $styles in their theme and accept they will need to
> build everything from scratch.  The rest of us can leverage the
> existing helper css quite nicely.
>
> Drupal 6 theming takes this much further.
>
> -sp
>
> On 8/10/07, Peter Apokotos < drupal@apokotos.com > wrote:
>> Pre-existing modules? If they have defined divs, classes and so on
>> then you could just adjust or add the settings to your new C.S.S.
>> with your new templates.  Of course I also think that the Drupal.css
>> file should go away and have only one style sheet for the majority of
>> items.  But I would leave the amount of style sheets to each theme
>> developer because not everyone works the same way.  I personally use
>> just one and use shorthand and compress the sheet as much as I can.
>> But I would still like to see all of the module developers use XHTML
>> 1.0 Strict, CSS 2.0 (3.0 possibly) and I won't pick on them only.
>> Drupal needs it too.  Another issue I have is either create a module
>> for the <HEAD>So that I don't have to dig down in the core of Drupal
>> to add or change items</HEAD>  Or just leave the head to be changed
>> independently for each page, article, book, node and so on.
>>
>> Peter
>>
>> On Aug 10, 2007, at 4:04 PM, Farsheed wrote:
>>
>>> How would such an extension deal with pre-existing CSS
>>> and HTML generated by core/other modules?
>>>
>>>
>>> Farsheed
>>>
>>>
>>>
>>>
>>>
>>> --- Peter Apokotos < drupal@apokotos.com> wrote:
>>>
>>>>
>>>> On Aug 10, 2007, at 10:59 AM, sime wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> Since I'm getting value out of reading this
>>>> thread, my conscience
>>>>> says I
>>>>> should mention my current project, even though
>>>> I've only used dw for a
>>>>> sum total of 3 days in my life.
>>>>>
>>>>> I plan to let dw users edit some individual page
>>>> elements with
>>>>> Dreamweaver, individual files for things like
>>>> "blocks", "left
>>>>> sidebar",
>>>>> complete with dummy content. I'm going to mark up
>>>> these files with
>>>>> locked tags. Then another process will do the
>>>> conversion into a real
>>>>> theme using these tags (the designer won't see
>>>> that). The designer
>>>>> will
>>>>> need to follow instructions to make sure things
>>>> are done right (eg.
>>>>> css
>>>>> files are correctly linked etc).
>>>>>
>>>>> It won't be a purist solution, but then again my
>>>> goals are not lofty.
>>>>> Simply allow dw designers to mess with a theme a
>>>> little, and in a
>>>>> controlled way.
>>>>>
>>>>> In the meantime, I'll keep reading this thread :)
>>>>>
>>>>> Simon
>>>>
>>>> One of the key features of this extension would be
>>>> the comments for
>>>> each of the template files.  In the comments you
>>>> would read what php
>>>> functions you can use or what should be used.  Also
>>>> the standard CSS
>>>> things like how to wrap the text around a picture in
>>>> the content.  Or
>>>> how to assign a common photo or icon to distinguish
>>>> what category
>>>> this content falls under.  Like you would find in
>>>> the CMS Geeklog.
>>>> And that is just the beginning.  For example I use
>>>> the Well Rounded
>>>> DW extension.  Why?  Is it because I am too
>>>> lazy...no it's because
>>>> there is a tool that is drag and drop and saves me
>>>> time.
>>>>
>>>> Peter
>>>> _______________________________________________
>>>> themes mailing list
>>>> themes@drupal.org
>>>> http://lists.drupal.org/mailman/listinfo/themes
>>>>
>>>
>>>
>>>
>>>
>>> ____________________________________________________________________
>>> __
>>> ______________Ready for the edge of your seat?
>>> Check out tonight's top picks on Yahoo! TV.
>>> http://tv.yahoo.com/
>>> _______________________________________________
>>> themes mailing list
>>> themes@drupal.org
>>> http://lists.drupal.org/mailman/listinfo/themes
>>
>> _______________________________________________
>> themes mailing list
>> themes@drupal.org
>> http://lists.drupal.org/mailman/listinfo/themes
>>
> _______________________________________________
> themes mailing list
> themes@drupal.org
> http://lists.drupal.org/mailman/listinfo/themes

_______________________________________________
themes mailing list
themes@drupal.org
http://lists.drupal.org/mailman/listinfo/themes



--
To strive, to seek, to find, and not to yield.
_______________________________________________
themes mailing list


_______________________________________________
themes mailing list
themes@drupal.org
http://lists.drupal.org/mailman/listinfo/themes




--
To strive, to seek, to find, and not to yield.