xwiki-devs October 2007

xwiki-devs@xwiki.org

31 participants
94 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

15 years

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, 4 months

Attaching an image from another document?

by Vincent Massol

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

16 years, 5 months

[xwiki-devs] [proposal] JS and CSS improvements

by Ludovic Dubost

Currently the albatross skin loads around 10 js and 10 css, which is quite a lot. We can improve loading time by: - compression and cache (raffaello will provide Apache configs specific to XWiki to help for that) - merging and optimizations of css/js (I've published http://www.xwiki.org/xwiki/bin/view/Code/MergeCSS to help on that) - removing unused css/js (now we need to find which one are unused) - conditional loading of css and js. This last improvement can help us a lot since some of the css/js are not even used in view mode, or are only used by a specific panel. For this my proposal is to add a feature to the core to allow conditional loading of CSS and JS files. The current macros in the header would instead of putting CSS and JS add a placeholder for additional CSS and JS. Then everywhere where we need these CSS/JS (in a panel, in a wiki page, in a template) we would call a macro #includecss or #includejs This macro would add in the context the CSS and JS to add. At the end of the template rendering the placeholder would be replaced by the added CSS and JS. The page would be served. This would allow to manage the way CSS and JS are added. WDYT ? Ludovic -- Ludovic Dubost Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic

16 years, 8 months

[Proposal] Internationalizing XWiki Applications

by Vincent Massol

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

16 years, 8 months

[xwiki-devs] Reintroduce the Resolved state in JIRA

by Sergiu Dumitriu

Hi, We should reintroduce the Resolved state in the issue workflow, and it should work like this: - When closing an issue, it will go in the Resolved state, which means that somebody provided a fix and it is committed in the repository. - Somebody else can test (manually) that the issue is indeed fixed/implemented, and it works as expected. If no, then it goes back to Open, otherwise it goes to Verified. - When all the needed tests and documentation are written, the issue can be closed completely, entering the Closed state. This should improve the way we write code, meaning that we don't just commit some quick fix code which nobody sees, and claim that the issue is fixed. Right now we're trying to do peer reviewing either by first attaching patches to the issue and have somebody review it, or by hoping that someone is reading the commit mails and notices if something is wrong. We should never make a release that has issues in the Resolved state, as it has unverified code, probably with missing documentation and proper tests. We should reserve a few days before each release for moving any Resolved issue to the Closed state, by verifying, testing and documenting it. Verifying issues can be done by outsiders, too, so we could involve the community more. Perhaps it would be a good idea to require two verifiers before moving the issue to verified, as testing on different systems can spot some bugs, like the full screen editor not working in Safari issue. Sergiu -- http://purl.org/net/sergiu

16 years, 11 months

[xwiki-devs] [Statistics][Proposal] Improve the statistics page

by Marius Dumitru Florea

Hi all, The statistics page needs improvement. See http://jira.xwiki.org/jira/browse/XE-37 for a brief introduction. I propose we take the following steps: 1) Extend the xwiki core api with: package com.xpn.xwiki.api; /** * Statistics api */ public class StatsService extends Api{ /** * Retrieve all-time statistics for top pages * * @param action Can be "view", "save", etc. * @param space The space from which to consider pages. If space is the empty string or null then the whole wiki is considered. * @param count The number of page stats to retrieve. * * @return a list of document stats */ List<DocumentStats> getTopPages(String action, String space, int count){} List<DocumentStats> getMonthTopPages(String action, String space, Date month, int count){} List<DocumentStats> getDayTopPages(String action, String space, Date day, int count){} /** * Retrieve all-time statistics for top contributors * * @param space The space in which to look for contributions. If space is the empty string or null then the whole wiki is considered. NOTE: currently the database stores statistics regarding only the whole wiki (e.g. the number of saves a user has made in the entire wiki, but not at space level). To implement space-level contributor statistics I need to consider page history, which is time-consuming (e.g. for each page in space, for each history entry ...). I go for offering (at least for the moment) user stats only at wiki level by removing this parameter. * @param count The number of user stats to retrieve * * @return The list of user stats */ List<VisitStats> getTopContributors(String space, int count){} List<VisitStats> getMonthTopContributors(String space, Date month, int count){} List<VisitStats> getDayTopContributors(String space, Date day, int count){} /** * Retrieve the evolution of the specified activity over a period of time * * @param action Can be "view", "save", etc. * @param docOrSpace The (full)name of a document or space or the empty string / null for the whole wiki * @param startDay The start date * @param endDay The end date * @param dayInterval The sample rate (e.g. at every 2 days) * * @return A map of (date, action count) pairs. */ Map<Date, Integer> getActivityPerDay(String action, String docOrSpace, Date startDay, Date endDay, int dayInterval){} Map<Date, Integer> getActivityPerMonth(String action, String docOrSpace, Date startMonth, Date endMonth, int monthInterval){} Map<Date, Integer> getActivityPerYear(String action, String docOrSpace, Date startYear, Date endYear, int yearInterval){} } 2) Add in the com.xpn.xwiki.api.XWiki the following method: public StatsService getStatsService(){} 3) Extend the com.xpn.xwiki.stats.api.XWikiStatsService with: List<DocumentStats> getTopPages(String action, String space, int count, XWikiContext context){} List<DocumentStats> getMonthTopPages(String action, String space, Date month, int count, XWikiContext context){} List<DocumentStats> getDayTopPages(String action, String space, Date day, int count, XWikiContext context){} List<VisitStats> getTopContributors(String space, int count, XWikiContext context){} List<VisitStats> getMonthTopContributors(String space, Date month, int count, XWikiContext context){} List<VisitStats> getDayTopContributors(String space, Date day, int count, XWikiContext context){} Map<Date, Integer> getActivityPerDay(String action, String docOrSpace, Date startDay, Date endDay, int dayInterval, XWikiContext context){} Map<Date, Integer> getActivityPerMonth(String action, String docOrSpace, Date startMonth, Date endMonth, int monthInterval, XWikiContext context){} Map<Date, Integer> getActivityPerYear(String action, String docOrSpace, Date startYear, Date endYear, int yearInterval, XWikiContext context){} 4) Adjust the com.xpn.xwiki.stats.impl.XWikiStatsServiceImpl 5) In com.xpn.xwiki.api.XWiki there are 2 methods related to statistics: * getCurrentMonthXWikiStats * getRefererText We could duplicate this methods in the StatsService and deprecate them in XWiki. 6) Currently the xwiki chart macro doesn't support hidden (aka not visible in page) data sources. This is how the char macro is used now: {chart:type=time|source=type:table;table_number:4;...} I propose to extend the macro to allow the following usage: {chart:type=time|source=type:table;...} {table} | Series1 | Series2 2001-2 | 181.8 | 129.6 2001-3 | 167.3 | 123.2 2001-4 | 153.8 | 117.2 {table} {chart} This extension consists in: * add chart macro's content to the parameters map given to the data source * adjust the TableDataSource to use this content when no table_number is specified 7) Create the xwiki-platform-applications/statistics application to host the statistics related pages. Different stats will be displayed using special panels that can be inserted into a page (see http://llunati.xwiki.com/xwiki/bin/view/Albatross/PanelInPage for a sample). I propose to use the Panels space for this pages (e.g use the path src/main/resources/Panels). Vincent could help me with this. 8) Create the Stats page (aka the UI). The Stats page is now in the XWiki space, meaning it is not accessible for the regular user (event when the statistics module is enabled). I don't really like this. I like more how jira.xwiki.org shows me its stats even when I'm not logged in. In the future, I think it would be great if the users could see page/space/wiki stats much the same they see now the xwiki code of the page (e.g. Show > Stats). For the moment I propose to make only a single stats page (XWiki.Stats). That's all. WDYT? -Marius

17 years

[xwiki-devs] work status

by Marius Dumitru Florea

Hi, Due to some technical problems I had over the past few days I haven't been able to stay online too much so I'm gonna catch up with you guys by telling you about my work status. 1. The new GWT based WYSIWYG editor is in 'stand-by' mode until I have an API for the WikiModel. You can see what I've done so far at http://www.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorBasedOnGwt#HThen…. 2. Regarding the WikiModel, I scanned the code from http://code.google.com/p/wikimodel/, I followed the discussion on this list and I read general stuff about Doxia. So I look forward to see Vincent's API for the WikiModel+Doxia. 3. I've created a plug-in wrapper for the JodaTime framework that is now available in both standard and enterprise distributions. I still have to write some selenium tests for it and of course the documentation on xwiki.org, in the code/plugins area. You can find more details at http://jira.xwiki.org/jira/browse/XWIKI-1820. 4. I'm currently working on the Stats page. I almost finished implementing the java part and the next step will be to create the stats (in page) panels using velocity and the chart macro. See http://jira.xwiki.org/jira/browse/XE-37 for more details. Regards, Marius

17 years

[xwiki-devs] Recent TeamCity errors

by Vincent Massol

Hi, There have been lots of TeamCity errors recently on the XE trunk build. This was caused by the fact that the Platform Web module build definition in TC was wrongly pointing to the old SVN mirror (when we were using ObjectWeb's SVN). It has not been updated by error. I have now updated it so the build should work again. However I've noticed some other errors were introduced in the build so we'll probably see some TC emails shortly. But these are REAL errors that we need to fix ASAP :) Thanks and sorry on behalf of the XWiki Infra Team -Vincent

17 years

[xwiki-devs] Named queries

by Jan Kodera

Hi, is possible in xwiki to use hibernate named queries? If so, how? Can I call the method searchDocuments and query name pass as parameter? Thanks. Honza

17 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs October 2007