Wicketstuff @ sourceforge

[Igor Vaynberg-2]

correct.

anyways, googlecode works fine. my company has TC building brix and it
works without issues.

-igor

On Mon, Nov 17, 2008 at 11:59 AM, James Carman
<[hidden email]> wrote:

> The issue is that it polls the SVN server, right?  Switching to
> another polling CI server wouldn't help, really.
>
> On Mon, Nov 17, 2008 at 2:49 PM, Jeremy Thomerson
> <[hidden email]> wrote:
>> Forgive my ignorance in this since I haven't been paying a lotof attention
>> to all the TeamCity discussions... but since TC is our big problem (or the
>> marriage of TC and SF), have we tried switching to Continuum or similar?
>> What do we need to accomplish such a thing?  Hardware?
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>> On Mon, Nov 17, 2008 at 1:07 PM, Nino Saturnino Martinez Vazquez Wael <
>> [hidden email]> wrote:
>>
>>> Im replying inline...
>>>
>>> Jeremy Thomerson wrote:
>>>
>>>> Nino,
>>>>  Does this mean that you want all Wicket Stuff projects to move to Google
>>>> Code
>>>>
>>> No I do not, I'd want to try one or two projects first, that rely on
>>> teamcity (because we only have problems with teamcity). If we have problems
>>> with google code as well it would be a waste of resources switching.
>>>
>>>>  because of the problems with the TeamCity builds and SourceForge?  If
>>>> so, I'd be hesitant to do it this way.  Here's a couple reasons why:
>>>>
>>>>   1. the very first sentence on your Google code page says that multiple
>>>>   licenses are not allowed - I've always been under the impression that
>>>> one of
>>>>   the reasons we had Wicket Stuff was so that integrations with
>>>> third-party
>>>>   libraries (incompatible with Apache license) could be done there (just
>>>> one
>>>>   reason)
>>>>
>>>>
>>> No there are several other reasons aswell, like the fact that the core devs
>>> do not maintain wicketstuff. But your point are very vaild, and some of the
>>> stuff projects uses libs that are incompatible with ASL... So if it should
>>> work this should be sorted out.
>>>
>>>>   2. We lose all code history - IF the switch were made, we should import
>>>>   the old repository.
>>>>
>>>>
>>> Yes, and thats one of the reasons why I've been so reluctant to do this.
>>>
>>>> It seems like the community should vote on this before such a big change
>>>> is
>>>> made.  Thoughts anyone?
>>>>
>>>>
>>> Yes I agree, and also feel that if anyone are up to the task of further
>>> talking with sourceforge this would probably be the way to go, one of my
>>> problems are that I do not have any administrative rights on the server
>>> where teamcity runs from so I cannot go further with teamcity since, they
>>> require details of that character.
>>>
>>>
>>> --
>>> -Wicket for love
>>>
>>> Nino Martinez Wael
>>> Java Specialist @ Jayway DK
>>> http://www.jayway.dk
>>> [phone]
>>>
>>>
>>
>

At the loss of the ability to have all the WicketStuff projects together in
one project and still have multiple licenses.  That's a big loss to what
WicketStuff is (IMHO)

--
Jeremy Thomerson
http://www.wickettraining.com


On Mon, Nov 17, 2008 at 2:07 PM, Igor Vaynberg <[hidden email]>wrote:

