You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Marek Šabo <ms...@buk.cvut.cz> on 2010/01/15 17:00:46 UTC
Templates in Wicket
Hi everyone,
I would like to know if someone can share their experience with
graphical templates under wicket. It's easy to provide markup code for
designers, they just need to preserve hierarchy of wicket elements,
right? But how do you cope with things like attribute modifier inside
application and dynamic loading of other css files? Or what is the most
common approach to this kind of thing?
Regards,
Marek
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Templates in Wicket
Posted by Igor Vaynberg <ig...@gmail.com>.
thats what html comments are for.
-igor
On Fri, Jan 15, 2010 at 9:55 AM, Douglas Ferguson
<do...@douglasferguson.us> wrote:
> That's what we are doing as well.
>
> The big gotcha is when you end up doing something in code, it throws them off.
>
> I.E. SimpleAttributeModifier,
>
> D/
>
> On Jan 15, 2010, at 10:14 AM, Jonathan Locke wrote:
>
>>
>>
>> we did almost exactly the same thing at thoof. although occasionally you'll
>> get a designer stuck on a build problem or something, it works really well.
>> definitely the best approach in my mind.
>>
>>
>> igor.vaynberg wrote:
>>>
>>> so you are giving designers markup from a wicket app? why not just let
>>> them run the app, that way they can go in and do things themselves?
>>>
>>> in my company out developers checkout the code and run mvn jetty to
>>> get the app up and running with markup reloading, then they go in with
>>> textmate or coda and tweak the markup.
>>>
>>> -igor
>>>
>>> On Fri, Jan 15, 2010 at 8:00 AM, Marek Šabo <ms...@buk.cvut.cz> wrote:
>>>> Hi everyone,
>>>>
>>>> I would like to know if someone can share their experience with graphical
>>>> templates under wicket. It's easy to provide markup code for designers,
>>>> they
>>>> just need to preserve hierarchy of wicket elements, right? But how do you
>>>> cope with things like attribute modifier inside application and dynamic
>>>> loading of other css files? Or what is the most common approach to this
>>>> kind
>>>> of thing?
>>>>
>>>> Regards,
>>>>
>>>> Marek
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://old.nabble.com/Templates-in-Wicket-tp27179274p27179469.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Templates in Wicket
Posted by Marek Šabo <ms...@buk.cvut.cz>.
Yep, thank you all for sharing your insights, anyway, most of the time I
work with single ui projects. I was just curious how you guys do it so I
would have PreparedStatement for pointy haired bosses :)
On 01/15/2010 06:55 PM, Douglas Ferguson wrote:
> That's what we are doing as well.
>
> The big gotcha is when you end up doing something in code, it throws them off.
>
> I.E. SimpleAttributeModifier,
>
> D/
>
> On Jan 15, 2010, at 10:14 AM, Jonathan Locke wrote:
>
>
>>
>> we did almost exactly the same thing at thoof. although occasionally you'll
>> get a designer stuck on a build problem or something, it works really well.
>> definitely the best approach in my mind.
>>
>>
>> igor.vaynberg wrote:
>>
>>> so you are giving designers markup from a wicket app? why not just let
>>> them run the app, that way they can go in and do things themselves?
>>>
>>> in my company out developers checkout the code and run mvn jetty to
>>> get the app up and running with markup reloading, then they go in with
>>> textmate or coda and tweak the markup.
>>>
>>> -igor
>>>
>>> On Fri, Jan 15, 2010 at 8:00 AM, Marek Šabo <ms...@buk.cvut.cz> wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> I would like to know if someone can share their experience with graphical
>>>> templates under wicket. It's easy to provide markup code for designers,
>>>> they
>>>> just need to preserve hierarchy of wicket elements, right? But how do you
>>>> cope with things like attribute modifier inside application and dynamic
>>>> loading of other css files? Or what is the most common approach to this
>>>> kind
>>>> of thing?
>>>>
>>>> Regards,
>>>>
>>>> Marek
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>>>
>> --
>> View this message in context: http://old.nabble.com/Templates-in-Wicket-tp27179274p27179469.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
Marek Šabo
Server Manager
Club SU CVUT Buben
Bubenečská Kolej (421)
XMPP: zeratul021@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Templates in Wicket
Posted by Douglas Ferguson <do...@douglasferguson.us>.
That's what we are doing as well.
The big gotcha is when you end up doing something in code, it throws them off.
I.E. SimpleAttributeModifier,
D/
On Jan 15, 2010, at 10:14 AM, Jonathan Locke wrote:
>
>
> we did almost exactly the same thing at thoof. although occasionally you'll
> get a designer stuck on a build problem or something, it works really well.
> definitely the best approach in my mind.
>
>
> igor.vaynberg wrote:
>>
>> so you are giving designers markup from a wicket app? why not just let
>> them run the app, that way they can go in and do things themselves?
>>
>> in my company out developers checkout the code and run mvn jetty to
>> get the app up and running with markup reloading, then they go in with
>> textmate or coda and tweak the markup.
>>
>> -igor
>>
>> On Fri, Jan 15, 2010 at 8:00 AM, Marek Šabo <ms...@buk.cvut.cz> wrote:
>>> Hi everyone,
>>>
>>> I would like to know if someone can share their experience with graphical
>>> templates under wicket. It's easy to provide markup code for designers,
>>> they
>>> just need to preserve hierarchy of wicket elements, right? But how do you
>>> cope with things like attribute modifier inside application and dynamic
>>> loading of other css files? Or what is the most common approach to this
>>> kind
>>> of thing?
>>>
>>> Regards,
>>>
>>> Marek
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Templates-in-Wicket-tp27179274p27179469.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Templates in Wicket
Posted by Jonathan Locke <jo...@gmail.com>.
we did almost exactly the same thing at thoof. although occasionally you'll
get a designer stuck on a build problem or something, it works really well.
definitely the best approach in my mind.
igor.vaynberg wrote:
>
> so you are giving designers markup from a wicket app? why not just let
> them run the app, that way they can go in and do things themselves?
>
> in my company out developers checkout the code and run mvn jetty to
> get the app up and running with markup reloading, then they go in with
> textmate or coda and tweak the markup.
>
> -igor
>
> On Fri, Jan 15, 2010 at 8:00 AM, Marek Šabo <ms...@buk.cvut.cz> wrote:
>> Hi everyone,
>>
>> I would like to know if someone can share their experience with graphical
>> templates under wicket. It's easy to provide markup code for designers,
>> they
>> just need to preserve hierarchy of wicket elements, right? But how do you
>> cope with things like attribute modifier inside application and dynamic
>> loading of other css files? Or what is the most common approach to this
>> kind
>> of thing?
>>
>> Regards,
>>
>> Marek
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/Templates-in-Wicket-tp27179274p27179469.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Templates in Wicket
Posted by Igor Vaynberg <ig...@gmail.com>.
so you are giving designers markup from a wicket app? why not just let
them run the app, that way they can go in and do things themselves?
in my company out developers checkout the code and run mvn jetty to
get the app up and running with markup reloading, then they go in with
textmate or coda and tweak the markup.
-igor
On Fri, Jan 15, 2010 at 8:00 AM, Marek Šabo <ms...@buk.cvut.cz> wrote:
> Hi everyone,
>
> I would like to know if someone can share their experience with graphical
> templates under wicket. It's easy to provide markup code for designers, they
> just need to preserve hierarchy of wicket elements, right? But how do you
> cope with things like attribute modifier inside application and dynamic
> loading of other css files? Or what is the most common approach to this kind
> of thing?
>
> Regards,
>
> Marek
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org