Hi,
Regarding the http://jira.xwiki.org/jira/browse/XWIKI-2963 issue, this
is how I propose the macro to look like:
{{columnedtext}}
{{column with="40%"}}
My first text
{{/column}}
{{column with="60%"}}
My second text
{{/column}}
{{/columnedtext}}
This way, depending on how many {{column}} blocks it finds, the macro
transformer has a complete overview over the text to be arranged in
columns.
What do you say?
Tnx.
Dan
Hi,
I'd like to remove the usage of Composable and instead inject directly
the ComponentManager.
Implementation note: I'll create a component manager component
wrapping ComponentManager (thus using Composable internally).
Here's my +1
Thanks
-Vincent
Hi devs,
I have been working on two small enhancements for officeimporter interface:
1. Use a drop-down list for target space input field. This list contains all
existing spaces + an option to create a new space.
2. Suggest the target page name based on the input file name.
To implement these two features I used bit of javascript which I embedded in
the XWiki.OfficeImporter page (inside <script> tags). I didn't bother using
JSX because this javascript fragment is really small. Is this ok?
In the first feature, the user can select one of existing spaces. If he
selects the [New Space] option, a javascript un-hides a text field into
which the user can type in the new space name. Question; should I worry
about browsers with javascript disabled? Any hints about how to handle such
a scenario? :)
The second feature calculates the target page name based on the input file
name and updates the "Target page" text field. If the user does not like the
auto-generated page name, he can adjust the value in "Target page" text
field manually. For an example, if the input file name is "My Word
Document.doc" the target page name will be "My Word Document". This
calculation + update is also done in javascript.
Please let me know what you think, I didn't commit these features because I
am not sure if my approach is ok.
Thanks.
- Asiri
I tried for a few weeks to make XWiki work for me and even though it
worked out well in the beginning I will not go into production with
it. These are the issues I had to deal with it:
1) Renaming Pages and Spaces leave the wiki somewhat in limbo because
the references are not working anymore. Copying around the pages seems
to do the trick but I leaves a lingering bad feeling.
For Example I can rename the Web Home of a Space but then the Space
because empty (? at the end). I cannot rename the WebHome because the
new Space already has that Document and then I need to manually copy
each document one by one.
2) Upgrade to a new minor release is a nightmare. Even though the WAR
file can be easily replaced and seems to work fine the upgrading of
documents is a blind flight because there is no list that tells me
what should be imported and not.
XWiki should now which documents where edited and so should be able
to give a hint if they were changes before importing them. I would
also like a way to create a diff of the existing file and the one I
like to import.
3) I cannot make XWiki work on JBoss without messing around with
Classloader settings. This is a no-go because I cannot afford to make
existing applications fail.
4) I cannot build the current XWiki code (from SVN) because the
XWikiDocument in the Core is messed up. I also have no idea how I can
get the code of an existing release (no docu). This means I cannot
figure out if I try to fix the classloading. This is the compiler error:
/Users/schaefa/Development/xwiki/trunks/core/xwiki-core/src/main/java/
com/xpn/xwiki/doc/XWikiDocument.java:[3273,15] cannot find symbol
symbol : method
getRenderedContent(java.lang.String,com.xpn.xwiki.XWikiContext)
location: class com.xpn.xwiki.doc.XWikiDocument
UPDATE: as of tonight I fail now building the WYSIWYG component (Mac
OS X 10.5.7, JDK 1.6, Maven 2.0.10):
INFO]
------------------------------------------------------------------------
[INFO] Building XWiki Platform - Web - WYSIWYG
[INFO] task-segment: [package]
[INFO]
------------------------------------------------------------------------
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: xwiki-license-resources}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [dependency:unpack {execution: unzip-gwt-libs}]
[INFO] Configured Artifact: com.google.gwt:gwt-dev:mac-libs:1.5.3:zip
[INFO] gwt-dev-1.5.3-mac-libs.zip already unpacked.
[INFO] [gwt:compile {execution: generate-javascript}]
[INFO] establishing classpath list (buildClaspathList - scope = COMPILE)
[INFO] google.webtoolkit.home (gwtHome) *not* set, using project POM
for GWT dependencies
Removing units with errors
[ERROR] Errors in 'file:/Users/schaefa/Development/xwiki/trunks/
web/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/client/util/
Attachment.java'
[ERROR] Line 27: No source code is available for type
com.xpn.xwiki.gwt.api.client.Attachment; did you forget to inherit a
required module?
[ERROR] Errors in 'file:/Users/schaefa/Development/xwiki/trunks/
web/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/client/
WysiwygService.java'
[ERROR] Line 136: No source code is available for type
com.xpn.xwiki.gwt.api.client.XWikiGWTException; did you forget to
inherit a required module?
[ERROR] Errors in 'file:/Users/schaefa/Development/xwiki/trunks/
web/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/client/Wysiwyg.java'
[ERROR] Line 49: No source code is available for type
com.xpn.xwiki.gwt.api.client.app.XWikiGWTDefaultApp; did you forget to
inherit a required module?
[ERROR] Line 67: No source code is available for type
com.xpn.xwiki.gwt.api.client.app.XWikiAsyncCallback; did you forget to
inherit a required module?
[ERROR] Errors in 'file:/Users/schaefa/Development/xwiki/trunks/
web/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/client/plugin/sync/
SyncPlugin.java'
[ERROR] Line 438: No source code is available for type
com.xpn.xwiki.gwt.api.client.dialog.MessageDialog; did you forget to
inherit a required module?
[ERROR] Line 438: No source code is available for type
com.xpn.xwiki.gwt.api.client.dialog.Dialog; did you forget to inherit
a required module?
[ERROR] Line 452: No source code is available for type
com.xpn.xwiki.gwt.api.client.XWikiGWTException; did you forget to
inherit a required module?
4b) In the same direction I was not able to check out the source of my
current released version.
5) Handling of images is cumbersome. If I have a lot of images to be
added to a page like a walkthrough then uploading the images is a
hercules task. I would expect that I could add x number of files or
mark a number of file before hitting upload or delete. This works in
the JSPWiki. I also saw that with JIRA I can add an image directly
from the clipboard into the web page. I am not a Web Expert and so I
don't know how difficult that is.
6) I tried to keep the images in one document and reference them in
the pages containing the text. But I can only use get the reference in
the WYSIWYG editor when the images are in the same page. I expect that
I can at least list all the image names from the entire space or from
another document. Sometimes I need to reuse the images or I want to
reuse the page without having to reupload all the images.
7) The Trail is broken in my installation bringing up an error page
even though the page is available. This is because I copied some pages
around and the trail is now pointing to the old defunct space.
8) How can I delete a space
9) In case I want to clean up my somewhat messy wiki and only export a
given Space so that I can recreate the Wiki and then import only that
given Space. Currently it seems I can only export everything and then
only select the space I want to be imported. I would prefer to do it
the other way around.
10) I see really strange reaction from the system when a Space name
(maybe even regular documents) contain a dot at the end. If that is an
issue why is the application no displaying a warning or error when
that happens (see my issue with the Trail).
I think that is bugging me the most right now. I still like XWiki the
most so far and would be disappointed if I could not use it. I also
would be willing to help dealing with the JBoss classloading issue if
I can get the build to compile.
Andreas Schaefer
CEO of Madplanet.com Inc.
Email: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter; andy_mpc
AIM: schaefera(a)me.com
vmassol (SVN) wrote:
> Author: vmassol
> Date: 2009-05-25 16:00:26 +0200 (Mon, 25 May 2009)
> New Revision: 20420
> Modified: platform/core/trunk/xwiki-shared-tests/src/main/java/org/xwiki/test/AbstractXWikiComponentTestCase.java
> ===================================================================
> --- platform/core/trunk/xwiki-shared-tests/src/main/java/org/xwiki/test/AbstractXWikiComponentTestCase.java 2009-05-25 13:59:40 UTC (rev 20419)
> +++ platform/core/trunk/xwiki-shared-tests/src/main/java/org/xwiki/test/AbstractXWikiComponentTestCase.java 2009-05-25 14:00:26 UTC (rev 20420)
> @@ -16,7 +16,6 @@
> * License along with this software; if not, write to the Free
> * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
> * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
> - *
> */
> package org.xwiki.test;
>
> @@ -25,7 +24,7 @@
>
> /**
> * Tests which needs to have XWiki Components set up should extend this class which makes the Component Manager
> - * available.
> + * available. Use this class for JUnit 3.x tests. For Junit 4.x tests use {@link AbstractComponentTestCase
What's this character?
> � instead.
> */
> public abstract class AbstractXWikiComponentTestCase extends MockObjectTestCase
> {
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Any suggestions on xwiki/velociy code/calls to use to
1. fetch a document by URL and create a DOM representation "in memory"
(on the server). e.g.
#set( $domstruct = $xwiki.pluginwanted.url2DOM("http://......") )##
(i realize there's existing code that first turns it into a wiki
document, which means storing it in the database).
2. search for a particular document section by id/name and/or tag e.g.
#set( $domsubstruct = $xwiki.pluginwanted.findDOM($domstruct,
"main-content", "<div>") )##
3. pass that DOM-subsection to an additional velocity call to output it
as HTML for presentation on the client's web-browser:
$xwiki.pluginwanted.outputDOM($domsubstruct)
Also, has anybody developed a "thumbnail view" for xwiki documents? I guess
I could just iframe an existing xwiki doc with xpage=plain and shrink/size
it appropriately, ala
http://www.dynamicdrive.com/forums/archive/index.php/t-2668.html .
Niels
http://nielsmayer.com
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.9 Release Candidate 1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
First release candidate of the XWiki Enterprise 1.9 version.
Main changes:
* The default syntax is now 'xwiki/2.0' which means that new
documents will be created with this syntax. Note that XWiki Enterprise
documents (user profile, recent changes, etc) are still using the
"xwiki/1.0" syntax, they will be migrated during the 2.0 release
cycle.
* WYSIWYG Improvements
** Ability to insert level 6 headings
** Allow adding and editing lists in table cells
** Allow adding complex content inside list items
* Important Bugs fixed
** Many WYSIWYG bugs fixed
** Many 2.0 syntax bugs fixed
** Many 1.0 to 2.0 conversion bugs fixed
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise19RC1
Note that general goals for XWiki Enterprise 1.9 are:
* Finish/stabilize/document new rendering
* Finish/stabilize/document new wysiwyg editor
* Finish/stabilize/document office importer + doc splitter/management
* Finish/stabilize/document webdav
* Finish/stabilize/document REST support
* Usability improvements
Thanks,
The XWiki dev team
Hi,
I'd like to switch to using the Embedded Container Manager for our
tests. The main reason is that I want to introduce the ability to
register dynamic mocks from our tests rather having to create static
stubs (the MockDocumentAccessBridge classes and co).
Note that our functional tests would still use plexus as the CM thus
ensuring that Plexus is correctly initialized.
Here's my +1
Thanks
-Vincent
Hi devs,
Since, in the GSoC timeline, the coding period starts soon (Saturday),
I'd like to propose to grant commit rights to the sandbox to the
following students:
- Alexandru Cismaru
- Anamaria Stoica
- Arun Reddy
- Chathura Prabuddha
- Cristina Scheau
- Teofil Achirei
- Tharindu Madushanka
- Venkatesh Nandakumar
--
Sergiu Dumitriu
http://purl.org/net/sergiu/