- xwiki-devs@xwiki.org - lists.xwiki.org

Re: [xwiki-devs] [xwiki-notifications] r24562 - platform/core/branches/xwiki-core-2.0/xwiki-core

by Sergiu Dumitriu

On 10/19/2009 11:27 AM, vmassol (SVN) wrote: > Author: vmassol > Date: 2009-10-19 11:27:22 +0200 (Mon, 19 Oct 2009) > New Revision: 24562 > > Modified: > platform/core/branches/xwiki-core-2.0/xwiki-core/pom.xml > Log: > XWIKI-4496: Unit tests need more heap space > > * Isolate tests. > > Merged from trunk (rev 24561) > > Modified: platform/core/branches/xwiki-core-2.0/xwiki-core/pom.xml > =================================================================== > --- platform/core/branches/xwiki-core-2.0/xwiki-core/pom.xml 2009-10-19 09:23:06 UTC (rev 24561) > +++ platform/core/branches/xwiki-core-2.0/xwiki-core/pom.xml 2009-10-19 09:27:22 UTC (rev 24562) > @@ -819,6 +819,14 @@ > </dependencies> > <build> > <plugins> > +<plugin> > +<groupId>org.apache.maven.plugins</groupId> > +<artifactId>maven-surefire-plugin</artifactId> > +<configuration> > + > +<forkMode>pertest</forkMode> Does this affect performace? As in longer time to run the tests? -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 11 months

3
4
0 0

[xwiki-devs] [VOTE] Release 2.0.2 tomorrow, earlier than planned

by Vincent Massol

Hi devs, Should we release 2.0.2 earlier than planned? Right now it's planned for the 2nd of nov but we have 2 important regressions and people are starting to upgrade to 2.0.1 * regression 1: office import doesn't work in multiwiki mode * regression 2: a table followed by a block with params doesn't render correctly (exception) Thus I'm proposing that we release 2.0.2 tomorrow (Thomas is ok to do it). We have the following issues already fixed in 2.0.2: http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10010… Here's my +1 Thanks -Vincent

15 years, 11 months

5
5
0 0

Re: [xwiki-devs] feedback on code section in Xwiki page

by Leon Wang

Hi Thomas, It works. This is so cool. :-) Thanks. -Leon

15 years, 11 months

1
0
0 0

[xwiki-devs] Applications: MultiPage Export, Recruitment, Todo Macro

by Ludovic Dubost

Hi, I've published a few applications we have been using for a little while: - Multi page export application: http://code.xwiki.org/xwiki/bin/view/Applications/MultiPageExportApplication It's an application allowing to generate PDFs or XARs from multiple page. In conjunction with the collection plugin it allows to create full reports from multiple wiki pages. - Recruitment application: http://code.xwiki.org/xwiki/bin/view/Applications/RecruitmentManagementAppl… It's a new version of the already published application. It now included user evaluations of candidates. - Todo Macro http://code.xwiki.org/xwiki/bin/view/Macros/TodoMacro A cool todo macro using the Wiki Macro feature of XWiki 2.0. You can add todos using the Wysiwyg editor and then manage them directly in view mode. The source code for these different applications is here: http://svn.xwiki.org/svnroot/xwiki/sandbox/applications/ Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

15 years, 11 months

3
2
0 0

[xwiki-devs] feedback on code section in Xwiki page

by Leon Wang

Hi everyone, It seems the code section in Xwiki page can display html tags with color which is cool, but it seems it can not recognize Java code and display it with color. If it can display all sort of codes with colors it will be perfect. Thanks. -Leon

15 years, 11 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r24550 - platform/core/trunk/xwiki-xml

by Thomas Mortagne

