Hi,
In the new rendering code I need to call some code that transforms
[[[wiki:][Space.]][Doc]] into a link. I'm proposing to introduce 2 new
classes/components in Core:
* DocumentName: Represents a Document's Name. It'll have 3 properties:
- String wiki
- String space
- String page
* DocumentNameFactory: Create a DocumentName from a string
representing a Document's name. Transforms [[[wiki:][Space.]][Doc]]
into a DocumentName object.
* The DocumentNameFactory would depend on the Execution component so
that it can use the current wiki, current space and current document
if these are not specified.
* This raises the question as to whether we should continue passing a
String representing a document name in our APIs in the future or
instead pass a DocumentName. I'm not yet sure what is the best answer
to this...
* Other question: In the Document object do we store the DocumentName
object or do we store instead only Space and Wiki objects? If it's the
latter then we need to fetch them from the DB which takes time. We
could also decide to only fetch them when requested with getSpace()
and getWiki() (i.e. lazy loading).
* BTW this also raises the question as to whether we want to have a
representation for space and wiki or not and instead only use tags, in
which case a document name is simply a String like "mypage". But then
it should be unique. So it could also be made of a list of identity
tags as in: "space=sp1,sp2:wiki:wiki1:language=fr:mypage". Or we could
standardize it as "wiki1:sp1,sp2:fr:mypage" and have the
DocumentNameFactory transform it into tags. In that case the
DocumentName object would be a Map of tags + the document name
("mypage"). I think we need to decide ASAP if we want to keep the
strict and hardcoded notion of Wiki>Space>Document>Object>Property or
instead go full tags since this changes completely the v2 interfaces
and code we're writing.
Let me know what you think.
Thanks
-Vincent
Yes you are right. But in toucan skin they using png for panel design.
If i change the style its reflecting for all the panels. And in the
style.css they have handled those style.
--
Prathap
On Thu, Jun 26, 2008 at 1:26 PM, Vincent Massol <vincent(a)massol.net> wrote:
Yes it's possible. Just look at the generated page in your browser in
source view to know to what class/id to attach to.
-Vincent
On Jun 26, 2008, at 9:46 AM, Prathap Pandian wrote:
> Hi,
>>
> Is it possible to apply separate CSS for each panels in the xwiki.
>
> If its possible can any one help me to change.
>
> When i am changing the CSS is applying for all the panels.
______________________________
>
> _________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
Hi,
Is it possible to apply separate CSS for each panels in the xwiki.
If its possible can any one help me to change.
When i am changing the CSS is applying for all the panels.
--
Prathap
On Jun 26, 2008, at 1:35 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-06-26 01:35:34 +0200 (Thu, 26 Jun 2008)
> New Revision: 10822
>
> Modified:
> xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> doc/XWikiDocument.java
> Log:
> Fixing the build
ooops sorry... i had started the build to check it worked but forgot
to look at the results...
Thanks
-Vincent
Dear all,
the new version of XEclipse is almost ready and I am planning to
release it in a week.
In order to publish it through Eclipse's standard update mechanism I
need to put an "update site"[1] somewhere (see also http://jira.xwiki.org/jira/browse/XECLIPSE-51)
.
I thought about different scenarios:
1) Put the update site directly in the SVN (like http://code.google.com/p/q4e/wiki/Installation)
2) Put the update site on http://maven.xwiki.org/
3) Put the update site elsewhere.
I don't think 1) is a good idea because we would put the plugin jars
under version control, but it is nevertheless interesting because
"publishing" a new version will consist in doing a simple commit,
making the process more automatic and traceable[2]
2) is not a good idea because an update site has nothing to do with
maven.
3) is ok but I don't know where "elsewhere" could be.
So the idea is to have two update sites, one for
"releases" (http://.../xeclipse/update) and one for snapshots
(http://.../xeclipse/update/dev) where to put in a XEclipse builds. I
know that this overlaps with the maven infrastructure, but this is
what Eclipse-oriented people expect (see http://jira.xwiki.org/jira/browse/XECLIPSE-90)
And probably 1) is a good solution.
WDYT?
-Fabio
[1] An update site is simply a directory with a site.xml and all the
plugin jars, published on the web.
[2] Side-note about update sites. As far as I know there is no way for
building them in an automatic way (unless a hackish, tricky, ant-based
way). The Maven PDE plugin doesn't support it, and the artifacts
generated by the maven build cannot be assembled together in an update
site (at least not without a lot of tricky steps I am not fully aware
of). So basically the safest way to generate an update site is to do
it in the IDE and "scp -r" the result to the target location. By
putting the update site in the SVN things would be easier, because
once the update site is generated, a commit would publish it directly.
Hi,
I'd like to discuss about filtering document names when they are
created, i.e directly in the XWikiDocument.setFullName()/setName()/
setSpace()/setDatabase() methods.
We could filter out (i.e. remove) the following characters:
* pipe: |
* greater than: >
* brackets: [ and ]
* apostrophe: '
* quote: "
* colon: :
* dot: .
* forward slash: /
Any other?
The reason for ., :, |, >, [ and ] is because these are reserved
characters in wiki link format.
Another option is to allow some escaping for these chars when writing
a wiki link.
Last we need to think about documents in the DB and which already have
these chars. Should we write a migrator to filter these chars too?
Probably.
WDYT?
Some related jira issues:
* http://jira.xwiki.org/jira/browse/XWIKI-1443
* http://jira.xwiki.org/jira/browse/XWIKI-2501
Thanks
-Vincent
Hi,
I am having this weired problem.
This is the velocity line
#set($esctext = $text.replaceAll("\\s+",""))
This should suppose to remove all the whitespaces in the text.
If I execute same in java code it works fine.
However if I use it in velocity code the same not working, we get $esctext
same as $test.
Now when I change the velocity code to
#set($esctext = $text.replaceAll(" ",""))
this is working all fine, and if the $text has single whitespaces, then this
gets replaced.
Thus bottom line is that replaceAll method is working fine and there is some
issue with regexp only.
Could someone please let me know if this is general issue with velocity or
something to do with xwiki.
Any reasons why its happening so?
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Reg-exp-not-working-in-velocity-code-tp18112487p18112…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
How to restrict already existing user while registering. Currently its not
showing
any alert(information) while adding the existing user from the
administration page.
--
Prathap