The only possible thing that one could do would need two aspects: 1. The lift side to produce particular JSON 2. The capp side to consume said JSON
Without a full "package", there aren't really any integration points as we have already got comet working with capp so the only thing remaining is overall user implementation experience. Cheers, Tim On 10 Mar 2010, at 09:40, Mads Hartmann Jensen wrote: > +1 for cappuccino > > Played around with it a while back - it's pretty amazing. > > What kind of intergration are we talking about? I wouldn't mind taking a look > at intergrating cappuccino. > > On 10/03/2010, at 10.37, Indrajit Raychaudhuri wrote: > >> ExtCore is MIT Licensed and a candidate for JSArtifacts impl [1]. >> I started dabbling with an implementation of ExtCoreArtifacts sometime >> back, but didn't have enough bandwidth to carry it forward. >> >> In case somebody is willing to run with this, there is a ticket for >> this already [2] >> >> Non ExtCore are GPLed and doesn't mix conveniently. Although there are >> some exceptions, I am not sure how practically that works license wise >> [3]. >> >> Cheers, Indrajit >> >> [1] http://www.extjs.com/products/extcore/ >> [2] http://www.assembla.com/spaces/liftweb/tickets/132 >> [3] http://www.extjs.com/products/floss-exception.php >> >> >> On Wed, Mar 10, 2010 at 1:55 PM, Marius <marius.dan...@gmail.com> wrote: >>> >>> Please see here >>> http://groups.google.com/group/liftweb/browse_thread/thread/5e4f5e424d33db40/32cccccfb6752954?lnk=gst&q=ExtJs#32cccccfb6752954 >>> >>> I'd strongly encourage you to integrate ExtJs with Lift and >>> potentially other frameworks. Depending on JS library licence we'd be >>> happy to have integrations with other JS frameworks. >>> >>> JsArtifacts should provide you the necessary abstractions for such >>> integrations but if you run into problems, please let us know. >>> >>> On Mar 10, 8:27 am, Jim Barrows <jim.barr...@gmail.com> wrote: >>>> On Tue, Mar 9, 2010 at 8:45 PM, aw <anth...@whitford.com> wrote: >>>>> It is time for me to add some serious widgets to my lift app. >>>> >>>>> So far, I am most enamored by ExtJS. >>>>> Another alternative could possibly be ZK. >>>> >>>>> Does anybody have any experience with these frameworks? Can you >>>>> comment on why integrating them with Scala/Lift would be a bad idea >>>>> (or not work)? >>>> >>>>> I searched for some historical posts on ExtJS and discovered some >>>>> threads about it's license and how it impacts inclusion in the lift >>>>> framework. Would a commercial license prohibit it from being a lift- >>>>> widget submodule candidate? >>>> >>>>> Does anybody have a better suggestion that you think can compete with >>>>> ExtJS? >>>> >>>> I'm using ExtJS in anger at 0rk. 3.1.1 is nice. 3.0.0 is weird. Some odd >>>> bugs being reported. We're also getting some weird interactions with some >>>> other js libraries ( I won't mention it, it's not available anymore, and if >>>> it was it just leave you scarred) and CSS. However, that's the other >>>> libraries fault more then ExtJS's. >>>> >>>> If you want something that looks and feels as close to a desktop app as you >>>> can get.. ExtJS can do the job well. With Lift providing the JSON, it >>>> would >>>> be hard to go wrong. That said.. ExtJS is not an easy beast to learn. >>>> It's >>>> even worse to try and L10N it easily. I would not try and use just pieces >>>> of it, it's really not designed to do that. It seems to me to be an all or >>>> nothing approach. That's not say you can't use it piecemeal, I think you >>>> lose a lot of flexibility (especially in layout) that way. >>>> >>>> I wouldn't use it if left to my own devices though, unless I had a >>>> requirement for a desktop app on the web. It's serious overkill. >>>> >>>> -- >>>> James A Barrows >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Lift" group. >>> To post to this group, send email to lift...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> liftweb+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/liftweb?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Lift" group. >> To post to this group, send email to lift...@googlegroups.com. >> To unsubscribe from this group, send email to >> liftweb+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/liftweb?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@googlegroups.com. > To unsubscribe from this group, send email to > liftweb+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