On Sun, Oct 18, 2009 at 14:00, vmassol <platform-notifications(a)xwiki.org> wrote: > Author: vmassol > Date: 2009-10-18 14:00:31 +0200 (Sun, 18 Oct 2009) > New Revision: 24550 > > Modified: > platform/core/trunk/xwiki-xml/pom.xml > Log: > Fixed invalid dependencies. At test time the Embedded CM needs to be available... This is already provided by shared-test, it's needed at this level only if the test directly use it. > > Modified: platform/core/trunk/xwiki-xml/pom.xml > =================================================================== > --- platform/core/trunk/xwiki-xml/pom.xml 2009-10-18 11:59:59 UTC (rev 24549) > +++ platform/core/trunk/xwiki-xml/pom.xml 2009-10-18 12:00:31 UTC (rev 24550) > @@ -68,6 +68,12 @@ > <version>${pom.version}</version> > <scope>test</scope> > </dependency> > + <dependency> > + <groupId>org.xwiki.platform</groupId> > + <artifactId>xwiki-core-component-default</artifactId> > + <version>${pom.version}</version> > + <scope>test</scope> > + </dependency> > </dependencies> > <build> > <plugins> > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications > -- Thomas Mortagne

15 years, 11 months

2
6
0 0

[xwiki-devs] XWiki will be at the Enterprise 2.0 Conference in San Francisco and then in Boston - Meetup possible

by Ludovic Dubost

Hi, I will be from Nov2-Nov6 in San Francisco and in the Bay Area. I will also be Nov 8-Nov 10 in Boston. If there are any people that would like to meet at these times, let me know. We could organize a meetup or I could come present XWiki in your company. I would be a great time to exchange about how XWiki is used and what is being done by other XWiki users. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

15 years, 11 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] XWiki updates, 11 documents have been modified since 2009/10/20 00:00

by Vincent Massol