> correct.
>
> anyways, googlecode works fine. my company has TC building brix and it
> works without issues.
>
> -igor
>
> On Mon, Nov 17, 2008 at 11:59 AM, James Carman
> <[hidden email]> wrote:
> > The issue is that it polls the SVN server, right?  Switching to
> > another polling CI server wouldn't help, really.
> >
> > On Mon, Nov 17, 2008 at 2:49 PM, Jeremy Thomerson
> > <[hidden email]> wrote:
> >> Forgive my ignorance in this since I haven't been paying a lotof
> attention
> >> to all the TeamCity discussions... but since TC is our big problem (or
> the
> >> marriage of TC and SF), have we tried switching to Continuum or similar?
> >> What do we need to accomplish such a thing?  Hardware?
> >>
> >> --
> >> Jeremy Thomerson
> >> http://www.wickettraining.com
> >>
> >>
> >> On Mon, Nov 17, 2008 at 1:07 PM, Nino Saturnino Martinez Vazquez Wael <
> >> [hidden email]> wrote:
> >>
> >>> Im replying inline...
> >>>
> >>> Jeremy Thomerson wrote:
> >>>
> >>>> Nino,
> >>>>  Does this mean that you want all Wicket Stuff projects to move to
> Google
> >>>> Code
> >>>>
> >>> No I do not, I'd want to try one or two projects first, that rely on
> >>> teamcity (because we only have problems with teamcity). If we have
> problems
> >>> with google code as well it would be a waste of resources switching.
> >>>
> >>>>  because of the problems with the TeamCity builds and SourceForge?  If
> >>>> so, I'd be hesitant to do it this way.  Here's a couple reasons why:
> >>>>
> >>>>   1. the very first sentence on your Google code page says that
> multiple
> >>>>   licenses are not allowed - I've always been under the impression
> that
> >>>> one of
> >>>>   the reasons we had Wicket Stuff was so that integrations with
> >>>> third-party
> >>>>   libraries (incompatible with Apache license) could be done there
> (just
> >>>> one
> >>>>   reason)
> >>>>
> >>>>
> >>> No there are several other reasons aswell, like the fact that the core
> devs
> >>> do not maintain wicketstuff. But your point are very vaild, and some of
> the
> >>> stuff projects uses libs that are incompatible with ASL... So if it
> should
> >>> work this should be sorted out.
> >>>
> >>>>   2. We lose all code history - IF the switch were made, we should
> import
> >>>>   the old repository.
> >>>>
> >>>>
> >>> Yes, and thats one of the reasons why I've been so reluctant to do
> this.
> >>>
> >>>> It seems like the community should vote on this before such a big
> change
> >>>> is
> >>>> made.  Thoughts anyone?
> >>>>
> >>>>
> >>> Yes I agree, and also feel that if anyone are up to the task of further
> >>> talking with sourceforge this would probably be the way to go, one of
> my
> >>> problems are that I do not have any administrative rights on the server
> >>> where teamcity runs from so I cannot go further with teamcity since,
> they
> >>> require details of that character.
> >>>
> >>>
> >>> --
> >>> -Wicket for love
> >>>
> >>> Nino Martinez Wael
> >>> Java Specialist @ Jayway DK
> >>> http://www.jayway.dk
> >>> [phone]
> >>>
> >>>
> >>
> >
>

[Ernesto Reinaldo Barreiro-4]

-1,

I do not use it myself but as  a user I would  hate to see something
removed just because it allows to use JSP like constructs. Anyway, a
willing user could extend markup processing to define his/her own JSP
like tags and make them work in Wicket...

Cheers,

Ernesto

Bruno Cesar Borges wrote:

> This might sound crazy, but what about dropping the support for the tag <wicket:link> ? :-)
>
> People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that.
>
> Example:
>
>    # Java
>    AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer("menus");
>
>    # HTML
>    <ul wicket:id="menus">
>      <li><a href="Users.html">Users</a></li>
>      <li><a href="Departments.html">Departments</a></li>
>    </ul>
>
> What do you guys think?
>
> Cheers,
> Bruno
> ***************************************************************************************************
> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s),
> podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por
> lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema.
> Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem
> expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente,
> o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas."
>
>
> "Warning: This message was sent for exclusive use of the addressees above identified, possibly
> containing information and or privileged/confidential documents whose content is protected by law.
> In case you have mistakenly received it, please notify the sender and delete it from your system.
> Be noticed that the law forbids the retention, dissemination, distribution, copy or use without
> express authorization from the sender. Personal opinions of the sender do not necessarily reflect
> CETIP's point of view, which is only divulged by authorized personnel."
> ***************************************************************************************************
>
>
>  

[Nino Saturnino Martinez Vazquez Wael]

Yeah, I wonder if we could just "override" the license by stating on the
main project page that the license are specified per project..?

Jeremy Thomerson wrote:
> At the loss of the ability to have all the WicketStuff projects together in
> one project and still have multiple licenses.  That's a big loss to what
> WicketStuff is (IMHO)
>
>  

--
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
[phone]

[Peter Ertl]

-1, too:

I use it just the way Igor describes. I usually set up a mock html  
page, then <wicket:link> the css and javascript. So I can easily test  
the page in preview mode and in wicket, too.

Once the application evolves I tend to remove <wicket:link> again and  
replace it with ResourceReference inside the pages and base pages.

Let it there, it's really useful. If people tend to be stupid no  
framework on earth will stop them from doing so.

Cheers
Peter


Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:

