Re: [Tikiwiki-devel] [Tikiwiki-cvs/svn] SF.net SVN: tikiwiki:[18545] branches/3.0/templates/styles/strasa/ tiki-view_blog.tpl

[Gary Cunningham-L. <ga...@cu...>]

It wasn't a casual decision for Strasa to have its own 
tiki-view_blog.tpl. I made that choice because Patrick was given the 
freedom (or was demanded? ;-) ) to come up with cool designs, and the 
result doesn't necessarily fall easily into existing templates. 
(Coelesce also has this character, and potential problems.) In the 
Strasa blog page, the order of divs for author, post title, and post 
content is changed from the default. When I first saw the design (and 
what became Coelesce) I thought this is really nice but it's quite a bit 
different from how post layout has been. Is it possible to do this with 
the default files?

As Nyloth said, it'd be good to not have theme-specific template 
variants and just use CSS to position things, but in my experience this 
can be hard to do in a way that works across all browsers. I'm all for 
getting rid of these extra templates, but if it was a matter of simply 
"merging" them back to the main templates, they wouldn't have been 
needed in the first place. Of course I may have missed a trick when 
trying to push and pull the Strasa blog design into the default 
template, or may have learned something since then, so maybe it's 
possible after all.

Bugs in the Strasa blog template were probably introduced when I 
modified the default file, so a lot of trouble would have been saved if 
it was bugfree from then. But the file has been used since the beginning 
of the Strasa theme in February and didn't seem to cause a problem until 
recently, which is interesting.

The Strasa template files haven't actually been touched much, but as for 
CSS, changes made in Strasa (or any particular theme) that could benefit 
other themes show the importance of layout.css, I think, since if the 
work isn't theme-specific, if the modification is made to the underlying 
imported stylesheet it will directly impact all themes that use it, so 
this is something to keep in mind for future theme improvements.

-- Gary

ma...@gm... wrote:
> +1
>
> But dont stop now luci and Gary - lets just merge the work in strassa  
> back in to the master template files after you are happy with strassa.
>
> I really appreciate the huge number of hours that Garry and Luci are  
> putting in to the strassa template.
>
> It is true - lots of good things are happening in the strassa  
> templates which we should move to a place where all themes will  
> benefit. So we can avoid having only one template that works 100% in 3.0
>
> Still I vote to have strassa working well, as soon as possible do the  
> merge latter.
>
> Matthew
> PS Hope this did not come across as negative I think the merge back is  
> important but I think for now we should get strassa working any way we  
> can. Let luci and garry have a break and then merge the fork.
>
> On 7 May 2009, at 18:07, WEBER Patrice wrote:
>
>> Hi all,
>>
>> My mail is mainly directed to luci & chibaguy ;)
>>
>> First of all, thanx for your huge work to make beautiful themes (css &
>> templates). I'm really happy to see tiki good progress in terms of
>> themes and I know that's not an easy job :)
>>
>> But, as someone who also work often on templates, I am embarassed by  
>> the
>> templates forked in some themes. I would like to have no template fork
>> for main/bundled themes, because:
>>  * it is extra work to change the main template and then other forked
>> templates,
>>  * it happens quite often that some modifications are only done on  
>> main
>> templates, so some fixes or new functionnalities are not available or
>> even not working on those themes because theme template and main
>> template are not in sync anymore
>>
>> So, my wish would be to remove theme templates as much as possible.
>>
>> Could we discuss about this ? What is the reason of forking templates
>> for main themes ?
>>
>> In my opinion, as we are producing the main code, we should be able to
>> do everything we want with css in most of cases, and by aadding some
>> options in some special cases.
>>
>> Maybe I'm wrong, so I prefer to ask in order to known if there is a
>> really good reason to keep forked themes.
>> If there really is some things that are not possible with just css,  
>> and
>> you don't know how to do with options, we can discuss and I'm ok to
>> help.
>>
>> Cheers,
>> Nyloth.
>>
>> -----Original Message-----
>
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Tikiwiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.325 / Virus Database: 270.12.21/2103 - Release Date: 05/07/09 18:05:00
>