Hi devs,
I've changed 2 components in JIRA:
* I've created a new component named "Dependency Upgrades" for when we upgrade third party deps used by XWiki at runtime (don't use this category for third-party deps used only at development time like Selenium)
* I've renamed "Build, Infrastructure and Tests" to "Development Issues only" to remove the confusion. This is for issues that shouldn't make it in the release notes since they're internal issues only used for our development process and do not affect users running XWiki.
See http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HRule:Do… for details
Let me know if there's any problem for you with this.
Thanks
-Vincent
In my "struggle" to adjust the size of the panels, I need to change the CSS
at multiple locations in order to change the width. I then thought "If the
width of a panel was a variable, and all other CSS where formulas which uses
that variable, I only have to change ONE parameter..."
So I did a quick search and found this site: LESS CSS <http://lesscss.org/>
Maybe this is something that is useful for XWiki?
--
View this message in context: http://xwiki.475771.n2.nabble.com/LESS-CSS-tp7587496.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi developers/contributors,
We have quite a lot of applications on http://extensions.xwiki.org
However several haven't been updated for a very long time even though XWiki has made progress.
I can think of 3 areas where help would be appreciated:
* Some apps have wiki pages in XWiki Syntax 1.0 version. Those need to be upgraded to XWiki Syntax 2.1.
* Some apps don't register themselves in the Applications Panel. To change that just need to create a new page with the proper XObject. You can copy the Blog.ApplicationsPanelEntry page to this app's space and edit it.
* Some apps don't automatically register translations and force the user to manually add documentation resource bundle in the Administration. There's now a better way which is to add an object of type XWiki.TranslationDocumentClass
Example of app that would need an update:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Polls+Application
So who's willing to help? :)
Note that the best strategy is to ensure that the application has a git repo on https://github.com/organizations/xwiki-contrib (there should be a Source button on the app page on extensions.xwiki.org too). If not, then let me know by answering this email and I'll create it for you and give you access so that you can make changes there. FYI the full process is documented at http://contrib.xwiki.org and I can help you with that.
Thanks!
-Vincent
Hi devs,
We need to solve http://jira.xwiki.org/browse/XWIKI-9157
I'm proposing to simply move all ScriptService implementations out of the internal package and make that a rule.
These classes are used by introspection and as such as not used as components and thus they should not be in the internal package.
Here's my +1 and I'm proposing to handle the move.
I can't think of anything that would break except some users who would have had an import in a groovy script on some internal Script Service but that's ok IMO.
Thanks
-Vincent
We've succeeded in having a wiki devroom for FOSDEM 2014 (https://fosdem.org/2014/)! :)
This means we have a full track for wikis and we're now organizing a Call for Participation.
I hope to see a lot of proposals from the XWiki community.
If you know other wiki communities please forward them this email so that they can participate. The more communities the better so that we can cross-pollinate.
Thanks
-Vincent Massol
Begin forwarded message:
> From: Quim Gil <qgil(a)wikimedia.org>
> Subject: [wikis-devroom] Call for participation
> Date: October 7, 2013 9:24:39 PM GMT+02:00
> To: wikis-devroom(a)lists.fosdem.org
>
> Wikis devroom - FOSDEM, Brussels, 1 & 2 February 2014
>
> CALL FOR PARTICIPATION
>
> IN SHORT
>
> We accept proposals for wiki related submissions. The formats accepted are 25min sessions or 5min lighting sessions. All proposals must be submitted via https://penta.fosdem.org/submission/
>
> Deadline: 30 November 2013
>
> Questions? Feedback? Willing to help?
> https://lists.fosdem.org/listinfo/wikis-devroom
>
>
> BACKGROUND
>
> Wikis are essential tools for online collaboration, open knowledge and free software. They are everywhere: from the mainstream Wikipedia to a myriad of public, academic and corporate knowledge bases and personal sites. And most of them are open source software.
>
> Wikis became popular thanks to the edit button allowing users to create and modify text-based web pages easily. Over the years wikis have become more powerful, handling more content types, allowing better look & feel, championing localization and integrating (sometimes) with other tools. The development continues, with hundreds of professional and volunteer contributors specializing in this area.
>
> There are also challenges: the competition from (mainly proprietary and corporate) social media and online office tools, keeping up with UX expectations from users, editors and sysadmins, compatibility across different wiki engines and other publishing tools, collaboration between wiki projects...
>
>
> SCOPE
>
> Wikis devroom is a place to showcase and discuss
>
> * new features, especially exploring areas beyond plain text editing
>
> * compatibility and integration with other tools and services
>
> * lessons learned from deployments, surveys, research...
>
> * cross-project collaboration
>
> We want to focus on sessions for a technical audience including savvy editors. Basic introductions for end users and long tutorials are out of scope.
>
>
> FORMAT
>
> One day, one room. Most of the schedule will be filled with sessions of about 25 minutes that have gone through a call for participation.
>
> We will have a WikiWiki Hour of lightning presentations (5 minutes each).
>
> We will organize a panel session with representation of key wiki projects - the specific topic to be decided as we confirm the participants.
>
>
> ORGANIZATION
>
> Quim Gil (MediaWiki), Vincent Massol (XWiki) and Jean-Marc Libs (Tiki).
> _______________________________________________
> wikis-devroom mailing list
> wikis-devroom(a)lists.fosdem.org
> https://lists.fosdem.org/listinfo/wikis-devroom
Hi devs,
I'd like to add an archetype module in xwiki-enterprise so that users can easily extend XE to create their own distributions.
It'll generate a multimodule project with *-web, *-ui, *-data and *-distribution modules (and possibly installers in a second version).
I remember some users asking for this (e.g. Fabio) and I have the need myself now.
WDYT?
Thanks
-Vincent
Since Enterprise embeds Workspaces by default since 5.2-m2, I think it does
not make any sense to release XWiki Manager (XEM) anymore.
The build is currently broken (because of the XAR organization changes).
So I propose to remove XWiki Manager:
- stop releasing it
- move the github repo to xwiki-contrib/retired
- update manager.xwiki.org to explain the changes in XWiki 5.2.
- move the manager jira to the retired category
- remove the build in ci.xwiki.org
Here is my non-binding +1.
LM
The XWiki development team is proud to announce the availability of XWiki 5.2.
This release comes with multiwiki support enabled by default: users
are able to create new wikis without the need to install additional
extensions. This is possible because the Workspace Application has
been integrated in XWiki Enterprise. We stopped the support for XWiki
Enterprise Manager as a consequence. Apart from this, the new release
brings a Solr-based live search (to replace the one based on Lucene)
and the ability to track active XWiki installs. The Distribution
Wizard has a new step to upgrade all wikis. Developers will be
interested by the new Wiki Stream framework which can already be used
to export large wikis in XAR format. A lot of bug fixes (135) and many
improvements (50) complete this release and make it worth trying.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki52
Thanks
-The XWiki dev team
Hello, i tried to implement the component example
http://extensions.xwiki.org/xwiki/bin/view/Extension/WikiComponent+Module
which is also available from
https://github.com/jvdrean/xwiki-proverb-example
When i put the compiled jar at WEB-INF/lib i get after starting the server
org.xwiki.query.QueryException: Exception while execute query. Query
statement = [ select doc.space , doc.name from XWikiDocument as doc ,
BaseObject as proverb
where ( proverb.proverb <> '' ) and doc.fullName=proverb.name and
proverb.className='XWiki.Proverb' ]
...
"Caused by: com.xpn.xwiki.XWikiException: Error number 0 in 3: Exception
while hibernate execute
Wrapped Exception: could not resolve property: proverb of:
com.xpn.xwiki.objects.BaseObject [ select doc.space , doc.name from
com.xpn.xwiki.doc.XWikiDocument a
s doc , com.xpn.xwiki.objects.BaseObject as proverb where ( proverb.proverb
<> '' ) and doc.fullName=proverb.name and proverb.className='XWiki.Proverb'
]
I use XWIKI v5.1 with embedded HsqlDB on Windows7. I dont get whats wrong
and really appreciate some hints.
My goal is to all new classes to a document or new properties to a page, but
even get this example. Has anyone an idea what i did wrong?
Regards,
Matthias
--
View this message in context: http://xwiki.475771.n2.nabble.com/Componente-Example-Proverb-Not-working-tp…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hello fellow developers,
what is the best practice to decide on a skin in the session and not carry it along with the URLs?
We are building a mobile UI and it should have more limited functionalities so that the same pages should eb visited by the same users with different skins depending if the device is a mobile or not.
thanks for hints.
Paul