> -1.
>
> this stuff is very useful for linking to css/js/image files. if people
> want to abuse it, it is their problem. people will find a way to abuse
> anything though.
>
> -igor
>
> 2008/11/17 Bruno Cesar Borges <[hidden email]>:
>> This might sound crazy, but what about dropping the support for the  
>> tag <wicket:link> ? :-)
>>
>> People are starting to use it frequently, and because of that,  
>> features will be requested. And then we might end with a tag  
>> library. But, to not freak everybody out, I suggest develop a  
>> markup container to do that.
>>
>> Example:
>>
>>  # Java
>>  AutoLinkMarkupContainer autolinks = new  
>> AutoLinkMarkupContainer("menus");
>>
>>  # HTML
>>  <ul wicket:id="menus">
>>    <li><a href="Users.html">Users</a></li>
>>    <li><a href="Departments.html">Departments</a></li>
>>  </ul>
>>
>> What do you guys think?
>>
>> Cheers,
>> Bruno
>> ***************************************************************************************************
>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)  
>> destinatários(s) acima identificado(s),
>> podendo conter informações e/ou documentos confidencias/
>> privilegiados e seu sigilo é protegido por
>> lei. Caso você tenha recebido por engano, por favor, informe o  
>> remetente e apague-a de seu sistema.
>> Notificamos que é proibido por lei a sua retenção, disseminação,  
>> distribuição, cópia ou uso sem
>> expressa autorização do remetente. Opiniões pessoais do remetente  
>> não refletem, necessariamente,
>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas  
>> autorizadas."
>>
>>
>> "Warning: This message was sent for exclusive use of the addressees  
>> above identified, possibly
>> containing information and or privileged/confidential documents  
>> whose content is protected by law.
>> In case you have mistakenly received it, please notify the sender  
>> and delete it from your system.
>> Be noticed that the law forbids the retention, dissemination,  
>> distribution, copy or use without
>> express authorization from the sender. Personal opinions of the  
>> sender do not necessarily reflect
>> CETIP's point of view, which is only divulged by authorized  
>> personnel."
>> ***************************************************************************************************
>>
>>

[rhansen]

+1, what about moving it to an optional package? wicket-tags ?

On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <[hidden email]> wrote:

> -1, too:
>
> I use it just the way Igor describes. I usually set up a mock html page,
> then <wicket:link> the css and javascript. So I can easily test the page in
> preview mode and in wicket, too.
>
> Once the application evolves I tend to remove <wicket:link> again and
> replace it with ResourceReference inside the pages and base pages.
>
> Let it there, it's really useful. If people tend to be stupid no framework
> on earth will stop them from doing so.
>
> Cheers
> Peter
>
>
> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>
>  -1.
>>
>> this stuff is very useful for linking to css/js/image files. if people
>> want to abuse it, it is their problem. people will find a way to abuse
>> anything though.
>>
>> -igor
>>
>> 2008/11/17 Bruno Cesar Borges <[hidden email]>:
>>
>>> This might sound crazy, but what about dropping the support for the tag
>>> <wicket:link> ? :-)
>>>
>>> People are starting to use it frequently, and because of that, features
>>> will be requested. And then we might end with a tag library. But, to not
>>> freak everybody out, I suggest develop a markup container to do that.
>>>
>>> Example:
>>>
>>>  # Java
>>>  AutoLinkMarkupContainer autolinks = new
>>> AutoLinkMarkupContainer("menus");
>>>
>>>  # HTML
>>>  <ul wicket:id="menus">
>>>   <li><a href="Users.html">Users</a></li>
>>>   <li><a href="Departments.html">Departments</a></li>
>>>  </ul>
>>>
>>> What do you guys think?
>>>
>>> Cheers,
>>> Bruno
>>>
>>> ***************************************************************************************************
>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>> destinatários(s) acima identificado(s),
>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>> seu sigilo é protegido por
>>> lei. Caso você tenha recebido por engano, por favor, informe o remetente
>>> e apague-a de seu sistema.
>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>> distribuição, cópia ou uso sem
>>> expressa autorização do remetente. Opiniões pessoais do remetente não
>>> refletem, necessariamente,
>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>> autorizadas."
>>>
>>>
>>> "Warning: This message was sent for exclusive use of the addressees above
>>> identified, possibly
>>> containing information and or privileged/confidential documents whose
>>> content is protected by law.
>>> In case you have mistakenly received it, please notify the sender and
>>> delete it from your system.
>>> Be noticed that the law forbids the retention, dissemination,
>>> distribution, copy or use without
>>> express authorization from the sender. Personal opinions of the sender do
>>> not necessarily reflect
>>> CETIP's point of view, which is only divulged by authorized personnel."
>>>
>>> ***************************************************************************************************
>>>
>>>
>>>
>

[James Carman]

The markup parser has to know how to deal with it I would think.  That
would be quite an undertaking to split that functionality out and make
it able to be plugged back in.

On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <[hidden email]> wrote:

> +1, what about moving it to an optional package? wicket-tags ?
>
> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <[hidden email]> wrote:
>
>> -1, too:
>>
>> I use it just the way Igor describes. I usually set up a mock html page,
>> then <wicket:link> the css and javascript. So I can easily test the page in
>> preview mode and in wicket, too.
>>
>> Once the application evolves I tend to remove <wicket:link> again and
>> replace it with ResourceReference inside the pages and base pages.
>>
>> Let it there, it's really useful. If people tend to be stupid no framework
>> on earth will stop them from doing so.
>>
>> Cheers
>> Peter
>>
>>
>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>
>>  -1.
>>>
>>> this stuff is very useful for linking to css/js/image files. if people
>>> want to abuse it, it is their problem. people will find a way to abuse
>>> anything though.
>>>
>>> -igor
>>>
>>> 2008/11/17 Bruno Cesar Borges <[hidden email]>:
>>>
>>>> This might sound crazy, but what about dropping the support for the tag
>>>> <wicket:link> ? :-)
>>>>
>>>> People are starting to use it frequently, and because of that, features
>>>> will be requested. And then we might end with a tag library. But, to not
>>>> freak everybody out, I suggest develop a markup container to do that.
>>>>
>>>> Example:
>>>>
>>>>  # Java
>>>>  AutoLinkMarkupContainer autolinks = new
>>>> AutoLinkMarkupContainer("menus");
>>>>
>>>>  # HTML
>>>>  <ul wicket:id="menus">
>>>>   <li><a href="Users.html">Users</a></li>
>>>>   <li><a href="Departments.html">Departments</a></li>
>>>>  </ul>
>>>>
>>>> What do you guys think?
>>>>
>>>> Cheers,
>>>> Bruno
>>>>
>>>> ***************************************************************************************************
>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>> destinatários(s) acima identificado(s),
>>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>>> seu sigilo é protegido por
>>>> lei. Caso você tenha recebido por engano, por favor, informe o remetente
>>>> e apague-a de seu sistema.
>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>> distribuição, cópia ou uso sem
>>>> expressa autorização do remetente. Opiniões pessoais do remetente não
>>>> refletem, necessariamente,
>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>> autorizadas."
>>>>
>>>>
>>>> "Warning: This message was sent for exclusive use of the addressees above
>>>> identified, possibly
>>>> containing information and or privileged/confidential documents whose
>>>> content is protected by law.
>>>> In case you have mistakenly received it, please notify the sender and
>>>> delete it from your system.
>>>> Be noticed that the law forbids the retention, dissemination,
>>>> distribution, copy or use without
>>>> express authorization from the sender. Personal opinions of the sender do
>>>> not necessarily reflect
>>>> CETIP's point of view, which is only divulged by authorized personnel."
>>>>
>>>> ***************************************************************************************************
>>>>
>>>>
>>>>
>>
>

[Igor Vaynberg-2]

it is already all pluggable and wicketlink handler is just a plugin
into the parser :)

-igor

On Tue, Nov 18, 2008 at 12:29 PM, James Carman
<[hidden email]> wrote:

> The markup parser has to know how to deal with it I would think.  That
> would be quite an undertaking to split that functionality out and make
> it able to be plugged back in.
>
> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <[hidden email]> wrote:
>> +1, what about moving it to an optional package? wicket-tags ?
>>
>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <[hidden email]> wrote:
>>
>>> -1, too:
>>>
>>> I use it just the way Igor describes. I usually set up a mock html page,
>>> then <wicket:link> the css and javascript. So I can easily test the page in
>>> preview mode and in wicket, too.
>>>
>>> Once the application evolves I tend to remove <wicket:link> again and
>>> replace it with ResourceReference inside the pages and base pages.
>>>
>>> Let it there, it's really useful. If people tend to be stupid no framework
>>> on earth will stop them from doing so.
>>>
>>> Cheers
>>> Peter
>>>
>>>
>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>
>>>  -1.
>>>>
>>>> this stuff is very useful for linking to css/js/image files. if people
>>>> want to abuse it, it is their problem. people will find a way to abuse
>>>> anything though.
>>>>
>>>> -igor
>>>>
>>>> 2008/11/17 Bruno Cesar Borges <[hidden email]>:
>>>>
>>>>> This might sound crazy, but what about dropping the support for the tag
>>>>> <wicket:link> ? :-)
>>>>>
>>>>> People are starting to use it frequently, and because of that, features
>>>>> will be requested. And then we might end with a tag library. But, to not
>>>>> freak everybody out, I suggest develop a markup container to do that.
>>>>>
>>>>> Example:
>>>>>
>>>>>  # Java
>>>>>  AutoLinkMarkupContainer autolinks = new
>>>>> AutoLinkMarkupContainer("menus");
>>>>>
>>>>>  # HTML
>>>>>  <ul wicket:id="menus">
>>>>>   <li><a href="Users.html">Users</a></li>
>>>>>   <li><a href="Departments.html">Departments</a></li>
>>>>>  </ul>
>>>>>
>>>>> What do you guys think?
>>>>>
>>>>> Cheers,
>>>>> Bruno
>>>>>
>>>>> ***************************************************************************************************
>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>> destinatários(s) acima identificado(s),
>>>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>>>> seu sigilo é protegido por
>>>>> lei. Caso você tenha recebido por engano, por favor, informe o remetente
>>>>> e apague-a de seu sistema.
>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>> distribuição, cópia ou uso sem
>>>>> expressa autorização do remetente. Opiniões pessoais do remetente não
>>>>> refletem, necessariamente,
>>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>>> autorizadas."
>>>>>
>>>>>
>>>>> "Warning: This message was sent for exclusive use of the addressees above
>>>>> identified, possibly
>>>>> containing information and or privileged/confidential documents whose
>>>>> content is protected by law.
>>>>> In case you have mistakenly received it, please notify the sender and
>>>>> delete it from your system.
>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>> distribution, copy or use without
>>>>> express authorization from the sender. Personal opinions of the sender do
>>>>> not necessarily reflect
>>>>> CETIP's point of view, which is only divulged by authorized personnel."
>>>>>
>>>>> ***************************************************************************************************
>>>>>
>>>>>
>>>>>
>>>
>>
>

