eZ Components forum

«

Previous topic

|

|

Next topic

»

Author	Message
Piotrek Karaś	Wednesday 14 October 2009 1:34:21 am As eZ Components make it more and more into eZ Publish, I expect an increasing amount of eZC-related issues to be discussed in the eZ forum. Shouldn't re-opening of eZ Components forum be reconsidered? -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Łukasz Serwatka	Wednesday 14 October 2009 1:45:42 am Hi Piotrek, I raised that topic long time ago and It was decided by the eZ Components core development team to do not use ez.no forum as communication channel. The preferred way is eZ Components mailing list and that one is followed by eZ Components core developers. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Piotrek Karaś	Wednesday 14 October 2009 2:05:11 am Hello Łukasz, Yes, I am aware of that as I did ask the same question and didn't push anymore ;) Just wondering if putting more and more of eZC into eZP won't change the reality a bit... Cheers, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
James Pic	Wednesday 02 December 2009 5:09:51 am Django users have a site where they can share reuseable blocks of code or classes, they call those "snippets": http://www.djangosnippets.org/ I don't know if eZ Publish users would need it. It would certainly be usefull to have an "eZ Components Snippets" forum, because eZ Components is pretty low level and users usually end doing reuseable codes. It would be cool to have a place to share snippets of code. This would be even more valuable than Django snippets because new versions of eZ Components won't break compatibility ... What do you think? "Well, everyday we'll make it - we'll make it the best we can." Jack D.
Gaetano Giunta	Tuesday 23 February 2010 1:24:14 am Agree with Piotrek on this one - giving more visibility / easier access into the ezc can only be a good thing! 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 18 2025 04:28:53
Script start
Timing:	Jan 18 2025 04:28:53
Module start 'layout'
Timing:	Jan 18 2025 04:28:53
Module start 'content'
Timing:	Jan 18 2025 04:28:53
Module end 'content'
Timing:	Jan 18 2025 04:28:53
Script end

Main resources:

Total runtime	0.0159 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	587.8906	152.6094
Module start 'layout'	0.0057	0.0030	740.5000	39.4141
Module start 'content'	0.0087	0.0050	779.9141	93.3047
Module end 'content'	0.0137	0.0021	873.2188	38.3047
Script end	0.0159		911.5234

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	17.5546	14	0.0002
Check MTime	0.0013	8.2098	14	0.0001
Mysql Total
Database connection	0.0007	4.5653	1	0.0007
Mysqli_queries	0.0024	15.1484	3	0.0008
Looping result	0.0000	0.0943	1	0.0000
Template Total	0.0018	11.0	1	0.0018
Template load	0.0010	6.0537	1	0.0010
Template processing	0.0008	4.9052	1	0.0008
Override
Cache load	0.0007	4.3707	1	0.0007
General
dbfile	0.0002	1.3057	8	0.0000
String conversion	0.0000	0.0509	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.0001 secs