Hi Devs,
I am a Master Student of Computer Science and of Business Information
Systems. I am developing my master thesis project on a case study coming
from Learnpad, unfortunately I have some problems in understanding the huge
amount of documentation provided by the XWiki website for developers,
anyway the idea behind my project is the following:
*Starting from a XWiki page, clicking on an hypothetical button, I want to
be able to start a Java application that will aplly changes to the XWiki
space, that are: *
- *Add and remove single or multiple pages to the space;*
- *Set the content of the new pages;*
- *Modify content of existing pages;*
I am wondering because it is not clear, for me, if I need to create a
new *extension
*or a new *component *or a *macro*(and the differences between them), how
to properly implement a java application for Xwiki or how to start it from
the Xwiki environment, if it is possible to modify XWiki spaces at runtime,
or how to associate java object to wiki pages....and stuff like that...
I've already read the documentation, checked the existing extension,
cheched the Github repository, but it is dispersive, sometimes too
technical (with some knowledge taken for granted) and sometimes too
general. In the end I am stucked because I don't know how to approach my
problem in this environment.
Do you have any suggestion to help me? I need to be put on the right truck
Kind Regards,
Giordano Ninonà.
Hi devs,
With 7.2 the differences between Wiki and Nested Spaces are smaller and we’re probably going to have more and more questions related to when should a user use a Wiki and when should he/she use a Space.
Thus I’ve started http://design.xwiki.org/xwiki/bin/view/Proposal/WikivsNestedSpaces
It would be great if you could either reply on this thread with differences that you see (and I’ll update the page) or update that page directly (preferred :)).
Once the page has good data, I’ll move the content to the documentation proper.
Thanks!
-Vincent
Hi Devs,
first of all I'd like to congratulate everyone who worked on the latest 7.x
releases. I tried a 7.4 snapshot locally and it's looking great! The
interface feels much simpler and fresher overall, well done!
Nested spaces bring about a significant change in the way information is
stored and organized in XWiki. They make it less necessary to create
sub-wikis to compartmentalise information.
Besides, at the moment a sub-wiki is almost exactly the same as the main
wiki upon creation. I've been doing plenty of demos of XWiki 7.4 at a
conference last week and it was difficult to explain the difference between
the main wiki and a sub-wiki.
Therefore, I would like to suggest the following changes:
1. *View the main wiki as a collaborative content repository* (what a
wiki is most often associated with). Therefore the main wiki would have the
most wiki-like features (treeview and tagcloud in a pane on the left) and
global activity stream on the home page. Users looking for a "simple" wiki
wouldn't even need to create sub-wikis.
2. *View subwikis as collaborative workspaces* (created for a project or
another type of shorter-lived initiative). A subwiki would retain the
appbar on the left, as well as panels on the right that are specific to
each app (ex: forum app, blog app...). The homepage would be made of
widgets surfacing information from the various apps installed. Additional
subwiki templates could be added later on, once flavors are built into the
product.
3. *Add the horizontal menu to the standard install.* In addition to
this, an entry should be added to the menu to automatically list existing
sub-wikis the user has access to. This would make navigation between wikis
more discoverable and easier to use.
My feeling is that these changes would make the distinction between nested
spaces and sub-wikis much easier to explain and understand for users:
- *Want to share generic information? Put it in the right location in
the main wiki.*
- *Want to work with others on a restricted project? Create a sub-wiki
for this purpose.*
With the addition of the horizontal menu, the main wiki would act as both a
portal to information and a knowledge repository.
Looking forward to your feedback,
Guillaume
Hello XWikiers,
I would need a wiki on myxwiki.org in order to test/demo collaboration with
somebody remote (and a pain to get a public IP for a local instance of
mine).
It would be temporary so it will be deletable after a while (I will let you
know when you can throw it away).
My username is lucaa, the wiki should be called lucaa.myxwiki.org .
Thank you very much,
Anca
Hi,
In previous years the xwiki.org project launched surveys about features we’d like to see implemented in XWiki (see http://www.xwiki.org/xwiki/bin/view/Main/Feedback).
After some discussions with fellow XWikiers we thought it could be interesting to launch a similar survey in 2015, especially with the 8.x cycle approaching. But this time instead of having a long list of features to vote on, we thought it might be more interesting to have a few open questions that the community could answer.
The aim of this short survey is to find out more about how satisfied (or not!) the members of the XWiki community are with the XWiki product.
We'd be happy to learn about:
* what you like / dislike about the product
* the features and improvements you’d like to see in the product in the future and especially for XWiki 8.x
The survey will run till November 13 and the results will be synthesised and made available mid-November through a blog post on the community blog ( http://blog.xwiki.org/xwiki/bin/view/Blog/ )
The survey has 6 questions and should only take a few minutes:
http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiProduct2015
Thanks a lot for your contributions and for helping improve the product,
-Silvia & Vincent
Hi devs,
I’m sorry I’m late on the this email (should have been sent a week ago at least).
I started discussing it a bit on http://markmail.org/message/4xlfdla2f3ds5rhq (regarding dates)
So the proposal is to continue with stabilization as per our cycle plan and especially to continue putting the priority on Nested Pages/Spaces which we need to be as stable as possible for 7.x, so that we can have a 7.4.x LTS.
The priority is to reduce this list of open issues to 0 (or close):
http://jira.xwiki.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=%…
A second priority is to finish the polishing of "Upgrade Tools” (ie DW) as much as possible since it was introduced in 7.x. More generally we need to fix/polish features that have been introduced in this cycle (7.x).
Proposed Dates:
===============
7.4M1: 30 November 2015
7.4M2: 14 December 2015
7.4RC1: 21 December 2015
7.4final: 28 December 2015
Note 1: we need to finish 7.4 by the end of the year to start a new cycle in early Jan
Note 2: we don’t have much margin with the Christmas holidays.
Thanks
-Vincent
Hi devs,
So this proposal appeared in some of my proposals but right now I created a
proper Proposal/Idea mail for it.
It's about having an 'Administer Page' section in the menus, similar to the
'Administer Wiki' and 'Administer Space' functionality.
The 'Administer Page' will be accessible to global admins, page creators
and users with (edit?/admin?) rights for the page.
>From what we currently have implemented it should contain the 'Rights
Editor' (?editor=rights) at page level.
In the future we could make 'Presentation', 'Page Elements' or 'Panel
Wizard' to be more granular and be set at Page level (have different panels
and style for just one page).
Some screenshots at
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/PageAdministration
Thanks,
Caty
Hi,
Currently we don't provide any README files for the repositories found on
https://github.com/xwiki
There are several remarks about this fact:
- README is promoted by GitHub as the way to summarize your project. That
green button "Add a README" won't disappear unless we create a file :)
- All the other major organizations provide READMEs for their repositories,
even if they have dedicated websites (a.k.a the README is not the only way
to document your project).
I think we should provide a README that contains just:
- Summary for the repo
- Links to the xwiki.org wiki about that particular repo
-- the links should be general and easy to maintain
-- they should facilitate access to devs for the most useful pages on
xwiki.org, promoting development and contributions.
I've created these proposals:
- Enterprise https://gist.github.com/evalica/b439c6dc98ca109e1f5b
- Platform https://gist.github.com/evalica/6431b99514d59bb7b66f
- Rendering https://gist.github.com/evalica/79298c6830480eff321d
- Commons https://gist.github.com/evalica/2affcfff5a4a40b418aa
The custom parts for each repository are Summary, Documentation, Download.
The generic parts are Release Notes, Tools, Community.
Let me know what you think.
Thanks,
Caty
P.S. For the LICENSE file we could just provide a link to the xwiki.org
page, see https://gist.github.com/evalica/8d58ec8353a30cad3386