xwiki-devs April 2012

xwiki-devs@xwiki.org

31 participants
86 discussions

[xwiki-devs] [GSOC] A basic search implementation with SOLR

by savitha sundaramurthy

Hi Paul , Eduard and Sergiu, I went through Fabio Mancinelli's code and with the help of few inputs from there , I have implemented a basic search functionality using solr. It also fixes the issue http://jira.xwiki.org/browse/XWIKI-6226 . I have indexed the page in English, french and Spanish. I have implemented these main functionality: 1) Simple text search using solr. 2) Used *Extended Dismax Parser *to customize search relevancy using boost index. 3) Hit highlighting for English. Below is the link to the source code https://github.com/savis/xwiki-platform-search XWiki front end , HTML and Velocity code https://gist.github.com/2295648 I wanted to send a pull request but I was playing around when renaming my username and deleted the forked repository and I'm having difficulty forking it again. So I have created a new repository and shared the code above. I have taken few screen shots and have attached the document. I'm working on my application and it should be done today. Thanking You, Savitha

13 years

[xwiki-devs] [Proposal] Supported Databases Strategy

by Vincent Massol

Hi devs, In the same spirit as what we have done for Browsers (see http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases since we don't have a clear strategy ATM. I propose that by "supporting" we mean: - issues created for these DBs in jira are not closed as won't fix and we make a best effort to fix them - we include these DBs in our tests (be them automated or manual) - when we create new features or modify existing features we make a best effort to verify that they work on the supported list of DBs Proposal: * HSQLDB: only support the version bundled in the standalone zip * MySQL: We officially support the last major version, i.e. 5.0+ ATM * PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM * Oracle: We officially support the last major version, i.e. 11g ATM * DB2: We don't officially support it. This means that we don't test against it, we don't ensure that new feature work on it but if someone raises an issue in jira and it's easy to fix (or if someone provides a patch) then we fix it. * Derby: Same as DB2 * Microsoft SQL Server: Same as DB2 * H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2 one day) * Others: Same as DB2 I also propose that in the Release notes for each version of XWiki we mention the list of DBs we have tested against and that we "support". Here's my +1 Thanks -Vincent

13 years

Re: [xwiki-devs] Poll/Survey Application - GSoC 2012

by Ecaterina Moraru (Valica)

Hi Rauf, First of all the discussions related to GSOC projects is best if they are public: other people could be interested in the subject, multiple mentors/community could respond to your questions. On Sat, Mar 31, 2012 at 11:57, Rauf Butt <raufbutt(a)gmail.com> wrote: > Dear Caty, > > Thanks for your response. After initial study of XWiki, below are my > findings > > 1. The database schema of XWiki is based on SQL and can be used with any > Sql based database but by default is MySql. > 2. There is an application to create polls at > http://extensions.xwiki.org/xwiki/bin/view/Extension/Polls+Application but > in this project, we need to create a widget. May be to embed the existing > poll application into a widget? > Regarding the exact details of this project idea, Ludovic would be best person to answer the questions. IMO could be the first objective to integrate the existing Polls application as a widget/gadget that could be integrated inside our Dashboard. See http://extensions.xwiki.org/xwiki/bin/view/Extension/Dashboard+Macro in order to find out more about how to use gadgets inside XWiki. The only difference between the Dashboard and the Polls application is that the Dashboard is already bundled with XWiki Enterprise, while the Polls Application is just a community extension. So the first step in reusing that code would be to analyze how much work would be to integrate the Polls code into the official bundled code, if it's the right solution, how much work is needed to combine Polls with AppWithinMinutes / Dashboard. 3. To create Survey, we would be using the available application: > http://extensions.xwiki.org/xwiki/bin/view/Extension/App+Within+Minutes+App…. > The demos show how to create applications with this extension. > > The idea behind AppWithinMinutes is to empower users to easily create applications. I think Ludovic wants to give users the ability to easily create Polls/Surveys, spread them (maybe by having them as gadget inside the Main.Dashboard) and analyze them at the end of the poll. > The project requirements include to modify the presentation (GUI) for this > survey and to display the survey results. > > Please correct me if there is some misunderstanding. > Should be correct. Thanks, Caty > > Kind Regards, > Rauf > > > > On 23 March 2012 11:35, Ecaterina Moraru (Valica) <h> wrote: > >> Hi Rauf, >> >> You should play with >> >> http://extensions.xwiki.org/xwiki/bin/view/Extension/App+Within+Minutes+App… >> >> also install from extensions >> http://extensions.xwiki.org/xwiki/bin/view/Extension/Polls+Application >> >> For the development documentation see >> http://dev.xwiki.org/xwiki/bin/view/Main/WebHome >> http://platform.xwiki.org/xwiki/bin/view/DevGuide/WebHome >> >> Thanks, >> Caty >> >> On Wed, Mar 21, 2012 at 03:11, Rauf Butt <raufbutt(a)gmail.com> wrote: >> >> > Dear Team XWiki, >> > >> > >> > I am very excited to contribute in open source community through the >> > platform of GSoC 2012. Last year, I contributed "Debugger Visualizers" >> to >> > MonoDevelop which had successfully become a part of Mono Develop. >> > >> > >> > >> > I have seen project ideas for GSoC 2012 at >> > http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/WebHome. I am >> > interested in "*Poll/Survey Application*". The reason for my interest is >> > that I have good working experience of HTML, Javascript, Java and >> related >> > technologies. I also checked out XWiki to start understanding it. >> > >> > >> > >> > My understanding of the requirements is as follows: >> > >> > >> > >> > 1. Create a Poll widget to include within a web page. >> > >> > 2. Show Poll results within the Poll widget. >> > >> > 3. Use AppWithinMinutes XWiki to create surveys. >> > >> > 4. Develop the look and feel of such surveys (GUI). >> > >> > 5. At the end of survey, show the results of survey. >> > >> > >> > >> > Have you got a template for the survey GUI or we need to brain storm on >> > this? >> > >> > What database/file storage would be used to store Poll/Survey results? >> > >> > >> > Your kind feedback would help me in better recognising the core project >> > requirements and develop a good proposal. >> > >> > >> > Regards, >> > >> > >> > >> > Rauf >> > >> > Regent's College London >> > _______________________________________________ >> > devs mailing list >> > devs(a)xwiki.org >> > http://lists.xwiki.org/mailman/listinfo/devs >> > >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> > >

