Thanks to everyone to answered and to Silvia for leading this survey! :)
We got some useful results. Always interesting to know the user’s pain points.
Thanks
-Vincent
PS: I sent this mail on the 21st of November but I’ve just found out that it wasn’t sent and was in my draft mailbox...
On 21 Nov 2015 at 16:41:28, Silvia Macovei (silvia.macovei(a)xwiki.com) wrote:
Hi everyone,
Thanks a lot to the 21 people who filled in the survey! In this post you
can find a summary of the results, with some interesting ideas on things to
implement in the future:
http://www.xwiki.org/xwiki/bin/view/Blog/ProductSatisfactionSurvey2015Resul…
Now XWiki developers can look at the list when deciding/discussing what
features/items to implement in 8.x and beyond. In a year or so we could do
a postmortem to see what has been implemented.
Thanks,
Silvia
Hi,
XWiki SAS is currently working on a Google Sites Importing module. The
current code (partially working) is already published here:
https://github.com/xwiki-contrib/application-googlesites
I would need a jira project for it so that issues with bugs in the import
are tracked..
Thanks
Ludovic
--*Ludovic Dubost*
*Founder and CEO*
ludovic(a)xwiki.com
skype: ldubost
Blog: http://blog.ludovic.org
Hi Devs,
I am writing because I can't find how to create new spaces*...*I am working
with XWiki Enterprise 7.2 and now there are only pages without any space...
How can I create new spaces? or better...There were some changes on this
aspect in XWiki?
Sorry but maybe I've missed something about that....
Giordano.
Hi devs,
I fixed a bug in 'wiki-editor-devtools' that make this extension
available for XWiki v6 (it was only available for XWiki v7 before). I'd
like to do a release today. If nobody is against, I'll start the
process during the afternoon. I'll need some help also for the Jira and
Nexus (but Vincent already told me he can be the guy, thanks).
Thanks,
--
Jean Simard
jean.simard(a)xwiki.com
Research engineer at XWiki SAS
http://www.xwiki.com
Committer on the XWiki.org project
http://www.xwiki.org
The XWiki development team is proud to announce the availability of XWiki 7.4 Milestone 1.
This is our last stabilization release for the XWiki 7.x Cycle. It brings polishing and stabilization for the Nested Pages feature and the changes in UI that resulted from it, especially for the Watchlist.
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/ReleaseNotesXWiki74M1
The following people have contributed code to this release (sorted alphabetically):
Marius Florea
Vincent Massol
Ecaterina Moraru
Eduard Moraru
Thomas Mortagne
Clemens Robbenhaar
Jean Simard
Manuel Smeria
Thanks for your support
-The XWiki dev team
The point is not to use someone else's code or even to duplicate
the logic to a perfect binary-compatible tee, the point is to be
"standard enough" that it's familiar to people who come in from
Github, StackOverflow, Slack, Reddit etc.
The php-inspired macro idea is another attempt at making it more
familiar to people and thus more intuitive.
Thanks,
Caleb
On 27/11/15 16:54, vincent(a)massol.net wrote:
>
>
>
> On 27 Nov 2015 at 16:41:34, Paul Libbrecht (paul@hoplahup.net(mailto:paul@hoplahup.net)) wrote:
>
>>
>>
>> Caleb James DeLisle wrote:
>>> I had just imagined an extension to the markdown standard, not sure
>>> exactly
>>> how macros ought to be implemented... One possibility:
>>>
>>>>> $doc.getFullName()
>>> ?>
>>>
>>> or
>>>
>>> ?>
>> Hey, that is very "standard" in the sense of PHP-ish.
>> I like it but I am sure it can clash heavily somewhere.
>>
>> Another proposal is here:
>> https://github.com/codingcoop/markdown-macros
>> More compact... thus less portable…
>
> Can you explain why you’re trying to do something that’s already implemented? You don’t like our current implementation?
>
> Thanks
> -Vincent
>
>> Paul
>
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
Hi Devs,
as you probably noticed it, Markdown has recently become somewhat of a
reference syntax for many developer tools, most notably GitHub. I have
recently discussed with teams using XWiki who are also using GitHub and
Slack and who are interested in being able to use Markdown syntax inside
XWiki.
Although it is already possible to use Markdown syntax in XWiki in a
limited way <http://rendering.xwiki.org/xwiki/bin/view/Main/Markdown11>, I
don't think that a wiki could really work with only Markdown, due to the
following limitations:
1. We have invested a lot in the XWiki rendering and the XWiki 2.1
syntax in order to make them address a lot of use cases and work seamlessly
with the WYSIWYG editor
2. Conversely, Markdown syntax is very limited by design
<https://daringfireball.net/projects/markdown/syntax> and does not
support many of the important features of XWiki syntax, forcing users to
rely on HTML for a lot of use cases
What's interesting however is that Markdown syntax is very close to XWiki
syntax in a number of regards, notably line breaks, bold and lists. Some
notable differences include the syntax for links, images and code blocks.
My line of thinking is the following: what if we made it possible as an
option for users of XWiki 2.1 syntax to have XWiki interpret the main
elements of Markdown syntax? In practice, this would mean adding a set of
5-10 additional rules to the rendering engine.
The obvious benefit would be to improve adoption of XWiki by dev teams who
are already familiar with Markdown. I don't see any obvious drawbacks
(besides the need to code and maintain the feature of course), but I
clearly don't master all the subtleties of the XWiki rendering engine.
Thanks,
Guillaume
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