I've rolled-back the spam. -Vincent On Oct 21, 2009, at 12:00 AM, notifications(a)xwiki.org wrote: > Hello Developers, > > This message is sent by XWiki. Here are the documents in your > watchlist that have been modified since the last notification: > <wiki.gif> xwiki > <space.gif> Main > <document.gif> Status Report-Tuesday,13 Oct 2009 Main.Status Report- > Tuesday,13 Oct 2009 > > Between 2009/10/20 11:56 and 2009/10/20 11:57, the document has been > modified 2 times, by 1 user(s): Ma teresa > (((======(((= Status Report from Tuesday, 6Report-Tuesday,13 Oct to > Monday, 12 Oct ======)))2009 = > ==== **Wednesday, 7====== Status Report from Tuesday, 6 Oct 2009 > (time-in-lieu)** ====to Monday, 12 Oct ======))) > ==== **//Wednesday, 7 Oct 2009 (time-in-lieu)//** ==== > ==== **Thursday,**//Thursday, 8 Oct 2009 (time-in-lieu)**(time-in- > lieu)//** ==== > On 2009/10/20 11:54, the document has been created by Ma teresa > <document.gif> Weekly Status Report by llim Main.Status Reports > > Between 2009/10/20 11:38 and 2009/10/20 11:50, the document has been > modified 4 times, by 1 user(s): Ma teresa > (((Weekly(((**Weekly Status Report beginning every Tuesday till > Monday the following week)))week**))) > (((=== 2009-10-06[[image:Edit.png||style="vertical-align: > middle;"]]2009-10-06 === > (((==== [[Status Report - Tuesday, 13 Oct 2009>>http://focus.bne.redhat.com/MainPortal/Members/llim/weekly-status-report/ar… > ]] ====(((====== ====== > Status Report from Tuesday, 6[[Status Report-Tuesday,13 Oct to > Monday, 12 Oct2009>>Status Report-Tuesday,13 Oct 2009||title="Status > Report-Tuesday,13 Oct 2009"]] > Status Report from Tuesday, 6 Oct to Monday, 12 Oct)))))) > )))))) > (((=== 2009-09-29 === > (((==== [[Status Report - Tuesday, 6 Oct 2009>>http://focus.bne.redhat.com/MainPortal/Members/llim/weekly-status-report/ar… > ]] ====(((=== [[image:Edit.png||style="vertical-align: > middle;"]]2009-09-29 === > (((====== [[Status Report - Tuesday, 6 Oct 2009>>http://focus.bne.redhat.com/MainPortal/Members/llim/weekly-status-report/ar… > ]] ====== > <attach.gif>Edit.png: null > 1.1 > On 2009/10/20 11:38, the document has been created by Ma teresa > <document.gif> Weekly Status Report Template Main.Status Reports > Template > > Between 2009/10/20 10:18 and 2009/10/20 11:58, the document has been > modified 6 times, by 1 user(s): Ma teresa > = Weekly Status Report =(% class="documentFirstHeading" %) > = Status Report - Tuesday, [DATE] 2009 = > **Weekly Status(((Status Report beginning every Tuesday till Monday > the following week**from Tuesday, [DATE] to Monday, [DATE]))) > (((((((% class="weblog-day-title" %)(((==== **//Monday, [DATE] 2009// > ** ==== > == 2009-10-06 == > ((((% class="weblog-heading" %)* task one > == [[Status Report - Tuesday, 13 Oct 2009>>http://focus.bne.redhat.com/MainPortal/Members/llim/weekly-status-report/ar… > ]] ==* task two > * task three > ((()))==== **//Tuesday, [DATE] 2009//** ==== > (((Status Report from Tuesday, 6 Oct to Monday, 12 Oct)))))))))* > task one > * task two > * task three > ((((% class="weblog-day-title" %)==== **//Wednesday, [DATE] 2009//** > ==== > == 2009-09-29 == > ((((% class="weblog-heading" %)* task one > == [[Status Report - Tuesday, 6 Oct 2009>>http://focus.bne.redhat.com/MainPortal/Members/llim/weekly-status-report/ar… > ]] ==* task two > * task three > ((()))==== **//Thursday, [DATE] 2009//** ==== > (((Status Report from Tuesday, 29 Sep to Monday, 5 Oct)))))))))* > task one > * task two > * task three > ==== **//Friday, [DATE] 2009//** ==== > * task one > * task two > * task three))) > == ==)))== > On 2009/10/20 10:17, the document has been created by Ma teresa > <document.gif> Support Main.Support > > On 2009/10/20 12:06, the document has been modified by Silvia Rusu > Once you have found the answer, please consider adding an entry in > the [FAQ>FAQ.WebHome] or updating an existing document on this wiki > so thatwiki. This way others will later benefit from that knowledge > aslike you’re benefiting from other’sother people’s knowledge while > browsing this site. > <metadata.gif>author: XWiki.VincentMassol > XWiki.SilviaRusu > <document.gif> status reports of s1 Main.aaa > > Between 2009/10/20 10:05 and 2009/10/20 11:24, the document has been > modified 6 times, by 1 user(s): Ma teresa > (% class="documentFirstHeading" %) > = Status Reports = > adsfadsfadsf[[[[image:Untitled.png||style="vertical-align: > middle;"]]Weekly Status Report Template>>Status Reports Template|| > rel="__blank" title="Weekly Status Report Template"]] > [[[[image:Untitled.png||style="vertical-align: middle;"]]Status > Reports>>Status Reports||title="Status Reports by llim"]] by llim > <attach.gif>Untitled.png: null > 1.1 > <metadata.gif>author: XWiki.VictorChen > XWiki.MaTeresa > On 2009/10/20 09:47, the document has been created by victor chen > <document.gif> aadfadsf Main.aadfadsf > > On 2009/10/20 09:51, the document has been created by victor chen > <space.gif> XWiki > <document.gif> MaTeresa XWiki.MaTeresa > > On 2009/10/20 09:58, the document has been modified by Ma teresa > <object.gif>XWiki.WatchListClass > On 2009/10/20 09:57, the document has been created by XWikiGuest > <document.gif> VictorChen XWiki.VictorChen > > On 2009/10/20 09:46, the document has been modified by victor chen > <object.gif>XWiki.WatchListClass > On 2009/10/20 09:45, the document has been created by XWikiGuest > <document.gif> donovaly XWiki.donovaly > > On 2009/10/20 14:42, the document has been modified by Uwe Stöhr > <object.gif>XWiki.WatchListClass > On 2009/10/20 14:42, the document has been created by XWikiGuest > <document.gif> ppfootstar XWiki.ppfootstar > > On 2009/10/20 17:38, the document has been created by XWikiGuest > <document.gif> silvergate XWiki.silvergate > > On 2009/10/20 00:10, the document has been modified by Mark > Kellenbergh > <object.gif>XWiki.WatchListClass > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

15 years, 11 months

1
0
0 0

[xwiki-devs] [Idea] Keep tabs opened for wiki pages

by Vincent Massol

