Hi,
#docextra tabs are particular important for content pages where users are
encouraged to comment, attach, revise history, etc.
But since XWiki is more than a wiki and the application usage has expanded,
we removed the #docextra tab from many XWiki Contrib applications, like:
File Manager, Forum, Calendar, etc.
The logic behind was that the applications have as main purpose the
management of applications entities, not commenting for example.
Also with the Flamingo Skin, the shortcuts to Comments, Attachments, etc.
can be found in the 'More actions' menu.
So, my question to you is: What do you think about removing the #docextra
also for default/bundled applications like:
- Blog.WebHome
- Dashboard.WebHome
- Panels.WebHome
- Scheduler.WebHome
- Stats.WebHome
- Main.WebHome?
If we adopt this practice we could document it on:
http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome#HApplicationDesign or
http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra…
Thanks,
Caty
The XWiki development team is proud to announce the availability of XWiki 7.3 Milestone 1.
This is the first of the 2 stabilization releases that happen at the end of each yearly Cycles. Lots of polishing has been done, especially for the recently introduced Nested Pages feature and its consequences on the UI redesign (modified menus for example).
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/ReleaseNotesXWiki73M1
The following people have contributed code to this release (sorted alphabetically on last name):
Pascal Bastien
Guillaume Delhumeau
Marius Dumitru Florea
Vincent Massol
Ecaterina Moraru
Eduard Moraru
Thomas Mortagne
Clemens Robbenhaar
Jean Simard
Gabriela Smeria
Manuel Smeria
Thanks for your support
-The XWiki dev team
Hi devs,
I’ve just committed a quote macro in rendering but I think it should an external extension since the real solution is to improve the wiki syntax to support block content.
I’m just requesting a github repo on contrib. Name: macro-quote
Thanks
-Vincent
Hi.
With 7.2, the content menus have changed a lot. The pain point is that we
have a too much crowded "more actions" menu.
Some discussions have already been done on this jira issue:
http://jira.xwiki.org/browse/XWIKI-12587
Caty have created a design page to re-organize the menus:
http://design.xwiki.org/xwiki/bin/view/Proposal/NestedMenuReorganization
I'm in favor of the solution 1.2.
So:
* -0 for solution 1.1 since the viewers are not what we use the most
(thanks to the extra tabs on the bottom) and it gives them too much
importance
* +1 for solution 1.2, even if we might encounter some difficulties saying
if an item is a base action or an advanced one.
* 0 for option A (too much clicks), but on the other hand I don't have an
alternative to propose.
* +1 for option B. The jira issue is already created (
http://jira.xwiki.org/browse/XWIKI-12636) and I think nobody would be
opposed to this.
* +0 for option C. The browser already have this ability, and yes, it
implies the hiding of the panels (thanks to some CSS we have). However, I
remember a client using this feature for a convoluted use-case: include a
light wiki page in an other website via an iframe. Anyway, we could still
keep the viewer but remove the link.
* +1 for D. I know that security through obscurity is not the best, but it
disturbs me to let an access to the source code of any wiki page, including
not-well-done applications created by users.
Thanks,
Guillaume
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hello devs,
Recently, a new version of the XWebIDE (
http://extensions.xwiki.org/xwiki/bin/view/Extension/XWebIDE+Application)
has been published which added the ability to work with Nested spaces in
the application.
In order to progress with the development of the extension, we've made a
list of future relevant features to add to the application. We'd now like
to have your opinion about the importance of each one of them (order the
features based on their priority) and your ideas for new ones. You can find
the list and add your vote in the table in the design wiki :
http://design.xwiki.org/xwiki/bin/view/Proposal/XWebIDE+Application+Improve…
We'd also like to know what are the required features which make you
believe you'll use the application in the future.
And feel free to provide any other feedback you may have about the current
version of the XWebIDE application.
Thanks,
Yann
Hi devs,
In the past few days I’ve written the first version of a test framework to allow unit testing wiki pages in our build (see http://jira.xwiki.org/browse/XWIKI-12643).
The advantages are:
* No running XWiki required
* Relatively fast to execute (<2s) and much faster than functional tests
Some remarks:
* It’s not meant to replace functional tests
* What pushed me to work on this was that I wanted to provide a test for XWIKI-11524 (Do not display hidden documents in feeds) which I fixed a week ago or so but at the time I couldn’t do that easily. I would have had to write a functional tests and 1) there was no test at all existing and setting up the scaffolding is a bit heavy for this small use case 2) I didn’t want to penalize our build by a minute more or so just to validate that a “hidden/document” query filter is executed...
Now it’s still an experiment at this stage as I don’t know how easy or hard it’ll be when writing unit tests for other pages and we’ll need to add more component declarations and setup for sure. On this topic we will need to start developing ComponentList annotation packs probably in order to not slow down execution of all wiki page tests.
Let me know what you think and in case nobody likes it we can always remove it and move it to contrib.
Thanks
-Vincent
Hi devs,
I am opening this discussion to move the discussion started in an issue
(XWIKI-12628) to its proper place, the ML. (Discussing into JIRA is very
bad since it lower the audience, we tend to have done it too much recently).
So the issue is that, in the Nested Document concept, we can create
children to inexistent (WebHome) page. This introduce some abnormalities:
- Administering inexistent page (including page rights, see
http://jira.xwiki.org/browse/XWIKI-12629)
- Children of inexistent page (see http://jira.xwiki.org/browse/XWIKI-12628
)
Since we agree that having nodes in the tree of pages is fine without
having the intermediate document created, we definitely need to better show
this concept to the final user. It would be a pain to explain to a user
that access rights for page children of an inexistent page is administrable
from that inexistent page. It is also very poor when you navigate from the
breadcrumb to a inexistent page as a normal user to reach "The requested
page could not be found." with no way to navigate further.
These inexistent page are not necessarily invisible, there is links to
them, and showing that as "error" page looks inappropriate IMO. So there is
probably a couple of things we could do to improve this:
A) display the list of children in addition to the actual message
B) display a "default" and nice (not an error) dashboard on them that allow
navigation (with a button for those that can edit, to create the page)
C) create them all the time, with the dashboard above by default
D) do not propose links to those page in the breadcrumb to users without
edit right on them ?
E) ... (please add more idea)
I am in favor of B) currently, since I do not think we are in an "error"
case like A) seems to expose.
I am wondering if D) could be useful as well to limit navigation to those
page or not for user that will not find them so useful... but it may exists
opposite UC.
WDYT ?
--
Denis Gervalle
SOFTEC sa - CEO
All,
I am trying to install the social login application, but I receive the
following error on install
Any ideas?
Kr
W
Failed to get fields for class
[org.xwiki.social.authentication.internal.DefaultSocialAuthManager] because
the class [Lorg/xwiki/crypto/passwd/PasswordCryptoService;] couldn't be
found in the ClassLoader.
class java.lang.NoClassDefFoundError: Failed to get fields for class
[org.xwiki.social.authentication.internal.DefaultSocialAuthManager] because
the class [Lorg/xwiki/crypto/passwd/PasswordCryptoService;] couldn't be
found in the ClassLoader.
at
org.xwiki.component.util.ReflectionUtils.getAllFields(ReflectionUtils.java:71)
at
org.xwiki.component.annotation.ComponentDescriptorFactory.createComponentDescriptor(ComponentDescriptorFactory.java:132)
at
org.xwiki.component.annotation.ComponentDescriptorFactory.createComponentDescriptors(ComponentDescriptorFactory.java:105)
at
org.xwiki.component.annotation.ComponentAnnotationLoader.register(ComponentAnnotationLoader.java:168)
at
org.xwiki.component.annotation.ComponentAnnotationLoader.initialize(ComponentAnnotationLoader.java:136)
at
org.xwiki.extension.jar.internal.handler.JarExtensionHandler.loadComponents(JarExtensionHandler.java:149)
at
org.xwiki.extension.jar.internal.handler.JarExtensionHandler.install(JarExtensionHandler.java:103)
at
org.xwiki.extension.handler.internal.DefaultExtensionHandlerManager.install(DefaultExtensionHandlerManager.java:85)
at
org.xwiki.extension.job.internal.AbstractExtensionJob.installExtension(AbstractExtensionJob.java:256)
at
org.xwiki.extension.job.internal.AbstractExtensionJob.applyAction(AbstractExtensionJob.java:204)
at
org.xwiki.extension.job.internal.AbstractExtensionJob.applyActions(AbstractExtensionJob.java:151)
at
org.xwiki.extension.job.internal.InstallJob.runInternal(InstallJob.java:150)
at org.xwiki.job.internal.AbstractJob.runInContext(AbstractJob.java:209)
at org.xwiki.job.internal.AbstractJob.run(AbstractJob.java:192)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Finished job of type [install] with identifier
[extension/action/org.xwiki.contrib:xwiki-social-login-ui/wiki:xwiki]
--
View this message in context: http://xwiki.475771.n2.nabble.com/Error-installing-Social-Login-Application…
Sent from the XWiki- Dev mailing list archive at Nabble.com.