JSON-view of any content object

«

Previous topic

|

|

Next topic

»

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

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 30 2025 19:50:48
Script start
Timing:	Jan 30 2025 19:50:48
Module start 'layout'
Timing:	Jan 30 2025 19:50:48
Module start 'content'
Timing:	Jan 30 2025 19:50:48
Module end 'content'
Timing:	Jan 30 2025 19:50:48
Script end

Main resources:

Total runtime	0.0246 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	588.6563	151.2109
Module start 'layout'	0.0053	0.0049	739.8672	221.1484
Module start 'content'	0.0102	0.0130	961.0156	1,002.0781
Module end 'content'	0.0231	0.0014	1,963.0938	37.9922
Script end	0.0245		2,001.0859

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	11.9550	14	0.0002
Check MTime	0.0010	4.2242	14	0.0001
Mysql Total
Database connection	0.0009	3.7600	1	0.0009
Mysqli_queries	0.0030	12.0715	3	0.0010
Looping result	0.0000	0.0689	1	0.0000
Template Total	0.0010	4.0	1	0.0010
Template load	0.0008	3.1356	1	0.0008
Template processing	0.0002	0.8681	1	0.0002
Override
Cache load	0.0005	2.2199	1	0.0005
General
dbfile	0.0012	4.8292	8	0.0001
String conversion	0.0000	0.0291	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0002 secs