Hi, Here's an idea: Have tabs in the xwiki UI so that when you navigate to a new page you can keep tabs opened and thus switch back and forth between opened pages quickly. Same as in an IDEA (or in the Nexus UI). Just an idea... (haven't even thought about how to implement it). -Vincent

15 years, 11 months

6
8
0 0

Re: [xwiki-devs] [xwiki-notifications] r24576 - in platform/core/trunk/xwiki-webdav/src/main/java/com/xpn/xwiki/plugin/webdav: . resources/domain resources/partial resources/views resources/views/attachments resources/views/pages

by Asiri Rathnayake

Hi, > --- > platform/core/trunk/xwiki-webdav/src/main/java/com/xpn/xwiki/plugin/webdav/XWikiDavServlet.java > 2009-10-20 11:50:17 UTC (rev 24575) > +++ > platform/core/trunk/xwiki-webdav/src/main/java/com/xpn/xwiki/plugin/webdav/XWikiDavServlet.java > 2009-10-20 11:51:34 UTC (rev 24576) > @@ -74,17 +74,17 @@ > /** > * Locator factory. {@link DavLocatorFactory} > */ > - private DavLocatorFactory locatorFactory; > + private transient DavLocatorFactory locatorFactory; > > /** > * Resource factory. {@link DavResourceFactory} > */ > - private DavResourceFactory resourceFactory; > + private transient DavResourceFactory resourceFactory; > > /** > * Session provider. {@link DavSessionProvider} > */ > - private DavSessionProvider sessionProvider; > + private transient DavSessionProvider sessionProvider; > This might be a bad way to fix the findbugs errors. I just used it to see if it works and committed without second thoughts. Any ideas on how to fix the "mutable servlet field" error in a better way? Thanks. - Asiri

15 years, 11 months

3
9
0 0

[xwiki-devs] [Discussion] Annotations feature current state and roadmap

by Anca Luca

Hello devs, The current state of the annotation feature in the sandbox can be described by the follwing: * there is a single type of annotation which can be added, using a specific javascript client backed by a rest service. Such an annotation contains an annotation text, the annotated content and its position and this type is highly coupled in the plugin implementation * the backing annotation storage is based on components, currently with an XWiki objects implementation but a different service can be easily created (there is one implemented for Scribo annotations stored in RDF) * for the moment, only xwiki documents and feed entries fetched by the feedreader plugin can be used as targets for annotations (the annotated documents), with the restriction that the content of the document is *not* generated using scripting. A component can be implemented for a new type of document but the current UI (the javascript client) is *specific to xwiki documents* * the javascript client (UI) is only in the state of a prototype: while proving that it works, it is not robust enough and the user experience is poor * annotation creation algorithm seems to perform well in practice, but we should put it to more real-world test (by releasing). Some *requirements* in terms of functionality, in order to make this an extensible and flexible feature, would be to: * be able to have different types of annotations (one to be able to easily specify fields for the annotations to add), with storage as xwiki objects. This needs to be flexible at all levels: UI and storage backend, preferably using xwiki scripting (no jars on the server side, or java coding) so that it can be easily customized. Also, the annotation UI should be thought of as easy to customize and create whatever forms and actions in a light manner. * be able to annotate any type of document (object inside such a document), namely all or any number of text fields in such an object. Preferably this should also be doable only using xwiki scripting or configuration. I would like to propose the following road to perfect this feature: *Version 1.0* (somewhere in the timeframe of XE 2.1 RCs) The aim would be to take feature out of sandbox preserving its current features: allowing to add a specific type of annotation saved as XWiki object on a regular, non scripted XWiki Document. We should: - format, improve comments, generally clean up the current code sandbox to match XWiki coding styles - refactor packages and components to remove some dependencies issues and increase flexibility - simplify flow, stripping out all code which is not strictly needed by the targeted functionality (such as the Feed entry handling code), and make it easily implementable by a component in a distinct jar (so that the Scribo requirements currently implemented can be preserved) - finish the javascript client: robust user interaction, intuitive interface, cleaned up integration with XE - ensure quality assurance process by a well setup battery of tests, unit and functional At this point I propose to have the annotation feature as an installable plugin but not included by default in XE, unless after a few bugfixing cycles. *Version 1.1* (somwhere in the timeframe of XE 2.2, at the beginning of next year) * first iteration on the 2 desired features. At this point one should be able to configure the type of annotation to add, UI should be accomodate this type, backing XWiki storage should be easy to integrate with any annotation storage service (for Scribo requirements), and one should easily set a field in a structured document which would support annotations. (Note that this might require heavy rewrite / refactor of the 1.0 version. We could decide to skip it and go straight to this version, but it would take longer.) * integration of Scribo requirements can be met at this point by setting the configurations according to the Scribo annotation type and target requirements. At this point, if we find appropriate, we could make the decision of including the annotation feature in XE by default *Version 1.2* (future) * finish the 2 requirements, integration with Scribo would be done in the same manner, by specific configuration and storage backend specific implementation. What do you think? For the moment I will focus on version 1's tasks while finding a good architecture to achieve the desired requirements, converting, where necessary, the direction of the development towards that goal. Thanks (for reading this very long mail), Anca