13 years

[xwiki-devs] Ideas for GSoC 2012

by Gianluca Sabena

Dear all, Some ideas for GSoC 2012: - Native Ace code editor support I think the future is to code online in the browser, I would like to see Ace Editor http://ace.ajax.org/ integrated in Xwiki as a native editor (not only for some objects), as an alternative to the wysiwyg, text and htmlarea editors for pages. The editor must support html, javascript, velocity and java syntax. The use case is: be able to write velocity ad groovy code in pages with a gui editor. - Node.js extension for real time editor I think in order to enhance collaboration we need a real time editor. I would like to see node.js integrated in Xwiki. In order to keep the architecture simpler I guess we could think to a "editing session". Use case: - three users wont to modify a page - they open a node.js session with the page content - work there - save the page back - we could use restful api to allow node.js to communicate with xwiki - Spreadsheet support I guess xwiki leaks spreadsheet support. This could be great for budgeting and control, in order to reduce attached excel files and move to a real collaboration over data. The Sheetserve community edition could be a source of inspiration http://extentech.com/estore/product_detail.jsp?showdetails=true&product_id=… (PS: Why don't move to Google groups for a better and simpler mailing- list management?) Thank you, Gianluca Sabena - - - - - - - - - - - - - - - - - - - www.intertesto.com - - - - - - - - - - - - - - - - - - - gianluca.sabena(a)intertesto.com skype: gianluca.sabena

13 years

Re: [xwiki-devs] GSoC 2012

by sasinda rukshan

Hi all, I am Sasinda Rukshan from University of Moratuwa Sri Lanka. I created a proposal for the Google Android XWiki Connector. link : http://dl.dropbox.com/u/30342197/x%20wiki.pdf (failed to attach it to the mail and send as the mail bounced back alerting the file is too big. : 603KB) Thank you. Sasinda Rukshan. On Sun, Apr 1, 2012 at 2:55 PM, sasinda rukshan <sasindarukshan(a)gmail.com>wrote: > Hi, > > I am Sasinda Rukshan from University of Moratuwa Sri Lanka. > I have attached here with a proposal for the Google Android XWiki > Connector. > > Thank You. > > Sasinda Rukshan. >

13 years

[xwiki-devs] Using MacroTransformationContext outside of Macro execution

by Grüner Heinrich

Hi, I want to parse XWiki Syntax in a independent thread (not via xwiki default transformation workflow). how is it possible to intantiate a valid MacroTransformationContext? This Context is needed to call the contentParser. I tried this: MacroTransformationContext mc=new MacroTransformationContext(new TransformationContext()); mc.setSyntax(Syntax.XWIKI_2_0); contentParser.parse(ts.getContent(),mc,true,true); but it threw the following Exception: org.xwiki.rendering.macro.MacroExecutionException: Failed to parse content [ == Werner == * test ] at org.xwiki.rendering.internal.macro.DefaultMacroContentParser.parseXDOM(DefaultMacroContentParser.java:122) at org.xwiki.rendering.internal.macro.DefaultMacroContentParser.parse(DefaultMacroContentParser.java:77) at org.centauron.xwiki.XWikiConnector.getCodeSnipsFromPage(XWikiConnector.java:117) at org.centauron.xwiki.XWikiConnector.getCodeSnipsFromPage(XWikiConnector.java:105) ... Any suggestions? Thanks, Stefan.

13 years

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs April 2012