Hello David,

you wrote:
>> 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.
It seems to be OK.

>> 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.
Yes,  and  it  is  could be used to avoid dups when copying topic/page
trees in Admin site (will be in 1.2.6).

>> 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.
> 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)?
This could be done in several ways:

1)  Creating  additional  table 'CodeSnippets' where snippets could be
organized  under  tree  structure  and  adding  special  PHP  function
mgd_include_snippet('path/to/snippet-name');    then   all   functions
defined in 'snippet-name' will be available in script context.

2)  Extending  midgard-lib  by  modules support and allowing people to
bind  mission  critic  functions  written  as  external  C  code. This
repositary     could     be     also     accessed    using    function
mgd_extension('path/to/extension-name',  arguments);  where  format of
arguments  would  be specified during extension's binding using usuall
midgard   vformat()  syntax  ($q,$d,  etc)  but  this  will  work  for
non-object types only.

It  seems to me that latter approach will appear somewhere in 2.0 land
but  also  both extension schemes could co-exist. I'll probably try to
add (1) into 1.2.6 if other developers will agree with this.

Best regards,
 Alexander                            mailto:[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]

Reply via email to