15 years, 11 months

6
16
0 0

[xwiki-devs] XWikiRemoteServiceServlet for component based GWT RPC services

by Marius Dumitru Florea

Hi devs, Following http://stuffthathappens.com/blog/2009/09/14/guice-with-gwt/ I've made a simple servlet that dispatches GWT requests to corresponding components. Here's the code: public class XWikiRemoteServiceServlet extends RemoteServiceServlet { public String processCall(String payload) throws SerializationException { try { RPCRequest req = RPC.decodeRequest(payload, null, this); RemoteService service = (RemoteService) Utils.getComponent(req.getMethod().getDeclaringClass()); return RPC.invokeAndEncodeResponse(service, req.getMethod(), req.getParameters(), req .getSerializationPolicy()); } catch (IncompatibleRemoteServiceException ex) { log("IncompatibleRemoteServiceException in the processCall(String) method.", ex); return RPC.encodeResponseForFailure(null, ex); } } } I tested it with the new MacroService component (to be committed in WYSIWYG code) and it works great. I'm wondering where to place this servlet since it's generic and should be used by all GWT applications that use services. I'm hesitating to place it in web/gwt because I think this is "new" code, component oriented while the gwt module depends on the old xwiki-core. Another question is if it's OK to use Utils.getComponent(Class) or should we find a way to inject the component manager. They use a GuiceFilter to do this in the tutorial I pointed out. WDYT? Thanks, Marius

15 years, 11 months

1
0
0 0

[xwiki-devs] Technical debt is increasing, let's fight it

by Vincent Massol

Hi, We now have the second run of sonar on xwiki at http://nemo.sonarsource.org/timemachine/index/178319 As you can see it's not going in the right direction and the technical debt is increasing. Even though I have been fixing several findbugs errors so it means even more were added... Can we make an effort to put it back on track and ensure it's going to be decreasing for the next run on next Monday? Thanks -Vincent

15 years, 11 months

1
0
0 0

[xwiki-devs] [Proposal] Create xwiki-gwt-diff module

by Marius Dumitru Florea

Hi devs, The diff package from the WYSIWYG editor source is used only by the sync (real time) plugin and it's suppose to be generic. I propose to move this package outside of the WYSIWYG editor in a separate module: platform/web/xwiki-gwt-diff The package will become: org.xwiki.gwt.diff.* You can see the sources here http://svn.xwiki.org/svnroot/xwiki/platform/web/trunk/wysiwyg/src/main/java… Here's my +1. WDYT? Thanks, Marius

15 years, 11 months

4
5
0 0

[xwiki-devs] [Proposal] Rename platform/gwt module to platform/xwiki-gwt-api

by Marius Dumitru Florea

Here's my +1. WDYT? Thanks, Marius

15 years, 11 months

2
3
0 0

[xwiki-devs] [Proposal] Rename platform/web/wysiwyg module to platform/web/xwiki-gwt-wysiwyg

by Marius Dumitru Florea

In addition I'd like to changed the package from: com.xpn.xwiki.wysiwyg.* to org.xwiki.gwt.wysiwyg.* Here's my +1. WDYT? Thanks, Marius

15 years, 11 months

2
2
0 0

[xwiki-devs] BoldTest.testTimeComplexity() generates StackOverflow error

by Vincent Massol

