Hi,
I have problem to get this application works properly, In this
article<http://www.xwiki.org/xwiki/bin/view/FAQ/How+to+implement+%22Approved+Revisi…>,
i'm supposed to do this to test it :
1. Create a page, say Main.Test with the content "Original Content"
2. Edit the page again to change the content to "New Content"
3. Add an XObject of type Revision.RevisionClass and set the
revisionfield to
1.1 (this is the version we want to display)
4. Save
This works
But when we …
[View More]change the order :
1. Add an XObject of type Revision.RevisionClass and set the
revisionfield to
1.1 (this is the version we want to display)
2. Create a page, say Main.Test with the content "Original Content"
3. Edit the page again to change the content to "New Content"
4. Save
it doesn't work anymore, you save the Revision object with the right
revision but it won't display it.
But this works for all revisions before adding the object.
Once you added the object, no matter how much changes you made, you won't
be able to display last revisions(created after adding the object)
BTW, when i give a wrong revision, the page display just
"$revDoc.getRenderedContent()"
One strange usecase :
1) i create a new page, make modifications and save 3 times
2) i add the object and give 1.1 for revision and save
3) when i edit the file, in the editor, i can find the last version, i
modify something and save
==> it's like, it'll save the revision 1.1 (setted to the added object)
When i make "compare selected version" between the last and the first, it
gives me the last change i made, but when i click on the last revision i
can't find the last change i made.
Any explanation please ?
Thanks in advance :)
[View Less]
Hi,
I'm changing historyinline.vm to add a link "Approve", in order to set the
approved revision in the object added to the document.
I added this tag in the foreach : do this make sens ? is it supposed to
work ?
<a href="" onclick="$doc.set("revision", $version)">Approve</a></td>
In my html source i find :
<a href="" onclick="">Approve</a>
the display is fine but no action, nothing happen
Thanks in advance :)
Hello,
First of all, Merci bcp Vincent for this How to implement "Approved
Revisions"?<http://www.xwiki.org/xwiki/bin/view/FAQ/How+to+implement+%22Approved+Revisi…>
I was able to choose which revision to display by following the "how to",
now i need to add the object automatically to any page in my wiki or at
least any page in a given space
Thanks in advance :)
The XWiki development team is proud to announce the availability of
XWiki 6.1 Milestone 1.
This release introduces the ability to change the width of the panel
columns and comes with an improved Active Installs feature (with
evolution graph and many new filters). Developers can now use the LESS
preprocessor for skin style sheets. A couple of bug fixes (18) and
some small improvements (24) make this release worth trying.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/…
[View More]Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki61M1
Thanks
-The XWiki dev team
[View Less]
Hello devs,
I would like a repository for the Hierarchy Macro on
https://github.com/xwiki-contrib.
Hierarchy Macro use jQuery and jsTree (http://www.jstree.com) to display
dynamique tree view of wiki documents based on parent/child relationships
Thank you in advance.
Lyes Bandou
Needs: As you already know, the new skin, Flamingo, is based on Bootstrap (
http://getbootstrap.com/) which use a CSS Preprocessor to have more
flexibility. There is 2 majors competitors in this field: LESS (
http://lesscss.org/) and SASS (http://sass-lang.com/). Bootstrap is using
LESS but they also provide an official port for SASS.
We need to execute one of these preprocessors at the runtime, to recompile
the Bootstrap CSS according to the current Color Theme.
After a long thread [1] where …
[View More]we have compared the 2 preprocessors, and
after some discussions on IRC, **I am proposing you to choose LESS**.
Why:
* It is the original preprocessor used by Bootstrap, and so the majority of
Bootstrap Themes that we can find on the web provides LESS sources. If we
want to be able to use all these themes, using LESS is clearly an advantage.
* Caty, Denis and I have a bit of experience with it. Bluebird [2], Junco
[3] and the current Flamingo skins are built with LESS.
* The syntax is not too close to Velocity, meanwhile SASS is.
* The Java integration, using Rhino, works quite well. Although there is an
issue [4] for which I have written a patch. I hope the LESS community will
handle it.
* It looks a bit more popular than SASS.
Here is my +1 for using LESS.
For the record, this is what I am going to do:
* Implement a cache to only compile LESS files when needed, because the
computation is costly. The cache will be flushed only when the current
color theme is modified.
* Write new components and a script service to compile LESS files that are
present in the skin directory, partially parsed with Velocity. In the
future, we might want to integrate it directly in the Skin Action, but that
means we need to change oldcore.
Thanks,
Guillaume (Louis-Marie)
---
[1] The thread "[Proposal] Integrate LESS css in XWiki":
http://markmail.org/message/hw45txkv2vk5dnqw
[2] Bluebird Skin:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Bluebird+Skin
[3] Junco Skin:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Junco+Skin
[4] LESS issue: https://github.com/less/less.js/issues/2005
[View Less]