[James Carman]

Would the user have to register the plugin manually or would it be
picked up merely by the jar being on the classpath?

On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg <[hidden email]> wrote:

> it is already all pluggable and wicketlink handler is just a plugin
> into the parser :)
>
> -igor
>
> On Tue, Nov 18, 2008 at 12:29 PM, James Carman
> <[hidden email]> wrote:
>> The markup parser has to know how to deal with it I would think.  That
>> would be quite an undertaking to split that functionality out and make
>> it able to be plugged back in.
>>
>> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <[hidden email]> wrote:
>>> +1, what about moving it to an optional package? wicket-tags ?
>>>
>>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <[hidden email]> wrote:
>>>
>>>> -1, too:
>>>>
>>>> I use it just the way Igor describes. I usually set up a mock html page,
>>>> then <wicket:link> the css and javascript. So I can easily test the page in
>>>> preview mode and in wicket, too.
>>>>
>>>> Once the application evolves I tend to remove <wicket:link> again and
>>>> replace it with ResourceReference inside the pages and base pages.
>>>>
>>>> Let it there, it's really useful. If people tend to be stupid no framework
>>>> on earth will stop them from doing so.
>>>>
>>>> Cheers
>>>> Peter
>>>>
>>>>
>>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>>
>>>>  -1.
>>>>>
>>>>> this stuff is very useful for linking to css/js/image files. if people
>>>>> want to abuse it, it is their problem. people will find a way to abuse
>>>>> anything though.
>>>>>
>>>>> -igor
>>>>>
>>>>> 2008/11/17 Bruno Cesar Borges <[hidden email]>:
>>>>>
>>>>>> This might sound crazy, but what about dropping the support for the tag
>>>>>> <wicket:link> ? :-)
>>>>>>
>>>>>> People are starting to use it frequently, and because of that, features
>>>>>> will be requested. And then we might end with a tag library. But, to not
>>>>>> freak everybody out, I suggest develop a markup container to do that.
>>>>>>
>>>>>> Example:
>>>>>>
>>>>>>  # Java
>>>>>>  AutoLinkMarkupContainer autolinks = new
>>>>>> AutoLinkMarkupContainer("menus");
>>>>>>
>>>>>>  # HTML
>>>>>>  <ul wicket:id="menus">
>>>>>>   <li><a href="Users.html">Users</a></li>
>>>>>>   <li><a href="Departments.html">Departments</a></li>
>>>>>>  </ul>
>>>>>>
>>>>>> What do you guys think?
>>>>>>
>>>>>> Cheers,
>>>>>> Bruno
>>>>>>
>>>>>> ***************************************************************************************************
>>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>>> destinatários(s) acima identificado(s),
>>>>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>>>>> seu sigilo é protegido por
>>>>>> lei. Caso você tenha recebido por engano, por favor, informe o remetente
>>>>>> e apague-a de seu sistema.
>>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>>> distribuição, cópia ou uso sem
>>>>>> expressa autorização do remetente. Opiniões pessoais do remetente não
>>>>>> refletem, necessariamente,
>>>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>>>> autorizadas."
>>>>>>
>>>>>>
>>>>>> "Warning: This message was sent for exclusive use of the addressees above
>>>>>> identified, possibly
>>>>>> containing information and or privileged/confidential documents whose
>>>>>> content is protected by law.
>>>>>> In case you have mistakenly received it, please notify the sender and
>>>>>> delete it from your system.
>>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>>> distribution, copy or use without
>>>>>> express authorization from the sender. Personal opinions of the sender do
>>>>>> not necessarily reflect
>>>>>> CETIP's point of view, which is only divulged by authorized personnel."
>>>>>>
>>>>>> ***************************************************************************************************
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>
>

[Peter Ertl]

What's the problem with just leaving it where it is?

If you don't like it ignore it - or am I missing something important  
here?

Am 18.11.2008 um 22:12 schrieb James Carman:

