You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Michael Sparer <mi...@gmx.at> on 2008/08/20 17:34:33 UTC
New wicketstuff-dojo project
After the update of wicketstuff-push (see
http://www.nabble.com/wicketstuff-push-update-to18765345.html) the question
came up if the push project shouldn't depend on the dojo project any longer
as ws-dojo uses dojo 0.4 and the new cometd implementation requires dojo
1.x.
Rodolfo Hansen, who volunteered to do the upgrade to the latest cometd
version, suggested to let wicketstuff-push cease to depend on ws-dojo. In
our current project, we're using both ws-dojo and ws-push. We really would
like to use the latest cometd release; we can't bear, however, the idea of
having two different dojo versions in the classpath - so we thought about
lifting ws-dojo to 1.1.
As Rodolfo mentioned, lifting ws-dojo to 1.1 isn't trivial due to
incompatibilities (i.e. API changes) between 0.4 and 0.9. However, we think
that lifting the ws-dojo project as a whole (with its dozens of components)
isn't necessary. We'd propose to start with ws-dojo's core functionality -
which is providing dojo resources and build facilites - and lift components
as needed.
We already managed to get the latest dojo release in and port some
components, but there's still a lot of work to be done. Therefore we suggest
to make a new project for wicketstuff-dojo with dojo 1.1 and rely on some
helping hands who port the components they use to dojo 1.1.
As for wicketstuff-push we still hope we can convince Rodolfo to keep the
dependency to (the then new) wicketstuff-dojo-1.1
So what do you, wicketeers, think about that?
If it's alright, our sf.net accounts are the following:
msparer (i already got some permissions, dunno if creating projects is among
them)
sfussenegger (no permissions so far)
regards,
Michael
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
View this message in context: http://www.nabble.com/New-wicketstuff-dojo-project-tp19070145p19070145.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: New wicketstuff-dojo project
Posted by Michael Sparer <mi...@gmx.at>.
Currently it's in our (private) SVN repository and we'd like to have some
things fixed before we gonna share it ... which will be in the course of
next week. if you're just using the wicketstuff classes for your d'n'd now
(speaking of the current wicketstuff-dojo) then it won't be too much work to
switch to the new version, as the api (more or less) stayed the same.
however if you're accessing the dojo api directly in your classes or custom
javascript files it will be a bit more of work to do the upgrade as dojo
1.1. is *not* backwards compatible with dojo 0.4
jwcarman wrote:
>
> Where is this stuff currently? I'm interested in doing some DnD stuff
> with Dojo and if there's better stuff out there than what's currently
> in wicketstuff-dojo, I'd love to take a look at it (not saying it's
> bad now, but if it could be better...).
>
> On Thu, Aug 28, 2008 at 4:07 AM, Michael Sparer <mi...@gmx.at>
> wrote:
>>
>> the components we're using in our projects have been ported to dojo 1.1
>> now,
>> including:
>> - FXOnClickFader
>> - FXOnClickSlider
>> - FXOnCliskWiper
>> - FXOnMouseOverFader
>> - DojoToaster
>> - Drag and Drop panels
>>
>> all other components have been dropped and should be added one by one
>> after
>> you diligent, highly motivated people porting the components you're using
>> ;-)
>>
>> Some API changes were unavoidable due to the new dojo version, and the
>> documentation of the classes is sometimes a bit spare and/or obsolete.
>>
>> one major point:
>> the cometd-part of the wicketstuff-push project has been integrated. as
>> the
>> push projects consists of about 20 classes and depends on dojo, it's,
>> from
>> my point of view, best located in the same project (Rodolfo's gonna kill
>> me
>> for that :-)).
>>
>> so it's basically ready to be shared with the community. in the current
>> structure the way to go is creating a new wicketstuff project, isn't it?
>>
>> so we'd have in trunk:
>> - wicketstuff-dojo (for dojo 0.4)
>> - wicketstuff-dojo-1.1 (for dojo 1.1 - including push)
>> - wicketstuff-push (for dojo 1.1. with its own dojo distribution
>> contained)
>>
>> and in branches
>> - wicketstuff-push (for dojo 0.4 before Rodolfo's major refactoring)
>>
>> that makes the already confusing wicketstuff even more confusing doesn't
>> it?
>> shouldn't we consider merging some projects?
>>
>> another problem might be to find the above mentioned motivated people ...
>> so if it's ok to share it as new wicketstuff project we'll go about
>> starting
>> a (short) wiki page explaining the differences and API changes and then
>> posting message to the user list for motivated people.
>>
>> what do you think?
>>
>>
>>
>> Nino.Martinez wrote:
>>>
>>> +1, and i'll even try to help when I have time:) I think I could make my
>>> ajax loading tooltip in there:)
>>>
>>> Michael Sparer wrote:
>>>> After the update of wicketstuff-push (see
>>>> http://www.nabble.com/wicketstuff-push-update-to18765345.html) the
>>>> question
>>>> came up if the push project shouldn't depend on the dojo project any
>>>> longer
>>>> as ws-dojo uses dojo 0.4 and the new cometd implementation requires
>>>> dojo
>>>> 1.x.
>>>>
>>>> Rodolfo Hansen, who volunteered to do the upgrade to the latest cometd
>>>> version, suggested to let wicketstuff-push cease to depend on ws-dojo.
>>>> In
>>>> our current project, we're using both ws-dojo and ws-push. We really
>>>> would
>>>> like to use the latest cometd release; we can't bear, however, the idea
>>>> of
>>>> having two different dojo versions in the classpath - so we thought
>>>> about
>>>> lifting ws-dojo to 1.1.
>>>>
>>>> As Rodolfo mentioned, lifting ws-dojo to 1.1 isn't trivial due to
>>>> incompatibilities (i.e. API changes) between 0.4 and 0.9. However, we
>>>> think
>>>> that lifting the ws-dojo project as a whole (with its dozens of
>>>> components)
>>>> isn't necessary. We'd propose to start with ws-dojo's core
>>>> functionality
>>>> -
>>>> which is providing dojo resources and build facilites - and lift
>>>> components
>>>> as needed.
>>>>
>>>> We already managed to get the latest dojo release in and port some
>>>> components, but there's still a lot of work to be done. Therefore we
>>>> suggest
>>>> to make a new project for wicketstuff-dojo with dojo 1.1 and rely on
>>>> some
>>>> helping hands who port the components they use to dojo 1.1.
>>>>
>>>> As for wicketstuff-push we still hope we can convince Rodolfo to keep
>>>> the
>>>> dependency to (the then new) wicketstuff-dojo-1.1
>>>>
>>>> So what do you, wicketeers, think about that?
>>>>
>>>> If it's alright, our sf.net accounts are the following:
>>>> msparer (i already got some permissions, dunno if creating projects is
>>>> among
>>>> them)
>>>> sfussenegger (no permissions so far)
>>>>
>>> Could you try if it's possible? I think it should be on svn, but not
>>> sure on team-city and jira
>>>> regards,
>>>> Michael
>>>>
>>>> -----
>>>> Michael Sparer
>>>> http://talk-on-tech.blogspot.com
>>>>
>>>
>>> --
>>> -Wicket for love
>>>
>>> Nino Martinez Wael
>>> Java Specialist @ Jayway DK
>>> http://www.jayway.dk
>>> +45 2936 7684
>>>
>>>
>>>
>>
>>
>> -----
>> Michael Sparer
>> http://talk-on-tech.blogspot.com
>> --
>> View this message in context:
>> http://www.nabble.com/New-wicketstuff-dojo-project-tp19070145p19196057.html
>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>
>>
>
>
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
View this message in context: http://www.nabble.com/New-wicketstuff-dojo-project-tp19070145p19201926.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: New wicketstuff-dojo project
Posted by James Carman <ja...@carmanconsulting.com>.
Where is this stuff currently? I'm interested in doing some DnD stuff
with Dojo and if there's better stuff out there than what's currently
in wicketstuff-dojo, I'd love to take a look at it (not saying it's
bad now, but if it could be better...).
On Thu, Aug 28, 2008 at 4:07 AM, Michael Sparer <mi...@gmx.at> wrote:
>
> the components we're using in our projects have been ported to dojo 1.1 now,
> including:
> - FXOnClickFader
> - FXOnClickSlider
> - FXOnCliskWiper
> - FXOnMouseOverFader
> - DojoToaster
> - Drag and Drop panels
>
> all other components have been dropped and should be added one by one after
> you diligent, highly motivated people porting the components you're using
> ;-)
>
> Some API changes were unavoidable due to the new dojo version, and the
> documentation of the classes is sometimes a bit spare and/or obsolete.
>
> one major point:
> the cometd-part of the wicketstuff-push project has been integrated. as the
> push projects consists of about 20 classes and depends on dojo, it's, from
> my point of view, best located in the same project (Rodolfo's gonna kill me
> for that :-)).
>
> so it's basically ready to be shared with the community. in the current
> structure the way to go is creating a new wicketstuff project, isn't it?
>
> so we'd have in trunk:
> - wicketstuff-dojo (for dojo 0.4)
> - wicketstuff-dojo-1.1 (for dojo 1.1 - including push)
> - wicketstuff-push (for dojo 1.1. with its own dojo distribution contained)
>
> and in branches
> - wicketstuff-push (for dojo 0.4 before Rodolfo's major refactoring)
>
> that makes the already confusing wicketstuff even more confusing doesn't it?
> shouldn't we consider merging some projects?
>
> another problem might be to find the above mentioned motivated people ...
> so if it's ok to share it as new wicketstuff project we'll go about starting
> a (short) wiki page explaining the differences and API changes and then
> posting message to the user list for motivated people.
>
> what do you think?
>
>
>
> Nino.Martinez wrote:
>>
>> +1, and i'll even try to help when I have time:) I think I could make my
>> ajax loading tooltip in there:)
>>
>> Michael Sparer wrote:
>>> After the update of wicketstuff-push (see
>>> http://www.nabble.com/wicketstuff-push-update-to18765345.html) the
>>> question
>>> came up if the push project shouldn't depend on the dojo project any
>>> longer
>>> as ws-dojo uses dojo 0.4 and the new cometd implementation requires dojo
>>> 1.x.
>>>
>>> Rodolfo Hansen, who volunteered to do the upgrade to the latest cometd
>>> version, suggested to let wicketstuff-push cease to depend on ws-dojo. In
>>> our current project, we're using both ws-dojo and ws-push. We really
>>> would
>>> like to use the latest cometd release; we can't bear, however, the idea
>>> of
>>> having two different dojo versions in the classpath - so we thought about
>>> lifting ws-dojo to 1.1.
>>>
>>> As Rodolfo mentioned, lifting ws-dojo to 1.1 isn't trivial due to
>>> incompatibilities (i.e. API changes) between 0.4 and 0.9. However, we
>>> think
>>> that lifting the ws-dojo project as a whole (with its dozens of
>>> components)
>>> isn't necessary. We'd propose to start with ws-dojo's core functionality
>>> -
>>> which is providing dojo resources and build facilites - and lift
>>> components
>>> as needed.
>>>
>>> We already managed to get the latest dojo release in and port some
>>> components, but there's still a lot of work to be done. Therefore we
>>> suggest
>>> to make a new project for wicketstuff-dojo with dojo 1.1 and rely on some
>>> helping hands who port the components they use to dojo 1.1.
>>>
>>> As for wicketstuff-push we still hope we can convince Rodolfo to keep the
>>> dependency to (the then new) wicketstuff-dojo-1.1
>>>
>>> So what do you, wicketeers, think about that?
>>>
>>> If it's alright, our sf.net accounts are the following:
>>> msparer (i already got some permissions, dunno if creating projects is
>>> among
>>> them)
>>> sfussenegger (no permissions so far)
>>>
>> Could you try if it's possible? I think it should be on svn, but not
>> sure on team-city and jira
>>> regards,
>>> Michael
>>>
>>> -----
>>> Michael Sparer
>>> http://talk-on-tech.blogspot.com
>>>
>>
>> --
>> -Wicket for love
>>
>> Nino Martinez Wael
>> Java Specialist @ Jayway DK
>> http://www.jayway.dk
>> +45 2936 7684
>>
>>
>>
>
>
> -----
> Michael Sparer
> http://talk-on-tech.blogspot.com
> --
> View this message in context: http://www.nabble.com/New-wicketstuff-dojo-project-tp19070145p19196057.html
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
Re: PDF's filename for dynamically generated PDFs
Posted by Matej Knopp <ma...@gmail.com>.
I was talking about content-disposition:inline
thus calling
webResponse.setHeader("Content-Disposition", "inline;
filename=\"yourfile.pdf\"");
-Matej
On Sat, Aug 30, 2008 at 2:18 AM, Stefan Lindner <li...@visionet.de> wrote:
> Hi Matej,
>
> calling
>
> webResponse.setHeader("Content-Disposition", "attachment; filename=\"yourfile.pdf\"");
>
> has he same effect as
>
> webResponse.setAttachmentHeader("thisIsMySuggesteFilename.pdf");
>
> It displays a dialog window with the choice s to open or to save the PDF document.
>
> But many thanks for your suggestion....
> Stefan
>
> -----Ursprüngliche Nachricht-----
> Von: Matej Knopp [mailto:matej.knopp@gmail.com]
> Gesendet: Samstag, 30. August 2008 01:49
> An: dev@wicket.apache.org
> Betreff: Re: PDF's filename for dynamically generated PDFs
>
> Perhaps Content-Disposition: Inline; filename="yourfile.pdf" header
> could do the trick?
>
> http://www.ietf.org/rfc/rfc2183.txt
>
> -Matej
>
> On Sat, Aug 30, 2008 at 1:40 AM, Stefan Lindner <li...@visionet.de> wrote:
>> Perhaps this is a general HTML/servlet question but I run into this
>> prblem under wicket. I have a link that dynamically generates a pdf. The
>> PDF is displayes in apopup page. I use Igor's pattern (see
>> http://www.nabble.com/Stream-Excel-to-the-client-td5363673.html#a5364044
>> ) and it works very well. The dynamically generated PDF is displayed in
>> a popup window. Now, when I try to save the PDF the propsed filaname
>> looks like
>>
>>
>> http___localhost_8080_AIOnline_app__wicket_interface=AI-Artikel_2_pdfVer
>> sion__ILinkListener__.pdf
>>
>> Is it possible to have a more meaningful file name suggestion? Having
>>
>> webResponse.setAttachmentHeader("thisIsMySuggesteFilename.pdf");
>>
>> gives the appearing dialog a good hint if I klick the save button" but
>> the PDF is not automatically displayed in a popup window. Is there any
>> resolution for this problem od is this a general HTML/servlet problem?
>>
>> Stefan
>>
>
RE: PDF's filename for dynamically generated PDFs
Posted by Stefan Lindner <li...@visionet.de>.
Hi Matej,
calling
webResponse.setHeader("Content-Disposition", "attachment; filename=\"yourfile.pdf\"");
has he same effect as
webResponse.setAttachmentHeader("thisIsMySuggesteFilename.pdf");
It displays a dialog window with the choice s to open or to save the PDF document.
But many thanks for your suggestion....
Stefan
-----Ursprüngliche Nachricht-----
Von: Matej Knopp [mailto:matej.knopp@gmail.com]
Gesendet: Samstag, 30. August 2008 01:49
An: dev@wicket.apache.org
Betreff: Re: PDF's filename for dynamically generated PDFs
Perhaps Content-Disposition: Inline; filename="yourfile.pdf" header
could do the trick?
http://www.ietf.org/rfc/rfc2183.txt
-Matej
On Sat, Aug 30, 2008 at 1:40 AM, Stefan Lindner <li...@visionet.de> wrote:
> Perhaps this is a general HTML/servlet question but I run into this
> prblem under wicket. I have a link that dynamically generates a pdf. The
> PDF is displayes in apopup page. I use Igor's pattern (see
> http://www.nabble.com/Stream-Excel-to-the-client-td5363673.html#a5364044
> ) and it works very well. The dynamically generated PDF is displayed in
> a popup window. Now, when I try to save the PDF the propsed filaname
> looks like
>
>
> http___localhost_8080_AIOnline_app__wicket_interface=AI-Artikel_2_pdfVer
> sion__ILinkListener__.pdf
>
> Is it possible to have a more meaningful file name suggestion? Having
>
> webResponse.setAttachmentHeader("thisIsMySuggesteFilename.pdf");
>
> gives the appearing dialog a good hint if I klick the save button" but
> the PDF is not automatically displayed in a popup window. Is there any
> resolution for this problem od is this a general HTML/servlet problem?
>
> Stefan
>
Re: PDF's filename for dynamically generated PDFs
Posted by Matej Knopp <ma...@gmail.com>.
Perhaps Content-Disposition: Inline; filename="yourfile.pdf" header
could do the trick?
http://www.ietf.org/rfc/rfc2183.txt
-Matej
On Sat, Aug 30, 2008 at 1:40 AM, Stefan Lindner <li...@visionet.de> wrote:
> Perhaps this is a general HTML/servlet question but I run into this
> prblem under wicket. I have a link that dynamically generates a pdf. The
> PDF is displayes in apopup page. I use Igor's pattern (see
> http://www.nabble.com/Stream-Excel-to-the-client-td5363673.html#a5364044
> ) and it works very well. The dynamically generated PDF is displayed in
> a popup window. Now, when I try to save the PDF the propsed filaname
> looks like
>
>
> http___localhost_8080_AIOnline_app__wicket_interface=AI-Artikel_2_pdfVer
> sion__ILinkListener__.pdf
>
> Is it possible to have a more meaningful file name suggestion? Having
>
> webResponse.setAttachmentHeader("thisIsMySuggesteFilename.pdf");
>
> gives the appearing dialog a good hint if I klick the save button" but
> the PDF is not automatically displayed in a popup window. Is there any
> resolution for this problem od is this a general HTML/servlet problem?
>
> Stefan
>
PDF's filename for dynamically generated PDFs
Posted by Stefan Lindner <li...@visionet.de>.
Perhaps this is a general HTML/servlet question but I run into this
prblem under wicket. I have a link that dynamically generates a pdf. The
PDF is displayes in apopup page. I use Igor's pattern (see
http://www.nabble.com/Stream-Excel-to-the-client-td5363673.html#a5364044
) and it works very well. The dynamically generated PDF is displayed in
a popup window. Now, when I try to save the PDF the propsed filaname
looks like
http___localhost_8080_AIOnline_app__wicket_interface=AI-Artikel_2_pdfVer
sion__ILinkListener__.pdf
Is it possible to have a more meaningful file name suggestion? Having
webResponse.setAttachmentHeader("thisIsMySuggesteFilename.pdf");
gives the appearing dialog a good hint if I klick the save button" but
the PDF is not automatically displayed in a popup window. Is there any
resolution for this problem od is this a general HTML/servlet problem?
Stefan
Re: New wicketstuff-dojo project
Posted by Rodolfo Hansen <rh...@kindleit.net>.
Ok, options A and B both would be over design.
So... Option C:
> C. Stopping support of wicketstuff-push and just having that inside
> wicketstuff-dojo.... (Obviously my least favorite option, I wouldn't have
> even considered it, if you hadn't forced my hand...)
Its basically just project dependencies, but, KISS is a good enough reason
to disband
wicketstuff-push...
I think the way to do it is: After you get wicketstuff-dojo stable and
checked int, mark some classes in wicketstuff-push as deprecated and point
them to the dojo project...
Maybe if sometime soon we integrate push into wicket's core (as per another
thread running around), then it doesn't matter what we decide...
Re: New wicketstuff-dojo project
Posted by Michael Sparer <mi...@gmx.at>.
> What about the people who don't want dojo? :p
Well as cometd is a project of the dojo foundation and they are the only
ones to provide a client side reference implementation in javascript so far,
using dojo isn't too far fetched is it? :)
> A. Create a project for the actual DOJO base: wicketstuff-dojo-core (or
> wicket-dojo-core), factoring out the common elements, and then, both
> wicketstuff-push, and wicketstuff-dojo-components depend on that one?
> (This
> means, since dojo now has a maven build, we could get things from there...
> ...maybe)
KISS I'd say ... if they depend on the same project and each project only
contains some 20 classes now and probably some more in the future, that's
kinda overengineered then.
> B. Rename wicketstuff-push wicketstuff-dojo-core and thats it... Make sure
> its known that Comet technology is there. (Seems harder to know dojo-core
> has comet and push but its dooable, and has less projects...)
I don't get that one, sorry.
> C. Stopping support of wicketstuff-push and just having that inside
> wicketstuff-dojo.... (Obviously my least favorite option, I wouldn't have
> even considered it, if you hadn't forced my hand...)
It's not stopping support it's moving the stuff from a sole project with
some copied classes and an own dojo to the place where the depending classes
and also the right dojo already is located.
if I understood you correctly, your only point against a merge is that you
don't want dojo at all in the push project? If yes please provide some major
advantages, I'm all ears :-)
regards,
Michael
>
> another problem might be to find the above mentioned motivated people ...
> so if it's ok to share it as new wicketstuff project we'll go about
> starting
> a (short) wiki page explaining the differences and API changes and then
> posting message to the user list for motivated people.
>
> what do you think?
>
>
>
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
View this message in context: http://www.nabble.com/New-wicketstuff-dojo-project-tp19070145p19218434.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: New wicketstuff-dojo project
Posted by Rodolfo Hansen <rh...@kindleit.net>.
On Thu, Aug 28, 2008 at 4:07 AM, Michael Sparer <mi...@gmx.at>wrote:
>
> the components we're using in our projects have been ported to dojo 1.1
> now,
> including:
> - FXOnClickFader
> - FXOnClickSlider
> - FXOnCliskWiper
> - FXOnMouseOverFader
> - DojoToaster
> - Drag and Drop panels
>
> all other components have been dropped and should be added one by one after
> you diligent, highly motivated people porting the components you're using
> ;-)
>
> Some API changes were unavoidable due to the new dojo version, and the
> documentation of the classes is sometimes a bit spare and/or obsolete.
>
> one major point:
> the cometd-part of the wicketstuff-push project has been integrated. as the
> push projects consists of about 20 classes and depends on dojo, it's, from
> my point of view, best located in the same project (Rodolfo's gonna kill me
> for that :-)).
YES!! Arhhg...
>
>
> so it's basically ready to be shared with the community. in the current
> structure the way to go is creating a new wicketstuff project, isn't it?
>
> so we'd have in trunk:
> - wicketstuff-dojo (for dojo 0.4)
> - wicketstuff-dojo-1.1 (for dojo 1.1 - including push)
> - wicketstuff-push (for dojo 1.1. with its own dojo distribution contained)
>
> and in branches
> - wicketstuff-push (for dojo 0.4 before Rodolfo's major refactoring)
>
> that makes the already confusing wicketstuff even more confusing doesn't
> it?
> shouldn't we consider merging some projects?
What about the people who don't want dojo? :p
Ok, you push things... How about these options:
A. Create a project for the actual DOJO base: wicketstuff-dojo-core (or
wicket-dojo-core), factoring out the common elements, and then, both
wicketstuff-push, and wicketstuff-dojo-components depend on that one? (This
means, since dojo now has a maven build, we could get things from there...
...maybe)
B. Rename wicketstuff-push wicketstuff-dojo-core and thats it... Make sure
its known that Comet technology is there. (Seems harder to know dojo-core
has comet and push but its dooable, and has less projects...)
And your suggestion:
C. Stopping support of wicketstuff-push and just having that inside
wicketstuff-dojo.... (Obviously my least favorite option, I wouldn't have
even considered it, if you hadn't forced my hand...)
>
> another problem might be to find the above mentioned motivated people ...
> so if it's ok to share it as new wicketstuff project we'll go about
> starting
> a (short) wiki page explaining the differences and API changes and then
> posting message to the user list for motivated people.
>
> what do you think?
>
>
>
Re: New wicketstuff-dojo project
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
Michael Sparer wrote:
> the components we're using in our projects have been ported to dojo 1.1 now,
> including:
> - FXOnClickFader
> - FXOnClickSlider
> - FXOnCliskWiper
> - FXOnMouseOverFader
> - DojoToaster
> - Drag and Drop panels
>
> all other components have been dropped and should be added one by one after
> you diligent, highly motivated people porting the components you're using
> ;-)
>
> Some API changes were unavoidable due to the new dojo version, and the
> documentation of the classes is sometimes a bit spare and/or obsolete.
>
> one major point:
> the cometd-part of the wicketstuff-push project has been integrated. as the
> push projects consists of about 20 classes and depends on dojo, it's, from
> my point of view, best located in the same project (Rodolfo's gonna kill me
> for that :-)).
>
> so it's basically ready to be shared with the community. in the current
> structure the way to go is creating a new wicketstuff project, isn't it?
>
> so we'd have in trunk:
> - wicketstuff-dojo (for dojo 0.4)
> - wicketstuff-dojo-1.1 (for dojo 1.1 - including push)
> - wicketstuff-push (for dojo 1.1. with its own dojo distribution contained)
>
> and in branches
> - wicketstuff-push (for dojo 0.4 before Rodolfo's major refactoring)
>
> that makes the already confusing wicketstuff even more confusing doesn't it?
> shouldn't we consider merging some projects?
>
YES it's a good idea.. I've also though of it.. At some point we'll
probably need to put some of the stuff in a legacy folder or something,
or maybe people should write which version their stuff project supports...
> another problem might be to find the above mentioned motivated people ...
> so if it's ok to share it as new wicketstuff project we'll go about starting
> a (short) wiki page explaining the differences and API changes and then
> posting message to the user list for motivated people.
>
> what do you think?
>
>
>
> Nino.Martinez wrote:
>
>> +1, and i'll even try to help when I have time:) I think I could make my
>> ajax loading tooltip in there:)
>>
>> Michael Sparer wrote:
>>
>>> After the update of wicketstuff-push (see
>>> http://www.nabble.com/wicketstuff-push-update-to18765345.html) the
>>> question
>>> came up if the push project shouldn't depend on the dojo project any
>>> longer
>>> as ws-dojo uses dojo 0.4 and the new cometd implementation requires dojo
>>> 1.x.
>>>
>>> Rodolfo Hansen, who volunteered to do the upgrade to the latest cometd
>>> version, suggested to let wicketstuff-push cease to depend on ws-dojo. In
>>> our current project, we're using both ws-dojo and ws-push. We really
>>> would
>>> like to use the latest cometd release; we can't bear, however, the idea
>>> of
>>> having two different dojo versions in the classpath - so we thought about
>>> lifting ws-dojo to 1.1.
>>>
>>> As Rodolfo mentioned, lifting ws-dojo to 1.1 isn't trivial due to
>>> incompatibilities (i.e. API changes) between 0.4 and 0.9. However, we
>>> think
>>> that lifting the ws-dojo project as a whole (with its dozens of
>>> components)
>>> isn't necessary. We'd propose to start with ws-dojo's core functionality
>>> -
>>> which is providing dojo resources and build facilites - and lift
>>> components
>>> as needed.
>>>
>>> We already managed to get the latest dojo release in and port some
>>> components, but there's still a lot of work to be done. Therefore we
>>> suggest
>>> to make a new project for wicketstuff-dojo with dojo 1.1 and rely on some
>>> helping hands who port the components they use to dojo 1.1.
>>>
>>> As for wicketstuff-push we still hope we can convince Rodolfo to keep the
>>> dependency to (the then new) wicketstuff-dojo-1.1
>>>
>>> So what do you, wicketeers, think about that?
>>>
>>> If it's alright, our sf.net accounts are the following:
>>> msparer (i already got some permissions, dunno if creating projects is
>>> among
>>> them)
>>> sfussenegger (no permissions so far)
>>>
>>>
>> Could you try if it's possible? I think it should be on svn, but not
>> sure on team-city and jira
>>
>>> regards,
>>> Michael
>>>
>>> -----
>>> Michael Sparer
>>> http://talk-on-tech.blogspot.com
>>>
>>>
>> --
>> -Wicket for love
>>
>> Nino Martinez Wael
>> Java Specialist @ Jayway DK
>> http://www.jayway.dk
>> +45 2936 7684
>>
>>
>>
>>
>
>
> -----
> Michael Sparer
> http://talk-on-tech.blogspot.com
>
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
Re: New wicketstuff-dojo project
Posted by Michael Sparer <mi...@gmx.at>.
the components we're using in our projects have been ported to dojo 1.1 now,
including:
- FXOnClickFader
- FXOnClickSlider
- FXOnCliskWiper
- FXOnMouseOverFader
- DojoToaster
- Drag and Drop panels
all other components have been dropped and should be added one by one after
you diligent, highly motivated people porting the components you're using
;-)
Some API changes were unavoidable due to the new dojo version, and the
documentation of the classes is sometimes a bit spare and/or obsolete.
one major point:
the cometd-part of the wicketstuff-push project has been integrated. as the
push projects consists of about 20 classes and depends on dojo, it's, from
my point of view, best located in the same project (Rodolfo's gonna kill me
for that :-)).
so it's basically ready to be shared with the community. in the current
structure the way to go is creating a new wicketstuff project, isn't it?
so we'd have in trunk:
- wicketstuff-dojo (for dojo 0.4)
- wicketstuff-dojo-1.1 (for dojo 1.1 - including push)
- wicketstuff-push (for dojo 1.1. with its own dojo distribution contained)
and in branches
- wicketstuff-push (for dojo 0.4 before Rodolfo's major refactoring)
that makes the already confusing wicketstuff even more confusing doesn't it?
shouldn't we consider merging some projects?
another problem might be to find the above mentioned motivated people ...
so if it's ok to share it as new wicketstuff project we'll go about starting
a (short) wiki page explaining the differences and API changes and then
posting message to the user list for motivated people.
what do you think?
Nino.Martinez wrote:
>
> +1, and i'll even try to help when I have time:) I think I could make my
> ajax loading tooltip in there:)
>
> Michael Sparer wrote:
>> After the update of wicketstuff-push (see
>> http://www.nabble.com/wicketstuff-push-update-to18765345.html) the
>> question
>> came up if the push project shouldn't depend on the dojo project any
>> longer
>> as ws-dojo uses dojo 0.4 and the new cometd implementation requires dojo
>> 1.x.
>>
>> Rodolfo Hansen, who volunteered to do the upgrade to the latest cometd
>> version, suggested to let wicketstuff-push cease to depend on ws-dojo. In
>> our current project, we're using both ws-dojo and ws-push. We really
>> would
>> like to use the latest cometd release; we can't bear, however, the idea
>> of
>> having two different dojo versions in the classpath - so we thought about
>> lifting ws-dojo to 1.1.
>>
>> As Rodolfo mentioned, lifting ws-dojo to 1.1 isn't trivial due to
>> incompatibilities (i.e. API changes) between 0.4 and 0.9. However, we
>> think
>> that lifting the ws-dojo project as a whole (with its dozens of
>> components)
>> isn't necessary. We'd propose to start with ws-dojo's core functionality
>> -
>> which is providing dojo resources and build facilites - and lift
>> components
>> as needed.
>>
>> We already managed to get the latest dojo release in and port some
>> components, but there's still a lot of work to be done. Therefore we
>> suggest
>> to make a new project for wicketstuff-dojo with dojo 1.1 and rely on some
>> helping hands who port the components they use to dojo 1.1.
>>
>> As for wicketstuff-push we still hope we can convince Rodolfo to keep the
>> dependency to (the then new) wicketstuff-dojo-1.1
>>
>> So what do you, wicketeers, think about that?
>>
>> If it's alright, our sf.net accounts are the following:
>> msparer (i already got some permissions, dunno if creating projects is
>> among
>> them)
>> sfussenegger (no permissions so far)
>>
> Could you try if it's possible? I think it should be on svn, but not
> sure on team-city and jira
>> regards,
>> Michael
>>
>> -----
>> Michael Sparer
>> http://talk-on-tech.blogspot.com
>>
>
> --
> -Wicket for love
>
> Nino Martinez Wael
> Java Specialist @ Jayway DK
> http://www.jayway.dk
> +45 2936 7684
>
>
>
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
View this message in context: http://www.nabble.com/New-wicketstuff-dojo-project-tp19070145p19196057.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: New wicketstuff-dojo project
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
+1, and i'll even try to help when I have time:) I think I could make my
ajax loading tooltip in there:)
Michael Sparer wrote:
> After the update of wicketstuff-push (see
> http://www.nabble.com/wicketstuff-push-update-to18765345.html) the question
> came up if the push project shouldn't depend on the dojo project any longer
> as ws-dojo uses dojo 0.4 and the new cometd implementation requires dojo
> 1.x.
>
> Rodolfo Hansen, who volunteered to do the upgrade to the latest cometd
> version, suggested to let wicketstuff-push cease to depend on ws-dojo. In
> our current project, we're using both ws-dojo and ws-push. We really would
> like to use the latest cometd release; we can't bear, however, the idea of
> having two different dojo versions in the classpath - so we thought about
> lifting ws-dojo to 1.1.
>
> As Rodolfo mentioned, lifting ws-dojo to 1.1 isn't trivial due to
> incompatibilities (i.e. API changes) between 0.4 and 0.9. However, we think
> that lifting the ws-dojo project as a whole (with its dozens of components)
> isn't necessary. We'd propose to start with ws-dojo's core functionality -
> which is providing dojo resources and build facilites - and lift components
> as needed.
>
> We already managed to get the latest dojo release in and port some
> components, but there's still a lot of work to be done. Therefore we suggest
> to make a new project for wicketstuff-dojo with dojo 1.1 and rely on some
> helping hands who port the components they use to dojo 1.1.
>
> As for wicketstuff-push we still hope we can convince Rodolfo to keep the
> dependency to (the then new) wicketstuff-dojo-1.1
>
> So what do you, wicketeers, think about that?
>
> If it's alright, our sf.net accounts are the following:
> msparer (i already got some permissions, dunno if creating projects is among
> them)
> sfussenegger (no permissions so far)
>
Could you try if it's possible? I think it should be on svn, but not
sure on team-city and jira
> regards,
> Michael
>
> -----
> Michael Sparer
> http://talk-on-tech.blogspot.com
>
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
RE: New wicketstuff-dojo project
Posted by Stefan Lindner <li...@visionet.de>.
The current wicketstuff dojo project seems to be no longer supported? I
wrote some emails to the listed project maintainers but I received only
one reply with no further plan on this project. Sooner or later the
current wicketstuff dojo will stop to work with wicket 1.4/1.5.
So I definitely prefer to have a new attempt wit dojo 1.1 that is
maintained and up-to-date.
Stefan
Re: New wicketstuff-dojo project
Posted by Stefan Fußenegger <st...@gmx.at>.
see
http://www.nabble.com/Dojo-1.1-integration-available-from-wicketstuff-to20625220.html
Michael Sparer wrote:
>
> After the update of wicketstuff-push (see
> http://www.nabble.com/wicketstuff-push-update-to18765345.html) the
> question came up if the push project shouldn't depend on the dojo project
> any longer as ws-dojo uses dojo 0.4 and the new cometd implementation
> requires dojo 1.x.
>
> Rodolfo Hansen, who volunteered to do the upgrade to the latest cometd
> version, suggested to let wicketstuff-push cease to depend on ws-dojo. In
> our current project, we're using both ws-dojo and ws-push. We really would
> like to use the latest cometd release; we can't bear, however, the idea of
> having two different dojo versions in the classpath - so we thought about
> lifting ws-dojo to 1.1.
>
> As Rodolfo mentioned, lifting ws-dojo to 1.1 isn't trivial due to
> incompatibilities (i.e. API changes) between 0.4 and 0.9. However, we
> think that lifting the ws-dojo project as a whole (with its dozens of
> components) isn't necessary. We'd propose to start with ws-dojo's core
> functionality - which is providing dojo resources and build facilites -
> and lift components as needed.
>
> We already managed to get the latest dojo release in and port some
> components, but there's still a lot of work to be done. Therefore we
> suggest to make a new project for wicketstuff-dojo with dojo 1.1 and rely
> on some helping hands who port the components they use to dojo 1.1.
>
> As for wicketstuff-push we still hope we can convince Rodolfo to keep the
> dependency to (the then new) wicketstuff-dojo-1.1
>
> So what do you, wicketeers, think about that?
>
> If it's alright, our sf.net accounts are the following:
> msparer (i already got some permissions, dunno if creating projects is
> among them)
> sfussenegger (no permissions so far)
>
> regards,
> Michael
>
-----
-------
Stefan Fußenegger
http://talk-on-tech.blogspot.com // looking for a nicer domain ;)
--
View this message in context: http://www.nabble.com/New-wicketstuff-dojo-project-tp19070145p20625326.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.