Archetypes <-> TICLE
"Simon Pamies" <[email protected]> Tue, 07 Oct 2003 18:07:58 +0200
| Newsgroups | gmane.comp.web.zope.plone.collective.ticle |
|---|---|
| Message-ID | <[email protected]> |
--=====_106554287829611=_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable (taken from plone.org) some interesting comments from: http://plone.org/development/current/projects/ticle_folder/proposal#bottom for all those guys who did not notice them. Archetypes have References --zwork, Thu, 02 Oct 2003 05:16:11 -0500 reply Most of the requirements above are covered elegantly ba Archetypes. You can define Relations through ReferenceFields? in the Schema per Instance you can freely manage References through copy/paste inside the= references tab what has to be done there is the storage of additional information attached= to the relations You have a working UID machinery we have it running in customer projects Integration into Plone/Zope The possibility of code generation from UML diagrams a flexible storage model (including relational databases) Before writing everything from scratch think improving Archetypes towards regards phil Archetypes --hfroebe, Sun, 05 Oct 2003 12:05:42 -0500 reply From an end-users point of view, I strongly agree with Phil's arguments. To= my mind - as a webmaster working with different sites based on Zope/Plone= - Archetypes represents one of the "crown jewels" and makes development of= content/workflow applications a breeze - even for a developer newbie like= me. I'm conviced that integrating the concept/ideas of Placeless= Content/Ticle-Project into the Archetypes Reference Machinery would make a= good product even better. holger froebe Archetypes --spamies, Tue, 07 Oct 2003 11:09:05 -0500 reply I also agree basically with that view. But we have some goals that do not= match the way that the Archetypes.ReferenceEngine? is going: TICLE should deal with 1.000.000 objects and more - I do not think that the= Archetypes engine can do that The UID engine do not follow any standards - some of the developers= supporting TICLE absolutely want that feature The Archetype relations are not objects - that makes it difficult to add= clean m:n relations or even metadata on objects The engine itself should be useable without Zope/Plone. Archetypes are very= plonish Our approach: Implement that engine without using Zope Core Classes (only ZODB based) Programming Zope Layer Programming CMF/Plone Layer that uses Archetypes and perhaps extend that= wonderful Product. Perhaps we can map the ReferenceEngine? methods to the= TICLE engine. That will be the intergration into the Archetypes Reference= Engine.. --=====_106554287829611=_ Content-Type: text/html; charset="us-ascii" <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD> <BODY style="FONT-FAMILY: Arial" text=#000000 bgColor=#ffffff> <DIV>(taken from plone.org)<BR></DIV> <DIV>some interesting comments from: </DIV> <DIV> </DIV> <DIV><A href="http://plone.org/development/current/projects/ticle_folder/proposal#bottom">http://plone.org/development/current/projects/ticle_folder/proposal#bottom</A></DIV> <DIV> </DIV> <DIV>for all those guys who did not notice them.</DIV> <DIV><BR><STRONG>Archetypes have References</STRONG> --zwork, <A href="http://plone.org/development/current/projects/ticle_folder/proposal#[email protected]">Thu, 02 Oct 2003 05:16:11 -0500</A> <A href="http://plone.org/development/current/projects/ticle_folder/proposal?subject=Archetypes%20have%20References&in_reply_to=%3C20031002051611-0500%40plone.org%3E#bottom"><FONT color=#436976>reply</FONT></A><BR>Most of the requirements above are covered elegantly ba Archetypes.</DIV> <UL> <LI>You can define Relations <UL> <LI>through ReferenceFields<A class=new title="create this page" href="http://plone.org/development/current/projects/ticle_folder/proposal/editform?page=ReferenceFields"><FONT color=#436976>?</FONT></A> in the Schema <LI>per Instance you can freely manage References through copy/paste inside the <CODE><FONT style="BACKGROUND-COLOR: #dee7ec">references</FONT></CODE> tab </LI></UL> <P>what has to be done there is the storage of additional information attached to the relations</P> <LI>You have a working UID machinery <P>we have it running in customer projects</P> <LI>Integration into Plone/Zope <LI>The possibility of code generation from UML diagrams <LI>a flexible storage model (including relational databases) </LI></UL> <P>Before writing everything from scratch think improving Archetypes towards</P> <P>regards phil</P> <P><A [email protected]></A><IMG style="MARGIN: 0px; BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none" src="http://plone.org/development/current/projects/ticle_folder/discussionitem_icon.gif"><B>Archetypes</B> --hfroebe, <A href="http://plone.org/development/current/projects/ticle_folder/proposal#[email protected]">Sun, 05 Oct 2003 12:05:42 -0500</A> <A href="http://plone.org/development/current/projects/ticle_folder/proposal?subject=Archetypes&in_reply_to=%3C20031005120542-0500%40plone.org%3E#bottom">reply</A><BR>From an end-users point of view, I strongly agree with Phil's arguments. To my mind - as a webmaster working with different sites based on Zope/Plone - Archetypes represents one of the "crown jewels" and makes development of content/workflow applications a breeze - even for a developer newbie like me. </P> <P>I'm conviced that integrating the concept/ideas of Placeless Content/Ticle-Project into the Archetypes Reference Machinery would make a good product even better. </P> <P>holger froebe</P> <P><A [email protected]></A><IMG style="MARGIN: 0px; BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none" src="http://plone.org/development/current/projects/ticle_folder/discussionitem_icon.gif"><B>Archetypes</B> --spamies, <A href="http://plone.org/development/current/projects/ticle_folder/proposal#[email protected]">Tue, 07 Oct 2003 11:09:05 -0500</A> <A href="http://plone.org/development/current/projects/ticle_folder/proposal?subject=Archetypes&in_reply_to=%3C20031007110905-0500%40plone.org%3E#bottom"><FONT color=#436976>reply</FONT></A><BR>I also agree basically with that view. But we have some goals that do not match the way that the Archetypes.ReferenceEngine<A class=new title="create this page" href="http://plone.org/development/current/projects/ticle_folder/proposal/editform?page=ReferenceEngine"><FONT color=#436976>?</FONT></A> is going:</P> <UL> <LI>TICLE should deal with 1.000.000 objects and more - I do not think that the Archetypes engine can do that <LI>The UID engine do not follow any standards - some of the developers supporting TICLE absolutely want that feature <LI>The Archetype relations are not objects - that makes it difficult to add clean m:n relations or even metadata on objects <LI>The engine itself should be useable without Zope/Plone. Archetypes are very plonish </LI></UL> <P>Our approach: </P> <UL> <LI>Implement that engine without using Zope Core Classes (only ZODB based) <LI>Programming Zope Layer <LI>Programming CMF/Plone Layer that uses Archetypes and perhaps extend that wonderful Product. Perhaps we can map the ReferenceEngine<A class=new title="create this page" href="http://plone.org/development/current/projects/ticle_folder/proposal/editform?page=ReferenceEngine"><FONT color=#436976>?</FONT></A> methods to the TICLE engine. That will be the intergration into the Archetypes Reference Engine..</LI></UL></BODY></HTML> --=====_106554287829611=_-- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf