Just my kind of solution,  short & simple but very smart !
Thanks for the link i had missed this post.

Eelco Hillenius wrote:
Also, check out what Ryan did, which is now integrated into Wicket:
http://jroller.com/page/wireframe?entry=preview_multiple_levels_of_components

Eelco

On 3/26/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
  
Wicket has markup inheritance and borders for layout/ templating and
<wicket:remove> for putting in dummy content so that you can design a
page as if it were complete with the templates etc.

Eelco


On 3/26/06, tcolar <[EMAIL PROTECTED]> wrote:
    
With JSF there are layouts, and that is helping a bit, so yes we have
footer, headers etc... and we try to keep those separated as much as
possible of course.
Those rearely change anyway, the main content is what changes the most.
On the other hand the layout thing as a big drawbak, the designer  will
only see the piece of html he is actually working on, say "footer", now
often the "header" contains the stylesheet call .... so he will see a
footer without style all by itself.

I don't know that there is a perfect solution to this, but the least
code there is in the html the better it works, so wicket is best for me.

Thomas Singer wrote:

      
then i just give them that back and they can use it to do all the pages
(though of course with JSF, JSP mess it's barely even doable to have
reusable templates IMO)
          
Shouldn't the web-application framework provide a mechanism for the
templates? What about the idea to have the "page general look" (e.g.
page header, navigation) in just *one file* (clean HTML, because
designed by the designer), where the content is in the other markup
files (clean HTML, because designed by the designer)?

--
Best regards,
Thomas Singer


tcolar schrieb:

        
The typical designer is unable to produce even valid HTML, let alone
            
good HTML >with proper CSS. Well designer typically use Dreamweaver or
such. So if the HTML/CSS is not good, blame that on on Micromedia I
usually get the designer to do an "initial template" in DW, and then
i "fix it", cleaning the html and CSS, and making the layout
"logical", then i just give them that back and they can use it to do
all the pages (though of course with JSF, JSP mess it's barely even
doable to have reusable templates IMO)

          
This is what is going wrong in your company. You shouldn't let the
            
average >designer produce HTML. Have them produce their screens in
Photoshop, and let a >technical person build the HTML. Well, we endup
having to do that because of JSF, but that is not a good process,
besides
converting from photoshop to HTML/CSS in a a text editor, is very
tedious. My main concern though here is not so much for the initial site
 development, but for the ongoing miantenance. The cotent maintenance
(text/images/layout) should preferably be possible to do just by
marketing/design people without involving developers. for one developers
can't speak marketing and vice-versa so it's wasting time, and i think
it's waste of resources having developers do this. But fact is with JSF,
develoers have to be called for even the most basic content layout
changes since the designer just can't work with that JSP mess.

          
The other thing that is going wrong is that you are using JSF ;)
            
true :-) , it is was up to me .....

Timo Stamm wrote:

          
tcolar schrieb:

            
That one kills me:

              
Patrick (WebWork): "I've found that "HTML/CSS developers" and "app
developers" rarely
                
are >separated

              
like Tapestry likes to pretend they are"
                
I could not disgree more with that, only geeks working on their ugly
 homepage say this.
              

I agree with it, and while I am not sure whether I am a geek, I
don't even have a homepage.

I think there is a misunderstanding. Patrick doesn't claim that
/design/ and app development are done by one person. He claims that
HTML/CSS and app development are done by one person.

The typical designer is unable to produce even valid HTML, let alone
good HTML with proper CSS.

This is what is going wrong in your company. You shouldn't let the
average designer produce HTML. Have them produce their screens in
Photoshop, and let a technical person build the HTML.

The other thing that is going wrong is that you are using JSF ;)


Timo


------------------------------------------------------- This SF.Net
email is sponsored by xPML, a groundbreaking scripting language that
extends applications into web and mobile media. Attend the live webcast
 and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

 _______________________________________________ Wicket-user mailing
list Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
            



------------------------------------------------------- This SF.Net
email
is sponsored by xPML, a groundbreaking scripting language that extends
applications into web and mobile media. Attend the live webcast and join
the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________ Wicket-user mailing
list Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

          
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
        


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

      


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
  

Reply via email to