|
»
New Extjs Ext.Direct
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 - 3 | Next > |
 |
New Extjs Ext.Direct
by Damian del Rivero L.
::
Rate this Message:
Hi there,
just wondering if you guys have seen this work from the Extjs team. http://extjs.com/blog/2009/05/13/introducing-ext-direct/ http://extjs.com/products/extjs/direct.php A platform and language agnostic technology to remote server-side methods to the client-side, how do you compare this specification with DWR solution. Would it be a good idea to wrap DWR around this new Interface ? I think Ext.Direct is a good solution to integrate Ext with DWR in a standard way. there is a new java project going on google: http://code.google.com/p/extdirect4java/ Leave your comments. Greetings. Damian del Rivero |
|
|
Re: New Extjs Ext.Direct
by Nicolás Pace
::
Rate this Message:
On Wed, May 13, 2009 at 1:15 PM, ddelrivero@...
<ddelrivero@...> wrote: > Hi there, > > just wondering if you guys have seen this work from the Extjs team. > > http://extjs.com/blog/2009/05/13/introducing-ext-direct/ > http://extjs.com/products/extjs/direct.php > > A platform and language agnostic technology to remote server-side methods to > the client-side, how do you compare this > specification with DWR solution. Would it be a good idea to wrap DWR around > this new Interface ? I think Ext.Direct is a good solution to integrate Ext > with DWR in a standard way. Great news!! I've been using dwrproxy for some time, and it solves the problem. Despite that, it is alway a good thing to have alternatives. I'll be looking into it! Thanks Damian! -- Ing. Nicolás Pace http://www.linkedin.com/in/nickar/ http://www.jornadasdelsur.org.ar/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
|
|
|
Re: New Extjs Ext.Direct
by David Marginian-2
::
Rate this Message:
Thanks, I hadn't see this and it looks like an interesting project. A lot of it sounds very familiar (imitation is the best form of flattery Joe). From the documentation I think they have a long way to go before this is a viable competitor to DWR. In my mind DWR has always had two main strengths:
1) Leave your Java code as is - It looks like Ext.Direct will still require you to serialize your Java return types into JSON (I may be wrong). DWR does this for you. And DWR can handles custom types and even Interface arguments out of the box. All of this means you can leave your Java code as is and return Java objects from your methods allowing for greater reuse across contexts.
2) Integration with other libraries and handling of Java specific features - Spring is the big one for me, also annotations configuration, etc.
It looks like there are a lot of other limitations to Ext.Direct right now (only passing an array of arguments, etc.). I may be wrong about this so correct me if I am. I will certainly take a more serious look at this when I have some time.
2009/5/13 Nicolás Pace <nicopace@...>
|
|
|
Re: New Extjs Ext.Direct
by Nicolás Pace
::
Rate this Message:
On Wed, May 13, 2009 at 2:36 PM, David Marginian
<david@...> wrote: > Thanks, I hadn't see this and it looks like an interesting project. A lot > of it sounds very familiar (imitation is the best form of flattery > Joe). From the documentation I think they have a long way to go before this > is a viable competitor to DWR. In my mind DWR has always had two main > strengths: > > 1) Leave your Java code as is - It looks like Ext.Direct will still require > you to serialize your Java return types into JSON (I may be wrong). DWR > does this for you. And DWR can handles custom types and even Interface > arguments out of the box. All of this means you can leave your Java code as > is and return Java objects from your methods allowing for greater reuse > across contexts. > > 2) Integration with other libraries and handling of Java specific features - > Spring is the big one for me, also annotations configuration, etc. > > It looks like there are a lot of other limitations to Ext.Direct right now > (only passing an array of arguments, etc.). I may be wrong about this so > correct me if I am. I will certainly take a more serious look at this when > I have some time. > I think that Damian and I didn't see Ext.Direct as a threat to DWR, but to a way of integrating DWR functionality with an excelent Javscript Framework like ExtJS. DWR has walked a long way to be where it is now, and it really does very well what it does, so there is no need to replace it, but it is nice that other projects like ExtJS looking at DWR with good eyes, and trying to integrate it in some way. Regards, > > 2009/5/13 Nicolás Pace <nicopace@...> >> >> On Wed, May 13, 2009 at 1:15 PM, ddelrivero@... >> <ddelrivero@...> wrote: >> > Hi there, >> > >> > just wondering if you guys have seen this work from the Extjs team. >> > >> > http://extjs.com/blog/2009/05/13/introducing-ext-direct/ >> > http://extjs.com/products/extjs/direct.php >> > >> > A platform and language agnostic technology to remote server-side >> > methods to >> > the client-side, how do you compare this >> > specification with DWR solution. Would it be a good idea to wrap DWR >> > around >> > this new Interface ? I think Ext.Direct is a good solution to integrate >> > Ext >> > with DWR in a standard way. >> >> Great news!! >> I've been using dwrproxy for some time, and it solves the problem. >> Despite that, it is alway a good thing to have alternatives. >> I'll be looking into it! >> >> Thanks Damian! >> >> -- >> Ing. Nicolás Pace >> http://www.linkedin.com/in/nickar/ >> http://www.jornadasdelsur.org.ar/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> > > -- Ing. Nicolás Pace http://www.linkedin.com/in/nickar/ http://www.jornadasdelsur.org.ar/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: New Extjs Ext.Direct
by David Marginian-2
::
Rate this Message:
From what I read it appears to be a direct competitor and I am not sure what the integration points would be. They generate a client side interface (like DWR) to a generic server (java, php, etc.) replacing the dwr interface scripts and the dwr engine with Ext.Direct plumbing. If the interface scripts are not generated by DWR and DWR's engine is not used I am not exactly sure how the two can be used together. Perhaps Damian's idea - "maybe DWR could generate a js wrapper around Ext.Direct interface" is an option but at this point I see some limitations on the Ext.Direct side which would make doing this not make much sense (because DWR has more features, passing more than just array params, etc.).
2009/5/13 Nicolás Pace <nicopace@...>
|
|
|
Re: New Extjs Ext.Direct
by Nicolás Pace
::
Rate this Message:
On Wed, May 13, 2009 at 3:21 PM, David Marginian
<david@...> wrote: > From what I read it appears to be a direct competitor and I am not sure what > the integration points would be. They generate a client side interface > (like DWR) to a generic server (java, php, etc.) replacing the dwr interface > scripts and the dwr engine with Ext.Direct plumbing. If the interface > scripts are not generated by DWR and DWR's engine is not used I am not > exactly sure how the two can be used together. Perhaps Damian's idea - > "maybe DWR could generate a js wrapper around Ext.Direct interface" is an > option but at this point I see some limitations on the Ext.Direct side which > would make doing this not make much sense (because DWR has more features, > passing more than just array params, etc.). Perhaps it would be easy simply to port the actual DWR interface in EXTJS, DWRProxy, to EXTJS3 than trying to fit dwr on Ext.Direct interface or viseversa. Regards, > > > 2009/5/13 Nicolás Pace <nicopace@...> >> >> On Wed, May 13, 2009 at 2:36 PM, David Marginian >> <david@...> wrote: >> > Thanks, I hadn't see this and it looks like an interesting project. A >> > lot >> > of it sounds very familiar (imitation is the best form of flattery >> > Joe). From the documentation I think they have a long way to go before >> > this >> > is a viable competitor to DWR. In my mind DWR has always had two main >> > strengths: >> > >> > 1) Leave your Java code as is - It looks like Ext.Direct will still >> > require >> > you to serialize your Java return types into JSON (I may be wrong). DWR >> > does this for you. And DWR can handles custom types and even Interface >> > arguments out of the box. All of this means you can leave your Java >> > code as >> > is and return Java objects from your methods allowing for greater reuse >> > across contexts. >> > >> > 2) Integration with other libraries and handling of Java specific >> > features - >> > Spring is the big one for me, also annotations configuration, etc. >> > >> > It looks like there are a lot of other limitations to Ext.Direct right >> > now >> > (only passing an array of arguments, etc.). I may be wrong about this >> > so >> > correct me if I am. I will certainly take a more serious look at this >> > when >> > I have some time. >> > >> >> >> I think that Damian and I didn't see Ext.Direct as a threat to DWR, >> but to a way of integrating DWR functionality with an excelent >> Javscript Framework like ExtJS. >> DWR has walked a long way to be where it is now, and it really does >> very well what it does, so there is no need to replace it, but it is >> nice that other projects like ExtJS looking at DWR with good eyes, and >> trying to integrate it in some way. >> Regards, >> >> > >> > 2009/5/13 Nicolás Pace <nicopace@...> >> >> >> >> On Wed, May 13, 2009 at 1:15 PM, ddelrivero@... >> >> <ddelrivero@...> wrote: >> >> > Hi there, >> >> > >> >> > just wondering if you guys have seen this work from the Extjs team. >> >> > >> >> > http://extjs.com/blog/2009/05/13/introducing-ext-direct/ >> >> > http://extjs.com/products/extjs/direct.php >> >> > >> >> > A platform and language agnostic technology to remote server-side >> >> > methods to >> >> > the client-side, how do you compare this >> >> > specification with DWR solution. Would it be a good idea to wrap DWR >> >> > around >> >> > this new Interface ? I think Ext.Direct is a good solution to >> >> > integrate >> >> > Ext >> >> > with DWR in a standard way. >> >> >> >> Great news!! >> >> I've been using dwrproxy for some time, and it solves the problem. >> >> Despite that, it is alway a good thing to have alternatives. >> >> I'll be looking into it! >> >> >> >> Thanks Damian! >> >> >> >> -- >> >> Ing. Nicolás Pace >> >> http://www.linkedin.com/in/nickar/ >> >> http://www.jornadasdelsur.org.ar/ >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: users-unsubscribe@... >> >> For additional commands, e-mail: users-help@... >> >> >> > >> > >> >> >> >> -- >> Ing. Nicolás Pace >> http://www.linkedin.com/in/nickar/ >> http://www.jornadasdelsur.org.ar/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> > > -- Ing. Nicolás Pace http://www.linkedin.com/in/nickar/ http://www.jornadasdelsur.org.ar/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: New Extjs Ext.Direct
by David Marginian-2
::
Rate this Message:
I haven't used Extjs in about 6 months but when I did I never had to use the DWRProxy. I used a JsonReader and my call from DWR populated a ExtJS grid with absolutely no issues. So I never quite understood the importance of integration between the two (since they seem to play together nicely by default). I haven't looked at the proxy in detail so I am not certain to how it benefits especially now that DWR supports JSON 3.x - I just know I didn't need it and I was doing some pretty advanced stuff (nested data grids, etc.).
2009/5/13 Nicolás Pace <nicopace@...>
|
|
|
Re: New Extjs Ext.Direct
by Frank W. Zammetti
::
Rate this Message:
JsonReader simply converts JSON to a collection of Records, it doesn't
perform the Ajax call to get the JSON... you must have done the DWR call yourself and then passed the response along to JsonReader. That's certainly not too complex a way to go and generally will work great as you say. However, the benefit to DWRProxy is that you can configure a DataStore to use it and then only deal with the Ext JS data abstractions... you no longer need to use DWR directly and therefore you could swap out DWR without affecting all your other data-bound code. More importantly, you can use the Store's event model to do everything and not even have to think about what the server-side looks like underneath. I love DWR as much as the next guy, and I typically despise more levels of abstraction in any solution, but in this case it's a very nice abstraction frankly that makes your code a bit simpler and more logically structured while giving you some added flexibility... I've been involved in a very large and complex project using Ext JS and DWR for about a year now, plus writing an Ext JS book over the past six months, so I've dealt with this all quite a bit lately :) As for Ext.Direct, I think you're read is right, it winds up being a competitor to DWR. To the best of my knowledge though, they currently only provide a PHP-based back-end, although it's designed for others too. I'm not sure what I think of it yet to be honest... For me at least, if you're a Java shop then I'd still sitck with DWR... more robust security infrastructure, reverse AJAX support, etc, just overall a more mature offering... if you're a mixed shop and have bought into Ext JS completely though, maybe the story is a little different. I'm still checking it out myself, although I have zero notion of moving off DWR, just want to be informed. -- Frank W. Zammetti Author of "Practical Ext JS Projects with Gears" (coming soon) and "Practical Dojo Projects" and "Practical DWR 2 Projects" and "Practical JavaScript, DOM Scripting and Ajax Projects" and "Practical Ajax Projects with Java Technology" (For info: apress.com/book/search?searchterm=zammetti&act=search) All you could possibly want is here: zammetti.com On Wed, May 13, 2009 3:08 pm, David Marginian wrote: > I haven't used Extjs in about 6 months but when I did I never had to use > the > DWRProxy. I used a JsonReader and my call from DWR populated a ExtJS grid > with absolutely no issues. So I never quite understood the importance of > integration between the two (since they seem to play together nicely by > default). I haven't looked at the proxy in detail so I am not certain to > how it benefits especially now that DWR supports JSON 3.x - I just know I > didn't need it and I was doing some pretty advanced stuff (nested data > grids, etc.). > > 2009/5/13 Nicolás Pace <nicopace@...> > >> On Wed, May 13, 2009 at 3:21 PM, David Marginian >> <david@...> wrote: >> > From what I read it appears to be a direct competitor and I am not >> sure >> what >> > the integration points would be. They generate a client side >> interface >> > (like DWR) to a generic server (java, php, etc.) replacing the dwr >> interface >> > scripts and the dwr engine with Ext.Direct plumbing. If the interface >> > scripts are not generated by DWR and DWR's engine is not used I am not >> > exactly sure how the two can be used together. Perhaps Damian's idea >> - >> > "maybe DWR could generate a js wrapper around Ext.Direct interface" is >> an >> > option but at this point I see some limitations on the Ext.Direct side >> which >> > would make doing this not make much sense (because DWR has more >> features, >> > passing more than just array params, etc.). >> >> Perhaps it would be easy simply to port the actual DWR interface in >> EXTJS, DWRProxy, to EXTJS3 than trying to fit dwr on Ext.Direct >> interface or viseversa. >> Regards, >> >> > >> > >> > 2009/5/13 Nicolás Pace <nicopace@...> >> >> >> >> On Wed, May 13, 2009 at 2:36 PM, David Marginian >> >> <david@...> wrote: >> >> > Thanks, I hadn't see this and it looks like an interesting project. >> A >> >> > lot >> >> > of it sounds very familiar (imitation is the best form of flattery >> >> > Joe). From the documentation I think they have a long way to go >> before >> >> > this >> >> > is a viable competitor to DWR. In my mind DWR has always had two >> main >> >> > strengths: >> >> > >> >> > 1) Leave your Java code as is - It looks like Ext.Direct will still >> >> > require >> >> > you to serialize your Java return types into JSON (I may be wrong). >> DWR >> >> > does this for you. And DWR can handles custom types and even >> Interface >> >> > arguments out of the box. All of this means you can leave your >> Java >> >> > code as >> >> > is and return Java objects from your methods allowing for greater >> reuse >> >> > across contexts. >> >> > >> >> > 2) Integration with other libraries and handling of Java specific >> >> > features - >> >> > Spring is the big one for me, also annotations configuration, etc. >> >> > >> >> > It looks like there are a lot of other limitations to Ext.Direct >> right >> >> > now >> >> > (only passing an array of arguments, etc.). I may be wrong about >> this >> >> > so >> >> > correct me if I am. I will certainly take a more serious look at >> this >> >> > when >> >> > I have some time. >> >> > >> >> >> >> >> >> I think that Damian and I didn't see Ext.Direct as a threat to DWR, >> >> but to a way of integrating DWR functionality with an excelent >> >> Javscript Framework like ExtJS. >> >> DWR has walked a long way to be where it is now, and it really does >> >> very well what it does, so there is no need to replace it, but it is >> >> nice that other projects like ExtJS looking at DWR with good eyes, >> and >> >> trying to integrate it in some way. >> >> Regards, >> >> >> >> > >> >> > 2009/5/13 Nicolás Pace <nicopace@...> >> >> >> >> >> >> On Wed, May 13, 2009 at 1:15 PM, ddelrivero@... >> >> >> <ddelrivero@...> wrote: >> >> >> > Hi there, >> >> >> > >> >> >> > just wondering if you guys have seen this work from the Extjs >> team. >> >> >> > >> >> >> > http://extjs.com/blog/2009/05/13/introducing-ext-direct/ >> >> >> > http://extjs.com/products/extjs/direct.php >> >> >> > >> >> >> > A platform and language agnostic technology to remote >> server-side >> >> >> > methods to >> >> >> > the client-side, how do you compare this >> >> >> > specification with DWR solution. Would it be a good idea to wrap >> DWR >> >> >> > around >> >> >> > this new Interface ? I think Ext.Direct is a good solution to >> >> >> > integrate >> >> >> > Ext >> >> >> > with DWR in a standard way. >> >> >> >> >> >> Great news!! >> >> >> I've been using dwrproxy for some time, and it solves the problem. >> >> >> Despite that, it is alway a good thing to have alternatives. >> >> >> I'll be looking into it! >> >> >> >> >> >> Thanks Damian! >> >> >> >> >> >> -- >> >> >> Ing. Nicolás Pace >> >> >> http://www.linkedin.com/in/nickar/ >> >> >> http://www.jornadasdelsur.org.ar/ >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: users-unsubscribe@... >> >> >> For additional commands, e-mail: users-help@... >> >> >> >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Ing. Nicolás Pace >> >> http://www.linkedin.com/in/nickar/ >> >> http://www.jornadasdelsur.org.ar/ >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: users-unsubscribe@... >> >> For additional commands, e-mail: users-help@... >> >> >> > >> > >> >> >> >> -- >> Ing. Nicolás Pace >> http://www.linkedin.com/in/nickar/ >> http://www.jornadasdelsur.org.ar/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: New Extjs Ext.Direct
by David Marginian-2
::
Rate this Message:
Thanks for the excellent description Frank. That is kinda what I figured but as I said I haven't worked with ExtJS a lot.
On Wed, May 13, 2009 at 1:40 PM, Frank W. Zammetti <fzlists@...> wrote: JsonReader simply converts JSON to a collection of Records, it doesn't |
|
|
|
|
|
|
|
|
Re: New Extjs Ext.Direct
by David Marginian-2
::
Rate this Message:
Having ExtJS and DWR play together is not a problem. You guys can (and already do) use the proxy.
Having Ext.Direct and DWR play together is a whole different story. I just don't see what the benefit is if we already have seemless integration using the proxy. Especially since DWR's remoting abilities are much more mature and full featured (interface arguments, overloaded method, varargs methods, named parameters, etc., etc.).
On Wed, May 13, 2009 at 2:45 PM, ddelrivero@... <ddelrivero@...> wrote: Yes Frank, you said it right. |
|
|
Re: New Extjs Ext.Direct
by Frank W. Zammetti
::
Rate this Message:
I definitely agree with Dave... from looking at Ext.Direct, I don't see
how you *could* use DWR... it seems to me kind of like saying we'll make a motor cycle and a bicycle work together... err... what?!? :) They're basically two extremely similar modes of transportation and you pick one or the other, but not both at the same time. Frank -- Frank W. Zammetti Author of "Practical Ext JS Projects with Gears" (coming soon) and "Practical Dojo Projects" and "Practical DWR 2 Projects" and "Practical JavaScript, DOM Scripting and Ajax Projects" and "Practical Ajax Projects with Java Technology" (For info: apress.com/book/search?searchterm=zammetti&act=search) All you could possibly want is here: zammetti.com David Marginian wrote: > Having ExtJS and DWR play together is not a problem. You guys can > (and already do) use the proxy. > > Having Ext.Direct and DWR play together is a whole different story. I > just don't see what the benefit is if we already have seemless > integration using the proxy. Especially since DWR's remoting > abilities are much more mature and full featured (interface arguments, > overloaded method, varargs methods, named parameters, etc., etc.). > > On Wed, May 13, 2009 at 2:45 PM, ddelrivero@... > <mailto:ddelrivero@...> <ddelrivero@... > <mailto:ddelrivero@...>> wrote: > > Yes Frank, you said it right. > > Despite Ext.Direct is a direct DWR's competitor, I think we can > make them to coexist, and use DWR as the core server > infraestructure as it is now. Maturity and experience is what DWR > is all about. > > Damian del Rivero > > ------------------------------------------------------------------------ > *From*: "Frank W. Zammetti" <fzlists@... > <mailto:fzlists@...>> > *Sent*: Wednesday, May 13, 2009 3:11 PM > > *To*: users@... <mailto:users@...> > *Subject*: Re: [dwr-user] New Extjs Ext.Direct > > > JsonReader simply converts JSON to a collection of Records, it doesn't > perform the Ajax call to get the JSON... you must have done the > DWR call > yourself and then passed the response along to JsonReader. That's > certainly not too complex a way to go and generally will work > great as you > say. > > However, the benefit to DWRProxy is that you can configure a > DataStore to > use it and then only deal with the Ext JS data abstractions... you no > longer need to use DWR directly and therefore you could swap out DWR > without affecting all your other data-bound code. More > importantly, you > can use the Store's event model to do everything and not even have to > think about what the server-side looks like underneath. > > I love DWR as much as the next guy, and I typically despise more > levels of > abstraction in any solution, but in this case it's a very nice > abstraction > frankly that makes your code a bit simpler and more logically > structured > while giving you some added flexibility... I've been involved in a > very > large and complex project using Ext JS and DWR for about a year > now, plus > writing an Ext JS book over the past six months, so I've dealt > with this > all quite a bit lately :) > > As for Ext.Direct, I think you're read is right, it winds up being a > competitor to DWR. To the best of my knowledge though, they currently > only provide a PHP-based back-end, although it's designed for > others too. > I'm not sure what I think of it yet to be honest... For me at > least, if > you're a Java shop then I'd still sitck with DWR... more robust > security > infrastructure, reverse AJAX support, etc, just overall a more mature > offering... if you're a mixed shop and have bought into Ext JS > completely > though, maybe the story is a little different. I'm still checking > it out > myself, although I have zero notion of moving off DWR, just want to be > informed. > > -- > Frank W. Zammetti > Author of "Practical Ext JS Projects with Gears" (coming soon) > and "Practical Dojo Projects" > and "Practical DWR 2 Projects" > and "Practical JavaScript, DOM Scripting and Ajax Projects" > and "Practical Ajax Projects with Java Technology" > (For info: apress.com/book/search?searchterm=zammetti&act=search > <http://apress.com/book/search?searchterm=zammetti&act=search>) > All you could possibly want is here: zammetti.com > <http://zammetti.com/> > > On Wed, May 13, 2009 3:08 pm, David Marginian wrote: > > I haven't used Extjs in about 6 months but when I did I never > had to use > > the > > DWRProxy. I used a JsonReader and my call from DWR populated a > ExtJS grid > > with absolutely no issues. So I never quite understood the > importance of > > integration between the two (since they seem to play together > nicely by > > default). I haven't looked at the proxy in detail so I am not > certain to > > how it benefits especially now that DWR supports JSON 3.x - I > just know I > > didn't need it and I was doing some pretty advanced stuff > (nested data > > grids, etc.). > > > > 2009/5/13 Nicolás Pace > > > >> On Wed, May 13, 2009 at 3:21 PM, David Marginian > >> wrote: > >> > From what I read it appears to be a direct competitor and I > am not > >> sure > >> what > >> > the integration points would be. They generate a client side > >> interface > >> > (like DWR) to a generic server (java, php, etc.) replacing > the dwr > >> interface > >> > scripts and the dwr engine with Ext.Direct plumbing. If the > interface > >> > scripts are not generated by DWR and DWR's engine is not used > I am not > >> > exactly sure how the two can be used together. Perhaps > Damian's idea > >> - > >> > "maybe DWR could generate a js wrapper around Ext.Direct > interface" is > >> an > >> > option but at this point I see some limitations on the > Ext.Direct side > >> which > >> > would make doing this not make much sense (because DWR has more > >> features, > >> > passing more than just array params, etc.). > >> > >> Perhaps it would be easy simply to port the actual DWR interface in > >> EXTJS, DWRProxy, to EXTJS3 than trying to fit dwr on Ext.Direct > >> interface or viseversa. > >> Regards, > >> > >> > > >> > > >> > 2009/5/13 Nicolás Pace > >> >> > >> >> On Wed, May 13, 2009 at 2:36 PM, David Marginian > >> >> wrote: > >> >> > Thanks, I hadn't see this and it looks like an interesting > project. > >> A > >> >> > lot > >> >> > of it sounds very familiar (imitation is the best form of > flattery > >> >> > Joe). From the documentation I think they have a long way > to go > >> before > >> >> > this > >> >> > is a viable competitor to DWR. In my mind DWR has always > had two > >> main > >> >> > strengths: > >> >> > > >> >> > 1) Leave your Java code as is - It looks like Ext.Direct > will still > >> >> > require > >> >> > you to serialize your Java return types into JSON (I may > be wrong). > >> DWR > >> >> > does this for you. And DWR can handles custom types and even > >> Interface > >> >> > arguments out of the box. All of this means you can leave your > >> Java > >> >> > code as > >> >> > is and return Java objects from your methods allowing for > greater > >> reuse > >> >> > across contexts. > >> >> > > >> >> > 2) Integration with other libraries and handling of Java > specific > >> >> > features - > >> >> > Spring is the big one for me, also annotations > configuration, etc. > >> >> > > >> >> > It looks like there are a lot of other limitations to > Ext.Direct > >> right > >> >> > now > >> >> > (only passing an array of arguments, etc.). I may be wrong > about > >> this > >> >> > so > >> >> > correct me if I am. I will certainly take a more serious > look at > >> this > >> >> > when > >> >> > I have some time. > >> >> > > >> >> > >> >> > >> >> I think that Damian and I didn't see Ext.Direct as a threat > to DWR, > >> >> but to a way of integrating DWR functionality with an excelent > >> >> Javscript Framework like ExtJS. > >> >> DWR has walked a long way to be where it is now, and it > really does > >> >> very well what it does, so there is no need to replace it, > but it is > >> >> nice that other projects like ExtJS looking at DWR with good > eyes, > >> and > >> >> trying to integrate it in some way. > >> >> Regards, > >> >> > >> >> > > >> >> > 2009/5/13 Nicolás Pace > >> >> >> > >> >> >> On Wed, May 13, 2009 at 1:15 PM, ddelrivero@... > <mailto:ddelrivero@...> > >> >> >> wrote: > >> >> >> > Hi there, > >> >> >> > > >> >> >> > just wondering if you guys have seen this work from the > Extjs > >> team. > >> >> >> > > >> >> >> > http://extjs.com/blog/2009/05/13/introducing-ext-direct/ > >> >> >> > http://extjs.com/products/extjs/direct.php > >> >> >> > > >> >> >> > A platform and language agnostic technology to remote > >> server-side > >> >> >> > methods to > >> >> >> > the client-side, how do you compare this > >> >> >> > specification with DWR solution. Would it be a good > idea to wrap > >> DWR > >> >> >> > around > >> >> >> > this new Interface ? I think Ext.Direct is a good > solution to > >> >> >> > integrate > >> >> >> > Ext > >> >> >> > with DWR in a standard way. > >> >> >> > >> >> >> Great news!! > >> >> >> I've been using dwrproxy for some time, and it solves the > problem. > >> >> >> Despite that, it is alway a good thing to have alternatives. > >> >> >> I'll be looking into it! > >> >> >> > >> >> >> Thanks Damian! > >> >> >> > >> >> >> -- > >> >> >> Ing. Nicolás Pace > >> >> >> http://www.linkedin.com/in/nickar/ > >> >> >> http://www.jornadasdelsur.org.ar/ > >> >> >> > >> >> >> > --------------------------------------------------------------------- > >> >> >> To unsubscribe, e-mail: > users-unsubscribe@... > <mailto:users-unsubscribe@...> > >> >> >> For additional commands, e-mail: > users-help@... <mailto:users-help@...> > >> >> >> > >> >> > > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> Ing. Nicolás Pace > >> >> http://www.linkedin.com/in/nickar/ > >> >> http://www.jornadasdelsur.org.ar/ > >> >> > >> >> > --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: users-unsubscribe@... > <mailto:users-unsubscribe@...> > >> >> For additional commands, e-mail: users-help@... > <mailto:users-help@...> > >> >> > >> > > >> > > >> > >> > >> > >> -- > >> Ing. Nicolás Pace > >> http://www.linkedin.com/in/nickar/ > >> http://www.jornadasdelsur.org.ar/ > >> > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscribe@... > <mailto:users-unsubscribe@...> > >> For additional commands, e-mail: users-help@... > <mailto:users-help@...> > >> > >> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > <mailto:users-unsubscribe@...> > For additional commands, e-mail: users-help@... > <mailto:users-help@...> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: New Extjs Ext.Direct
by Frank W. Zammetti
::
Rate this Message:
One thing worth mentioning is that there is currently no canonical DWRProxy, at least not that I'm aware of. It's always been just a solution people stumble upon foating around in the Ext JS forums for a particular problem... people tend to take that code and do with it what they will. For example, the project I referred to uses one particular version of the code from one particular forum thread (there's a couple different implementations) and then I hacked the hell out of it to better suit our needs, so it's essentially *another* new implementation :)
I think there's probably room for improvement in that proxy, and I for one would love to see a de facto standard implementation... I could even see taking what I've done and building upon it, once I'm done with my book and have a few spare cycles. Whether it's me or not, my code or not, that's something I'd definitely be in favor of, especially if it wound up in the official Ext JS or DWR distributions (I think you could argue it fits in either place). -- Frank W. Zammetti Author of "Practical Ext JS Projects with Gears" (coming soon) and "Practical Dojo Projects" and "Practical DWR 2 Projects" and "Practical JavaScript, DOM Scripting and Ajax Projects" and "Practical Ajax Projects with Java Technology" (For info: apress.com/book/search?searchterm=zammetti&act=search) All you could possibly want is here: zammetti.com ddelrivero@... wrote: > yes Nicolás you are right.. perhaps DWR shouldn't even try to > interface with Ext.Direct and just do some ports around a Data.Proxy, > and use DWR as it is now. DWR still has many advantages over > Ext.Direct, (you are not bound to any UI library). But I have to admit > that I love Extjs as my js ajax/effects/ui library > > Damian del Rivero > > ------------------------------------------------------------------------ > *From*: "Nicolás Pace" <nicopace@...> > *Sent*: Wednesday, May 13, 2009 2:02 PM > *To*: users@... > *Subject*: Re: [dwr-user] New Extjs Ext.Direct > > On Wed, May 13, 2009 at 3:21 PM, David Marginian > wrote: > > From what I read it appears to be a direct competitor and I am not > sure what > > the integration points would be. They generate a client side interface > > (like DWR) to a generic server (java, php, etc.) replacing the dwr > interface > > scripts and the dwr engine with Ext.Direct plumbing. If the interface > > scripts are not generated by DWR and DWR's engine is not used I am not > > exactly sure how the two can be used together. Perhaps Damian's idea - > > "maybe DWR could generate a js wrapper around Ext.Direct interface" > is an > > option but at this point I see some limitations on the Ext.Direct > side which > > would make doing this not make much sense (because DWR has more > features, > > passing more than just array params, etc.). > > Perhaps it would be easy simply to port the actual DWR interface in > EXTJS, DWRProxy, to EXTJS3 than trying to fit dwr on Ext.Direct > interface or viseversa. > Regards, > > > > > > > 2009/5/13 Nicolás Pace > >> > >> On Wed, May 13, 2009 at 2:36 PM, David Marginian > >> wrote: > >> > Thanks, I hadn't see this and it looks like an interesting > project. A > >> > lot > >> > of it sounds very familiar (imitation is the best form of flattery > >> > Joe). From the documentation I think they have a long way to go > before > >> > this > >> > is a viable competitor to DWR. In my mind DWR has always had two > main > >> > strengths: > >> > > >> > 1) Leave your Java code as is - It looks like Ext.Direct will still > >> > require > >> > you to serialize your Java return types into JSON (I may be > wrong). DWR > >> > does this for you. And DWR can handles custom types and even > Interface > >> > arguments out of the box. All of this means you can leave your Java > >> > code as > >> > is and return Java objects from your methods allowing for greater > reuse > >> > across contexts. > >> > > >> > 2) Integration with other libraries and handling of Java specific > >> > features - > >> > Spring is the big one for me, also annotations configuration, etc. > >> > > >> > It looks like there are a lot of other limitations to Ext.Direct > right > >> > now > >> > (only passing an array of arguments, etc.). I may be wrong about > this > >> > so > >> > correct me if I am. I will certainly take a more serious look at > this > >> > when > >> > I have some time. > >> > > >> > >> > >> I think that Damian and I didn't see Ext.Direct as a threat to DWR, > >> but to a way of integrating DWR functionality with an excelent > >> Javscript Framework like ExtJS. > >> DWR has walked a long way to be where it is now, and it really does > >> very well what it does, so there is no need to replace it, but it is > >> nice that other projects like ExtJS looking at DWR with good eyes, and > >> trying to integrate it in some way. > >> Regards, > >> > >> > > >> > 2009/5/13 Nicolás Pace > >> >> > >> >> On Wed, May 13, 2009 at 1:15 PM, ddelrivero@... > >> >> wrote: > >> >> > Hi there, > >> >> > > >> >> > just wondering if you guys have seen this work from the Extjs > team. > >> >> > > >> >> > http://extjs.com/blog/2009/05/13/introducing-ext-direct/ > >> >> > http://extjs.com/products/extjs/direct.php > >> >> > > >> >> > A platform and language agnostic technology to remote server-side > >> >> > methods to > >> >> > the client-side, how do you compare this > >> >> > specification with DWR solution. Would it be a good idea to > wrap DWR > >> >> > around > >> >> > this new Interface ? I think Ext.Direct is a good solution to > >> >> > integrate > >> >> > Ext > >> >> > with DWR in a standard way. > >> >> > >> >> Great news!! > >> >> I've been using dwrproxy for some time, and it solves the problem. > >> >> Despite that, it is alway a good thing to have alternatives. > >> >> I'll be looking into it! > >> >> > >> >> Thanks Damian! > >> >> > >> >> -- > >> >> Ing. Nicolás Pace > >> >> http://www.linkedin.com/in/nickar/ > >> >> http://www.jornadasdelsur.org.ar/ > >> >> > >> >> > --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: users-unsubscribe@... > >> >> For additional commands, e-mail: users-help@... > >> >> > >> > > >> > > >> > >> > >> > >> -- > >> Ing. Nicolás Pace > >> http://www.linkedin.com/in/nickar/ > >> http://www.jornadasdelsur.org.ar/ > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscribe@... > >> For additional commands, e-mail: users-help@... > >> > > > > > > > > -- > Ing. Nicolás Pace > http://www.linkedin.com/in/nickar/ > http://www.jornadasdelsur.org.ar/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: New Extjs Ext.Direct
by RJones1
::
Rate this Message:
I think unless Ext changes their license model, the DWRProxy would need to live in the Ext project. Remember once upon a time we started down this integration path and then they changed their license model at which point we said, no thanks. All that said I have not kept up with Ext since they made the change (and frainkly it annoyed me) so it maybe time to give another glance to see if the prior decision should still stand.
Randy ________________________________________ From: Frank W. Zammetti [fzlists@...] Sent: Wednesday, May 13, 2009 5:36 PM To: users@... Subject: Re: [dwr-user] New Extjs Ext.Direct One thing worth mentioning is that there is currently no canonical DWRProxy, at least not that I'm aware of. It's always been just a solution people stumble upon foating around in the Ext JS forums for a particular problem... people tend to take that code and do with it what they will. For example, the project I referred to uses one particular version of the code from one particular forum thread (there's a couple different implementations) and then I hacked the hell out of it to better suit our needs, so it's essentially *another* new implementation :) I think there's probably room for improvement in that proxy, and I for one would love to see a de facto standard implementation... I could even see taking what I've done and building upon it, once I'm done with my book and have a few spare cycles. Whether it's me or not, my code or not, that's something I'd definitely be in favor of, especially if it wound up in the official Ext JS or DWR distributions (I think you could argue it fits in either place). -- Frank W. Zammetti Author of "Practical Ext JS Projects with Gears" (coming soon) and "Practical Dojo Projects" and "Practical DWR 2 Projects" and "Practical JavaScript, DOM Scripting and Ajax Projects" and "Practical Ajax Projects with Java Technology" (For info: apress.com/book/search?searchterm=zammetti&act=search) All you could possibly want is here: zammetti.com ddelrivero@... wrote: > yes Nicolás you are right.. perhaps DWR shouldn't even try to > interface with Ext.Direct and just do some ports around a Data.Proxy, > and use DWR as it is now. DWR still has many advantages over > Ext.Direct, (you are not bound to any UI library). But I have to admit > that I love Extjs as my js ajax/effects/ui library > > Damian del Rivero > > ------------------------------------------------------------------------ > *From*: "Nicolás Pace" <nicopace@...> > *Sent*: Wednesday, May 13, 2009 2:02 PM > *To*: users@... > *Subject*: Re: [dwr-user] New Extjs Ext.Direct > > On Wed, May 13, 2009 at 3:21 PM, David Marginian > wrote: > > From what I read it appears to be a direct competitor and I am not > sure what > > the integration points would be. They generate a client side interface > > (like DWR) to a generic server (java, php, etc.) replacing the dwr > interface > > scripts and the dwr engine with Ext.Direct plumbing. If the interface > > scripts are not generated by DWR and DWR's engine is not used I am not > > exactly sure how the two can be used together. Perhaps Damian's idea - > > "maybe DWR could generate a js wrapper around Ext.Direct interface" > is an > > option but at this point I see some limitations on the Ext.Direct > side which > > would make doing this not make much sense (because DWR has more > features, > > passing more than just array params, etc.). > > Perhaps it would be easy simply to port the actual DWR interface in > EXTJS, DWRProxy, to EXTJS3 than trying to fit dwr on Ext.Direct > interface or viseversa. > Regards, > > > > > > > 2009/5/13 Nicolás Pace > >> > >> On Wed, May 13, 2009 at 2:36 PM, David Marginian > >> wrote: > >> > Thanks, I hadn't see this and it looks like an interesting > project. A > >> > lot > >> > of it sounds very familiar (imitation is the best form of flattery > >> > Joe). From the documentation I think they have a long way to go > before > >> > this > >> > is a viable competitor to DWR. In my mind DWR has always had two > main > >> > strengths: > >> > > >> > 1) Leave your Java code as is - It looks like Ext.Direct will still > >> > require > >> > you to serialize your Java return types into JSON (I may be > wrong). DWR > >> > does this for you. And DWR can handles custom types and even > Interface > >> > arguments out of the box. All of this means you can leave your Java > >> > code as > >> > is and return Java objects from your methods allowing for greater > reuse > >> > across contexts. > >> > > >> > 2) Integration with other libraries and handling of Java specific > >> > features - > >> > Spring is the big one for me, also annotations configuration, etc. > >> > > >> > It looks like there are a lot of other limitations to Ext.Direct > right > >> > now > >> > (only passing an array of arguments, etc.). I may be wrong about > this > >> > so > >> > correct me if I am. I will certainly take a more serious look at > this > >> > when > >> > I have some time. > >> > > >> > >> > >> I think that Damian and I didn't see Ext.Direct as a threat to DWR, > >> but to a way of integrating DWR functionality with an excelent > >> Javscript Framework like ExtJS. > >> DWR has walked a long way to be where it is now, and it really does > >> very well what it does, so there is no need to replace it, but it is > >> nice that other projects like ExtJS looking at DWR with good eyes, and > >> trying to integrate it in some way. > >> Regards, > >> > >> > > >> > 2009/5/13 Nicolás Pace > >> >> > >> >> On Wed, May 13, 2009 at 1:15 PM, ddelrivero@... > >> >> wrote: > >> >> > Hi there, > >> >> > > >> >> > just wondering if you guys have seen this work from the Extjs > team. > >> >> > > >> >> > http://extjs.com/blog/2009/05/13/introducing-ext-direct/ > >> >> > http://extjs.com/products/extjs/direct.php > >> >> > > >> >> > A platform and language agnostic technology to remote server-side > >> >> > methods to > >> >> > the client-side, how do you compare this > >> >> > specification with DWR solution. Would it be a good idea to > wrap DWR > >> >> > around > >> >> > this new Interface ? I think Ext.Direct is a good solution to > >> >> > integrate > >> >> > Ext > >> >> > with DWR in a standard way. > >> >> > >> >> Great news!! > >> >> I've been using dwrproxy for some time, and it solves the problem. > >> >> Despite that, it is alway a good thing to have alternatives. > >> >> I'll be looking into it! > >> >> > >> >> Thanks Damian! > >> >> > >> >> -- > >> >> Ing. Nicolás Pace > >> >> http://www.linkedin.com/in/nickar/ > >> >> http://www.jornadasdelsur.org.ar/ > >> >> > >> >> > --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: users-unsubscribe@... > >> >> For additional commands, e-mail: users-help@... > >> >> > >> > > >> > > >> > >> > >> > >> -- > >> Ing. Nicolás Pace > >> http://www.linkedin.com/in/nickar/ > >> http://www.jornadasdelsur.org.ar/ > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscribe@... > >> For additional commands, e-mail: users-help@... > >> > > > > > > > > -- > Ing. Nicolás Pace > http://www.linkedin.com/in/nickar/ > http://www.jornadasdelsur.org.ar/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: New Extjs Ext.Direct
by Frank W. Zammetti
::
Rate this Message:
With the usual IANAL disclaimer, my understanding is that there is a
FLOSS exception[1] for extensions that would allow you to distribute such a thing under a less restrictive license... but, even if you chose not to exercise that, you can always distribute the extension under GPL3[2] without any problem. I for one don't have a single issue putting something like this under the GPL (even though I might object if we were talking about a larger application). So, in short, it doesn't seem to me that licensing would be a concern at all. [1] http://extjs.com/products/ux-exception.php [2] http://extjs.com/products/license.php Frank -- Frank W. Zammetti Author of "Practical Ext JS Projects with Gears" (coming soon) and "Practical Dojo Projects" and "Practical DWR 2 Projects" and "Practical JavaScript, DOM Scripting and Ajax Projects" and "Practical Ajax Projects with Java Technology" (For info: apress.com/book/search?searchterm=zammetti&act=search) All you could possibly want is here: zammetti.com Randy Jones wrote: > I think unless Ext changes their license model, the DWRProxy would need to live in the Ext project. Remember once upon a time we started down this integration path and then they changed their license model at which point we said, no thanks. All that said I have not kept up with Ext since they made the change (and frainkly it annoyed me) so it maybe time to give another glance to see if the prior decision should still stand. > > Randy > > ________________________________________ > From: Frank W. Zammetti [fzlists@...] > Sent: Wednesday, May 13, 2009 5:36 PM > To: users@... > Subject: Re: [dwr-user] New Extjs Ext.Direct > > One thing worth mentioning is that there is currently no canonical DWRProxy, at least not that I'm aware of. It's always been just a solution people stumble upon foating around in the Ext JS forums for a particular problem... people tend to take that code and do with it what they will. For example, the project I referred to uses one particular version of the code from one particular forum thread (there's a couple different implementations) and then I hacked the hell out of it to better suit our needs, so it's essentially *another* new implementation :) > > I think there's probably room for improvement in that proxy, and I for one would love to see a de facto standard implementation... I could even see taking what I've done and building upon it, once I'm done with my book and have a few spare cycles. Whether it's me or not, my code or not, that's something I'd definitely be in favor of, especially if it wound up in the official Ext JS or DWR distributions (I think you could argue it fits in either place). > > -- > Frank W. Zammetti > Author of "Practical Ext JS Projects with Gears" (coming soon) > and "Practical Dojo Projects" > and "Practical DWR 2 Projects" > and "Practical JavaScript, DOM Scripting and Ajax Projects" > and "Practical Ajax Projects with Java Technology" > (For info: apress.com/book/search?searchterm=zammetti&act=search) > All you could possibly want is here: zammetti.com > > > ddelrivero@... wrote: > >> yes Nicolás you are right.. perhaps DWR shouldn't even try to >> interface with Ext.Direct and just do some ports around a Data.Proxy, >> and use DWR as it is now. DWR still has many advantages over >> Ext.Direct, (you are not bound to any UI library). But I have to admit >> that I love Extjs as my js ajax/effects/ui library >> >> Damian del Rivero >> >> ------------------------------------------------------------------------ >> *From*: "Nicolás Pace" <nicopace@...> >> *Sent*: Wednesday, May 13, 2009 2:02 PM >> *To*: users@... >> *Subject*: Re: [dwr-user] New Extjs Ext.Direct >> >> On Wed, May 13, 2009 at 3:21 PM, David Marginian >> wrote: >> >>> From what I read it appears to be a direct competitor and I am not >>> >> sure what >> >>> the integration points would be. They generate a client side interface >>> (like DWR) to a generic server (java, php, etc.) replacing the dwr >>> >> interface >> >>> scripts and the dwr engine with Ext.Direct plumbing. If the interface >>> scripts are not generated by DWR and DWR's engine is not used I am not >>> exactly sure how the two can be used together. Perhaps Damian's idea - >>> "maybe DWR could generate a js wrapper around Ext.Direct interface" >>> >> is an >> >>> option but at this point I see some limitations on the Ext.Direct >>> >> side which >> >>> would make doing this not make much sense (because DWR has more >>> >> features, >> >>> passing more than just array params, etc.). >>> >> Perhaps it would be easy simply to port the actual DWR interface in >> EXTJS, DWRProxy, to EXTJS3 than trying to fit dwr on Ext.Direct >> interface or viseversa. >> Regards, >> >> >>> 2009/5/13 Nicolás Pace >>> >>>> On Wed, May 13, 2009 at 2:36 PM, David Marginian >>>> wrote: >>>> >>>>> Thanks, I hadn't see this and it looks like an interesting >>>>> >> project. A >> >>>>> lot >>>>> of it sounds very familiar (imitation is the best form of flattery >>>>> Joe). From the documentation I think they have a long way to go >>>>> >> before >> >>>>> this >>>>> is a viable competitor to DWR. In my mind DWR has always had two >>>>> >> main >> >>>>> strengths: >>>>> >>>>> 1) Leave your Java code as is - It looks like Ext.Direct will still >>>>> require >>>>> you to serialize your Java return types into JSON (I may be >>>>> >> wrong). DWR >> >>>>> does this for you. And DWR can handles custom types and even >>>>> >> Interface >> >>>>> arguments out of the box. All of this means you can leave your Java >>>>> code as >>>>> is and return Java objects from your methods allowing for greater >>>>> >> reuse >> >>>>> across contexts. >>>>> >>>>> 2) Integration with other libraries and handling of Java specific >>>>> features - >>>>> Spring is the big one for me, also annotations configuration, etc. >>>>> >>>>> It looks like there are a lot of other limitations to Ext.Direct >>>>> >> right >> >>>>> now >>>>> (only passing an array of arguments, etc.). I may be wrong about >>>>> >> this >> >>>>> so >>>>> correct me if I am. I will certainly take a more serious look at >>>>> >> this >> >>>>> when >>>>> I have some time. >>>>> >>>>> >>>> I think that Damian and I didn't see Ext.Direct as a threat to DWR, >>>> but to a way of integrating DWR functionality with an excelent >>>> Javscript Framework like ExtJS. >>>> DWR has walked a long way to be where it is now, and it really does >>>> very well what it does, so there is no need to replace it, but it is >>>> nice that other projects like ExtJS looking at DWR with good eyes, and >>>> trying to integrate it in some way. >>>> Regards, >>>> >>>> >>>>> 2009/5/13 Nicolás Pace >>>>> >>>>>> On Wed, May 13, 2009 at 1:15 PM, ddelrivero@... >>>>>> wrote: >>>>>> >>>>>>> Hi there, >>>>>>> >>>>>>> just wondering if you guys have seen this work from the Extjs >>>>>>> >> team. >> >>>>>>> http://extjs.com/blog/2009/05/13/introducing-ext-direct/ >>>>>>> http://extjs.com/products/extjs/direct.php >>>>>>> >>>>>>> A platform and language agnostic technology to remote server-side >>>>>>> methods to >>>>>>> the client-side, how do you compare this >>>>>>> specification with DWR solution. Would it be a good idea to >>>>>>> >> wrap DWR >> >>>>>>> around >>>>>>> this new Interface ? I think Ext.Direct is a good solution to >>>>>>> integrate >>>>>>> Ext >>>>>>> with DWR in a standard way. >>>>>>> >>>>>> Great news!! >>>>>> I've been using dwrproxy for some time, and it solves the problem. >>>>>> Despite that, it is alway a good thing to have alternatives. >>>>>> I'll be looking into it! >>>>>> >>>>>> Thanks Damian! >>>>>> >>>>>> -- >>>>>> Ing. Nicolás Pace >>>>>> http://www.linkedin.com/in/nickar/ >>>>>> http://www.jornadasdelsur.org.ar/ >>>>>> >>>>>> >>>>>> >> --------------------------------------------------------------------- >> >>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>> For additional commands, e-mail: users-help@... >>>>>> >>>>>> >>>>> >>>> >>>> -- >>>> Ing. Nicolás Pace >>>> http://www.linkedin.com/in/nickar/ >>>> http://www.jornadasdelsur.org.ar/ >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>>> >>> >> >> -- >> Ing. Nicolás Pace >> http://www.linkedin.com/in/nickar/ >> http://www.jornadasdelsur.org.ar/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > > __________ Information from ESET Smart Security, version of virus signature database 4073 (20090513) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: New Extjs Ext.Direct
by davidmarginian
::
Rate this Message:
License issues or not my opinion here is to leave it out of DWR. My
reasoning is that writing and maintaining the proxy seems to involve more knowledge of ExtJS than DWR. Also, I think ExtJs is more likely to change in a way that will break the proxy. Unless of course, Frank will maintain it :). Frank W. Zammetti wrote: > With the usual IANAL disclaimer, my understanding is that there is a > FLOSS exception[1] for extensions that would allow you to distribute > such a thing under a less restrictive license... but, even if you > chose not to exercise that, you can always distribute the extension > under GPL3[2] without any problem. I for one don't have a single > issue putting something like this under the GPL (even though I might > object if we were talking about a larger application). > > So, in short, it doesn't seem to me that licensing would be a concern > at all. > > [1] http://extjs.com/products/ux-exception.php > [2] http://extjs.com/products/license.php > > Frank > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: New Extjs Ext.Direct
by Frank W. Zammetti
::
Rate this Message:
Hehe, I did kind of walk into that, didn't I :)
I certainly see you're point, and it's the same sort of question you're always led to ask in situations like this... one could slice it either way (putting it under Ext versus DWR) and I think there's valid arguments both ways... of course, I think the ideal solution might be that "DWR community extensions" sub-project that's been mentioned a couple of times... Ext already has that, so it could always go there too. In other words, no reason it has to ship with either (although I think there's benefit there if it does). Well, in any case, I just added it to my "projects to work on should I ever come to my senses and stop writing books" list :) Not really much sense debating where to put it when there's not really anything to put somewhere in the first place :) Frank -- Frank W. Zammetti Author of "Practical Ext JS Projects with Gears" (coming soon) and "Practical Dojo Projects" and "Practical DWR 2 Projects" and "Practical JavaScript, DOM Scripting and Ajax Projects" and "Practical Ajax Projects with Java Technology" (For info: apress.com/book/search?searchterm=zammetti&act=search) All you could possibly want is here: zammetti.com David Marginian wrote: > License issues or not my opinion here is to leave it out of DWR. My > reasoning is that writing and maintaining the proxy seems to involve > more knowledge of ExtJS than DWR. Also, I think ExtJs is more likely > to change in a way that will break the proxy. Unless of course, Frank > will maintain it :). > Frank W. Zammetti wrote: >> With the usual IANAL disclaimer, my understanding is that there is a >> FLOSS exception[1] for extensions that would allow you to distribute >> such a thing under a less restrictive license... but, even if you >> chose not to exercise that, you can always distribute the extension >> under GPL3[2] without any problem. I for one don't have a single >> issue putting something like this under the GPL (even though I might >> object if we were talking about a larger application). >> >> So, in short, it doesn't seem to me that licensing would be a concern >> at all. >> >> [1] http://extjs.com/products/ux-exception.php >> [2] http://extjs.com/products/license.php >> >> Frank >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > > __________ Information from ESET Smart Security, version of virus > signature database 4073 (20090513) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: New Extjs Ext.Direct
by mikewse
::
Rate this Message:
Frank W. Zammetti wrote:
> I think the ideal solution might be that "DWR community > extensions" sub-project that's been mentioned a couple > of times... Yes, it's a nice idea. It would need some structure to be able to differentiate between different projects' statuses, commiters, and cla availability, so there is some effort in making it happen. But I think it is something we could start thinking about. Best regards Mike --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| < Prev | 1 - 2 - 3 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
