Bhavin Turakhia wrote:
> Some features that are REQUIRED
>
> - Staging - allowing to make changes and view them without publishing them
> on the website itself. i dont mean at articles and workflow level. i mean an
> entire staging copy viewable separately and allowing me to make changes for
> instance to a style an article a code-init section and see it without the
> fear that others online seeing my website rght now are also seeing it
Will be in Midgard 2.0
> - Caching - pages that have already been generated should not again result
> in processing of code-init, database queries and page generation. this would
> really speeden up things.
Already available via PHP output buffer mechanism (see
http://php.net/ob_start)
> - Versioning - with rollback and roll forward capabilities if possible
> (almost CVS like - infact we could call it Content Versioning System) :o)
Available on nadmin, will be part of Midgard 2.0 hopefully.
> - Other misc stuff
> * Allowing to put &(variablename:moniker) inside articles too. That helps
> big time atleast in my structure
possible if article is evaluated as PHP. eg. &(article.content:p);
> * Allowing to call a particular article's/topic's/style's/page's attributes
> within itself. For eg this is what I mean -
>
> An article has following fields
>
> title
> abstract
> extra1
> extra2
> extra3
> content
>
> Now the content is the main guy I use to display stuff. However in the
> content I have data thts repeated in the TITLE etc for instance
>
> TITLE: Midgard Rules
> CONTENT:
> <b>Midgard Rules</b>
> It is indeed no doubt that midgard is thebest
>
> Now abv would be better if i could do something like
> TITLE: Midgard Rules
> CONTENT:
> <b><[title]></b>
> It is indeed no doubt that midgard is thebest
>
> Thus the title would automatically be replaced by the TITLE of that
> particular article. This could be extended to parameters/topics etc etc.
> Thus changing the title attribute directly would also change all references
> to it.
already implemented with pages as is (only for title and author though),
but possible with any other object with &(article.title); syntax.
> * Referencing Articles the same way as the styles inside styles/pages
> An Article should be callable inside a style like <[article.articlename]> or
> something like that
This is possible with the php4 version using the :i formatter with the
&(); syntax (not documented yet).
in an element parsed *before*:
<?
$art = mgd_get_article_by_name($topicid, "myarticle");
$article["myarticle"] = "echo '<h1>$art->title</h1>$art->content';";
?>
in another element parsed *after*:
<p>&(article.myarticle:i);</p>
> * mgd_walk_topic_tree should have sort options for score - or best situation
> all sort options just like mgd_list_topics - i needed this desperately to
> create a hierarchial menu and had toprogram the whole thing myself
you can now specify sort parameters to mgd_walk_xxx_tree:
mgd_walk_xxx_tree(string func_name, int root, int maxlevel, mixed
&xparam, [int order, [string sort]]);
--
Best Regards,
David Guerizec Free Software Developer
Aurora R&D [EMAIL PROTECTED]
Midgard core developer http://www.midgard-project.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