> Would the user have to register the plugin manually or would it be
> picked up merely by the jar being on the classpath?
>
> On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg <[hidden email]
> > wrote:
>> it is already all pluggable and wicketlink handler is just a plugin
>> into the parser :)
>>
>> -igor
>>
>> On Tue, Nov 18, 2008 at 12:29 PM, James Carman
>> <[hidden email]> wrote:
>>> The markup parser has to know how to deal with it I would think.  
>>> That
>>> would be quite an undertaking to split that functionality out and  
>>> make
>>> it able to be plugged back in.
>>>
>>> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <[hidden email]
>>> > wrote:
>>>> +1, what about moving it to an optional package? wicket-tags ?
>>>>
>>>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <[hidden email]>  
>>>> wrote:
>>>>
>>>>> -1, too:
>>>>>
>>>>> I use it just the way Igor describes. I usually set up a mock  
>>>>> html page,
>>>>> then <wicket:link> the css and javascript. So I can easily test  
>>>>> the page in
>>>>> preview mode and in wicket, too.
>>>>>
>>>>> Once the application evolves I tend to remove <wicket:link>  
>>>>> again and
>>>>> replace it with ResourceReference inside the pages and base pages.
>>>>>
>>>>> Let it there, it's really useful. If people tend to be stupid no  
>>>>> framework
>>>>> on earth will stop them from doing so.
>>>>>
>>>>> Cheers
>>>>> Peter
>>>>>
>>>>>
>>>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>>>
>>>>> -1.
>>>>>>
>>>>>> this stuff is very useful for linking to css/js/image files. if  
>>>>>> people
>>>>>> want to abuse it, it is their problem. people will find a way  
>>>>>> to abuse
>>>>>> anything though.
>>>>>>
>>>>>> -igor
>>>>>>
>>>>>> 2008/11/17 Bruno Cesar Borges <[hidden email]>:
>>>>>>
>>>>>>> This might sound crazy, but what about dropping the support  
>>>>>>> for the tag
>>>>>>> <wicket:link> ? :-)
>>>>>>>
>>>>>>> People are starting to use it frequently, and because of that,  
>>>>>>> features
>>>>>>> will be requested. And then we might end with a tag library.  
>>>>>>> But, to not
>>>>>>> freak everybody out, I suggest develop a markup container to  
>>>>>>> do that.
>>>>>>>
>>>>>>> Example:
>>>>>>>
>>>>>>> # Java
>>>>>>> AutoLinkMarkupContainer autolinks = new
>>>>>>> AutoLinkMarkupContainer("menus");
>>>>>>>
>>>>>>> # HTML
>>>>>>> <ul wicket:id="menus">
>>>>>>> <li><a href="Users.html">Users</a></li>
>>>>>>> <li><a href="Departments.html">Departments</a></li>
>>>>>>> </ul>
>>>>>>>
>>>>>>> What do you guys think?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Bruno
>>>>>>>
>>>>>>> ***************************************************************************************************
>>>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>>>> destinatários(s) acima identificado(s),
>>>>>>> podendo conter informações e/ou documentos confidencias/
>>>>>>> privilegiados e
>>>>>>> seu sigilo é protegido por
>>>>>>> lei. Caso você tenha recebido por engano, por favor, informe o  
>>>>>>> remetente
>>>>>>> e apague-a de seu sistema.
>>>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>>>> distribuição, cópia ou uso sem
>>>>>>> expressa autorização do remetente. Opiniões pessoais do  
>>>>>>> remetente não
>>>>>>> refletem, necessariamente,
>>>>>>> o ponto de vista da CETIP, o qual é divulgado somente por  
>>>>>>> pessoas
>>>>>>> autorizadas."
>>>>>>>
>>>>>>>
>>>>>>> "Warning: This message was sent for exclusive use of the  
>>>>>>> addressees above
>>>>>>> identified, possibly
>>>>>>> containing information and or privileged/confidential  
>>>>>>> documents whose
>>>>>>> content is protected by law.
>>>>>>> In case you have mistakenly received it, please notify the  
>>>>>>> sender and
>>>>>>> delete it from your system.
>>>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>>>> distribution, copy or use without
>>>>>>> express authorization from the sender. Personal opinions of  
>>>>>>> the sender do
>>>>>>> not necessarily reflect
>>>>>>> CETIP's point of view, which is only divulged by authorized  
>>>>>>> personnel."
>>>>>>>
>>>>>>> ***************************************************************************************************
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>

[James Carman]

That's my opinion, also.  I voted -1 to removing wicket:link.  I was
more just curious about the inner workings of the parser at this point
:)

On Tue, Nov 18, 2008 at 4:59 PM, Peter Ertl <[hidden email]> wrote:

