CDDB extension - content structure layout

Next topic

Author	Message
Kristof Coomans	Thursday 08 June 2006 10:37:37 am Hi guys Some of you probably have read I'm working on an extension to import CDDB disc info into eZ publish. I'd like to know how you would structure this disc info into the eZ publish content tree. Would you use seperate disc - track objects or put it all in one class? You can view a little example of the disc info I get from freedb at http://blog.coomanskristof.be/wp-content/uploads/2006/06/cddb.jpg. Thanks in advance! independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Łukasz Serwatka	Thursday 08 June 2006 1:25:54 pm Hi Kristof, Presented view looks very nice. How you solved searching for track which exists on several discs? disc - track variant will be more flexible. Disc as parent object and tracks as children. Import should use browse mode for better navigation in content structure where you want to place it. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Xavier Dutoit	Thursday 08 June 2006 11:52:32 pm Hi, I guess it depends on what you want to do with it. This being said, one of the nice things about MP3s is that we focus more on each track individualy (I'm listing to "so what"), and not on the track as an item of the disk (pre MP3, it was track #1 of "kind of blue"). I think that's likely that each track is going to live it's own life, independant of the album. Having different nodes for each track would is things like creating your own compliations and so on. X+ P.S. Replacing Miles by Tool works as well for my example ;) http://www.sydesy.com
Kristof Coomans	Sunday 11 June 2006 2:21:00 am Hi guys Thanks for your input! What would you do with the track offsets? Should they all be stored in the disc object, or in the track object? Or should I just drop them? What if I have 2 or more discs with exactly the same song? Would you use the same track object again with an additional node location? independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Kristof Coomans	Friday 28 July 2006 9:29:38 am Hi guys, me again :-) To make my online disc collection more attractive, I'd also like to display the cover images. I started playing with the Amazon SOAP webservice (using nusoap, currently only a CLI script). I'm already able to search for items and retrieve metadata and images. Now my question is: do you see any way to make a generally useable eZ publish extension out of this? It could be of use for other products as well (DVD's, ...). Xavier, you have written something to query Amazon and Google in the past ( http://ez.no/community/forum/developer/include_google_search )? Does this only integrate in the search module? independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Xavier Dutoit	Thursday 03 August 2006 1:27:00 pm Hi Kristof, In the past as you say ;) I integrated it with Amazon, google search and some wether report service.The weather isn't about search, but the two other where. Contact me if you want more detail, that's kind of a long time ago ;) X+ http://www.sydesy.com
Xavier Dutoit	Thursday 03 August 2006 1:30:09 pm Hi, I'd say that you can use the priority of the children as the track number. X+ http://www.sydesy.com

eZ debug

Timing:	Jan 18 2025 20:52:04
Script start
Timing:	Jan 18 2025 20:52:04
Module start 'layout'
Timing:	Jan 18 2025 20:52:04
Module start 'content'
Timing:	Jan 18 2025 20:52:05
Module end 'content'
Timing:	Jan 18 2025 20:52:05
Script end

Main resources:

Total runtime	0.7763 sec
Peak memory usage	4,096.0000 KB
Database Queries	71

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0051	589.1484	152.6406
Module start 'layout'	0.0051	0.0036	741.7891	39.4766
Module start 'content'	0.0087	0.7656	781.2656	632.5625
Module end 'content'	0.7742	0.0020	1,413.8281	20.1250
Script end	0.7762		1,433.9531

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0037	0.4720	16	0.0002
Check MTime	0.0015	0.1876	16	0.0001
Mysql Total
Database connection	0.0006	0.0830	1	0.0006
Mysqli_queries	0.7000	90.1687	71	0.0099
Looping result	0.0011	0.1361	69	0.0000
Template Total	0.7448	95.9	2	0.3724
Template load	0.0021	0.2692	2	0.0010
Template processing	0.7426	95.6648	2	0.3713
Template load and register function	0.0001	0.0120	1	0.0001
states
state_id_array	0.0009	0.1210	1	0.0009
state_identifier_array	0.0009	0.1136	2	0.0004
Override
Cache load	0.0018	0.2340	42	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0759	3	0.0002
Fetch class attribute name	0.0020	0.2535	10	0.0002
XML
Image XML parsing	0.0015	0.1954	3	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0041	14	0.0000
General
dbfile	0.0014	0.1838	30	0.0000
String conversion	0.0000	0.0009	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
7	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
7	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 23 Number of unique templates used: 5

Time used to render debug report: 0.0002 secs