|
Author
|
Message
|
|
Xavier Dutoit
|
Monday 24 September 2007 12:11:45 am
Cool, Add yourself to the project and feel free to share with the others ;) X+ P.S. As you've seen, they are only a few options (fetch node and fetch children), with a few parameters about how many content you want to fetch (just the node, the attributes, the owner). I'm fully aware we need more fetch functions (tree, with include limitation...), and I gladly welcome your additions !
http://www.sydesy.com
|
|
Paul Forsyth
|
Friday 02 November 2007 4:40:43 am
Hi Andre, Quick question about how JSON is used within eZ. Is it now officially adopted by eZ? Im deciding at the moment about dropping support for XAJAX and going JSON with various pieces of work i have on my plate. Thanks, Paul
|
|
Paul Borgermans
|
Friday 02 November 2007 5:44:23 am
Hi Paul, Both approaches have partly a different scope: xajax is easy to expose kernel/your php classes and functions to Javascript, JSON is more a data transport mechanism With eZ Publish 4.x, expect more JSON use ... so you can say we adopt it indeed. Regards Paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Paul Forsyth
|
Friday 02 November 2007 6:01:54 am
Thanks Paul, I'll test this out locally to see if our simple xajax scripts are as simple with json, with xavier's extension. I've really enjoyed using xajax as no-fuss method of ajax-ing with eZ. Paul
|
|
Xavier Dutoit
|
Monday 05 November 2007 12:44:28 am
Hi, Have a look at json/explorer Simple exemple of fetching json datas as the server, template process them on the client side and display them. X+
http://www.sydesy.com
|
|
Gaetano Giunta
|
Sunday 26 April 2009 10:48:53 am
For a 100% template-based approach to json, look into ggxmlview extension on projects.ez.no, too
Principal Consultant International Business
Member of the Community Project Board
|
