Hi,
We have the need to isolate groups of components. For ex a wiki macro
created in a subwiki should only be visible in that subwiki by default.
Here's an implementation proposal that I'm planning to implement:
* There's a Root Component Manager (the current CM)
* There are 3 components
Thomas,
Be careful that you need to update the jython macro doc on
code.xwiki.org too since it says both macro names can be used I think.
Thanks
-Vincent
On Sep 8, 2009, at 10:08 AM, tmortagne (SVN) wrote:
Author: tmortagne
Date: 2009-09-08 10:08:09 +0200 (Tue, 08 Sep 2009)
New Revision:
+1
On Tue, Sep 8, 2009 at 09:28, Vincent Massolvinc...@massol.net wrote:
Hi,
We have the need to isolate groups of components. For ex a wiki macro
created in a subwiki should only be visible in that subwiki by default.
Here's an implementation proposal that I'm planning to implement:
*
Hi Hel,
Fixed. Some Kello Kitty perso did some vandalism on the site.
Thanks
-Vincent
On Sep 8, 2009, at 9:44 AM, hel-o wrote:
Hi,
there seems to be a problem with the translation wiki, just logged
in, only
language available is zh and theres a application hallo
hel.
-
On Tue, Sep 8, 2009 at 10:25 AM, Vincent Massol vinc...@massol.net wrote:
Hi Hel,
Fixed. Some Kello Kitty perso did some vandalism on the site.
What interest could this kitty have in this vandalism ???
Thanks
-Vincent
On Sep 8, 2009, at 9:44 AM, hel-o wrote:
Hi,
there seems
On Sep 8, 2009, at 10:35 AM, Pascal Voitot wrote:
On Tue, Sep 8, 2009 at 10:25 AM, Vincent Massol vinc...@massol.net
wrote:
Hi Hel,
Fixed. Some Kello Kitty perso did some vandalism on the site.
What interest could this kitty have in this vandalism ???
Either incompetency or just
+1
Vincent Massol wrote:
Hi,
We have the need to isolate groups of components. For ex a wiki macro
created in a subwiki should only be visible in that subwiki by default.
Here's an implementation proposal that I'm planning to implement:
* There's a Root Component Manager (the current
It seems like there is increasing need for saving groups of documents in
a single transaction. I was thinking maybe this would be a good method:
XWiki.saveDocuments(ListXWikiDocument XWikiContext)
It would be up to the calling method to set the comment and isMinorEdit
field in the documents
On Tue, Sep 8, 2009 at 12:53, Caleb James
DeLislecalebdeli...@lavabit.com wrote:
It seems like there is increasing need for saving groups of documents in
a single transaction. I was thinking maybe this would be a good method:
XWiki.saveDocuments(ListXWikiDocument XWikiContext)
It would be up
Hi everyone,
With Colibri we've started to display the doc title as the document's
rendered title. This is a big change that not only affects Colibri but
in general the way people write documents.
Here's what I suggest:
1) Display doc titles with div
2) Display document content headers
On Tue, Sep 8, 2009 at 14:48, Vincent Massolvinc...@massol.net wrote:
Hi everyone,
With Colibri we've started to display the doc title as the document's
rendered title. This is a big change that not only affects Colibri but
in general the way people write documents.
Here's what I suggest:
1) Display doc titles with div
isn't H1 more semantically correct?
2) Display document content headers using h1-h6
3) Display doc titles with a larger font size than h1 (or h1 with a
smaller font size)
This is not necessary. H1 means the first title in a document. The name of
the
Hi,
On Sep 8, 2009, at 3:22 PM, Ecaterina Valica wrote:
1) Display doc titles with div
isn't H1 more semantically correct?
Maybe yes. It just looked strange to me to have 2 H1 but I'm ok with
whatever our HTML experts say :)
2) Display document content headers using h1-h6
3) Display
Hi!
Ecaterina Valica wrote:
1) Display doc titles with div
isn't H1 more semantically correct?
2) Display document content headers using h1-h6
3) Display doc titles with a larger font size than h1 (or h1 with a
smaller font size)
This is not necessary. H1 means the
Vincent Massol wrote:
Hi,
On Sep 8, 2009, at 3:22 PM, Ecaterina Valica wrote:
1) Display doc titles with div
isn't H1 more semantically correct?
Maybe yes. It just looked strange to me to have 2 H1 but I'm ok with
whatever our HTML experts say :)
Well, it is a little strange,
On Sep 8, 2009, at 3:50 PM, Vincent Massol wrote:
On Sep 8, 2009, at 3:27 PM, Vincent Massol wrote:
Hi,
On Sep 8, 2009, at 3:22 PM, Ecaterina Valica wrote:
1) Display doc titles with div
isn't H1 more semantically correct?
Maybe yes. It just looked strange to me to have 2 H1 but I'm
On Sep 8, 2009, at 3:22 PM, Ecaterina Valica wrote:
1) Display doc titles with div
isn't H1 more semantically correct?
2) Display document content headers using h1-h6
3) Display doc titles with a larger font size than h1 (or h1 with a
smaller font size)
This is not necessary. H1
Ecaterina Valica wrote:
1) Display doc titles with div
isn't H1 more semantically correct?
2) Display document content headers using h1-h6
3) Display doc titles with a larger font size than h1 (or h1 with a
smaller font size)
This is not necessary. H1 means the first title in a
[Ricardo Rodriguez] Your EPEC Network ICT Team wrote:
Hi!
Ecaterina Valica wrote:
1) Display doc titles with div
isn't H1 more semantically correct?
2) Display document content headers using h1-h6
3) Display doc titles with a larger font size than h1 (or h1 with a
smaller
On Sep 8, 2009, at 3:27 PM, Vincent Massol wrote:
Hi,
On Sep 8, 2009, at 3:22 PM, Ecaterina Valica wrote:
1) Display doc titles with div
isn't H1 more semantically correct?
Maybe yes. It just looked strange to me to have 2 H1 but I'm ok with
whatever our HTML experts say :)
2)
On Tue, Sep 8, 2009 at 2:48 PM, Vincent Massol vinc...@massol.net wrote:
Hi everyone,
With Colibri we've started to display the doc title as the document's
rendered title. This is a big change that not only affects Colibri but
in general the way people write documents.
Here's what I
On Sep 8, 2009, at 5:28 PM, Marta Girdea wrote:
On Tue, Sep 8, 2009 at 2:48 PM, Vincent Massol vinc...@massol.net
wrote:
Hi everyone,
With Colibri we've started to display the doc title as the document's
rendered title. This is a big change that not only affects Colibri
but
in
Sergiu Dumitriu wrote:
1. The document title is already unique, using the special HTML
element designed for titles: title. The problem is that it also
contains context information: the document name, the wiki description
2. Nothing prohibits using several H1 elements, so we should not make
On Tue, Sep 8, 2009 at 17:56, Marius Dumitru
Floreamariusdumitru.flo...@xwiki.com wrote:
Sergiu Dumitriu wrote:
1. The document title is already unique, using the special HTML
element designed for titles: title. The problem is that it also
contains context information: the document name, the
1. The document title is already unique, using the special HTML
element designed for titles: title. The problem is that it also
contains context information: the document name, the wiki description
2. Nothing prohibits using several H1 elements, so we should not make
= generate H2. We were doing
On Tue, Sep 8, 2009 at 15:06, Thomas Mortagnethomas.morta...@xwiki.com wrote:
On Tue, Sep 8, 2009 at 14:48, Vincent Massolvinc...@massol.net wrote:
Hi everyone,
With Colibri we've started to display the doc title as the document's
rendered title. This is a big change that not only affects
On Sep 8, 2009, at 3:06 PM, Thomas Mortagne wrote:
On Tue, Sep 8, 2009 at 14:48, Vincent Massolvinc...@massol.net
wrote:
Hi everyone,
With Colibri we've started to display the doc title as the document's
rendered title. This is a big change that not only affects Colibri
but
in
-version2.0.7-20090811/version
+version2.0.7-20090908/version
/dependency
/dependencies
/dependencyManagement
Modified: platform/core/trunk/xwiki-rendering/xwiki-rendering-
parsers/xwiki-rendering-parser-wikimodel/src/main/java/org/xwiki/
rendering/internal/parser
28 matches
Mail list logo
