+1 from me too.
I still think it is important that we finish the web UI we are
currently working on, so that we will have one UI out of the box.
/Anne
On 27. juli. 2009, at 17.34, Mrinal Wadhwa wrote:
Ethan,
I am very much in favor of that approach ... I had written about
this in an
I believe it's fixed.
It seemed to be a problem with Scala's pattern matching of nested case
classes.
On Sun, Jul 26, 2009 at 11:51 PM, Vassil Dichev vdic...@apache.org wrote:
Can you provide the whole stack trace and perhaps open a bug in Lift at
http://github.com/dpp/liftweb/issues
I
Ethan,
We've had an Air client since day 1 and have all the APIs to support the AIR
client (other than user authentication). What APIs are missing for your YQL
version?
Thanks,
David
On Mon, Jul 27, 2009 at 8:02 AM, Ethan Jewett esjew...@gmail.com wrote:
It sounds like the project has been
On Tue, Jul 28, 2009 at 4:51 PM, Mrinal Wadhwa mrinal.wad...@gmail.comwrote:
David,
I wasn't aware we already had calls for conversations, actions and pools
...
There should be calls for conversations and actions. Pools are new, so
there may not be calls for those.
just saw them, are
thanks
On Wed, Jul 29, 2009 at 5:23 AM, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Tue, Jul 28, 2009 at 4:51 PM, Mrinal Wadhwa mrinal.wad...@gmail.com
wrote:
David,
I wasn't aware we already had calls for conversations, actions and pools
...
There should be calls for
Hey David,
I don't think anything is missing for the YQL client, but I have the feeling
that as more people start developing on top of the API directly we'll start
to see ways to improve it, be that to make it more RESTful as was discussed
previously, or something else we haven't thought of yet.
