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

Re: [xwiki-devs] [xwiki-notifications] r18051 - in platform/core/trunk/xwiki-rendering: xwiki-rendering-api/src/main/java/org/xwiki/rendering/internal/transformation xwiki-rendering-api/src/test/java/org/xwiki/rendering/internal/transformation xwiki-

by Thomas Mortagne

fixed On Fri, Mar 27, 2009 at 09:50, Vincent Massol <vincent(a)massol.net> wrote: > > On Mar 26, 2009, at 9:48 PM, tmortagne (SVN) wrote: > >> Author: tmortagne >> Date: 2009-03-26 21:48:42 +0100 (Thu, 26 Mar 2009) >> New Revision: 18051 >> >> Added: >> platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/test/ >> java/org/xwiki/rendering/internal/transformation/ >> TestSimpleInlineMacro.java >> platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- >> rendering-macro-box/src/test/resources/macrobox6.test >> platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ >> resources/macros/macro14.test >> Modified: >> platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/main/ >> java/org/xwiki/rendering/internal/transformation/ >> MacroTransformation.java >> platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/test/ >> java/org/xwiki/rendering/internal/transformation/TestSimpleMacro.java >> platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/test/ >> resources/META-INF/plexus/components.xml >> platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- >> rendering-macro-box/src/test/java/org/xwiki/rendering/ >> RenderingTests.java >> platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ >> java/org/xwiki/rendering/RenderingTests.java >> Log: >> XWIKI-3461: A non-inline {{box}} after an inline one is rendered as >> inline >> > > [snip] > >> Modified: platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/ >> xwiki-rendering-macro-box/src/test/java/org/xwiki/rendering/ >> RenderingTests.java >> =================================================================== >> --- platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- >> rendering-macro-box/src/test/java/org/xwiki/rendering/ >> RenderingTests.java 2009-03-26 19:50:15 UTC (rev 18050) >> +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- >> rendering-macro-box/src/test/java/org/xwiki/rendering/ >> RenderingTests.java 2009-03-26 20:48:42 UTC (rev 18051) >> @@ -37,11 +37,12 @@ >> { >> RenderingTestSuite suite = new RenderingTestSuite("Test Box >> Macro"); >> >> - suite.addTestsFromResource("macrobox1", true); >> + /*suite.addTestsFromResource("macrobox1", true); >> suite.addTestsFromResource("macrobox2", true); >> suite.addTestsFromResource("macrobox3", true); >> suite.addTestsFromResource("macrobox4", true); >> - suite.addTestsFromResource("macrobox5", true); >> + suite.addTestsFromResource("macrobox5", true);*/ > > Seems you have forgotten to remove comments. > > [snip] > > Thanks > -Vincent > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne

16 years, 6 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r18051 - in platform/core/trunk/xwiki-rendering: xwiki-rendering-api/src/main/java/org/xwiki/rendering/internal/transformation xwiki-rendering-api/src/test/java/org/xwiki/rendering/internal/transformation xwiki-rendering-api/src/test/resources/META-INF/plexus xwiki-rendering-macros/xwiki-rendering-macro-box/src/test/java/org/xwiki/rendering xwiki-rendering-macros/xwiki-rendering-macro-box/src/test/resources xwiki-rendering-tests/src/test/java/org/xwiki/rendering xwiki-

by Vincent Massol

On Mar 26, 2009, at 9:48 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-03-26 21:48:42 +0100 (Thu, 26 Mar 2009) > New Revision: 18051 > > Added: > platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/test/ > java/org/xwiki/rendering/internal/transformation/ > TestSimpleInlineMacro.java > platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-box/src/test/resources/macrobox6.test > platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ > resources/macros/macro14.test > Modified: > platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/main/ > java/org/xwiki/rendering/internal/transformation/ > MacroTransformation.java > platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/test/ > java/org/xwiki/rendering/internal/transformation/TestSimpleMacro.java > platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/test/ > resources/META-INF/plexus/components.xml > platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-box/src/test/java/org/xwiki/rendering/ > RenderingTests.java > platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ > java/org/xwiki/rendering/RenderingTests.java > Log: > XWIKI-3461: A non-inline {{box}} after an inline one is rendered as > inline > [snip] > Modified: platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/ > xwiki-rendering-macro-box/src/test/java/org/xwiki/rendering/ > RenderingTests.java > =================================================================== > --- platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-box/src/test/java/org/xwiki/rendering/ > RenderingTests.java 2009-03-26 19:50:15 UTC (rev 18050) > +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-box/src/test/java/org/xwiki/rendering/ > RenderingTests.java 2009-03-26 20:48:42 UTC (rev 18051) > @@ -37,11 +37,12 @@ > { > RenderingTestSuite suite = new RenderingTestSuite("Test Box > Macro"); > > - suite.addTestsFromResource("macrobox1", true); > + /*suite.addTestsFromResource("macrobox1", true); > suite.addTestsFromResource("macrobox2", true); > suite.addTestsFromResource("macrobox3", true); > suite.addTestsFromResource("macrobox4", true); > - suite.addTestsFromResource("macrobox5", true); > + suite.addTestsFromResource("macrobox5", true);*/ Seems you have forgotten to remove comments. [snip] Thanks -Vincent

16 years, 6 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r18050 - in platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-toc/src: main/java/org/xwiki/rendering/internal/macro/toc test/java/org/xwiki/rendering test/resources

by Vincent Massol

On Mar 26, 2009, at 8:50 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-03-26 20:50:15 +0100 (Thu, 26 Mar 2009) > New Revision: 18050 > > Added: > platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-toc/src/test/resources/macrotoc9.test > Modified: > platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-toc/src/main/java/org/xwiki/rendering/internal/macro/ > toc/TocMacro.java > platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-toc/src/test/java/org/xwiki/rendering/ > RenderingTests.java > platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-toc/src/test/resources/macrotoc3.test > Log: > XWIKI-3462: TOC not displaying properly > [snip] > Added: platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/ > xwiki-rendering-macro-toc/src/test/resources/macrotoc9.test > =================================================================== > --- platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-toc/src/test/resources/ > macrotoc9.test (rev 0) > +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki- > rendering-macro-toc/src/test/resources/macrotoc9.test 2009-03-26 > 19:50:15 UTC (rev 18050) > @@ -0,0 +1,129 @@ > +.#----------------------------------------------------- > +.input|xwiki/2.0 Maybe a little description here to explain what this test is testing since it's not immediately obvious. > > +.#----------------------------------------------------- > += Level 1 > + > +{{toc start=1 depth=3 numbered=false scope=page /}} > + > +== Level 2a > + > +=== Level 3a > + > +=== Level 3b > + > += Level 2b > + > +=== Level 3c [snip] Thanks -Vincent

16 years, 6 months

2
1
0 0

[xwiki-devs] [PROPOSAL] wiki=false by default in html macro

by Thomas Mortagne

Hi devs, Currently in the html macro the wiki parser is applied. That means that if you expected the html you put inside the macro you could have unpleasant surprises. I think putting just html in the html (eventually some velocity) is the most common use case and it's easier for a user to understand that the wiki content inside the html macro is not applied because it's not enabled that "this does not looks like the html I put". Another way to say it is that we will get a lot more mail on the list with wiki=true than wiki=false ;) I propose to change wiki=true by wiki=false by default. Here is my +1 -- Thomas Mortagne

16 years, 6 months

4
4
0 0

[xwiki-devs] Annotations for our components

by Vincent Massol

Hi devs, I'm continuing on this topic since I really believe we need annotations now. However I think it's best to have our own annotations for injection. One reason we need annotation (amongst other needs) is in order to be able to create a xwiki uberjar for rendering modules for example. With components.xml you cannot easily merge jars since you'd need to merge components.xml so you'd need to write some xslt code for that. Another reason is that we have to comment in the code things such as "this field is injected automatically by the component manager". Of course this comment is forgotten most of the time. It's much nicer to have a @Inject annotation. Last we need annotations if we want to be able to more easily support different IOC frameworks since otherwise it means that for each fwk we need to do again all components mappings in a static way. Of course one basic need is evidently to reduce the number of config lines we have to write and the errors associated with them. I'm going to look into plexus annotations for a starter (+ guice) to see how they do it and then I'll make a proposal for annotations. Let me know what you think. Thanks -Vincent

16 years, 6 months

3
4
0 0

[xwiki-devs] [Proposal] Components Annotations

by Vincent Massol

Hi, To start with I propose to model against the plexus annotations but more simple: * Component * Requirement * Configuration /** * Marks a class as a XWiki component. */ @Documented @Retention(RUNTIME) @Target(TYPE) @Inherited public @interface Component { Class<?> role(); String hint() default ""; String instantiationStrategy() default ""; } /** * Configures a requirement. */ @Documented @Retention(RUNTIME) @Target({ FIELD, METHOD }) @Inherited public @interface Requirement { Class<?> role() default Object.class; String hint() default ""; // // HACK: This is here to support component requirement lists, which can take a list of hints // String[] hints() default {}; } Note: not sure yet why plexus says it's a hack. /** * Marks a field as a configuration element with a default value. */ @Documented @Retention(RUNTIME) @Target(FIELD) @Inherited public @interface Configuration { String name() default ""; String value(); } So for example in the code you'd have: @Component(role=Parser.class) public class WikiModelXWikiParser implements Parser... { @Requirement private LinkParser linkParser; .... wdyt? I'm still researching. Thanks -Vincent

16 years, 6 months

2
2
0 0

[xwiki-devs] [VOTE] Release date and roadmap for 1.8.1

by Vincent Massol

Hi, I'm proposing that we release XE 1.8.1 on the 6th of April. It would have been 3 weeks since the release of 1.8 and we'll have plenty of important fixes and improvements for our users. Note that 1.8.1 is mainly for rendering/wysiwyg improvements. The roadmap is currently defined in jira: - For wysiwyg http://tinyurl.com/d75olg - For rendering http://tinyurl.com/cwpchk Note that more issues will be put for rendering and other domain. The idea is to time box this for the 6th of April. Here's my +1 Thanks -Vincent

16 years, 6 months

5
4
0 0

Re: [xwiki-devs] [xwiki-notifications] r18027 - in platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg: client/plugin/macro/exec client/widget/rta/internal server server/cleaner/internal server/converter/internal

by Vincent Massol

Hi Marius, On Mar 26, 2009, at 12:26 AM, mflorea (SVN) wrote: > Author: mflorea > Date: 2009-03-26 00:26:55 +0100 (Thu, 26 Mar 2009) > New Revision: 18027 > > Modified: > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > client/plugin/macro/exec/RefreshExecutable.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > client/widget/rta/internal/IEBehaviorAdjuster.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/DefaultWysiwygService.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/cleaner/internal/DefaultHTMLCleaner.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/cleaner/internal/WysiwygCleaningFilter.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/converter/internal/EventsHTMLConverter.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/converter/internal/XWikiHTMLConverter.java > Log: > Updated the WYSIWYG code due to: > * XWIKI-3456: Provide way to control the HTML cleaning filters > executed by the HTML Cleaner > * XWIKI-3457: XHTML parser shouldn't run the HTML Cleaner > Also some minor IE fixes. [snip] > import com.xpn.xwiki.web.Utils; > import com.xpn.xwiki.wysiwyg.server.cleaner.HTMLCleaner; > @@ -49,8 +53,12 @@ > { > org.xwiki.xml.html.HTMLCleaner cleaner = > (org.xwiki.xml.html.HTMLCleaner) > Utils.getComponent(org.xwiki.xml.html.HTMLCleaner.ROLE); > - Document document = cleaner.clean(new > StringReader(dirtyHTML)); > - filter.filter(document); > + HTMLCleanerConfiguration config = > cleaner.getDefaultConfiguration(); > + List<HTMLFilter> filters = new ArrayList<HTMLFilter>(); > + filters.add(filter); I think it would be good to add a good comment here explaining why you have to run your filter first. > > + filters.addAll(config.getFilters()); > + config.setFilters(filters); > + Document document = cleaner.clean(new > StringReader(dirtyHTML), config); > return XMLUtils.toString(document); > } > } [snip] Thanks -Vincent

16 years, 6 months

2
1
0 0

[xwiki-devs] [Proposal] Find out active XE installations

by Vincent Massol

Hi devs, I think it would be interesting for us to know how many people install and use our software. Of course we'd need to do this in a non intrusive manner that adds value for the user. Here's an idea Ludovic and I have discussed: * In the administration page add a blog panel by default (replacing the create page panel for ex which IMO isn't needed there) showing the last 5 RSS feeds from xwiki.org -> This is useful for the admin users since they need to know the latest versions and news about the software they use -> They can remove the panel easily if they don't want to see news -> We can generate a unique id based on the user's system (http://johannburkard.de/blog/programming/java/Java-UUID-generators-compared… ) so that we can identify active installs We could then define what we call an active install (say a ping at least once every month for ex) and we can find: - how many new installs per day/month/year - how many users stop using xwiki after some time and what the average time it's used actively Obviously we won't get perfect data (people will remove the panel, others won't be connected to the internet, etc) that but it seems to me it would a good guess. Once we get this data we could display it on xwiki.org (we could even display it in the stats space with the other data). WDYT? Thanks -Vincent

16 years, 6 months

3
5
0 0

[xwiki-devs] GSOC 2009 : Google Docs Integration in XWIKI

by Arun Reddy

Hello devs, I am interested in the idea of "Google Docs Integration in XWIKI ". This idea is an extension to the existing Google Docs Plugin : http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Google+Docs+Integrat… I have successfully installed that plugin with the help of sergiu and ludovic. Learnt how it works. Looking out how to integrate various google documents ( docs,spreasheets,. powerpoint) into xwiki. I will be happy if you can post few of your ideas on what all features can be included and considered for extending this feature. -- Best Regards, Arun Reddy

16 years, 6 months

2
2
0 0

[xwiki-devs] status of "Social Networking via OpenID support in Xwiki?" for GSOC?

by Niels Mayer

I've noted some more comments about widget integration in general, but nothing as specific or useful (IMHO) as a project to integrate http://www.google.com/friendconnect/ ( http://www.youtube.com/v/N94s7ix0JPo&hl=en&autoplay=1 ) with Xwiki. That way people with the appropriate ID/credentials compatible w/ google friendconnect's OpenID would be able to login and leave authenticated comments on a wiki. A while back Thilina Buddhika ( http://www.mail-archive.com/devs@xwiki.org/msg07563.html ) expressed interest in this subject on this list; I was wondering if that interest continues, or if others might find this an interesting pursuit for GSOC 2009. The user experience should be that those w/ openID credentials should get an automatic login into Xwiki, and that the same authentication would also drive the friendconnect "widgets." I think the widgets themselves could easily be integrated into Xwiki's existing panel system. Therefore, the main work would be in creating a smoothly-integrated OpenID-based auth system giving appropriately credentialed users an automatic "authenticated guest" login. This login allows authenticated comments and registration, making commenting much easier and straightforward in Xwiki. Also, registration could always associated with a real user and not a spam account at mail.ru... Although the construction of widget "panels" itself might be simple, some of the authorization issues might be thorny. For example, do you publicly display your friends-list-widget-panel to all unauthenticated users and search engines, or do only logged-in users get access? Likewise, when "friends" log in or view your site, they might automatically receive special privilege based on their authenticated-friend status, e.g. view-access to a private part of the wiki, for example. This might require extension of the Rights system in Xwiki with extra roles alongside "unathenticated user", such as "openid authenticated user" and "openid authenticated friend." ... Here's the original messages and a summary of replies: On 02 Feb 2009, Thilina Buddhika wrote: [xwiki-devs] Possible project ideas for XWiki in GSoC 2009 I have a growing interest on XWiki and willing to take part in its development. I am also planning to apply for GSoC 2009 (yet to be announced) and I have realised that XWiki is a challenging and promising open source project for GSoC 2009. When watching the developer list, I found this mail by Niels Mayer with the subject,* "Social Networking via OpenID support in Xwiki?"*. And It looks like an intersting idea. I also found that there was a GSoC 2008 project related to this idea [1]. So is it possible to continue this project further? Other than the above idea, I would like to know the other possible project ideas for GSoC 2009. If it is too early I am posting about this, then lets leave it for the next couple of weeks. Anyway I am trying to get familiarized with Xwiki until the GSoC 2009 is announced. [1] - http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SSOAndOpenIDSupport ................................... from: Niels For some strange reason, I think this is an excellent idea :-) > > Of these, which has the easiest to integrate: > http://www.google.com/friendconnect/ > http://developers.facebook.com/connect.php > > http://developer.myspace.com/Community/blogs/devteam/archive/2008/12/09/int… > > Friendconnect has always looked most interesting of the lot, since it will > give you a variety of customizable friendconnect "widgets" . Once you > request and customize a particular instance, google generates the code and > presents it in a scrollable textarea. > > Reusing the framework of one of Xwiki's existing panels is a good way to > wrap Google Friendconnect socialnetworking into an Xwiki site. You'd > basically take the code and paste it into the panel document. Then layout > one or more of the google panels into the "sidebars" in Xwiki. This permits > xwiki to layout the friendconnect panels as if they were :"one of it's > own." > > Probably the easiest first-experiment would be to take an existing panel > that you probably don't use, like /xwiki/bin/inline/Panels/Welcome; as > 'Admin' click "edit" and then paste in the google code between > #panelheader("Welcome") and #panelfooter(). Later, create more via > http://nielsmayer.com/xwiki/bin/view/Panels/CreatePanel ... > > This video shows what happens on the google-side: > http://www.youtube.com/v/N94s7ix0JPo&hl=en&autoplay=1 > > I haven't looked at friendconnect's OpenID implementation so I don't know > how it would coexist or overlap w/ Xwiki's auth. > I'd assume you'd create an implementation per > > http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-core/src/main/… > follow instructions in > > http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication#HCustomA… > > You mentioned GSOC 2008 and > http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SSOAndOpenIDSupport > ... > what is the status of any code completed to date? > ............................... Vincent Massol: I'm pretty sure we'll all want to have widget integration as a GSOC > 2009 project (open social, etc). > ............................... Thomas Mortagne: > The OpenId authenticator and provider already works pretty well based > in the current not very clean authentication api with some hack > > because Markus did not had choice to do this otherwise. I just did not > had time to integrate it yet in the trunk but Raffaello Pelagalli > started do to some test with it to integrate between > http://l10n.xwiki.org and xwiki.org farms (l10n is on its own instance > > of XWiki). > > See http://jira.xwiki.org/jira/browse/XWIKI-2630 , > http://jira.xwiki.org/jira/browse/XWIKI-2588 and > http://jira.xwiki.org/jira/browse/XSALBATROSS-34 > > .................................. Markus Lanthaler: > Right. The implementation is complete but I guess the tests are still > missing (kind of difficult to write meaningful tests for it). > > The implementation supports both, RP and server. XWiki can accept OpenIDs > from other sites as well as issue OpenIDs to be used on other sites > supporting OpenID. That way you can use your XWiki account all over the web > > (well at least on sites that support OpenID). > > Niels http://nielsmayer.com

16 years, 6 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r17994 - in platform/core/branches/xwiki-core-1.8: xwiki-core/src/main/java/com/xpn/xwiki/doc xwiki-core/src/test/java/com/xpn/xwiki/doc xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/bloc

by Thomas Mortagne

On Wed, Mar 25, 2009 at 15:51, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: > tmortagne (SVN) wrote: >> + if (header.getLevel().getAsInt() <= HeaderLevel.LEVEL2.getAsInt()) { > > Couldn't the level be Comparable? Actually, as an enum, it already is. Improving the code by using it. Thanks Sergiu > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne

16 years, 6 months

1
0
0 0

[xwiki-devs] [Proposal] XE 1.9 + XE 2.0 + Roadmap for XE 1.9

by Vincent Massol

Hi devs, XE 2.0 ===== We've had discussion about XE 2.0 in the past. I think now is the right time to release it and we should prepare to do so. Two reasons; 1) We've had a lot of new features (new rendering, new wysiwyg, webdav, REST, office import, usability improvements, etc) added recently in 1.8 and this alone warrants calling it 2.0. The new rendering and new wysiwyg could be set as default in XE 2.0. 2) XE 1.0 marked a stability level. XE 2.0 will mark another stability level (I'm thinking about the old wysiwyg editor which could be said to be stable...) 3) It's been almost exactly 2 years since we released XE 1.0, it's high time for a major release. However since we still have a bit of work to fully finish the new rendering and new wysiwyg and since we want user feedback from 1.8 to ensure we get a rock solid 2.0 release I propose to have a XE 1.9 release before the XE 2.0 (which would be a promotion of XE 1.9 final with the config change to have new syntax/wysiwyg as defaults). The other advantage of releasing XE 2.0 is that we want to start the maintenance period for the old rendering/old wysiwyg as early as possible to get new people to use the new system. Once 2.0 is released we'll continue releasing bugfix versions of 1.9.x from time to time but we'll advise people to switch to 2.x. I propose we keep support for the old 1.0 syntax (either using the old code or using the 1.0 --> 2.0 syntax converter) for 1 year. This is the time we have to make our existing users switch to the new syntax. Note that with the automatic converters it shouldn't be something too difficult. Roadmap for XE 1.9 ================ General:It's a stabilization release meaning we must resist putting new things in it and fix what doesn't work well enough. Content proposal: * Finish/stabilize/document new rendering - Thomas/Vincent * Finish/stabilize/document new wysiwyg editor - Marius/Anca * Finish/stabilize/document office importer + doc splitter/management - Asiri * Finish/stabilize/document webdav - Asiri * Finish/stabilize/document REST support - Fabio * Finish/stabilize/document new blog application - Sergiu/Guillaume * Continue UI improvements (ex: new treeview, new search interface, full list to be defined) - JV/Ecaterina/Guillaume * Fix search using lucene plugin - ???? * Finish XE French translations - JV/Guillaume * Fix other bugs (watchlist, page names with special chars, etc) - All * Refactoring of apps to use more of SSX - Jerome? Note: I don't think we can commit to have a new skin system or a new skin in place for the 1.9 timeframe. Proposed Dates: * 1.9M1: 6 April * 1.9M2: 4 May * 1.9RC1: 18 May * 1.9RC2/Final: 1 June * 2.0: 15 June WDYT? Thanks -Vincent

16 years, 6 months

11
20
0 0

Re: [xwiki-devs] [xwiki-notifications] r17994 - in platform/core/branches/xwiki-core-1.8: xwiki-core/src/main/java/com/xpn/xwiki/doc xwiki-core/src/test/java/com/xpn/xwiki/doc xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/block xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/internal/renderer xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/internal/renderer/chaining xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/liste

by Sergiu Dumitriu

tmortagne (SVN) wrote: > + if (header.getLevel().getAsInt() <= HeaderLevel.LEVEL2.getAsInt()) { Couldn't the level be Comparable? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 6 months

1
0
0 0

[xwiki-devs] [Proposal] New Search Interface

by Ecaterina Valica

Hi devs, This week I've been working on making a new UI proposal for the existing XWiki search interface. I would really apreciate your feedback on my proposal mockups that can be found at http://incubator.myxwiki.org/xwiki/bin/view/Mockups/Search+Interface#propos… If you're interested in more information, other mockups variation and analysis can be found on the same page. Thank you, Ecaterina Valica

16 years, 6 months

5
10
0 0

[xwiki-devs] About idea on Xwki Jabber, Google Talk and Skype Integration

by Tharindu Madushanka

Hai, I am an undergraduate student at University of Moratuwa, Faculty of Information Technology. I have experience working with Jabber protocol and I am interested in knowing more information about this idea on* integrating Jabber, Google Talk and Skype with XWiki*. I am new to Xwiki project and learning it these days. Few things I need to know are as follows, actually I need to clarify whether I got the idea correctly 1) Xwiki users should be able to save their jabber logins at their profile page including password for the jabber id and also it should allow users to enter any private jabber server details as well 2) Once user loggs in it will login to the specified accounts 3) At some where on wiki web page we need to display the chat list * - It includes all Google Talk, Jabber or Skype contacts - I mean XWiki user can chat with any of his im friends from this chat tool, this will be a private chat * - XWiki users could be invited to join for a group chat by someone who creates a group, by using the chat tool on web page * *This is what I have understood by the project idea, can you *please correct me if there is any confusion between what I have understood with the idea given at XWiki site itself* *Ques1 & 2* What is meant by 'tool should allow to list the chats actively launched or monitored by the wiki' ? What is meant by 'A Jabber AJAX chat tool can also be integrated for users not having Jabber or Google talk installed' ? I could not understand above two sentenses fully that were at XWiki ideas page. Please can any body clarify me on this. Thank you, *H.T.M. Gamage ** *Student,* * Faculty of Information Technology, University of Moratuwa, SriLanka. Mobile: +94 (71) 5518852 ChatID: tharindufit Blog : tharindufit.wordpress.com

16 years, 6 months

2
3
0 0

[xwiki-devs] [GSoc 2009] XWiki integration with OpenOffice

by Cristina Scheau

Hi! My name is Cristina Scheau , a graduating student in Computer Science at “Politehnica” University from Bucharest. I worked 6 months on .NET framework at http://bsgroup.ro/ , coding in VB.NET (most part) , and in C# some features. I also worked 6 months at http://www.amamobile.com/ as JAVA Programmer. Last summer I was intern at http://www.crestatech.com in Santa Clara, CA, where I developed an application using C and VC++. I’ve also worked at some personal projects using JavaScript, AJAX, HTML,PHP,antlr. I am interested in more Xwiki projects but especially in Xwiki integration with Open Office. I have some questions regarding this topic. 1. For the server side, can one reuse the code from Xword?(or is it desired a totally new implementation?) 2. The project includes also the Xwiki integration with Open Office spreadsheet and presentation or just with OO Writer? Another problem ( i don’t know if this is the right place to post) is that, I suggest a small improvement of UI for Xword. If the user cannot connect to the wiki server (changing the Xword options), a notification message should be displayed. It is a little bit confusing displaying only an empty navigation space and all the action buttons in the ribbon being enabled ( I saw that the buttons issue is set in JIRA so i won’t give details). I mention that I used Xword 1.0.0.66. Thanks in advance, Cristina Scheau

16 years, 6 months

3
2
0 0

[xwiki-devs] Listing developers and contributors, copyright policy

by Sergiu Dumitriu

Hi devs, In the early days of XWiki, we used to put @author tags inside Java source files. Later on, we decided that this is a bad practice, and started removing them, on the premise that we will have a NOTICE file listing all authors and contributors. And although we managed to remove almost all @author tags, the NOTICE file doesn't list any developers or contributors, listing just XWiki as a company as the copyright holder. This would be OK if we had a policy stating that all Intellectual Properties belong to XWiki. But we don't. So, shouldn't we make an official policy? Here are some alternatives: I. Individual copyright - we list developers - we list all contributors and their contributions - contributors retain the IP for their submitted code II. Collective copyright - we list developers - we list all contributors and their contributions - XWiki as a collective is the only copyright holder, and we specify that any submitted patch will be the property of the community - having a non-profit organization would help III. Umbrella copyright with acknowledgments - we don't list developers - we list all contributors (including devs) - XWiki SAS as a company is the only copyright holder, and we specify that any submitted patch will be copyrighted by XWiki IV. Umbrella copyright, no acknowledgments - we don't list developers or contributors (in the pom, the web hall of fame can and should still exist) - XWiki SAS is the only copyright, and we specify that any submitted patch will be copyrighted by XWiki Currently we're doing IV, but we don't make this explicit. I'd vote for II, as this is a more Open way. On the technical side, Maven already provides support for listing contributors and developers, for the moment these sections are empty. We can change the NOTICE template to automatically list them. An important question is where do we list people? - In the parent pom, which implies frequent releases of the parent, which means frequent version changes for all the other modules. - In each project's pom, which means that new contributions will only require releasing the affected module, but it will be harder, if not impossible, to aggregate contributions. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 6 months

5
5
0 0

[xwiki-devs] OfficeImporter wysiwyg plugin issues (File Import Tab)

by Asiri Rathnayake

Hi Devs, As reported @ http://jira.xwiki.org/jira/browse/XWIKI-3288 and http://jira.xwiki.org/jira/browse/XAOFFICE-10, OfficeImporter wysiwyg plugin has issues with importing some documents on some platforms. When importing documents from the wysiwyg plugin, the approach we follow is to upload the file that need to be imported into the current page and then import the corresponding attachment. But this scheme has two problems: 1) If the file being uploaded contains special characters, the attachment name will be different from the file name. And this will cause the officeimporter to fail because after uploading the file we will be making a second request to import the attachment with the original file name (but now there is no such attachment). 2) The fileName returned by GWT FileUpload widget is different from Firefox to IE. While Firefox returns the file name, IE returns the whole file path. This causes the officeimporter wysiwyg plugin to fail completely under IE (File Import Tab only). The solution I can see is the following, 1) Upload the file as an attachment just as before. 2) Make a second rpc call. This RPC call will import the latest attachment to the current page by the current user. This way we don't need to worry about crappy file names and browser specific stuff. I know it's a bit ugly but it will work. WDYT? Thanks.

16 years, 6 months

4
4
0 0

[xwiki-devs] Want to work with XWiki Jabber, Google Talk, Skype Integration

by Shamal Roy

Hello, I am inderested with "XWiki Jabber, Google Talk, Skype Integration" idea. There Jabber and gtalk both are XMPP based chat server. For any XMPP we can use smack api. personal servers also can be integrated, my idea is to create a common interface for any XMPP based chat server. And for skype intregration can be possible using skype client api. I was worked in a project of social networking server using J2EE, which has a module for chat with its own XMPP server(Open Fire). I was worked on this module. This past experience make me interested for the "XWiki Jabber, Google Talk, Skype Integration" idea. Hope I have the ability to contribute a little to open source XWiKi project. -- -------------------------------------------------------------- Regards, Shamal Roy

16 years, 6 months

1
0
0 0

[xwiki-devs] Congratulations for the XE 1.8 release!

by Vincent Massol

For once, let's self-congratulate ourselves. I want to thank everyone who has participated to the development of the XWiki Enterprise 1.8 release. I know all committers have been extremely busy, working night and days, and the work they have all achieved is tremendous. Well done guys! Thanks -Vincent PS: Now let's finish completely this new rendering/wysiwyg for 1.9 final :)

16 years, 6 months

3
3
0 0

Re: [xwiki-devs] [xwiki-notifications] r17953 - platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc

by Sergiu Dumitriu

fmancinelli (SVN) wrote: > Author: fmancinelli > Date: 2009-03-23 22:15:24 +0100 (Mon, 23 Mar 2009) > New Revision: 17953 > > Modified: > platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiUtils.java > platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java > Log: > XWIKI-3449: Authenticated XWiki user name might be incorrect in XMLRPC login > XWIKI-3450: Allow guest access to be disabled in XMLRPC > + /* Check if we must grant access when no token is provided */ > + boolean allowGuest = context.getWiki().ParamAsLong("xwiki.authentication.always", 0) != 1; > + Fabio, you are using this parameter wrong. This doesn't mean that only authenticated users are allowed, but it controls the optimization done by Thomas, which is to only check the authentication only if there is no Principal in the session. This parameter forces to check the cookies at each request instead of using the session object. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 6 months

2
2
0 0

[xwiki-devs] Collaborative Business Drawing and Google Summer of Code

by Kojo Gambrah-Sampaney

Hello, I am planning to submit an application for the upcoming Google Summer of Code 2009 to develop a collaborative drawing/mapping application for xwiki using GWT but with some variation. I intend to achieve this by developing a web front end to the Compendium Mapping tool. Compendium is very flexible concept mapping tool that was recently fully open-sourced. It is extensible through the use of 'stencils' which allow for modelling in other modelling languages such as UML. I would like to know what you think about this. Your input will be very much appreciated. Kind Regards, Kojo Gambrah-Sampaney.

16 years, 6 months

2
2
0 0

[xwiki-devs] Is the usage of /testbin/ obsolete or still usefull ?

by Denis Gervalle

Hi all, When the XWiki class is instantiated, it is done in a way that made it almost singleton, except for one special case that seems to be for test purposed, but I feel it is now useless. I am asking because if XWiki is a singleton, some very often used synchronisation could be optimized to avoid useless locking. Here is the excerpt from getMainXWiki() that shows this special case: String xwikiname = "xwiki"; XWiki xwiki = null; XWikiEngineContext econtext = context.getEngineContext(); try { if (context.getRequest().getRequestURL().indexOf("/ testbin/") != -1) { xwikiname = "xwikitest"; context.setDatabase("xwikitest"); context.setOriginalDatabase("xwikitest"); } } catch (Exception e) { } context.setMainXWiki(xwikiname); Anyone knows for what it was ? is it still in use ? could it be removed ? Denis

16 years, 6 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r17954 - in platform/core/trunk: xwiki-bridge/src/main/java/org/xwiki/bridge xwiki-core/src/main/java/com/xpn/xwiki/doc

by Vincent Massol

On Mar 24, 2009, at 8:36 AM, asiri (SVN) wrote: > Author: asiri > Date: 2009-03-24 08:36:32 +0100 (Tue, 24 Mar 2009) > New Revision: 17954 > > Modified: > platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/ > DocumentModelBridge.java > platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/ > DocumentName.java > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/ > XWikiDocument.java > Log: > XWIKI-3427: Introduce DocumentModelBridge.setParent() method > > * Changed tha parameter type of setParent() method from > DocumentModelBridge to DocumentName. > > Modified: platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/ > bridge/DocumentModelBridge.java > =================================================================== > --- platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/ > DocumentModelBridge.java 2009-03-23 21:15:24 UTC (rev 17953) > +++ platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/ > DocumentModelBridge.java 2009-03-24 07:36:32 UTC (rev 17954) > @@ -30,11 +30,11 @@ > public interface DocumentModelBridge > { > /** > - * Sets the parent document attribute of this document to the > given value. > + * Sets the parent document name attribute for this document. > * > - * @param parent the {@link DocumentModelBridge} representing > the parent document. > + * @param parentName name of the parent document. > */ > - void setParent(DocumentModelBridge parent); > + void setParent(DocumentName parentName); > > /** > * Retrieve the full name of the document, in the > <code>Space.Name</code> format, for example <tt>Main.WebHome</tt>. > > Modified: platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/ > bridge/DocumentName.java > =================================================================== > --- platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/ > DocumentName.java 2009-03-23 21:15:24 UTC (rev 17953) > +++ platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/ > DocumentName.java 2009-03-24 07:36:32 UTC (rev 17954) > @@ -77,4 +77,14 @@ > { > return this.page; > } > + > + /** > + * Converts this {@link DocumentName} into a string > representation. > + * > + * @return a string representing this {@link DocumentName} of > the form wiki:space.page. > + */ > + public String toString() > + { > + return getWiki() + ":" + getSpace() + "." + getPage(); This will fail if the wiki, space or page are null. Note that the serializer should resolve not specified values when calling getXXX() using current wiki/space. You can do this by injecting the Execution component and accessing the XWikiContext. Then you can call getDoc().getSpace() to get the current space. Use "WebHome" when the page isn't specified and use getDatabase() when the wiki isn't specified. Also you should create a DocumentNameSerializer() interface and a DefaultDocumentNameSerializer implementation: String serialize(DocumentName(); Then refactor XWikiDocument to use DocumentNameSerializer in setFullName() Thanks -Vincent > + } > } > > Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > doc/XWikiDocument.java > =================================================================== > --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/ > XWikiDocument.java 2009-03-23 21:15:24 UTC (rev 17953) > +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/ > XWikiDocument.java 2009-03-24 07:36:32 UTC (rev 17954) > @@ -71,6 +71,7 @@ > import org.suigeneris.jrcs.rcs.Version; > import org.suigeneris.jrcs.util.ToString; > import org.xwiki.bridge.DocumentModelBridge; > +import org.xwiki.bridge.DocumentName; > import org.xwiki.rendering.block.Block; > import org.xwiki.rendering.block.HeaderBlock; > import org.xwiki.rendering.block.LinkBlock; > @@ -570,9 +571,9 @@ > /** > * {@inheritDoc} > */ > - public void setParent(DocumentModelBridge parent) > - { > - this.parent = parent.getFullName(); > + public void setParent(DocumentName parentName) > + { > + this.parent = parentName.toString(); > } > > public String getFullName()

16 years, 6 months

1
0
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