> What's the problem with just leaving it where it is?
>
> If you don't like it ignore it - or am I missing something important here?
>
> Am 18.11.2008 um 22:12 schrieb James Carman:
>
>> Would the user have to register the plugin manually or would it be
>> picked up merely by the jar being on the classpath?
>>
>> On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg <[hidden email]>
>> wrote:
>>>
>>> it is already all pluggable and wicketlink handler is just a plugin
>>> into the parser :)
>>>
>>> -igor
>>>
>>> On Tue, Nov 18, 2008 at 12:29 PM, James Carman
>>> <[hidden email]> wrote:
>>>>
>>>> The markup parser has to know how to deal with it I would think.  That
>>>> would be quite an undertaking to split that functionality out and make
>>>> it able to be plugged back in.
>>>>
>>>> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <[hidden email]>
>>>> wrote:
>>>>>
>>>>> +1, what about moving it to an optional package? wicket-tags ?
>>>>>
>>>>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <[hidden email]> wrote:
>>>>>
>>>>>> -1, too:
>>>>>>
>>>>>> I use it just the way Igor describes. I usually set up a mock html
>>>>>> page,
>>>>>> then <wicket:link> the css and javascript. So I can easily test the
>>>>>> page in
>>>>>> preview mode and in wicket, too.
>>>>>>
>>>>>> Once the application evolves I tend to remove <wicket:link> again and
>>>>>> replace it with ResourceReference inside the pages and base pages.
>>>>>>
>>>>>> Let it there, it's really useful. If people tend to be stupid no
>>>>>> framework
>>>>>> on earth will stop them from doing so.
>>>>>>
>>>>>> Cheers
>>>>>> Peter
>>>>>>
>>>>>>
>>>>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>>>>
>>>>>> -1.
>>>>>>>
>>>>>>> this stuff is very useful for linking to css/js/image files. if
>>>>>>> people
>>>>>>> want to abuse it, it is their problem. people will find a way to
>>>>>>> abuse
>>>>>>> anything though.
>>>>>>>
>>>>>>> -igor
>>>>>>>
>>>>>>> 2008/11/17 Bruno Cesar Borges <[hidden email]>:
>>>>>>>
>>>>>>>> This might sound crazy, but what about dropping the support for the
>>>>>>>> tag
>>>>>>>> <wicket:link> ? :-)
>>>>>>>>
>>>>>>>> People are starting to use it frequently, and because of that,
>>>>>>>> features
>>>>>>>> will be requested. And then we might end with a tag library. But, to
>>>>>>>> not
>>>>>>>> freak everybody out, I suggest develop a markup container to do
>>>>>>>> that.
>>>>>>>>
>>>>>>>> Example:
>>>>>>>>
>>>>>>>> # Java
>>>>>>>> AutoLinkMarkupContainer autolinks = new
>>>>>>>> AutoLinkMarkupContainer("menus");
>>>>>>>>
>>>>>>>> # HTML
>>>>>>>> <ul wicket:id="menus">
>>>>>>>> <li><a href="Users.html">Users</a></li>
>>>>>>>> <li><a href="Departments.html">Departments</a></li>
>>>>>>>> </ul>
>>>>>>>>
>>>>>>>> What do you guys think?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Bruno
>>>>>>>>
>>>>>>>>
>>>>>>>> ***************************************************************************************************
>>>>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>>>>> destinatários(s) acima identificado(s),
>>>>>>>> podendo conter informações e/ou documentos
>>>>>>>> confidencias/privilegiados e
>>>>>>>> seu sigilo é protegido por
>>>>>>>> lei. Caso você tenha recebido por engano, por favor, informe o
>>>>>>>> remetente
>>>>>>>> e apague-a de seu sistema.
>>>>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>>>>> distribuição, cópia ou uso sem
>>>>>>>> expressa autorização do remetente. Opiniões pessoais do remetente
>>>>>>>> não
>>>>>>>> refletem, necessariamente,
>>>>>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>>>>>> autorizadas."
>>>>>>>>
>>>>>>>>
>>>>>>>> "Warning: This message was sent for exclusive use of the addressees
>>>>>>>> above
>>>>>>>> identified, possibly
>>>>>>>> containing information and or privileged/confidential documents
>>>>>>>> whose
>>>>>>>> content is protected by law.
>>>>>>>> In case you have mistakenly received it, please notify the sender
>>>>>>>> and
>>>>>>>> delete it from your system.
>>>>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>>>>> distribution, copy or use without
>>>>>>>> express authorization from the sender. Personal opinions of the
>>>>>>>> sender do
>>>>>>>> not necessarily reflect
>>>>>>>> CETIP's point of view, which is only divulged by authorized
>>>>>>>> personnel."
>>>>>>>>
>>>>>>>>
>>>>>>>> ***************************************************************************************************
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
>

[Nino Saturnino Martinez Vazquez Wael]

With the risk of hijacking the thread. It's really easy registering new
stuff with the parser, I recently had a look at something in the
formcomponent hieracy, and you just call a method or 2 to register new
tags.. :)

James Carman wrote:

