Thanks, but what I wanted was a synthesis of where to put what and how would what be interpreted in where and under what conditions. That's why I listed every form field so that it would be easy for a replyer to just put his comments besides the fields and say, for example: "HTML there yes" "No php here" "only midgard here", etc...
Therefore, again : Topic -> Name (HTML?, Code?, Text? <[page/style element]>?) -> Description (HTML?, Code?, Text?<[page/style element]>?) -> Extra (HTML?, Code?, Text?<[page/style element]>?) -> Code (HTML?, Code?, Text?<[page/style element]>?) Article -> Extra1 (HTML?, Code?, Text?<[page/style element]>?) -> Extra2 (HTML?, Code?, Text?<[page/style element]>?) -> Extra3 (HTML?, Code?, Text?<[page/style element]>?) -> Abstract (HTML?, Code?, Text?<[page/style element]>?) -> Content (HTML?, Code?, Text?<[page/style element]>?) Page -> Content (HTML?, Code?, Text?<[page/style element]>?) Page Element ->Content (HTML?, Code?, Text?<[page element]>?) Style Element ->Content (HTML?, Code?, Text?<[style element]>?) ----- Original Message ----- From: "Pascal Van Hecke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, February 17, 2002 2:25 PM Subject: Re: [midgard-user] Programming the site : where to put code, text, HTML or page/style elements > > I would like to have a final status as to where code > > or HTML should go, as > > to what portion of the "article-topic-page-style > > element-page element" forms > > may have code, normal text, or HTML. > > > > So I would like an understanding and a final status > > regarding HTML, code, > > normal text and onto what goes where. Where can we > > put or refer to what. > > Underlying these questions is : I want to understand > > how the processing is > > performed on those different fields and I also want > > to understand what > > process executes what or parses what. > > Well, there's nothing to understand there, since you > yourself determine the process. As Sergei Sergei > Dolmatov pointed out in his reply, you can store > either text, html and php in your articles, and you > can use several format specifiers to display the > article content, abstract, title and so on in the > appropriate way: > http://www.midgard-project.org/manual/en/part.concepts.syntaxaddition.php > > As for the role of articles versus pages and styles, > the main idea is that the articles and topics > hierarchy contains pure content. Pages then > correspond to the different URLs in your site, and > contain code specific for that URL (can be code > extracting articles and topics in some way or another, > or a plain php web app), whereas styles contain both > html and php to define layout across several pages. > I suggest you start with the introductory articles on > http://www.webtechniques.com/archives/2000/05/jepson/ > and > http://www-106.ibm.com/developerworks/library/w-midgard/, > the authors did a really good job to make that > distinction clear. > regards, > pascal > > PS: I was at FOSDEM this weekend, were some of you as > well? > > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Sports - Coverage of the 2002 Olympic Games > http://sports.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
