xwiki-devs May 2008

xwiki-devs@xwiki.org

53 participants
158 discussions

by handey＠gmail.com

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

14 years, 8 months

[xwiki-devs] [Proposal] XWiki "2.0" Syntax

by Vincent Massol

Hi, Since I'm rewriting the new Rendering component (see http://dev.xwiki.org/xwiki/bin/view/Design/NewRenderingArchitecture) , we need to finalize the new syntax we want to have. Right now I'v planned to use the same wiki syntax as now (http://platform.xwiki.org/xwiki/bin/view/Main/ XWikiSyntax#HTextStyles) with only one change: all macros now need to be closed. For example: {macro}...{/macro} and {macro:text|param=value|.../} Is that ok with everyone or do we want to make changes? Thanks -Vincent

14 years, 9 months

[xwiki-devs] [VOTE] Deprecation strategy

by Vincent Massol

We need a deprecation strategy, i.e. decide for how long we keep @deprecated methods/classes. I propose to keep them for 2 full releases after the current version is released as final. For example if a method is deprecated in, say Core 1.3M2 then the method will be removed in 1.6M1. Of course any major new release can deprecate anything so a XWiki 2.0 is expected to break backward compatibility. So for methods deprecated in 1.0 we can remove them in 1.3M1, M2, etc. WDYT? If ok then I'll add this to our dev practice guide too. Note that for this to be easy anyone deprecating methods should add the information of when it was deprecated. For example: /** * @param time the time in milliseconds * @return the time delta in milliseconds between the current date and the time passed * as parameter * @deprecated replaced by {@link com.xpn.xwiki.api.Util#getTimeDelta(long)} since 1.3M2 */ public int XWiki.getTimeDelta(long time) { return this.util.getTimeDelta(time); } Here's my +1 Thanks -Vincent

15 years, 5 months

[xwiki-devs] Tutorial to write validations and tooltips in forms

by Ludovic Dubost

Hi developers, I've written a tutorial to help write validation and tooltips in forms. It's available here: http://platform.xwiki.org/xwiki/bin/view/DevGuide/Creating+a+form+with+vali… Some features are enabled only with the following patch: http://jira.xwiki.org/jira/browse/XWIKI-2386 Reviews of the patch are welcome for inclusion in the XWiki Core. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

15 years, 11 months

[xwiki-devs] about RTF export

by [Ricardo Rodriguez] Your EPEC Network ICT Team

Hi all, I am working with a XE 1.3.8295 installation where RTF export works fine. But it will be great programmatically control the output layout (namely, pictures printed size, space before and after paragraphs or headings, space before and after pictures, footnotes,... Please, could you point me in the right direction to face this requirement? Thanks indeed for your help. Ricardo -- Ricardo Rodríguez Your EPEC Network ICT Team

15 years, 11 months

LANG property in startup script in standalone version

by Vincent Massol

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

16 years

[xwiki-devs] How can I dynamically create a panel?

by Glenn Everitt

I was trying to figure out how to dynamically create a panel so I was looking at create.vm shown here: #if($tocreate=="panel") #set($docname=$title.replaceAll("/", "%2F")) #if(!$template || $template == "") #set($template="Panels.PanelTemplate") #end #set($newdoc=$xwiki.getDocument($docname)) #if($newdoc.isNew()) #set($pcontent = "#") #set($pcontent = $pcontent.concat("panelheader('${title}')${xwiki.getNl()}${xwiki.getNl()}#")) #set($pcontent = $pcontent.concat("panelfooter()")) #set($pcontent = $util.encodeURL($pcontent)) $response.sendRedirect($newdoc.getURL("inline", "template=${template}&Panels.PanelClass_0_name=${title}&Panels.PanelClass_0_content=$pcontent")) #else $response.sendRedirect($newdoc.getURL("view", "xpage=docalreadyexists")) #end #end . . and I quickly got lost. It looks like you first create a document from in panels space something like XWikiDocument doc = context.getWiki().getDocument("XWiki.MyPanell", context); Then it looks like $pcontent concatenates some calls to velocity macros together. Then it looks like it is url encoded so it can be passed as http response. Then I am completely lost with the sendRedirect statement. Does it redirect to process the templates and then return the response? Is there a better example for me to look at or perhaps someone generous enough to provide me with even more help? You guys have been very generous with help and I would like to Thank you! BTW congratulations on the "Big News" Glenn Everitt -- View this message in context: http://www.nabble.com/How-can-I-dynamically-create-a-panel--tp16406339p1640… Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years

[xwiki-devs] my attempt at building a development curriki

by Paul Libbrecht

Hello fellow developers, I followed http://curriki.xwiki.org/xwiki/bin/view/Main/InstallationInstructions building with maven 2.0.9 on MacOSX to get curriki running on a development machine. - building went very fine - tried changing things in xwiki.cfg but the indicated property is not there and xwiki.cfg contains an amount of "undefined" values, importantly the encoding and default-Skin among others. I could add each of the missing properties (i.e. the properties used in xwiki.cfg generation) by adding sibblings of the element <xwikiCfgEditCommentMandatory>. Similarly, I could add the dependency on our postgres driver by enriching the dependencies in this pom.xml, and I could add a few properties which seemed not correct in xwiki.cfg in the xwikiCfgAdditionalProperties element. I also activated superadmin... the indicated admin password didn't work there I think. - changing the hibernate.cfg.xml I could do as well, but it should be said not to change the one in target... since it gets overriddent at every build, but the one in web/src/main/webapp/WEB-INF At the end I got, with two changed files, a webapp that seems to match my expectations and which actually started. Ideally, these changes should happen in an extra file... is there space for this? Something such as ~/build.properties in maven-1? After changing catalina.sh to bump memory, I could import the xar (which I built as well). There I got stuck because I had to put albatross and not toucan as default and base skins. After that I could import the xar and it started looking like curriki. The log showed an amount of errors which I've ignored thus far. I concluded with the three manual steps... are they here to stay? Should I try to update the installation instructions or are there enhancements to my procedure? I'm pretty happy with this adventure.... I could, right away, record a podcast. paul

16 years, 1 month

[xwiki-devs] IncludeForm Macro

by Archana Mettu

Hello developers, Thank you for responding to my previous query. Can you please explain the differences between the following two macros, what advantages does includeInContext provide over the other? 1. includeForm() 2. includeInContext() Having retrieved an object on a page, how can I update some fields of that object and save? Doc.save() saves the document changing its version.... but, doesn't update the object-parameters. What am I missing? Regards, Archana Mettu.

16 years, 1 month

[xwiki-devs] [GSOC] Today is GSOC project starting day

by Vincent Massol

Hi GSOCers, The bonding period is over and today starts your GSOC project period. Note that this doesn't mean you should drop whatever JIRA issue you had assigned to yourself. Please continue to work on it and *finish* it. It's important. However it means that from today onwards you can start working on your project. The most important thing to do is send an email on the xwiki dev list explaining: * what architecture you're envisioning to use for your project. If you have doubts/questions please mention them. * A general planning breaking down the high level tasks you have to do and giving deadlines for each. That'll help you reach your objectives and in that manner we (the mentors and the community in general) can also help you by reviewing milestone objectives and helping you achieve them * what are your next steps and when you're planning to have them done * Any questions you have Please use the mailing list over IRC and especially over direct skype/ chat. Again it's really important that you work with the community. The success of your SOC depends on that as much as finishing your project. Thanks, good luck and have fun! -Vincent on behalf of the XWiki mentors

16 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs May 2008