I'll let you know.  Having a good ExtJS + LIft story would be very handy
when I talk to the Grails fans in the office.


-Josh

On Mon, May 18, 2009 at 5:08 PM, David Pollak <feeder.of.the.be...@gmail.com
> wrote:

>
>
> On Mon, May 18, 2009 at 9:28 AM, Josh Suereth <joshua.suer...@gmail.com>wrote:
>
>> Is there a way for me to *know* the potential stateful snippets I could
>> call using the "lift_page" javascript variable?
>
>
> Actually, you're not calling stateful snippets, you're calling a Json
> handler.
>
> Please take a look at http://demo.liftweb.net/json_more
>
> This is an example of sending data from the UI via JavaScript calls and
> getting a callback when the server has processed the results.
>
> Does this help?
>
>
>
>>   Most of my views are completely in JavaScript, and my server calls can
>> take in any kind of data (JSON or raw parameters) and return JSON.  IF you
>> can point me at "the right way" to do this, I'll set up a demo sight showing
>> the style of web development we do at work.
>>
>> -Josh
>>
>>
>> On Mon, May 18, 2009 at 11:59 AM, David Pollak <
>> feeder.of.the.be...@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, May 18, 2009 at 6:02 AM, Josh Suereth 
>>> <joshua.suer...@gmail.com>wrote:
>>>
>>>> A question I've had is how hard would it be to support a ExtJS based
>>>> application (i.e. the server side only needs to be a remote JSON
>>>> framework).   I assume this would be just-as-difficult as providing a
>>>> REST-based API to your data.  We use ExtJS extensively at work, and there
>>>> are some pors/cons to having 90% of your UI code run inside the browser.  
>>>> In
>>>> our situation, the server-side controllers are doing very little (our
>>>> business tier is pretty robust and includes portions outside the scope of
>>>> any web framework).  Anyway, in my prototyping with lift, it was a very 
>>>> nice
>>>> AJAXy framework, but I could never determine how to unify the "ExtJS wants
>>>> me to program like X and Lift wants me to program like Y" bridge.  Not that
>>>> one excludes the other, but I was never sure if I was in the "sweet" spot.
>>>>
>>>> From what I could tell, 90% application would have lived in a bunch of
>>>> rewrite rules.  Can anyone fill me in on what I might have missed?
>>>
>>>
>>> Josh,
>>>
>>> It's actually brain-damaged simple to do JSON request handlers in Lift.
>>> See http://demo.liftweb.net/json
>>>
>>> You set up patterns to handle the incoming JSON requests.  Combining this
>>> with extractors makes things type-safe, secure, and very concise.
>>>
>>> If you need more, please let me know.
>>>
>>> Thanks,
>>>
>>> David
>>>
>>>
>>>>
>>>>
>>>> -Josh
>>>>
>>>>  On Sun, May 17, 2009 at 11:55 PM, David Pollak <
>>>> feeder.of.the.be...@gmail.com> wrote:
>>>>
>>>>> You can mix ExtJS into the project without any work at all.  If you
>>>>> want to use ExtJS exclusively, then you'll need to do the adapter thing so
>>>>> Lift knows how to communicate with the server (Ajax, Comet, etc.)
>>>>>
>>>>>
>>>>> On Sun, May 17, 2009 at 4:15 PM, Charles F. Munat <c...@munat.com>wrote:
>>>>>
>>>>>>
>>>>>> Wait. Is that right, guys? Does the LGC need JQuery or YUI?
>>>>>>
>>>>>> If not, then you only need to use an adapter and one of those if you
>>>>>> are
>>>>>> going to use the built-in Lift Js helper methods. So I guess it's
>>>>>> possible to use ExtJs 3.0 without any adapter if you're not going to
>>>>>> use
>>>>>> the helper methods.
>>>>>>
>>>>>> Sorry if I'm just confusing the issue. I am using ExtJs on a Lift site
>>>>>> with no problems (other than that ExtJs is a PITA).
>>>>>>
>>>>>> Chas.
>>>>>>
>>>>>> Charles F. Munat wrote:
>>>>>> > You'll need to use an adapter for either JQuery or YUI because the
>>>>>> Lift
>>>>>> > garbage collector depends on that.
>>>>>> >
>>>>>> > There are no Lift JS functions specific to ExtJs, but as you'll be
>>>>>> using
>>>>>> > either JQuery or YUI for the GC, you can use Lift's JQuery/YUI
>>>>>> helpers
>>>>>> > for non-ExtJs stuff. For things specific to ExtJs, you'll have to
>>>>>> build
>>>>>> > your own helpers, but you can probably just copy, paste, and modify
>>>>>> the
>>>>>> > others to get what you want.
>>>>>> >
>>>>>> > ExtJs probably can't be built into Lift because of licensing issues,
>>>>>> so
>>>>>> > you'll have to do some work for yourself.
>>>>>> >
>>>>>> > Chas.
>>>>>> >
>>>>>> > Jesse Eichar wrote:
>>>>>> >> Hi,
>>>>>> >>
>>>>>> >> I was wondering how plausible using ExtJS since Lift adds some Ajax
>>>>>> >> libraries.  ExtJS requires adapters to work nicely with others.  I
>>>>>> am
>>>>>> >> not sure if the adapters need to be ran with the specific version
>>>>>> of
>>>>>> >> (say YUI or JQuery) the library that is shipped with Ext or if the
>>>>>> >> adapters are enough by then selves.
>>>>>> >>
>>>>>> >> But really my question is:  Is it possible to use advanced ExtJS in
>>>>>> >> Lift?  And what would the recommended way be?
>>>>>> >>
>>>>>> >> Thanks,
>>>>>> >> Jesse
>>>>>> >>
>>>>>> >
>>>>>> > >
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lift, the simply functional web framework http://liftweb.net
>>>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>>>> Follow me: http://twitter.com/dpp
>>>>> Git some: http://github.com/dpp
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Lift, the simply functional web framework http://liftweb.net
>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>> Follow me: http://twitter.com/dpp
>>> Git some: http://github.com/dpp
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@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
-~----------~----~----~----~------~----~------~--~---

Reply via email to