Hi Alexander
> David wrote:
> > Here is a piece of code I wrote for an intranet, I provide it "as is" to
> > feed the debate...
> > You can put it in the code-init element of an ACTIVE page, and you'll
need
> > the functions mgd_get_xxxx_by_name you can find at this url
> > (http://www.midgard-project.org/article/1420.html), or just wait for the
> > 1.2.6 release of midgard.
> Thank you, David! BTW, did you tested this snippet with Midgard
1.2.6-beta?
Unfortunatly, I just have a prod server, so I couldn't test any beta
version...
> Also some problems might exist accessing topics and articles by name. At
least, one should
> carefully select names for topics and articles (and write
> them in URl-safe form). This will generate problem with customized
interfaces where editor
> places an article into some topic and doesn't know how to
> select a correct name for it. A quick solution will be automaticaly name
articles and
> topics using their real names but creating their shortened equalents
> (which should be used then as path names).
This is the way I used to create article and topic names, and if the name
already exists, the user is prompted to change the name.
> Another problem lies in duplication of names in
> some enviroment (this is common problem for cooperative
> work of many editors). How do you think to solve such problems?
Well, if the URIs are not hard-coded, and all the links are dynamically
generated from a mgd_list_topic_articles loop, then we could solve the
problem of duplicate names by numbering the dups.
>
> I just thought that we can package all snippets you wrote using future
Midgard 1.2.6
> replication service
> and distribute them as a part of documentation.
No problem, I just have to clean up my DB to make them useable by everyone,
and some functions need improvement (I have to talk with you about these,
maybe we could integrate them in the core to make them faster (just like
mgd_get_xxxx_by_name ones ;-)).
> Then, for example, one could use
> 'Repligard' utility to extract snippet from XML source together with
> simple demonstration suite (style, demo-host, and demo-topic) and
automatically place it
> into database where it could be viewed via browser.
> Also this SnippetDoc :-) will have your articles about snippets placed
into demo-topics,
> so they will available to browse them online.
> But SnippetDoc will not be installed into DB by default such as Admin and
Demo sites. It
> allows people study Midgard step by step and use only needed
> snippets.
> How do you think?
This sounds ok to me.
Just one thing (and I'm talking to the whole dev team here): will it be a
library space where we could put all these little helpfull functions, and
make them available for every sites in the DB, or will we have to replicate
them for each host (maybe in Midgard 2.0) ?
>
> Sincerely yours,
> Alexander.
Best regards,
[EMAIL PROTECTED]
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
