RE: greetings...

I think a lot good points have been brought up about the issue of
separation of content and who controls what...

My 2 cents... Let the module/block developer build the default layout...
The theme developer (site owner) can override that layout if need be....
I think both zoom and Josh agree on using templates... It's a simple
matter of who overrides who.. Mod devs or theme devs    

In 80% of the situations I think the default (module dev layout) will be
used.   BUT give the theme author the chance to change things and make
the module stand out from the crowd if they want to... 

Now, taking that approach does make the template a bit more complex for
the theme developer to deal with... But with flexibility sometimes comes
complexity.


Furbo

With great power comes great responsibility.... 




-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Scott Kindley
Sent: Tuesday, September 10, 2002 4:30 AM
To: Envol-dev
Subject: Re: [envdev] greetings...


On Tue, 2002-09-10 at 02:46, josh wrote:
> > 
> > Instead I personally think the theme/skin designers should handle 
> > the look and layout based on the theme engine and let the block or 
> > module developer concentrate on providing it's respective functions 
> > or service. But that's just my opinion.
> > 
> 
> I think the theme developer should provide a default look and feel 
> that the module can inherit, but the module developer should have the 
> option and capability to override it.  And as far as layout goes, 
> maybe we're talking about two different things.  Say I develop a 
> module that allows users to add and view events...Well to add, there 
> needs to be a form and when viewing, I want the event listing content 
> to be formatted a particular way.  The theme developer doesn't know 
> how those things should be formatted, you follow?  So it makes sense 
> for me to have a module-level template for inclusion to describe what 
> that layout should look like.  Of course, the same goes for blocks.  
> Now if I'm missing something, please be so kind as to educate me.
> 

This is where I think we disagree. The look and layout is left to the
website owner not the block or module developer. So by utilizing the
theme engine and it's templates the website owner controls what the
layout and look is.

Following that basic premise I see no way you can allow a block or
module developer to exercise control over the layout and look of any
website. Templates or otherwise. For example a block is a block and a
module is a module..they both offer a function to your website. 

The theme/skin and theme engine offer the look, layout and feel of the
website. So on a more basic level the block/modules deliver content
while the theme/skin and theme engine control the presentation. This is
a separation of content and presentation that has to exist regardless of
the theme engine one ultimately decides to use.

> 
> > I believe I saw your post to the pn-dev list and I think it was 
> > responded to that current PN peolpe are dropping BL in favor of a 
> > different template driven theme engine called FastTemplates.
> 
> More vaporware, eh?
> 

No this time I think FastTemplates is a real entity.

> > 
> > Yes. They have been established and the docs are available here:
> > 
> > http://www.envolution.com/modules.php?op=modload&name=Sections&file=
> > index&req=listarticles&secid=5
> > 
> 
> sweet.  i'll check out those documents and provide you with hopefully 
> relevant and useful feedback.
> 
Enjoy!

Zoom


_______________________________________________
Envdev mailing list
[email protected]
http://www.madhatt.info/mailman/listinfo/envdev_madhatt.info