Hello,
I am working on creating blog entries using xwiki. I was wondering if it would be possible to create a template for the blog entries so that they will be more structured?
Thank you for your time and help!
Hande Aksac
Hi,
Does anyone know why we have the following LANG property defined in
our startup scripts:
#!/bin/sh
export LANG=fr_FR.ISO8859-1
JETTY_HOME=.
JETTY_PORT=8080
JAVA_OPTS=-Xmx300m
java $JAVA_OPTS -Dfile.encoding=iso-8859-1 -Djetty.port=$JETTY_PORT -
Djetty.home=$JETTY_HOME -jar $JETTY_HOME/start.jar
I think this is bad as it's french and I don't think we should set it
for the user.
That said, if it's there its probably because it was required in the
past, hence my question here.
To summarize: anyone sees any issue if I remove that "export LANG" line?
Thanks
-Vincent
Hi,
I'd like to attach an image to the current document but the image is
attached to another document. I couldn't find the answer in the FAQ.
It would be great if the {image:} radeox macro allowed for this.
Right now the only solution I'v found (which is a bit ugly) is to use an
HTML <img> tag as in:
<img src="/xwiki/bin/download/XWiki/Toolbar/image.gif" />
Any other solution I would have missed?
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
Hi,
Here's my proposal for internationalizing XWiki apps. The idea is to
propose several solutions for XWiki apps writers:
* Use case 1: I have lots of text on my page
- solution: use XWiki's mechanism for translating page by creating
several editions of the page in the different languages
* Use case 2: I want translation resources for my application only
and I'd like to share resources between pages
- solution: use: $msg("mykey",
"MySpace.MyTranslationDocForThisApplication")
- MySpace.MyTranslationDocForThisApplication is a standard
document to which a XWiki.PropertiesClass object is attached
- It'll search first in that doc's PropertiesClass and if not
found in XWiki's registered document bundles and if not there in
XWiki's static resource bundle files
* Use case 3: I want translation resources only for a given page
- solution: use: $msg("mykey", $doc)
- You'll need to have attached a PropertieClass object to the page
where $msg is used
- It'll search first in that object and if not found in XWiki's
registered document bundles and if not there in XWiki's static
resource bundle files
* Use case 4: I want to have a global translation resources for all
my apps in the wiki
- solution: use: $msg("mykey")
- You'll need to have created ad registered resource bundle
documents in the Wiki preferences
- It'll search first in XWiki's registered document bundles and if
not there in XWiki's static resource bundle files
Implementation details:
* Add XWikiMessageTool.get(String, String) API
* Add XWiki.PropertiesClass class in XE in the Administration
Application + a class sheet for presenting the properties nicely
WDYT?
Thanks
-Vincent
Hi,
With the 1.1M3 release we have currently only released a hsql version
of the platform WAR. That war only includes the HSQL JAR but not the
driver JARS for other DBs.
In our current build we can generate the platform WAR for other DBs
using for ex: mvn install -Pmysql. That includes the driver JAR for
that DB.
Before we were bundling all driver JARs into our WAR so our users may
be a bit confused and we need to decide on the strategy we want to
have. I can see 3 possible strategies:
1) 1 WAR per database
- We could start by releasing only 2 WARs: one for HSQL and one for
MySQL. I don't think we need more and releasing more is going to be a
pain as each WAR weights 40MB.
2) 1 WAR with everything
- Cons: having all these DB drivers makes our WAR fatter
- Possible solution: we only release the HSQL and MySQL drivers
3) 1 empty WAR
I feel 3) might actually be the best solution for the following reasons:
- if the user is non technical he'll install the standalone version
- if the user is technical it means he shouldn't have any problem
following install instructions that tell him to download such driver
at such location and put it in WEB-INF/lib
- we only release one common WAR and our XWiki Platform is
environment independent (which is a new property to have I think)
- releasing one WAR makes our release process simpler (only 40MB to
release once)
WDYT?
Thanks
-Vincent
I had no problem to install Xwiki in the Tomcat environment.
But when I deployed Xwiki under OC4J followed the OC4J Installation
instructions
("http://www.xwiki.org/xwiki/bin/view/AdminGuide/InstallationOC4J"),
javascript did not work properly – it looks like the path to external
.js-files couldn't be found.
Both IE and Firefox show javascript errors nearly on each page, although
JavaScript is not deactivated in browser.
I can open the home page, go to xwiki/bin/admin/XWiki/XWikiPreferences,
upload xwiki-enterprise-wiki-1.1~.xar, but cannot expand it to choose the
files I want to import.
I have tried to include some JavaScript functions from import.js direct in
the importinline.vm source – it works fine.
What's the difference between:
<script type="text/javascript"
src="$xwiki.getSkinFile("import.js")"></script> - it generates path to
/xwiki/skins/albatross/import.js
and
<script type="text/javascript" src="$xwiki.getSkinFile("import.js",
true)"></script> - generates path to
/xwiki/bin/skin/skins/albatross/import.js
Why only some paths to js- and css files are defined with the parameter
“true”?
Is there something specific to keep in mind concerning path under OC4J?
Should I make additional entries in some xml-files?
Any tips please?
Regards,
adoro
--
View this message in context: http://www.nabble.com/OC4J---JavaScript-tf4310450.html#a12271014
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
I am getting error while importing Xwiki.XwikiPreferences. Can you
please tell me why this is happening?
I am using tomcat and Oracle 10g database.
--
Thanks,
ANUJ
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi David,
On Aug 30, 2007, at 7:51 PM, David Ward wrote:
> Author: dward
> Date: 2007-08-30 19:51:15 +0200 (Thu, 30 Aug 2007)
> New Revision: 4670
>
> Added:
> xwiki-products/curriki/branches/curiki-1.2/
> Log:
> - Branch created for Curriki 1.2 release
>
>
> Copied: xwiki-products/curriki/branches/curiki-1.2 (from rev 4669,
> xwiki-products/curriki/trunk)
It seems the version numbers in the pom.xml files for curriki are
wrong since that you're tagging some old revs with 1.2.x. Poms says
1.0-SNAPSHOT.
Should that be fixed?
Thanks
-Vincent
PS: I think we should have dedicated SVN/Mailing lists for curriki
since it's not meant to follow the same practices than xwiki. Also
every time curriki makes a commit, it increases the svn revs for
xwiki and vice-versa. We need to think about that. Last trunks-devs/
users for xwiki/curriki should be separate IMO. WDY?
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi,
The current default profile, when building trunks-devs or
trunks-users, is to build all components, including curriki, XEM,
multiwiki. There is a profile defined for building only XE, but it is
not the default one.
Given the fact that most users only want to build XE, this should be
the default profile. So I'd like to:
- make the default profile = 'xe'
- add an 'all' profile, which builds all the modules
WDYT?
Sergiu
--
http://purl.org/net/sergiu
Hi all,
I deploying Xwiki-1.0.exe on windows xp. However, i noticed the database schema provided in the installation
xwiki_db.script doesn't matched with the one online at http://www.xwiki.org/xwiki/bin/view/DevGuide/DatabaseSchema.
Why issit so?
Regards
---------------------------------
Real people. Real questions. Real answers. Share what you know.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