Hi Sergiu, Could you have a look at BoldTest.testTimeComplexity(). It generates a stackoverflow error in the console: java.lang.StackOverflowError at java.util.regex.ASCII.isType(ASCII.java:185) at java.util.regex.Pattern$Ctype.isSatisfiedBy(Pattern.java:3444) at java.util.regex.Pattern$CharProperty$1.isSatisfiedBy(Pattern.java: 3337) at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168) at java.util.regex.Pattern$Behind.match(Pattern.java:4648) at java.util.regex.Pattern$LazyLoop.match(Pattern.java:4353) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227) at java.util.regex.Pattern$BranchConn.match(Pattern.java:4078) at java.util.regex.Pattern$Curly.match2(Pattern.java:3821) at java.util.regex.Pattern$Curly.match(Pattern.java:3748) at java.util.regex.Pattern$Branch.match(Pattern.java:4114) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168) Thanks -Vincent

15 years, 11 months

1
0
0 0

Re: [xwiki-devs] GWT tree Interact with WYSIWYG editor

by Leon Wang

Hi Marius, Since the first approach which is "1) edit the wysiwyg_createEditor velocity macro from macros.vm" is simpler, I will modify macros.vm. You said "new WysiwygEditor($jsVarName); with something like window["${fieldId}_editor"] = new WysiwygEditor($jsVarName);" Could you please explain briefly what does "window["${fieldId}_editor"]" mean? What is it for? Is it a function of javascript? In the macros.vm I found "Wysiwyg.onModuleLoad(function() {new WysiwygEditor($jsVarName); $jsVarName = undefined;});", I did not find any "window" stuff. So after the first step, I got the reference, is the reference stored in window["${fieldId}_editor"] variable? Since don't depend at all on WYSIWYG Java code is not possible and do not bring you more work, I think should go with "i) access the editor in Java (GWT) code by writing a simple native getter". For the code you provided "editorJSReference.@com.xpn.xwiki.wysiwyg.client.editor.WysiwygEditorApi::editor;" I never saw code like this, is the @ for Java annotation or Component? Is there any document I can read to learn about the related rationale/knowledge? 'cause I have no clue what it means. So this line will return the WYSIWYG editor's reference restored/declared in the macros.vm file? I tried to add a new page in the draft document for Loading GWT in Xwiki page, It seems I can't add new page, only editing existing document. Should I add something behind your "Writing GWT applications in XWiki", so you could create a new one or something else. If there are work I can do to save your time or to make Xwiki better, feel free to assign me the work. I am more than happy to help. Thank you for taking your time to help me! -Leon

15 years, 11 months

2
1
0 0

[xwiki-devs] Duplications & debt - REST/XMLRPC and WebDAV

by Vincent Massol

Hi Asiri, I see there's 10% of code duplication in the webdav module: http://nemo.sonarsource.org/project/index/181898 This is the highest of all modules. Do you think you could have a look? Second worst is REST with 5% http://nemo.sonarsource.org/components/index/178319 In term of technical debt, WebDAV module is also high with 9.5% and the highest is the XMLRPC module with 12.2%. Thanks -Vincent

15 years, 11 months

4
5
0 0

[xwiki-devs] Meeting Manager Annoucement

by Ludovic Dubost

Hi, We have published the Meeting Manager application which has been sponsored by "Groupe Glon". The meeting manager is an XWiki 2.0 application which allows to plan and manage meetings and meeting cycles. It's a very nice and complete application. You can plan your meeting by setting an agenda, adding participants and propose a vote for meeting dates (a little like Doodle). You can then write your meeting notes. You can download the Meeting manager application here: http://code.xwiki.org/xwiki/bin/view/Applications/MeetingManagerApplication For developers, the source code is available here: http://svn.xwiki.org/svnroot/xwiki/sandbox/applications/xwiki-application-m… Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

15 years, 11 months

1
0
0 0

[xwiki-devs] More memory needed for build?

by Vincent Massol

Hi, Today I just got my first OOM when building xwiki. It happened in the xwiki-core tests: Running com.xpn.xwiki.notify.PropertyChangedRuleTest org.apache.maven.surefire.booter.SurefireExecutionException: Java heap space; nested exception is java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space The bad part is that I'm building with: MAVEN_OPTS=-Xmx1024m Anyone else has noticed a memory req increase in the build? Thanks -Vincent

