> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@users.forge.objectweb.org]
> Sent: lundi 16 octobre 2006 20:14
> To: xwiki-commits(a)objectweb.org
> Subject: [xwiki-commits] r1396 - in xwiki/trunk: . core lib
> src/main/web/WEB-INF
[snip]
> Modified: xwiki/trunk/src/main/web/WEB-INF/version.properties
> ===================================================================
> --- xwiki/trunk/src/main/web/WEB-INF/version.properties 2006-10-16
> 06:33:23 UTC (rev 1395)
> +++ xwiki/trunk/src/main/web/WEB-INF/version.properties 2006-10-16
> 18:14:00 UTC (rev 1396)
> @@ -1,2 +1,2 @@
> -#Sun Aug 20 09:09:03 CEST 2006
> -build.number=0021
> +#Mon Oct 16 18:05:24 GMT 2006
> +build.number=0022
I've committed this by mistake. It's really a bad practice to modify source files in the source tree and not in the build tree as this leads to this type of errors.
Do I need to revert this?
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Demandez � ceux qui savent sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
Hi,
We have currently some work undergoing on the WYSIWYG Editor by Nam.
http://jira.xwiki.org/jira/browse/XWIKI-382
We would love some testers and get feedback about it. To test it on your
installation, you need to replace the tiny_mce and wiki_editor
directories with the one from the attachment on jira.
Here is currently my feedback about the editor:
- The style does not switch to standard text when you hit enter after a
title (that's a behavior that would be great)
- the window size is not good for the table window
- If you finish a bloc in a table with a carriage return and an empty
line the conversion fails. Here is an example of that failure.
{table}
Title 1|Title 2
abcd |abcd\\
{table}
- an empty line in a table fails to convert to wysiwyg from the wiki syntax
{table}
|
{table}
- titles should not be allowed in list
- there should be a standard text button (first item in the title list)
- windows are too slow to come up
- translations appear after a while in the windows
- clicking on an image and then the image button does not retrieve the
current image parameters.
- you need to find a way to center an image (the text 'center' as the
alignement info could add a <div align='center'> tag).
- xwiki should find the windows size ratio of an image and/or explain
to the user that setting up only the width or the height will take care
of preserving the ratio
- font size, color, and type should be changeable
- other improvements would be predefined and customizable styles in the
editor
Ludovic
--
Ludovic Dubost
XPertNet: http://www.xpertnet.fr/
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost AIM: nvludo Yahoo: ludovic
Hi,
Following my post entitled "[Proposal] Plugins and xwiki distributions" I'd
like to propose that we reorganize our SVN. Here's what I propose:
xwiki/
|_ xwiki/
|_ trunks/
|_ branches/
|_ tags/
|_ xwiki-plugins/
|_ trunks/
|_ emailnotification/
|_ lucene/
|_ ...
|_ branches/
|_ tags/
|_ xwiki-apps/
|_ trunks/
|_ branches/
|_ tags/
|_ xwiki-clients/
|_ trunks/
|_ branches/
|_ tags/
|_ xwiki-sandbox/
|_ trunks/
|_ branches/
|_ tags/
|_ xwiki-tools/
|_ trunks/
|_ branches/
|_ tags/
The rationale:
* It's really cumbersome to have trunks/, tags/ and branches/ for each
single module. It's easier and better to have only one per category (xwiki,
xwiki-apps, xwiki-clients, etc). Of course each project inside these can
still release in its own lifecycle and tag independently. For example check
the plugins/tags/ dir for Maven
(https://svn.apache.org/repos/asf/maven/plugins/tags/) and you'll see that
each plugin is released separately.
* Having trunks/ at different levels doesn't sound like a good idea.
Actually I discovered this when trying to create svn:externals for all
trunks. The same would happen if you tried to check out all the trunks
manually. You would currently get some directories that are not under
version control (xwiki-plugins/, xwiki-clients/, etc). The reason is that
there's no way to check the contents of these directories by taking only the
trunks and still having them under svn control.
Thus my belief is that trunks/ dir at different directory levels in a SVN
directory is not a good idea if everything is in the same project.
Again a good structure is shown by Maven:
https://svn.apache.org/repos/asf/maven/ (all the trunks/ are at the same
level)
* Last, we have a gelc/gelcv1 dir. I don't think we should put version in
the directory structure but rather use trunks and branches for this. I think
it'd be better to use the trunk for v1 and when a v2 comes out, move the v1
to a branch and the v2 to the trunk.
I'd like to reorganize the svn tree to follow what I've defined above. Let
me know if you're ok for me to do it. As some of you might have some
uncommitted changes in your local repo let me know if I can do it. I'd like
to start with the xwiki-plugins/ tree.
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Demandez � ceux qui savent sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
All,
I have created an FAQ pages in xwiki. I created them with a user that has "admin, edit, programming" rights. It works greate for that user or any admin user. However, when I try to create an FAQ entry (FAQ.FAQClass) instance with a user that has "view, edit" right, the FAQ entry does not show text box and text area's in the inline for. So my question is what kind of right to general users need to do this?
Thanks,
Tony Nuzzi
