xwiki-devs

xwiki-devs@xwiki.org

9399 discussions

[xwiki-devs] [Proposal] Notifications : Add "in-context" switches

by Guillaume Delhumeau

*TL;DR* - Add a button in each page that will allow you to subscribe to all events that happens to that page. - When you subscribe to a page with this "in-context" bell, it must not affect your other preferences regarding notifications. *Full Post* Hello developers, With Clément Aubin, we are implementing new features in the Notifications Application in order to be able to remove the Watchlist Application. *Status* Currently, a user can subscribe to different kinds of events (ex: "update", "comment", "blog published", etc...). Recently, we have also added the ability to restrict on which locations we are interested in, for each kind of events. For example, we are now able to say, "for the *update* event, show me notifications only about the wiki ABC and for the *blog post* event, show me notifications only about the space XYZ". If you have no restriction (a.k.a "filters") on an event type, then you receive notifications for every event matching the event type in the wiki, no matter the location of the entity it concerns. *Objectives* In the Watchlist Application, we had 3 switches on the top menu that was displayed on every page, and these switches were "watch this wiki / watch this space / watch this page". That would be great if we could have the same for the notifications. *Proposal* - Add the ability to subscribe to all events that happen in a given location, no matter their type (≈ what the watchlist does). - In each page, add a button to subscribe to the current location: https://pasteboard.co/GAqEi6M.png (thanks Caty for the mockup) - Problem: if you previously had no restriction, you suddenly add a new one that will prevent you to receive any notifications concerning the other locations. A bit like the rights module: adding a right to someone at some level will dismiss rights for all other people. I guess we all agree it's a problem on the User Experience point of view. - Proposition: the restriction added by the "in-context" button should be *inactive if there is no other restriction enabled manually via the notification preferences UI*. - Rational: - When you are on the notifications preferences, you can actually see all restrictions, so you can understand that creating one will make you lose all notifications that do not honor the restrictions. - However, when you are on a page, you don't see all the restrictions. If you click on the "subscribe" bell naively, you might not expect it will impact all other notifications. It would actually be very confusing. - In addition: if we add an "auto-watch" option, that add the page you just saved to the list of locations you are interested in, we need to have this feature too. Otherwise saving a document will make all other notifications silent. That is our plan. Cast you ideas! Thanks, Guillaume

8 years, 1 month

Re: [xwiki-devs] Your form "Downloading XWiki (xwiki.org)" got a response

by Vincent Massol

Hi Sascha, Thanks for filling out this form, this help us! :) See below > On 3 Aug 2017, at 20:05, Response Report <report(a)formassembly.com> wrote: > > Your form "Downloading XWiki (xwiki.org)" has received the following response: > > Submitted on: 03/08/17 20:05:15 [snip] > Would you like to get into details? > Q. Suggest Improvements > R. Dashboard Design - Ready to start designs / Templates - improvement in navigation > Missing features: Professional project management with milestones, deadlines, effort, time measuring, UML diagram support Let me try to explain what exists and you can tell me if it’s enough or not, ok? :) * "Dashboard Design". We have this: http://extensions.xwiki.org/xwiki/bin/view/Extension/Dashboard%20Application (and http://extensions.xwiki.org/xwiki/bin/view/Extension/Dashboard%20Macro). You can drag and drop widgets to move them around, add columns, etc. What’s missing? * "Ready to start designs / Templates”. We are bundling these templates: http://extensions.xwiki.org/xwiki/bin/view/Extension/Templates%20Applicatio…. Is that good enough? * " improvement in navigation”. Could you give some examples/more details? * "Missing features: Professional project management with milestones, deadlines, effort, time measuring”. Indeed but it’s not the goal of XWiki to provide a professional project management tool; there are plenty of (web)apps that do this much better already :). We do have a lightweight version though: http://extensions.xwiki.org/xwiki/bin/view/Extension/Generic%20Project%20Ma… * "UML diagram support”. We do support this through several macros. - http://extensions.xwiki.org/xwiki/bin/view/Extension/PlantUML%20Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/YUML%20Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/Sequence%20Diagram%20M… WDYT? I’d love to know more from you and to understand what we’re missing. Thanks -Vincent XWiki committer > > Q. Anything else > R. > > > Where should we send the data? > Q. Send to > R. - Keep the data anonymously on XWiki.org > > > Who are you? > Q. Name > R. Sascha Wichert > > Q. Email > R. Wichert(a)inztitut.de > > Q. Job Title > R. > > Q. Country > R. Germany > > > > > > >

