struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Delamere" <h...@michael-delamere.de>
Subject Re: uncoupling Web Design/Web Development
Date Mon, 29 Jul 2002 21:09:08 GMT
I agree entirely!  There are many advantages of doing it the way you are.
For us however it would be a big step and the time certainly isnĀ“t there!

Then again, currently there is no need for us to generate so many differnet
types of views at present.
WAP and WEB at the most....

Michael

----- Original Message -----
From: "Jacob Hookom" <hookomjj@uwec.edu>
To: "'Struts Users Mailing List'" <struts-user@jakarta.apache.org>
Sent: Monday, July 29, 2002 10:56 PM
Subject: RE: uncoupling Web Design/Web Development


> Basically, it was a strict requirement of the system, and this MVC2 is
> not implemented throughout the site in this manner, primarily for
> reporting features.
>
> Do the math, either generate 40 jsps that spit out HTML, then another 40
> for WML, then another 40 for PDF (120 JSPs), or just have a single set
> of 40 JSPs that output XML and then 3 stylesheets.  It really depends on
> the application and how strict the design templates are across your
> pages.  It may not be the best idea if for each XML JSP, you need to
> generate a set of 3 stylesheets.
>
> In addition, we are using the code I wrote that uses XSLTC to compile
> the XSL documents for faster transformation which makes this structure a
> lot more viable.  You might want to look at cocoon as a much larger
> basis of this MVC2 pattern that has its own optimizations.
>
> Jacob Hookom
> Comprehensive Computer Science
> University of Wisconsin, Eau Claire
>
>
> -----Original Message-----
> From: Michael Delamere [mailto:home@michael-delamere.de]
> Sent: Monday, July 29, 2002 3:42 PM
> To: Struts Users Mailing List
> Subject: Re: uncoupling Web Design/Web Development
>
> I really like your idea but how long did it take for everyone involved
> to
> adapt to this approach?
> Surely it must take some time until efficiency comes back into the flow
> of
> things.  Then again, I suppose when it does, everything becomes much
> easier.
>
> Regards,
>
> Michael
>
>
> ----- Original Message -----
> From: "Jacob Hookom" <hookomjj@uwec.edu>
> To: "'Struts Users Mailing List'" <struts-user@jakarta.apache.org>
> Sent: Monday, July 29, 2002 10:33 PM
> Subject: RE: uncoupling Web Design/Web Development
>
>
> > I am working on a big project for an insurance company and we are
> doing
> > everything in XML/XSLT.  That way, the programmers can write JSP's or
> > Servlets that just generate XML data and then depending on who's
> making
> > the request, it formats the page as WML, PDF, or HTML.  That way the
> > designers can just come up with stylesheets and the programmers just
> > generate straight XML data.
> >
> > Jacob Hookom
> > Comprehensive Computer Science
> > University of Wisconsin, Eau Claire
> >
> >
> > -----Original Message-----
> > From: Michael Delamere [mailto:home@michael-delamere.de]
> > Sent: Monday, July 29, 2002 1:23 PM
> > To: Struts Users Mailing List
> > Subject: Re: uncoupling Web Design/Web Development
> >
> > This may not be ideal but the way we do it is that the designers give
> us
> > their static content (html pages) and we feed it into the
> jsps/velocity
> > templates.
> >
> > That way we have more control over the dynamic elements in the webpage
> > and
> > they can play and fiddle with their html code as much as they like
> :-).
> >
> > Regards Michael
> >
> >
> > ----- Original Message -----
> > From: "Greg Hess" <ghess@wrappedapps.com>
> > To: "Struts Mail List" <struts-user@jakarta.apache.org>
> > Sent: Monday, July 29, 2002 8:10 PM
> > Subject: uncoupling Web Design/Web Development
> >
> >
> > > Hi All,
> > >
> > > I have designed a web application that is dependant on a work flow,
> > the
> > user
> > > interface is constructed by Web Designers and the server side is
> done
> > by
> > Web
> > > Developers. The web designers are now comfortable using the struts
> > tags
> > and
> > > so on but they hate the fact that they have to follow the work flow
> in
> > order
> > > to see changes on a specific page. They would like to be able to
> view
> > a
> > page
> > > directly, out side the work flow in order to perform the web design.
> > >
> > > I am not sure how I should facilitate this or if I should?
> > >
> > > Any comments/suggestions would be greatly appreciated.
> > >
> > > Thanks,
> > >
> > > Greg
> > >
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:struts-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:struts-user-help@jakarta.apache.org>
> >
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.380 / Virus Database: 213 - Release Date: 7/24/2002
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.380 / Virus Database: 213 - Release Date: 7/24/2002
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:struts-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> <mailto:struts-user-help@jakarta.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail:
> <mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:struts-user-help@jakarta.apache.org>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.380 / Virus Database: 213 - Release Date: 7/24/2002
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.380 / Virus Database: 213 - Release Date: 7/24/2002
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@jakarta.apache.org>


Mime
View raw message