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
Hi devs,
For the past weeks I've been working on a skin based on Bootstrap[1]. You
can read more about it and test the new Junco Skin at
http://extensions.xwiki.org/xwiki/bin/view/Extension/Junco+Skin
This proposal is about using the Junco Skin (Blueberry
Theme<http://extensions.xwiki.org/xwiki/bin/view/Extension/Junco+Skin#HTheme:Blue…>)
for xwiki.org.
I prepared some responsive screenshots for the xwiki.org Homepage and an
Extension page.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/XWikiOrgJuncoHomep…
This is my +1
Please report any issues on https://github.com/evalica/bootswatch/issues
__Advantages__
- a change is always welcomed, shows the users there is activity on the
website;
- the skin is responsive;
- by using Bootstrap we have the whole framework's power to use (grids,
components, etc.);
- we have the chance to test a bit the skin in production and see the
possible bugs, in order to later integrate;
- IMO the skin looks nice :)
__Disadvantages__
- the only disadvantage is that there will be bugs and they will take some
time to be detected and fixed;
__Platform integration problems__
1. currently the new skin uses the HTML5 doctype. This is needed if we were
to use some Bootstrap JS components (carousel, menus, etc.) - which we
currently don't on xwiki.org, so I could use the old doctype (but lose some
of the testing purpose). Because of the HTML5 doctype, the HTML validation
fails. See http://jira.xwiki.org/browse/XWIKI-7552
2. Junco Skin currently doesn't have support for changing the ColorThemes
on the fly. I would need the help of a developer to fix this problem. Is
not so much a problem for xwiki.org (I could fix them by duplicating some
code in the xwiki.org skin), but it is a problem for the integration.
3. Being build on Bootstrap, it needs LESS to compile the files into CSS.
Again I would need a developer to see how we could integrate the building
of the themes in platform. Right now this is done locally, partially manual
by using Grunt.
Tell me what you think and take some time to test the skin,
Caty
[1] http://getbootstrap.com/
Hi devs !
In 5.2, we have introduced Workspace Application in XE. Now, we should go
further and merge Wiki Application with Workspaces.
= New idea =
* Add a "hidden" field to the Wiki. For example, I would like to be able to
create wiki:
** which can not be seen by others
** which does not appear in searches
** e.g: workspacetemplate, or on a farm if I don't want people to know that
I host a company AND its competitor
= Options =
* In your wiki, do you want to have the "Home" menu?
* In your wiki, do you want to create your own users?
= XARs and template =
* The home menu is enabled only if the user want it (trivial)
* The registration button should redirect to the home wiki depending on the
configuration (trivial)
* Disable XWiki.AdminRegistrationSheet, XWiki.AdminUsersSheet from the
Administration (depending on the configuration)
* Create a new UI, partially based on the current WorkspaceManager and
WikiManager spaces.
= API =
* Create a new API: xwiki-platform-wiki.
* The old modules (xwiki-platform-wiki-manager and
xwiki-platform-workspace) go into legacy, and we mark them as deprecated.
* The new API will use the new modules of Vincent:
https://github.com/xwiki/xwiki-platform/compare/feature-resource-and-wiki-m…
= Proposal for the API =
* xwiki-platform-wiki
** xwiki-platform-wiki-descriptor
*** xwiki-platform-wiki-descriptor-api
**** WikiDescriptor.java
***** ID
***** Alias
***** Hidden
***** Description?
***** Ability to add custom data (where all will be stored)
**** WikiDescriptorManager.java
***** getAll()
***** set()
***** remove()
***** getByWikiAlias()
***** getByWikiId()
** xwiki-platform-wiki-manager (but this name conflicts with the previous
module that we put into legacy...)
*** WikiManager.java
**** createWiki() (create an empty wiki)
**** deleteWiki()
**** copyWiki()
** xwiki-platform-wiki-template
*** WikiTemplateManager.java
**** setWikiAsTemplate()
**** unsetWikiAsTemplate()
**** getWikiTemplates()
**** isWikiTemplate()
** xwiki-platfrom-wiki-user (handle or not the local users)
*** WikiUsersManager.java
**** canWikiHasLocalUsers()
**** setCanWikiHasLocalUsers()
**** getWikiOwner()
**** setWikiOwner()
**** getMembershipType() (join/invite only/ask to join)
**** setMembershipType()
**** getWikiUsers() (list of the local users + those who are
'members' of the wiki)
** xwiki-platform-wiki-script (for script services)
*** Wiki.java (only an helper)
**** getDescriptor()
**** getId()
**** getAlias()
**** addAlias()
**** removeAlias()
**** getReference()
**** IsTemplate()
**** setIsTemplate()
**** getOwner()
**** setOwner()
**** canHasLocalUsers()
**** setCanHasLocalUsers()
**** getMembershipType()
**** setMembershipType()
**** getUsers()
**** isHidden()
**** setHidden()
**** getDescription()
**** setDescription()
*** WikiManagerScript.java ("$services.wikimanager" but the name
conflicts with the previous module...)
**** getAllWikis()
**** getHomeWiki()
**** getWikiByAlias()
**** getWikiById()
**** getWikiTemplates()
**** createWiki()
**** deleteWiki()
**** copyWiki()
**** isWikiExists()
**** isWikiNameAvailable()
**** joinWiki()?
**** askToJoinWiki()?
** xwiki-platform-wiki-ui (pages for both the home AND the (sub)wikis)
*** ...
+ write tests
+ need a migration path
+ in the future:
* Create a new wiki from a flavor:
** instead of creating a wiki from a template, you give an extension ID
If you like this proposal, I will try to implement it as close it is
possible, but I may change some elements to minimize dependencies. I will
tell you.
WDYT?
Thanks,
Louis-Marie