8 years, 1 month

[xwiki-devs] [VOTE] Bundle the blame-api as core extension

by Eduard Moraru

Hi, devs, During a hackathon session, I have done a refresh on XWiki's code viewer ("code.vm") and integrated the Blame API [1] developed by Denis to add line-by-line blame information, just like GitHub's blame feature. Please see the associated Jira issue that also includes before and after screenshots: https://jira.xwiki.org/browse/XWIKI-14578 The Blame API module is a commons module since 2014 but not bundled neither in the WAR nor in the flavor, so, in order to go along and merge my work, I'd need it to be available as a core extension (to be also usable by code.vm). I have not studied it deeply, but the module seems to be doing its job well and the result is very nice and it is very generic. Being able to perform a blame analysis builds upon the diff module and both are features of XWiki's versioning capabilities, so, IMO, both should be considered core extensions (and not only the diff module, which already is core). The PR is available at https://github.com/xwiki/xwiki-platform/pull/605 Here is my (obvious) +1 to bundle the blame-api and merge the PR which includes the UI. Thanks, Eduard ---------- [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Blame%20Module

8 years, 1 month

[xwiki-devs] [Proposal] Change the default blog post layout to 'image' layout

by Mohamed Boussaa

Hello XWikiers, Starting from the version 9.4 of the Blog application we introduced the notion of blog post layouts (see details here: http://extensions.xwiki.org/ xwiki/bin/view/Extension/Blog%20Application). Currently when a user creates/edit a blog he has the possibility to select the layout of the blog posts, 2 layouts are available FTM: the Calendar layout (default) and the image layout. The image layout uses an image thumbnail in order to allow a more visual and appealing display of the blog posts this is why an image selector was added to the blog post form. Because the default layout is 'Calendar' the image selector on the blog post form can be confusing for the user because the uploaded image doesn't appear anywhere. This proposal is about changing the default blog posts layout from 'Calendar' to 'image' in order to avoid the confusion. I propose to: - Change the default post layout to 'image' layout for new blogs - Change the layout of the default Blog to 'image' layout - Add an image to the introduction blog post created when installing the blog app. Find attached some examples of images that can be used on the introduction post. - On the blog post form add a short description to the image selector to explain the objective of the image. *Introduction blog post images* *1) * *2)* *3) * *4)* ** WDYT? Thanks, Mohamed

8 years, 1 month

[xwiki-devs] [GSoC] Extension Repository Connector - Pypi released!

by Krzysiek Płachno

Hey! I'm happy to announce that Extension Repository Connector - Pypi is released - http://extensions.xwiki.org/xwiki/bin/view/Extension/Extension%20Repository… XWiki has possibility to scirpt on its pages in Python. Under the hood it's Java Scripting API and Jython that takes care of running this script and returning result to page. Jython has implementation only for standard libraries. That's why Extension Repository Connector - Pypi is created - to be able to import to XWiki other (non-standard) python packages that are hosted on pypi: https://pypi.python.org/pypi. I'd be grateful for any feedback :) Best, Krzysztof

8 years, 1 month

[xwiki-devs] [ANN] Two new committers: Alex and Clement

by Vincent Massol

