Hi devs,
I have complied the content assistance for xwiki API.Now the proposals are
readout from a seperate resource file.There are seperate file for each
context type ( i.e seperate files for $xwiki ,$doc .. ) .At the moment the
API information is stored in the files in the following format
xwiki.copyDocument(java.lang.String docname, java.lang.String
sourceWiki,java.lang.String targetWiki, java.lang.String wikilanguage)
is transtatet to
a single line entry in the xwiki.txt resourse file as bellow
copyDocument String docname String sourceWiki String targetWiki
String wikilanguage
Now i'm looking at velocity variable proposal and error notification.In
order to provide content assistance and error marking, there is a
requirement to parse and build the an object model of document which
contains both XWiki and Velocity. AFAIK, XDOM only supports XWiki. Is there
an object model which can r present these two languages.
For velocity code, there is a possibility to use the parser shipped with
Apache Velocity. But then we need to develop our own object model.
Any help would be greatly appreciated.
-- Malaka
Hello,
Do you foresee a special syntax for groovy scripts as you already have for
velocity using {{velocity}} with some more features?
My idea is to be able to code cleanly using groovy and to put some "generic"
part of scripts in separated documents and to be able to import them in
other docs containing other parts of scripts.
It would be really nice to be able to type some part of scripts or to define
some groovy classes in a page and tell "this is groovy code which is not
"WIKI-renderable" as is".
Then we could simply import/include this script in another page (just paste
the code without any rendering) using something like
#include("MySpace.MyGroovyDoc").
xwiki.parseGroovyXXX is useful sometimes but not when you only want to
include some part of scripts.
Existing #includeXXX macros always render the content and here I only want
to paste a script from somewhere else (xwiki.getDocument("").getContent() in
fact)
Moreover the idea would be also to allow using both "xwiki.parseGroovy" and
the #include macro for the same groovy "document". For the time being, one
need to use the trick
/* groovygroovy #* */
/* *# */
and then you are condemned to use xwiki.parseGroovyXXX because no other
function can interprete this tricky syntax.
best regards
Pascal
We should try it. Who's game to upgrade our FOP version and verify our
PDF/RTF exports still work?
Thanks
-Vincent
Begin forwarded message:
> From: Jeremias Maerki <jeremias(a)apache.org>
> Date: August 6, 2008 8:05:47 AM CEDT
> To: fop-dev(a)xmlgraphics.apache.org, fop-
> users(a)xmlgraphics.apache.org, general(a)xmlgraphics.apache.org, general(a)xml.apache.org
> , announce(a)apache.org, XSL-FO(a)yahoogroups.com, www-xsl-fo(a)w3.org
> Subject: [ANN] Apache FOP 0.95 Released
>
> Apache FOP (Formatting Objects Processor) is a print formatter
> driven by
> XSL Formatting Objects [1] and an output independent formatter. It
> is a
> Java application that reads a formatting object tree and renders the
> resulting pages to a specified output. Output formats currently
> supported include PDF, PS, PCL, AFP, Print and TIFF/PNG. Apache FOP is
> Open Source software and published under the Apache License v2.0.
>
> It took longer than expected but we're happy to present the final
> Apache
> FOP 0.95 stable release. This is basically a bugfix release to
> 0.95beta.
> The most important changes since the previous stable release (0.94)
> are:
> - many bug fixes and improvements in tables, better support for keeps
> and breaks, new features: conditional borders and background on
> columns and header/footer/body;
> - better image handling thanks to the new image loading framework
> provided by the Apache XML Graphics Commons dependency;
> - improvements and bugfixes for font handling and font
> auto-detection/-registration;
> - performance improvements and memory optimizations for the property
> handling in the FO tree.
> - elimination of a potential multi-threading problem.
> - some feature enhancements for RTF output (partial fo:leader support,
> fo:page-number-citation)
>
> Please note that support for Java 1.3 has been dropped. Only one
> type of
> binaries is provided now, that will run on 1.4+ JREs.
>
> Other important release notes are available at
> http://xmlgraphics.apache.org/fop/0.95/releaseNotes_0.95.html
>
> For a more complete list of changes, please visit
> http://xmlgraphics.apache.org/fop/0.95/changes_0.95.html
>
> For download information, see the following page:
> http://xmlgraphics.apache.org/fop/download.html
>
>
> [1] http://www.w3.org/TR/xsl11/
>
>
> On behalf of the Apache XML Graphics team,
> Jeremias Maerki
Hi,
I am student with RMIT University and I am working on a project on open-source wiki application. I have a basic idea of velocity, struts, eclipse, maven, java, xml, etc. as a part of the courses that I am doing in university. Thats is why I looked at the xwiki workspace application.
To build my project, I went thru various helps available at xwiki site like:
- http://dev.xwiki.org
- http://platform.xwiki.org
I want to study the source code so that I can understand it better. So, I want to see the source code in eclipse. I went thru the help on above site but I am not sure how to deploy the code in eclipse. I wanted this to do this to make changes in the code and run it to see how it affects the existing environment.
In my earlier projects, I had the distribution of files (.war) which included both source and classes, but xwiki_workspaces.war has only class distribution. So, i am unable to make changes and see its affects.
Any help would be appreciated.
ac
Hi,
Is there any way to access to page object attributes and/or unrendered page
content ? Thanks in advance.
--
Hoani CROSS
Globotraders Tahiti Founder [http://globotraders-tahiti.com]
How can I set and get a new session variable in xwiki. Something like:
context.getRequest().getHttpServletRequest().getSession().setAttribute("The_name",value);
context.getRequest().getHttpServletRequest().getSession().getAttribute("The_name");
Thanks for the help
--
View this message in context: http://n2.nabble.com/Session-Variables-tp674006p674006.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
I've published in svn a tool based on velocidoc
(http://sourceforge.net/projects/velocidoc/) to allow to generate
javadoc style documentation for velocity macros.
You'll find links to it and an example of generating for the XWiki
Platform Web templates directory on the wiki:
http://dev.xwiki.org/xwiki/bin/view/Drafts/Documenting+XWiki+Velocity+Macros
From now on we should start documeting velocity macros with the
following syntax:
#**
* Description of the macro
* @param paramname desc
* @param paramname desc
* @author author
*#
A later improvement will allow parsing XWiki xml files and extract
documentation of the pages in the same format.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi XWikiers,
I've recently worked on a refactoring of the page footer and I'd like
to get some feedback about it.
Features:
* New "information" section displaying parent, backlinks, included pages, etc
* New "history" section (as described in the original albatross spec)
* Tags edition with suggest (information)
* Lazy loading of sections via AJAX
* Url hash (#comments) taken into account, for example
autoload/scroll after having upladed an attachments.
* Unobstrusive JavaScript (links are working with JS turned off)
Since a demo is worth a thousand words, you can try it here :
http://jv.myxwiki.org/xwiki/bin/view/Main/
WDYT ?
Thanks,
JV.
Hello,
I have been working for some time compiling my own snapshot XWikiEnterprise
1.5 (I was following the trunk in fact) but I have stopped following the
trunk in order to test some things... Apparently now the version is 1.6...
Before looking directly in the code with my own eyes, I prefer asking a few
questions about all the new features (modular architecture, new rendering,
new macros etc...):
Are they integrated in the last available tags? (the modular architecture
has appeared long time ago but it's not the default archi yet)
Does it break any compatibility?
Do you still use the old implementations as the default one?
When do you intend to replace the old archi with the new one? Do you have an
idea of the roadmap for this? Is version 2.0 the version when the old
implementations will disappear?
I need to have such information in order to know if I go on upgrading using
the trunk because it brings some bug corrections without breaking any
existing things?
or do I use a tag version to have a stable and fixed platform?
I don't fear using new versions and examining bugs and even correcting them
as long as they don't destroy my database?
Best regards
Pascal
Hi Asiri,
I've worked a little on WebDAV interoperability and made quite some
progress.
We now have on Mac:
- WebDAV working for browsing and downloading files
- WebDAV working for drag and dropping files
- WebDAV working with vi in view, edit and save (it says on save that
the file was changed while editing although it's not true)
- WebDAV working with a patched version of OpenOffice (with a fix for
locking) or with official NeoOffice in view edit and save
- WebDAV working with TextEdit in view, edit but NOT save
Mac OSX generates phony attachments to store temporart files. TextEdit
fails because it tries to create a file then MOVE it (it might be
because of the same locking issue as OpenOffice).
And on Windows XP:
With Novell NetDrive (mapping webdav to a driver letter):
- WebDAV allowing browsing, dowloading , drag and dropping
- WebDAV working with notepad and OpenOffice in view, edit, save
With Microsoft Web Folders (2 versions on SP2 tested including the
latest patch from Microsoft, SP3 would need to be tested)
- WebDAV allowing browsing, dowloading , drag and dropping
- WebDAV allowing to double click or open from notepad or OpenOffice but
by copying to a temp read only file. You then can SAVE AS to the WebDAV
folder.
It might be possible that MS Office allows to handle this differently.
With Microsoft WebDAV redirector (same one available on Vista)
- Nothing works at all. I've tried almost all I could to try to use it
to map a network drive on the webdav folder.. The constraints are pretty
hard on the web dav server and even though I was not able to have it
fully working. I find it a dead end.
On Windows Vista:
- Nothing works at all
It seems possible to install a Web Folders package on Vista and have the
behavior of XP.
In any case, the Microsoft solution is sub-optimal on Windows. Novell
NetDrive (free download findable on the web) or WebDrive (it's
commercial counterpart) seem to be much more efficient.
Maybe MSOffice works correctly with WebFolders but this needs to be tested.
On Mac the behavior is pretty nice with the patched version of
OpenOffice (patch is published there:
http://tools.openoffice.org/issues/show_bug.cgi?id=81536 let's hope
they put it in the standard distrib).
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost