I would also use a single space at first glance. Make things better
isolated.
What we really need are sub spaces or rather hierarchical paths. See
Now that I've picked it up...
Is there any real reason why the AppManager has to span 6 spaces?
I can understand having XAppManager, and perhaps XAppUtil or
XAppResource (XAppApp doesnt' really work.. :-) but I don't like
having XApp, and XAppClasses and XAppManager and XAppResources and
XAppSheets and XAppTemplates..
that's just a waste of spaces... users ask for lists of spaces all of
the time.. why should we be adding so many?
I would prefer:
XApp.XWikiApplicationXapp
XApp.XWikiApplicationXwikiapplicationclass
XAppManager.CreateApplication
XAppManager.WebHome
XAppManager.Translations
XAppManager.XWikiApplicationClass
XAppManager.XWikiApplicationClassSheet
XAppManager.XWikiApplicationClassTemplate
XAppManager is then clearly the XAppManager application, and XApp's
are the applications it manages. I REALLY REALLY REALLY don't like
having things spread out spaghetti in a lot of spaces... Maybe that's
fine on small installs, but when you have 100 or so spaces, it's
annoying to spontaneously pick up 4 more...
On 10/1/07, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote:
> 2007/10/1, Thomas Mortagne <thomas.mortagne(a)xwiki.com>om>:
>> Hi Stéphane,
>>
>> 2007/10/1, Stéphane Laurière <slauriere(a)xwiki.com>om>:
>>> Thomas Mortagne wrote:
>>>> Hi all,
>>>>
>>>> Actually application descriptor contains a field that list all
>>>> document application contains.
>>>>
>>>> I would like to add to Application Manager a way to be able to add
>>>> "all the documents of space SpaceName" for example.
>>>
>>> That would be a nice feature indeed.
>>>
>>> I started using the ApplicationManager for the XWiki help desk
>>> app. The
>>> management of translations is really handy! I'm adding
"{table}" at
>>> the beginning and the end of the list of properties for a better
>>> display.
>>>
>>>> I already implemented a solution and I would like you to
>>>> comment and
>>>> me to modify if needed.
>>>>
>>>> When XWikiApplication.resolveDocumentsNames is called, it list all
>>>> document and one by one look if the document name is between
>>>> "[" and
>>>> "]", if so it consider document name as sql matching string
usable
>>>> with "like". So for example you will add "[XWiki.%]"
if you
>>>> want to
>>>> add all documents in the XWiki space to the application document
>>>> list.
>>>
>>> Sounds ok to me, but do we really need the brackets?
>>>
>>> Couldn't we simply write this type of list:
>>> XAppManager.%|XAppResources.Translations
>>
>> I added % for... lets say security reasons as an URL and so a page
>> name can contains "%" I thinks but not very sure on that.
>>
>>>
>>> It would then be parsed and submitted to the sql engine directly,
>>> couldn't it? We could use the "like" clause for all
>>> occurrencies, or
>>> check whether each occurrence contains the character '%' in case
>>> the
>>> "like" clause is more heavy than an exact match clause.
>
> I forgot, I said "one by one" but all "[]" matching in a list
are
> merged in only one sql request. It can also be easily merged between
> applications and all his dependencies too.
>
>>>
>>>> This feature is supported for "documents list" and also
"document
>>>> list to include"
>>>
>>> Actually, what's the purpose of the field "document list to
>>> include" and
>>> "document links"? I couldn't find the info from the online
>>> documentation
>>> at
http://www.xwiki.org/xwiki/bin/view/Code/
>>> ApplicationManagerApplication
>>
>> "includes" and "links" target multi wikis. It is the pages
that are
>> included or linked when create a wiki from a template wiki. It is
>> used
>> to configure what is shared between wikis.
>>
>> "Links" is not used yet as it need not supported feature in XWiki :
>> real links between pages, I forgot to hide it in interface.
>>
>>>
>>> Cheers
>>>
>>> Stéphane
>>>
>>>> WDYT ?