We have structured our development in the same manner. However now that we are on a second(design) iteration the web designers are complaining that it is time consuming to have to run through the complete work flow in order to view small changes to the UI.
I am not sure if I should design the business logic to support default values in a "design mode" so that the designers could view the pages directly with default beans loaded into some scope. This would be time consuming as every Action would have to support this "design mode". Right now for testing I simply populate the database with default values but you still have to follow the work flow in order to view pages. I am thinking that I will compromise and allow direct access points strategically throughout the app. I don't have the time to do this right now so my current response to design is to bear with me. What do others do to relieve this conflict? Any help much appreciated, Greg -----Original Message----- From: Melissa L Kelley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 4:12 PM To: Struts Users Mailing List Subject: RE: uncoupling Web Design/Web Development On Mon, 29 Jul 2002, Jacob Hookom wrote: Well, this may not be of any help if you are in the middle of development, but I take the approach that after the business requirements have been gathered, the designers go in one corner to work on the interface and the developers go in another to work on the technical design. Then designers can create html prototypes which can be used to get the look and feel down and approved by the business client/end users, and the developers can work on the business objects. Then you can get together and tie it together using Struts. It has worked well for me so far. By the time I get back with the person/people doing the interface, most of that has been flushed out so the designers' main job is taking their prototypes and converting them to the view compenent using the appropriate tags, and any changes to the design of the pages are small. --> stu: www.stuology.net It just no longer is plain simple safe fun when it's the psycho chimp that has the ray gun ------------------------------------------------ Stuology -- A million monkeys can't be wrong > -----Original Message----- > From: Michael Delamere [mailto:[EMAIL PROTECTED]] > 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" <[EMAIL PROTECTED]> > To: "Struts Mail List" <[EMAIL PROTECTED]> > 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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
