10 Nov
2012
10 Nov
'12
1:36 p.m.
On Nov 10, 2012, at 1:16 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote:
On Fri, Nov 9, 2012 at 11:53 AM, Vincent Massol
<vincent(a)massol.net> wrote:
You're proving my point :) "Context" has a lot of meanings and is very
fuzzy, especially for a user. It can mean anything...
Again we're not talking about the best terminology from a development point of view
here but for an end-user UI.
"visibility" is exactly how the user thinks about it: is my component going to
be visible in the farm, in the wiki, etc). He doesn't care how technically it's
done and whether there's an underlying notion of some context, etc.
Thanks
-Vincent
On Oct 29, 2012, at 5:33 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com>
wrote:
I prefer "visibility" because it's easier to understand IMO.
"scope" is
like saying "stuff".
I don't agree with you, scope generally means "context" (when talking
about
a software at least) which is exactly what we are talking about here a lot
more than visibility. On Thu, Oct 25, 2012 at 6:07 PM, Jean-Vincent
Drean <jv(a)xwiki.com>
wrote:
> On Thu, Oct 25, 2012 at 4:07 PM, Thomas
Mortagne
> <thomas.mortagne(a)xwiki.com> wrote:
>> Hi devs,
>>
>> Following the discussion about general architecture of the new
>> localization module here is a more detailed proposal for the
>> dynamically registered wiki translations pages.
>>
>> Here is how I propose to indicate that a document contains key=value
>> pair translations:
>> * put an object of class "XWiki.TranslationDocumentClass"
>
> I would have preferred TranslationClass but I see your point.
>
>> * set the "visibility" field to "Global", "Current
wiki", "Current
user"
WDYT about scope ? I'm implementing
http://jira.xwiki.org/browse/XWIKI-8234 and I went for scope there
because I think it's more than just "visibility".
OK for scope, I proposed "visibility" it to follow wiki macros but I
don't like it much either. But it's a
detail… Again all I'd like is consistency which is now broken...
Thanks
-Vincent
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs >> As for the content of the document it
will stay the same as in
>> preferences based documents for now.
>>
>> I have other fields in mind for later (on demand, translation message
>> syntax, etc.) but this is a 4.3 proposal here.
>>
>> WDYT ?
>>
>> Here is my +1.
>> --
>> Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs