Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: domain of ap-cocoon-users@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: users@cocoon.apache.org
From: "Ilja Smoli" <ilja@frontdesk.ee>
Subject: Re: separation of roles
Date: Wed, 16 Feb 2005 15:17:52 +0200
Lines: 72
Message-ID: <cuvgef$7bd$1@sea.gmane.org>
References: <cuv2id$ok$1@sea.gmane.org> <cuv6pu$bsf$1@sea.gmane.org>
 <cuv7pc$eg6$1@sea.gmane.org> <cuv8s1$he1$1@sea.gmane.org>
 <cuv9n4$k0j$1@sea.gmane.org>
 <286c0cac2e8c422752d299047d259fe6@robinwyles.com>
Sender: news <news@sea.gmane.org>

Thx for reply..
Problem is that only designers know where must be located all stuff like:
menu, this image, that image, logo, table..etc..
So where is this flexibility?
For eg. using struts: designers can write jsps and use tags (jstl, struts.
yee yee they will have to learn it), while developers provide them with
objects in request ...
So in cocoon designers have to learn xslt... Where is advantage of cocoon in
this aspect?


"Robin Wyles" <rob@robinwyles.com> wrote in message
news:286c0cac2e8c422752d299047d259fe6@robinwyles.com...
> Hi...
>
> Would it not be possible (or desirable!) for you, the developers, to
> write the XSLT which outputs properly structured XHTML pages with
> meaningful ID's, class attributes etc. Then the designers should be
> able to style the pages with CSS alone, right?
>
> You can give them your transformed XHTML for each pipeline and then say
> - here you go style that with CSS!
>
> I am actually an ex designer turned developer and this is how I tend to
> do things. I find that there is little that can't be achieved design
> wise using CSS with properly structured XHTML. The current app I am
> working on has a skinning system (it delivers pages of similar
> structure for different clients), and each client skin comprises of
> only images and CSS files.
>
> Robin
>
>
> On 16 Feb 2005, at 12:23, Ilja Smoli wrote:
>
> > Thats I was talkin about!!
> > There is no designers who know XSLT... So again developers writing
> > <tr> <td>
> > .... :-(
> > Where is separation.....? auuu...
> >
> > "Jorg Heymans" <jh@domek.be> wrote in message
> > news:cuv8s1$he1$1@sea.gmane.org...
> >>
> >>
> >> Ilja Smoli wrote:
> >>> Hm...
> >>> Then this xml must be transformed to nice html and this must be done
> >>> by
> >>> designers (throught XSLT)...
> >> s/must be/can be/
> >>
> >>> So actually developers have nothing to do? :-) Except some CForms
> >>> definitions and sitemap managing?
> >>> Oh maybe a little bit of flow script for CForms...
> >> well if your website is mainly displaying information without complex
> >> wizards or flows than the developers could an easy day yes. Mind you i
> >> have not met a lot of designers that felt comfortable with xslt, so
> >> there might well be overlap sometimes.
> >>
> >>
> >> Jorg
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org