15 years, 11 months

2
4
0 0

Re: [xwiki-devs] Background button of WYSIWYG toolbar and GWT

by Leon Wang

Thank you Guillaume! It works now! Hello Marius, I have improved the document http://platform.xwiki.org/xwiki/bin/view/AdminGuide/WysiwygEditor by giving an example how to add a new button to the toolbar of WYSIWYG editor. At first, I thought only Xwiki people who created Xwiki can edit the document. Today I tried to register and I know I can edit it too! That's great! I also can write a document about how to Load GWT application to Xwiki page, do you know where should I place this new document? Should I place it in a existing page or should place create a new page? Marius, I will digest what your replied last time. Thank you! :-D PS: I will be in China during Dec 26 ~ Jan 11, 2011, if anyone xwiki people have a chance to come to Beijing let me know I will should you around. Have a nice week everyone!

15 years, 11 months

2
1
0 0

[xwiki-devs] XWiki at the Enterprise 2.0 Conference in California

by Ludovic Dubost

We did it !!!! http://enterprise2blog.com/2009/10/drum-roll-please-our-launch-pad-finalist… I want to all thank you for helping making this happen. This is just great for XWiki. With this conference where we get 5 minutes on stage in the keynote room + a mini-pod in the exposition room, we will get a huge exposure for XWiki. If there are some Californian's that want to meet while I'm there in San Francisco, please tell me. It Nov 2nd, 3rd at the Moscone. I'll probably stay a few days after. Do come see us at the exposition. If you have a great usage of XWiki come even more to show it to other potential users of XWiki. The best way to help XWiki is to spread it's usage. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

15 years, 11 months

3
2
0 0

[xwiki-devs] [Colibri] CSS Cleanup

by Ecaterina Valica

Hi devs, One of the items for the 2.1 XE is: "Clean the colibri skin so that it's no longer a pile of code added on top of Toucan" I would ask you to help me test the cleanup for the Colibri skin. The cleanup was made on the XE 2.0 release. You can find colibri.css, ie-6.css and ie-all.css at: http://incubator.myxwiki.org/xwiki/bin/download/Skins/ColibriClean/colibri.… http://incubator.myxwiki.org/xwiki/bin/download/Skins/ColibriClean/ie-6.css http://incubator.myxwiki.org/xwiki/bin/download/Skins/ColibriClean/ie-all.c… >From the original colibri.css size of 73,9 Ko and 4408 lines of code, now we have 29,7 Ko and 1526 lines of code. My problem is that I didn't delete too much. You can find the leftovers at: http://incubator.myxwiki.org/xwiki/bin/download/Skins/ColibriClean/colibriL… The code could be even more compressed if there weren't so many inconsistencies in the markup for doing the same thing (ex. button usage, panel input elements, etc). I didn't use anything from the colibri/ie.css - so this can be deleted if the cleanup is accepted and committed. There are some standards in the cleanup, like: - alphabetical order for the css proprieties; - 2 spaces indentation for the proprieties; - comment headers for separation and grouping of different parts of the code; - "Overwrites" and "Should be in" comments for dependencies overwriting. It would be nice if the code can be tested in a more "advanced" manner to cover for the unusual parts that I might not cover in my testing. There are some minor differences from the XE2.0 Colibri in the display. My request is: if you find one of those be sure it doesn't have another style associated or the problem is not in the CSS, but in the markup. You can report bugs replying to this mail or on the incubator page http://incubator.myxwiki.org/xwiki/bin/view/Skins/ColibriClean Thank you, Caty

15 years, 11 months

2
3
0 0

[xwiki-devs] [Proposal] Automatically inherit the "View" right from the "Edit" right

by Guillaume Lerouge

Hi Devs, right now an user can have edit rights on a page even though he does not have the view right on that page. This sounds weird to me since that user can still access the page's content by going to the right URL. Thus I think it would be better to have the view right inherited from the edit right (if an user can edit a page he should also be able to view it). Is there any drawback to this? Here's the matching JIRA issue: http://jira.xwiki.org/jira/browse/XWIKI-4491 Thanks for your feedback, Guillaume -- Guillaume Lerouge Product Manager - XWiki SAS Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/

15 years, 11 months

3
3
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs