Hello!
I'd like it to be possible to create links with default labels.
I mean, [[Space.Page]], [[http://website/]] without "label>>".
Speaking for myself, I'd like magnet links to have default labels
mostly.
I have recompiled WYSIWIG editor several times, and I have added new
Wizard steps, so I've got some experience with GWT.
I'm thinking about several use cases. The user should be able to
enter magnet link as is. The user should be able to construct magnet
link from scratch. And a hybrid use case: the users enters a magnet
link in the first wizard step and improves it in the second one. An
improvement is e. g. changing file name, adding alternative
source and so on. I'm implementing two wizard steps: "enter" and
"improve".
Most often, it is wanted a label to be default. Default magnet
label generator produces things like
"klein_shock_doctrine.djvu (8.19 Mb)". These default labels mirror
a content of magnet links in a human-readable form.
But it is not obvious how to achieve this. I've tweaked GWT editor
to allow empty labels in magnet links, but such links look empty in
WYSIWIG and are being deleted on save.
--
If you want to get to the top, you have to start at the bottom
Hello Xwiki Devs,
I plan to create a new wiki on myxwiki.org for a large comunity of
non-technical users (~1K), so Xwiki is my first choice.
However I will add new features to the wiki, like: OpenId and JForum, so
what I'm asking if there is a possibility to RE-deploy my modified webapp
onto myxwiki.org afterwards, OR once the created wiki there is no other
possibility to improve it ...
If the answer would be yes, I would be grateful for a How-To. If not, I
would search for dedicated hosting, and still be grateful for your work!
Best regards!
--
Hello devs,
I'd like to add a new test framework aimed on catching XML escaping bugs
that we currently have almost everywhere. Escaping bugs cause broken,
unusable pages when special characters are used in
space/page/category/user/whatever names and often present serious
security issues. This test framework will run automatic tests and also
allow for writing manual tests.
Currently, escaping tests are usually written using selenium2, see e.g.:
http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution-test/ui-te…
This is a bad solution, slow and tricky to write.
Writing unit tests for such bugs is also not a good solution, because
most of the time they originate in velocity templates. It is hard to
test a single template in isolation, they usually require access to many
API functions.
The solution I propose works similar to webstandards tests. The
framework searches for all templates and documents in XWiki Enterprise
*.xar and *.war and generates automatic escaping tests for each of them.
Each test then requests URLs from XWiki server with different
parameters and runs a custom validator that searches for not escaped
data in the response. Manual tests can also be added easily.
The implementation can be found in the sandbox:
https://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-enterprise-test-e…
It currently implements some simple automated escaping tests on all
templates and applications from the XAR. The parameters to use are
chosen based on the source, using matching with regular expressions
(searches for things like $request.get("something")).
Full test run takes 8 minutes on my laptop. Current results: Tests run:
499, Failures: 166, Errors: 3, Skipped: 0 (there are still some false
positives that I need to track down though).
Files and test classes can be excluded from the tests using various
properties set in maven (see pom.xml). Usual -Dtest and -Dpattern are
also supported, e.g. to test all pages from "Blog" space, run:
mvn -Dtest=ApplicationTest -Dpattern='^Blog/' install
Some implementation details:
org.xwiki.escaping.suite
It is a custom JUnit4 test suite. It reads given zip file, then creates
and initializes instances of the test class for each found file. The
test class must implement FileTest (defines initialize()) and annotated
with @RunWith(ArchiveSuite.class). Test classes can decide based on
file name and content whether they can test the given file or not.
ApplicationTest and TemplateTest use this suite.
org.xwiki.escaping.framework
Contains base classes for the escaping tests (implement downloading data
from server, regex-based "parsing" etc.), escaping validator etc.
org.xwiki.escaping
Contains the tests (2 automatic and 1 manual).
Instances of the test classes (built by ArchiveSuite or manual ones) a
run using the default JUnit4 test runner, so all fancy test method
annotations are supported.
I propose to add this test framework to the main repository starting
with 2.5 branch. This will give us more time to fix current issues
(problematic files can be easily excluded to generate less noise).
WDYT?
Regards,
Alex
Hello,
we are developing an application which uses the XML-RPC API of XWiki. It is the only way to get to the data stored in the wiki in our case (except DB access, which we want to avoid in first place). In our data model there is a media entity which serves as a container for the revisions of this given media entity. That means I need all the versions of an attachment, not just the current/latest version.
I do not see a way to get to these data via the XML-RPC client interface. Is there a way to get all the versions of an attachment? And if so, is there also a way to determine the version number of a given attachment?
Thx in advance for your answers!
The XWiki development team is pleased to announce the release of XWiki
Enterprise and XWiki Enterprise Manager 2.4.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
The highlights of this release are a new template-based page creation,
invitations, object and class editor improvements (especially the
ability to remove class properties), and several security and
performance improvements.
Important changes since XWiki Enterprise 2.3.2:
* Changed the default search engine from the direct database search
to Lucene, plus a new section in the Administration page for managing
the search engine
* New template based page creation, which allows to define
templates for new pages
* A new Invitation Manager application, which allows users to
invite other people to join the wiki
* The ability to insert external images in the WYSIWYG editor
* One-click paste button in the WYSIWYG toolbar
* The ability to add one-click buttons for inserting certain macros
* The ability to delete and to disable/re-enable class properties
* Usability improvements for the object and class editors
* Usability improvements for the Watchlist
* Faster page loading using defered scripts
* Many fixes against Cross-Site Scripting attacks
* Many other bug fixes
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXWikiEnterprise24 and
http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXEM24
Thanks
-The XWiki dev team
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi Everyone,
I am novice to XWiki. I want to use XWiki standalone rendering module outside XWiki. I followed the instructions on the following page.
http://code.xwiki.org/xwiki/bin/view/Modules/RenderingModule
I've configured a project in NetBeans IDE and included following JAR to the classpath.
xwiki-core-rendering-standalone-2.2.4.jar
Here is the hello world example:
package xwikitest;
import java.io.StringReader;
import java.util.logging.Level;
import java.util.logging.Logger;
import org.xwiki.component.embed.EmbeddableComponentManager;
import org.xwiki.rendering.converter.Converter;
import org.xwiki.rendering.renderer.printer.*;
import org.xwiki.rendering.syntax.Syntax;
public class HelloWorld {
public static void main(String[] args) {
new HelloWorld().sayHello();
}
public void sayHello() {
EmbeddableComponentManager ecm = new EmbeddableComponentManager();
ecm.initialize(this.getClass().getClassLoader());
WikiPrinter printer = new DefaultWikiPrinter();
Converter converter;
try {
converter = ecm.lookup(Converter.class);
converter.convert(new StringReader("Hello **World**"), Syntax.MEDIAWIKI_1_0, Syntax.XHTML_1_0, printer);
System.out.println(printer.toString());
} catch (Exception ex) {
Logger.getLogger(HelloWorld.class.getName()).log(Level.SEVERE, null, ex);
}
}
}
But it's raising following exception at line ecm.initialize(this.getClass().getClassLoader());
Exception in thread "main" java.lang.RuntimeException: Failed to dynamically load components with annotations
at org.xwiki.component.annotation.ComponentAnnotationLoader.initialize(ComponentAnnotationLoader.java:136)
at org.xwiki.component.embed.EmbeddableComponentManager.initialize(EmbeddableComponentManager.java:69)
at xwikitest.Main.test(Main.java:32)
at xwikitest.Main.main(Main.java:27)
Caused by: java.lang.ClassNotFoundException:
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:315)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at org.xwiki.component.annotation.ComponentAnnotationLoader.initialize(ComponentAnnotationLoader.java:97)
... 3 more
Java Result: 1
Am I missing any other jar(s)?
Any prompt help will be highly appreciated.
Farrukh
FYI
-------- Original Message --------
Subject: The Apache Software Foundation Announces Apache FOP Version 1.0
Date: Wed, 21 Jul 2010 19:39:47 +0200
From: Simon Pepping <spepping(a)leverkruid.eu>
Reply-To: fop-users(a)xmlgraphics.apache.org
To: fop-dev(a)xmlgraphics.apache.org <fop-dev(a)xmlgraphics.apache.org>,
fop-users(a)xmlgraphics.apache.org <fop-users(a)xmlgraphics.apache.org>,
general(a)xmlgraphics.apache.org <general(a)xmlgraphics.apache.org>,
general(a)xml.apache.org
Redesigned, Stable Version of Pioneering XSL Formatting Objects
Processor Rounds Out Apache XML Software Stack
FOREST HILL, Md., July 21 -- The Apache Software Foundation (ASF) -
the all-volunteer developers, stewards, and incubators of nearly 150
Open Source projects and initiatives - today announced the Version 1.0
release of Apache FOP, the Open Source XSL Formatting Objects
Processor.
An Apache project since 1999, FOP is one of the industry's first print
formatters driven by W3C-standard XSL Formatting Objects created to
display, convert, and print to formats such as PDF, PostScript, SVG,
RTF, and XML. In addition, FOP is among the most commonly-used
output-independent formatters.
The Apache FOP code base has grown over the past decade under the
guidance of a Project Management Committee (PMC) who oversee its
day-to-day activities and community development.
"FOP v.1.0 provides a good subset of the W3C XSL-FO 1.0/1.1
specification. Its stable, 1.0 designation provides added recognition
as the productive tool it has been for years," said Jeremias Marki,
member of the Apache XML Graphics Project Management Committee. "Its
redesign and improved features in the layout engine makes it an even
better experience for the many developers and users who produce
millions of pages each year."
Apache FOP is in use at Accenture, Airbus, Australia Post, BNP
Paribas, Capgemini, Credit Suisse, CSC, Denic, European Patent Office,
FedEx, Ford, HP, IBM, IntelliData, Marriot International, Morgan
Stanley, Polaris, Siemens, Swiss Federal Institute of Intellectual
Property, Tecra, US Army, US House of Representatives, and Wyona,
among many others. In addition, FOP is the default implementation
bundled in XML editors such as XSLfast, Oxygen, and XMLSpy.
"Thunderhead relies on open standards, and FOP is at the heart of our
innovative NOW platform. We are proud to have been able to play a part
in its development," said Glen Manchester, CEO of Thunderhead. "As
long-time supporters of FOP, our congratulations go to the whole FOP
team at Apache on reaching the Version 1.0 milestone."
The release of FOP v.1.0 completes a free XML software stack,
comprising: Apache Xerces, Apache Xalan, and Apache FOP. The ability
to insert graphics into one's print output is possible using Apache
Batik. The Apache XML stack makes transforming and formatting XML data
(for example DocBook XML) a viable option for individual and start-up
users without business cash flow.
"Some 'overnight successes' take ten years or more," said James
Governor, Analyst and Founder of RedMonk. "Apache FOP seems to be one
of them."
"The training wheels are long gone," said Apache XML Graphics PMC
Chair Simon Pepping. "FOP's popularity is undisputed; FOP is used from
an individual developer's pet project to large-scale document
production. FOP is not yet 'feature complete', and work on it is
continuing. We hope this important step forward will motivate skilled
developers to jump in and help us make Apache FOP even better."
Availability
FOP v.1.0 is released under the Apache Software License
v2.0. Downloads, documentation, and related resources are available at
http://xmlgraphics.apache.org/fop/.
--
Simon Pepping
home page: http://www.leverkruid.eu
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe(a)xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help(a)xmlgraphics.apache.org
Hi devs,
The 2.4 release was planned for yesterday, but since the 2.4 release
manager is unavailable, and we didn't decide on a replacement in time,
I'd like to do the 2.4 release as soon as possible, after I fix the
remaining failing tests.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi guys, I am not sure that this is right place to post it, but this mailing
list looks like a good place for this post.
Recently I have browsed to XWiki Eclipse web site it looked nice but after
taking a look, I saw a place for collaboration here:
During last year one of directions for my company(OnPositive Technologies)
was developing of a good/mature true WYSIWYG Java framework for Wiki and
actually arbitrary markup authoring.
To the moment project is very near to first release and provides full
support for Tract Wiki markup(Adding parsers for another kinds of markup is
less or more trivial). So I suggest that integrating it to XWiki Eclipse may
be a good fit.
For more details about project please see the screen cast here:
http://www.screencast.com/t/MDkzYzM4.
P.S. Any comments/questions are very appreciated.
Best Regards,
Pavel Petrochenko
OnPositive Technologies(http://www.onpositive.com).
Hi,
Since we're way off for our release dates of XE 2.4 (we'll need to do a retrospective and understand what happened so that we improve ourselves for the next time), I'd like to propose the following new dates:
Original Dates:
- XE 2.4RC1: 28 June 2010
- XE 2.4 RC2 (if needed): 5 July 2010
- XE 2.4 Final: 12 July 2010
New proposed dates:
- XE 2.4RC1: 7th of July
- XE 2.4Final: 15th of July
BTW just to be sure, from now on we should only fix bugs and be very careful about not introducing any risky things, in order to prevent forcing us to have a RC2 since we're short on time.
WDYT?
Thanks
-Vincent
On Wed, Jul 14, 2010 at 16:21, Ludovic Dubost <ludovic(a)xwiki.org> wrote:
>
> This looks good.
>
> I have remarke though if this should be published on the incubator or on
> xwiki.org directly.
> My understanding is that the incubator is there for showing new
> applications based on the latest version of XWiki (including milestones).
>
> Shouldn't design proposal and standards be published on dev.xwiki.org ?
>
Standards should be published on xwiki.org when they reach a final status
and after a vote has been submitted.
IMO everything that is final and can be used for documentation should be on
xwiki.org.
On the other hand, I view incubator.myxwiki.org as a place where people can
experiment and brainstorm. Lots of design proposal are not fully
implemented, suffers changes or just remain at the proposal level, so they
are not relevant for all the people.
Also a reason I prefer that design proposals stay on incubator is to reduce
the noise on xwiki bot on IRC. A proposal suffers many variations and they
could flood the bot.
Thanks,
Caty
>
> Ludovic
>
> Le 14/07/10 13:40, Ecaterina Valica a écrit :
>
>> Hi,
>>
>> In order to assure the consistency of visual elements, we need to have
>> some
>> standards. There is already some work in progress at
>> http://incubator.myxwiki.org/xwiki/bin/view/Standards/
>> Things that mature and are final decided, will be added at
>> http://dev.xwiki.org/xwiki/bin/view/UserExperience/
>>
>> One of this proposed standards is "Items Hover State"
>> Whenever we have multiples items displayed, the hovered item will be
>> marked
>> with $theme.highlightColor .
>> http://incubator.myxwiki.org/xwiki/bin/view/Standards/HoverStateItems
>>
>> We already cover this pattern in most of the cases, but there are still
>> some
>> inconsistencies:
>> - comments: only the header is highlighted;
>> - attachments, colorthemes are not highlighted at all;
>> - trees and WYSIWYG elements have a different color (I don't know if we
>> can
>> change this to use the color themes variables);
>> - maybe others?
>>
>> Having a stardard for this kind of things it will be easier to know what
>> elements are out of order, and what needs to be fixed in order to assure
>> the
>> consistency.
>> Please vote for "Items Hover State"
>>
>> Here's my +1
>>
>
Hi,
In order to assure the consistency of visual elements, we need to have some
standards. There is already some work in progress at
http://incubator.myxwiki.org/xwiki/bin/view/Standards/
Things that mature and are final decided, will be added at
http://dev.xwiki.org/xwiki/bin/view/UserExperience/
One of this proposed standards is "Items Hover State"
Whenever we have multiples items displayed, the hovered item will be marked
with $theme.highlightColor .
http://incubator.myxwiki.org/xwiki/bin/view/Standards/HoverStateItems
We already cover this pattern in most of the cases, but there are still some
inconsistencies:
- comments: only the header is highlighted;
- attachments, colorthemes are not highlighted at all;
- trees and WYSIWYG elements have a different color (I don't know if we can
change this to use the color themes variables);
- maybe others?
Having a stardard for this kind of things it will be easier to know what
elements are out of order, and what needs to be fixed in order to assure the
consistency.
Please vote for "Items Hover State"
Here's my +1
Thanks,
Caty
We're excited to let you know that Apurv Gupta has invited you to Dropbox!
Apurv Gupta has been using Dropbox to sync and share files online and across computers, and thought you might want it too.
Visit http://www.dropbox.com/link/20.r0l_GBru7F/NjI0OTMxNDUyNw to get started.
- The Dropbox Team
____________________________________________________
To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/67552c22895d/devs%40xwiki.org
== Shift Turnover Logs ==
{{velocity}}
#set($sql = ", BaseObject as obj where obj.name=doc.fullName and
obj.className='ShiftLog.ShiftLogClass' and
obj.name<>'ShiftLog.ShiftLogTemplate' order by doc.creationDate desc")
##set($sql = ", BaseObject as obj where obj.name=doc.fullName and
obj.className='ShiftLog.ShiftLogClass' and
obj.name<>'ShiftLog.ShiftLogTemplate'")
#set($results = $xwiki.searchDocuments($sql))
#if($results.empty)
No Shift Logs has been created yet!
#else
#foreach ($item in $results)
#if($doc.title != "ShiftLogSheet")
#set($ShiftLog = $xwiki.getDocument($item))
* [[${ShiftLog.display("question").replace("<p>", "").replace("</p>",
"")}>>${item}]]
$xwiki.getDocument($doc.getAuthor()).getObject('XWiki.XWikiUsers').getPr
operty('email').getValue()
#end
#end
#end
{{/velocity}}
)))
)))
All I want to do is display who edited the file last. All this is
currently doing is showing who made the Shift Log.WebHome
Thanks, Grant
Grant Sales
Security Operations Analyst
ING
111 Washington Ave South
Minneapolis, MN 55401
Tel: 612.342.7889
Fax: 612.342.3428
Cell: 320.761.0966
Email: grant.sales(a)us.ing.com
www.ing-usa.com
ING. Your future. Made easier. (r)
---------------------------------------------------------
NOTICE: The information contained in this electronic mail message is confidential and intended only for certain recipients. If you are not an intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication and any attachments is strictly prohibited. If you have received this communication in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.
============================================================================================
#panelheader('Send this page by email')
#if($context.user == 'XWiki.XWikiGuest')
You need to be logged in to send a page by email.
#else
<form id="sendpage" name="sendpage"
action="../$doc.getSpace()/$doc.getName()?sendbyemail=1" method="post">
RECIPIENT: <br />
<input size="18" type="text" name="recipient" value="Enter an email
address" />
<div id="emailmore" class="hidden">
CC: <br />
<input size="18" type="text" name="cc" value="" />
BCC: <br />
<input size="18" type="text" name="bcc" value="" />
COMMENT: <br />
<textarea cols="18" rows="3" name="comment" value=""></textarea>
<label><input style="width: 13px;" name="includepagecomments"
type="checkbox" value="commentsyes" /> Include page comments</label><br
/>
<label><input style="width: 13px;" name="includepageattachments"
type="checkbox" value="attachmentsyes" /> Include page
attachments</label> <br />
</div><span id="more" style="cursor: pointer; text-decoration:
underline;" onclick="toggleClass($('emailmore'), 'hidden')">More</span>
\\
<input type="submit" value="Send page by email">
</form>
#if($request.sendbyemail == 1)
#set($emailrecipient = "$request.recipient")
#set($emailcc = "$request.cc")
#set($emailbcc = "$request.bcc")
#set($emailcomment = "$request.comment")
#if($emailcc != "")
#set($testcc = "$emailcc")
#else
#set($testcc = $xwiki.null)
#end
#if($emailbcc != "")
#set($testbcc = "$emailbcc")
#else
#set($testbcc = $xwiki.null)
#end
#set ($commentlist = $doc.getObjects('XWiki.XWikiComments'))
#set ($pagecomments = "
#foreach ($comment in $commentlist)
| Comment by $xwiki.getUserName($comment.author, false) :
$comment.comment
#end
")
Code isn't working.
I get this error.
The page has not been sent. There might be an error in the email
addresses you entered.
Is there some sort of thing that I need to configure in xwiki to get the
mail sender working correctly? Or is there an error in the code?
I installed the mail sender plugin and mail sender pannel application.
Thanks, Grant
Grant Sales
Security Operations Analyst
ING
111 Washington Ave South
Minneapolis, MN 55401
Tel: 612.342.7889
Fax: 612.342.3428
Cell: 320.761.0966
Email: grant.sales(a)us.ing.com
www.ing-usa.com
ING. Your future. Made easier. (r)
---------------------------------------------------------
NOTICE: The information contained in this electronic mail message is confidential and intended only for certain recipients. If you are not an intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication and any attachments is strictly prohibited. If you have received this communication in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.
============================================================================================
The XWiki development team is pleased to announce the release of XWiki
Enterprise and XWiki Enterprise Manager 2.3.2.
This is a bug fix release for the 2.3 branches.
Important Bugs fixed:
* [XWIKI-4566] - Users/groups from other wikis are not properly taken
into account when put in a local group
* [XWIKI-5228] - XWiki 2.0 renderer doesn't escape ~ in image reference
* [XWIKI-5277] - Velocity macro cache keeps growing leading to memory issues
* [XWIKI-5278] - Velocity Macros are considered global and not
isolated in XWiki Syntax 2.0
* [XWIKI-5282] - Wiki macros based on user or wiki are not unregistered
* [XWIKI-5302] - Query string is not properly escaped in tags add links
* [XWIKI-5332] - Velocity macro cache still keeps growing
* [XWIKI-5335] - Sometimes velocity macros defined in wiki pages are
not recognized
For more information see the Releases notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise232
and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM232
Thanks
-The XWiki dev team
Hi devs,
Following the implementation of gadgets we'd need to discuss the
approach of implementing xwiki as an open social container (also see
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HXWikiasOpenSo…
for the discussion). There are 2 approaches that can be used:
Short story:
Option A): open social gadgets are imported as xwiki macros (one macro
for each imported gadget), the xwiki dashboard works with macros as
gadgets, to publish the xwiki macros as gadgets we provide an automatic
transformation of xwiki macros in open social gadgets XML definition
Option B): dashboard accepts a single macro inside, the {{gadget}}
macro, which will specify a reference to the gadget to display (URL to
XML if it's open social, page reference if it's xwiki gadget) and the
parameters, there would be a mechanism to automatically publish these
xwiki pages as gadgets (to be used either by this {{gadget}} macro or by
other containers).
Long story (also discussing possible approaches for subproblems, and
also containing some pros & cons):
Option A)
See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalA-Gad…
Option B)
See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalB-All…
WDYT? Do you think there are other possible approaches that should be
added to this list before the vote? What do you think would be more
suitable?
Some usage scenarios are documented at
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HScenarios
. Please, if you feel the list is not complete, contribute your usecases.
Thanks,
Anca
Hi devs,
In order to integrate XWiki in a portal (
http://dev.xwiki.org/xwiki/bin/view/Drafts/PortletIntegration ) we need
to change a bit the front end to:
* ensure XWiki's HTML element IDs are unique within the portal page
* ensure XWiki's stylesheets doesn't affect other portlets and the
portal page itself
* ensure XWiki content is not affected by stylesheets of other portlets
or the portal page itself
We could do the following:
(1) "Mark" IDs and class names whenever they are used in JavaScript
code, both in-line and stand-alone, using two identify functions:
id(String) and className(String). This is required because identifying
automatically IDs and class names in JavaScript code is not always possible.
(2) Automatically rewrite IDs and class names in CSS and HTML (except
in-line JavaScript) and "marked" IDs and class names in both in-line and
stand-alone JavaScript code before the response for each of the
resources (page included) reaches the client. This can be easily done in
the XWiki portlet bridge (
http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-portlet/ ).
Final IDs and class names will include the portlet identifier and the
XWiki namespace (e.g. a simple 'x' prefix).
(3) Split XWiki's stylesheets (e.g. colibri.css) in two:
(a) general rules, including skin reset
(b) XWiki specific rules (i.e. with selectors including class names or IDs)
and import only (b) in portlet mode.
WDYT?
Thanks,
Marius