Chad wrote:-
>This may be okay for module developers to work with but I'm certain it'll
>be a turnoff to designers<
Sounds like Chad is considering people like me - I have found Gallery a
wonderul place to start learning to play with the way my galleries look and
work. I don;t have formal computing training, and yet have learned a lot
here.
(My localserver problams seem to be solved do I am getting back to this
again).
I enjoyed the earlier versions of Gallery where there were straightforward
instructions "How to change a theme", easy to follow without a lot of geek
knowledge - easy for Grandma with Windows OS and just a little ftp etc
knowledge to Change the header, general appearance and colours.
To my mind, Gallery does a great service to people like me, giving us an
opportunity to advance our knowledge and feel proud of our achievement.
Thanks Chad and others for keeping us in mind.
Gaynor - (old woman, amateur geek)
----- Original Message -----
From: "Chad Kieffer" <
chad@...>
To: "Bharat Mediratta" <
bharat@...>
Cc: "Gallery Community" <
gallery-devel@...>
Sent: Wednesday, May 27, 2009 5:55 AM
Subject: Re: [Gallery-devel] [G3/Patch] More flexibility with themes
> On May 26, 2009, at 11:14 AM, Bharat Mediratta <
bharat@...>
> wrote:
>
>> Romain LE DISEZ wrote:
>>> My patch was a way to provide inheritance capabilities for the
>>> themes.
>>> But the problem with it is that the themes can only inherit of
>>> "default". Inheritance can be generalized by adding a variable to
>>> theme.info :
>>> parent = <theme name>
>>>
>>> But I'm not sure you are interested with that, so I will not waste
>>> time
>>> on it unless you ask me. My second patch was also about
>>> inheritance...
>>>
>>> So for now, with your patch, I can't create a theme with only :
>>> mytheme/
>>> theme.info
>>> views/
>>> simple_uploader.html.php
>>> (I must copy the default theme and add the file
>>> simple_uploader.html.php)
>>
>> We made a decision early on that we'd try to avoid things like theme
>> inheritance because we were afraid that added complexity here would be
>> difficult to explain to themers. Instead we opted for what I
>> believe to
>> be a more commonplace theming approach: cut and paste. I figure
>> that it
>> is trivial for a themer to just make a new variant of a theme with the
>> one or two changes that they want, and if we make cloning themes
>> really
>> easy then we'll have a proliferation of simpler themes to work with.
>>
>> thoughts?
>
> I still believe this is the right choice and inline with current CMS
> theming systems. I believe copy/paste approach reaches the largest
> segment of themers.
>
> Setting up inheritance complicated themes for end users by adding
> dependencies. This may be okay for module developers to work with but
> I'm certain it'll be a turnoff to designers.
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like
> Barbarian
> Group, R/GA, & Big Spaceship.
http://p.sf.net/sfu/creativitycat-com> __[ g a l l e r y - d e v e l ]_________________________
>
> [ list info/archive -->
http://gallery.sf.net/lists.php ]
> [ gallery info/FAQ/download -->
http://gallery.sf.net ]
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship.
http://p.sf.net/sfu/creativitycat-com
__[ g a l l e r y - d e v e l ]_________________________
[ list info/archive -->
http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download -->
http://gallery.sf.net ]