> That's my opinion, also.  I voted -1 to removing wicket:link.  I was
> more just curious about the inner workings of the parser at this point
> :)
>
> On Tue, Nov 18, 2008 at 4:59 PM, Peter Ertl <[hidden email]> wrote:
>  
>> What's the problem with just leaving it where it is?
>>
>> If you don't like it ignore it - or am I missing something important here?
>>
>> Am 18.11.2008 um 22:12 schrieb James Carman:
>>
>>    
>>> Would the user have to register the plugin manually or would it be
>>> picked up merely by the jar being on the classpath?
>>>
>>> On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg <[hidden email]>
>>> wrote:
>>>      
>>>> it is already all pluggable and wicketlink handler is just a plugin
>>>> into the parser :)
>>>>
>>>> -igor
>>>>
>>>> On Tue, Nov 18, 2008 at 12:29 PM, James Carman
>>>> <[hidden email]> wrote:
>>>>        
>>>>> The markup parser has to know how to deal with it I would think.  That
>>>>> would be quite an undertaking to split that functionality out and make
>>>>> it able to be plugged back in.
>>>>>
>>>>> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <[hidden email]>
>>>>> wrote:
>>>>>          
>>>>>> +1, what about moving it to an optional package? wicket-tags ?
>>>>>>
>>>>>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <[hidden email]> wrote:
>>>>>>
>>>>>>            
>>>>>>> -1, too:
>>>>>>>
>>>>>>> I use it just the way Igor describes. I usually set up a mock html
>>>>>>> page,
>>>>>>> then <wicket:link> the css and javascript. So I can easily test the
>>>>>>> page in
>>>>>>> preview mode and in wicket, too.
>>>>>>>
>>>>>>> Once the application evolves I tend to remove <wicket:link> again and
>>>>>>> replace it with ResourceReference inside the pages and base pages.
>>>>>>>
>>>>>>> Let it there, it's really useful. If people tend to be stupid no
>>>>>>> framework
>>>>>>> on earth will stop them from doing so.
>>>>>>>
>>>>>>> Cheers
>>>>>>> Peter
>>>>>>>
>>>>>>>
>>>>>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>>>>>
>>>>>>> -1.
>>>>>>>              
>>>>>>>> this stuff is very useful for linking to css/js/image files. if
>>>>>>>> people
>>>>>>>> want to abuse it, it is their problem. people will find a way to
>>>>>>>> abuse
>>>>>>>> anything though.
>>>>>>>>
>>>>>>>> -igor
>>>>>>>>
>>>>>>>> 2008/11/17 Bruno Cesar Borges <[hidden email]>:
>>>>>>>>
>>>>>>>>                
>>>>>>>>> This might sound crazy, but what about dropping the support for the
>>>>>>>>> tag
>>>>>>>>> <wicket:link> ? :-)
>>>>>>>>>
>>>>>>>>> People are starting to use it frequently, and because of that,
>>>>>>>>> features
>>>>>>>>> will be requested. And then we might end with a tag library. But, to
>>>>>>>>> not
>>>>>>>>> freak everybody out, I suggest develop a markup container to do
>>>>>>>>> that.
>>>>>>>>>
>>>>>>>>> Example:
>>>>>>>>>
>>>>>>>>> # Java
>>>>>>>>> AutoLinkMarkupContainer autolinks = new
>>>>>>>>> AutoLinkMarkupContainer("menus");
>>>>>>>>>
>>>>>>>>> # HTML
>>>>>>>>> <ul wicket:id="menus">
>>>>>>>>> <li><a href="Users.html">Users</a></li>
>>>>>>>>> <li><a href="Departments.html">Departments</a></li>
>>>>>>>>> </ul>
>>>>>>>>>
>>>>>>>>> What do you guys think?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Bruno
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ***************************************************************************************************
>>>>>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>>>>>> destinatários(s) acima identificado(s),
>>>>>>>>> podendo conter informações e/ou documentos
>>>>>>>>> confidencias/privilegiados e
>>>>>>>>> seu sigilo é protegido por
>>>>>>>>> lei. Caso você tenha recebido por engano, por favor, informe o
>>>>>>>>> remetente
>>>>>>>>> e apague-a de seu sistema.
>>>>>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>>>>>> distribuição, cópia ou uso sem
>>>>>>>>> expressa autorização do remetente. Opiniões pessoais do remetente
>>>>>>>>> não
>>>>>>>>> refletem, necessariamente,
>>>>>>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>>>>>>> autorizadas."
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> "Warning: This message was sent for exclusive use of the addressees
>>>>>>>>> above
>>>>>>>>> identified, possibly
>>>>>>>>> containing information and or privileged/confidential documents
>>>>>>>>> whose
>>>>>>>>> content is protected by law.
>>>>>>>>> In case you have mistakenly received it, please notify the sender
>>>>>>>>> and
>>>>>>>>> delete it from your system.
>>>>>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>>>>>> distribution, copy or use without
>>>>>>>>> express authorization from the sender. Personal opinions of the
>>>>>>>>> sender do
>>>>>>>>> not necessarily reflect
>>>>>>>>> CETIP's point of view, which is only divulged by authorized
>>>>>>>>> personnel."
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ***************************************************************************************************
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                  
>>    

--
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
[phone]