Hi all, I’m pleased to announce that the XWiki Core Committers have voted 2 new committers: * Alex Cotiuga * Clement Aubin Congrats guys! You’ll now have the pleasure of being able to commit without waiting for someone else to apply it. Note that when you’re not sure and want to request a review, you can still do PRs if you want. It’s now your choice :) I’ve sent you invitations for the XWiki Github org. I’ve also added you to the committers group on xwiki.org. Make sure to read http://dev.xwiki.org/xwiki/bin/view/Community/Committership :) Last but not least, I’ve added you to the Release Manager roster: http://dev.xwiki.org/xwiki/bin/view/ReleasePlans/#HNextReleaseManagers (let me know if you really don’t want to be a RM and I’ll remove you!). Thank you very much for your interest in making XWiki progress and be better every day. Thanks -Vincent

8 years, 1 month

[xwiki-devs] Nexus account creation

by Clément Aubin

Hi Devs ! Could it be possible to have a new account on nexus.xwiki.org with the username `caubin` in order to perform the release of the first version of https://github.com/xwiki-contrib/listener-urlnormalizer. Thanks, -- Clément Aubin Web Developer Intern @XWiki SAS clement.aubin(a)xwiki.com More about us at http://www.xwiki.com

8 years, 1 month

[xwiki-devs] [ANN] XWiki 9.6 released

by Thomas Mortagne

The XWiki development team is proud to announce the availability of XWiki 9.6. This release brings improvements to Notifications, like live email notifications, the ability to get notifications through RSS feed or to override their default display. It is now possible also to generate table of content for another page, or to define recommended extensions versions and optional extension dependencies so they can be uninstalled by the Extension Manager. 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/Data/XWiki/9.6 Thanks for your support -The XWiki dev team

8 years, 1 month

Re: [xwiki-devs] [Proposal] Change the default blog post layout to 'image' layout

by Denis Gervalle

Hi Mohamed, Obviously, I am +1 for the new default, since it is also my proposal. Regarding the image for the introductory blog post, I would use a more photo like an image, to be more demonstrative, illustrating blogging, writing, office or whatever, maybe with an X in it somewhere. Be careful about the copyrights of the image, of course. Thanks, -- Denis Gervalle SOFTEC sa - CEO On Sun, Jul 23, 2017 at 14:55, Mohamed Boussaa <mohamed.boussaa(a)xwiki.com> wrote: Hello XWikiers, Starting from the version 9.4 of the Blog application we introduced the notion of blog post layouts (see details here: http://extensions.xwiki.org/ xwiki/bin/view/Extension/Blog%20Application). Currently when a user creates/edit a blog he has the possibility to select the layout of the blog posts, 2 layouts are available FTM: the Calendar layout (default) and the image layout. The image layout uses an image thumbnail in order to allow a more visual and appealing display of the blog posts this is why an image selector was added to the blog post form. Because the default layout is 'Calendar' the image selector on the blog post form can be confusing for the user because the uploaded image doesn't appear anywhere. This proposal is about changing the default blog posts layout from 'Calendar' to 'image' in order to avoid the confusion. I propose to: - Change the default post layout to 'image' layout for new blogs - Change the layout of the default Blog to 'image' layout - Add an image to the introduction blog post created when installing the blog app. Find attached some examples of images that can be used on the introduction post. - On the blog post form add a short description to the image selector to explain the objective of the image. *Introduction blog post images* *1) * *2)* *3) * *4)* ** WDYT? Thanks, Mohamed

8 years, 1 month

[xwiki-devs] [Proposal] Changes in Macro Browser

by Vincent Massol

Hi devs, Needs: * We need some “Deprecated” macro category so that users understand when a macro is deprecated and are less tempted to use it * We need to not show “Internal” macros by default to not “pollute” the Macro list by default Proposal: * When the “All Macros” is selected display all macros *except* those from 2 categories: “Deprecated” and “Internal”. * If the user needs/wants to use those macros, he’ll need to explicitly select those categories. * When we want to deprecate a Macro we move it from its category to the “Deprecated” category, before removing it further in the future (when is to be defined on an adhoc basis) Technical details: * Change https://github.com/xwiki-contrib/application-ckeditor/blob/master/plugins/s… to implement this new behavior WDYT? Thanks -Vincent

8 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs