Hi devs !
Currently working on
[XWIKI-14353](https://jira.xwiki.org/browse/XWIKI-14353), I think that
the live e-mail notification system could be implement as 2 different ways :
1. In its notification preferences, a user can select if he wants a mail
daily, hourly or weekly (that’s already in place). We could add a new
"live" option that does exactly what is expected : it sends a mail as
soon as a document has been updated.
2. We could also provide a completely different option that sends live
e-mails, but regular notification mails are still sent depending on the
user preference and acts as a hourly / daily or weekly "digest".
Finally one idea would be to use the same system that is implemented in
discourse : a mail is sent approximately 10 minutes after an event is
triggered, this means that if a user A is subscribed to the events
coming form a document X, if this document is updated by someone else,
the updates coming from the document in the next 10 minutes will be
grouped in a single mail that will be sent to A. This could potentially
be more scalable as less mails are sent to the users.
WDYT ?
Thanks,
--
Clément Aubin
Web Developer Intern @XWiki SAS
clement.aubin(a)xwiki.com
More about us at http://www.xwiki.com
Hi all!
This is the third update regarding the progress of the Redpen integration
project.
Some of the info can also be accessed in the design page over here:
<http://design.xwiki.org/xwiki/bin/view/Proposal/RedPenIntegration>
I have created a UI on XWiki. The two main parts are such:
First, the application homepage will allow users to key in possible spelling
and expression errors, and their recommended corrections. I have not started
on building the backend in Java to process this database yet, but I'll start
on it within the next couple of weeks.
Second, there is a setting page within the global administration wiki that
allows the user to key in basic settings parameters e.g. setting maximum
sentence length.
The functionality is still restricted to validating a wiki page on document
save, but I will be implementing the function to run redpen validation as a
Job next, right after i finish fixing and stabilising some issues within the
code.
Any comments?
--
View this message in context: http://xwiki.475771.n2.nabble.com/GSOC-Update-3-RedPen-Integration-tp760425…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi Sarthak,
> On 28 Jun 2017, at 20:35, Sarthak Gupta <sarthakgupta072(a)gmail.com> wrote:
>
> Hello Vincent,
>
> On Wed, Jun 28, 2017 at 1:30 PM, Vincent Massol <vincent(a)massol.net> wrote:
> Hi Sarthak,
>
> > On 27 Jun 2017, at 14:58, Sarthak Gupta <sarthakgupta072(a)gmail.com> wrote:
> >
> > Hi all,
> > This mail is regarding the status of the project Glossary Application.
> > I have developed the basic UI for the application which enables a user to
> > add a glossary application and also search the already existing glossary
> > item in the glossary space. The UI is still not very user-friendly as I had
> > decided to finish off the leftover designing part after adding more
> > features and just before the release of the first version.
> >
> > The next part of the project was "adding transformations". I have written
> > the code for basic transformation but still facing some errors in it. Hope
> > the errors may be rectified after some code review.
> >
> > The task that will be left before releasing the first basic version will be
> > "the ability to add glossary items from the wiki pages by selecting the
> > words on Wiki pages". More details on
> > http://design.xwiki.org/xwiki/bin/view/Proposal/GlossaryApplication
> > <http://design.xwiki.org/xwiki/bin/view/Proposal/GlossaryApplication>.
> >
> > Also, tests are to be written for each fo the above.
> >
> > Rest of the features which are to be added (See Design Page) will be
> > implemented after the release of the first version. :)
>
> Thanks for the update.
>
> Some general comments first: I found that the work is going too slow and I’m a bit disappointed by the progress. At this stage you’re actually less advanced than the FAQ application and the Glossary app is really just a copy of that (the part located in wiki pages). You should have finished both the UI and the Transformation at this point. TBH the work done shouldn’t amount for more than 2-3 days of work for someone new to XWiki.
>
>
> Yes, I totally agree and deeply regret that the work done is too less than expected. The main reason for this was that I was basically facing problem with the language. I was hearing some things for the first time in my life, I used to google them a lot but because of having a very less experience in programming(1 year roughly), I was finding difficulty to relate things with each other thus not able to find the right resources to understand the concepts properly, so used to get stuck on them for days. I still face these things but certainly I am better now and will try to catch up. :)
>
> Some more specific comments on the code of what I’ve reviewed:
> * The POMs have plenty of errors and you haven’t used the information that can be found http://contrib.xwiki.org nor the FAQ application’s POM as I have explained a few times (missing licenses, missing metadata, etc), incorrect README.
> * You committed IDE files in the SCM (see the rules from http://dev.xwiki.org).
>
> * Would be better to use nested pages and put the Code space under the Glossary space.
>
> Could you please explain the one point above. Not getting it.
See http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra… and especially:
"Technical pages must be put in a subspace named Code”
Would be great if you could review those best practices btw.
XWiki supports nested pages, see http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization/ for more details.
>
> * You’re using the wrong package for your java class (it should be in org.xwiki.contrib and not org.xwiki.rendering): https://github.com/xwiki-contrib/application-glossary/blob/master/applicati…
> * Would be great if you could add some unit tests for the transformation (again check the wikioword transformation which has tests). Without it, it’s hard to test and I can’t help you without that (would take too long to debug in XWiki).
>
> I will correct all the above errors ASAP.
>
> * Note that you haven’t implemented yet a cache in the transformation and tight now your transformation would simply slow down the whole XWiki :)
>
> Could you provide some pointers on this?Some example or guide that I can refer to?
This means implementing an Event Listener that listens to glossary xobjects addition/deletion/updates and updates a cache of glossary keys and document references. A cache can be a simple structure such as a Map.
You can google “xwiki event listener” for more info on that. There are also several examples in xwiki-platform. Check classes implementing the EventLiostener interface.
Thanks!
-Vincent
>
> Maybe you need to catch up technically on several technologies and that’s why the progress is a bit slow. I hope you’re learning a lot which would be good!
>
>
> That's right! I am learning a lot.. :)
>
> Thanks
> Sarthak Gupta
>
> Thanks
> -Vincent
>
> >
> > Thanks
> > Sarthak Gupta
The XWiki development team is not so proud to announce the
availability of XWiki 9.5.1.
This version fix important bugs found in 9.5: broken flavor picker in
the Distribution Wizard, broken sub wiki template creation and missing
extensions notifications in the profile.
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.5.1
Thanks for your support
-The XWiki dev team
Greetings everyone!
I’m really excited to announce the First Milestone version of the DokuWiki importer extension!
Available in the Extension store: http://extensions.xwiki.org/xwiki/bin/view/Extension/DokuWiki/Text/
Notes:
This version can recreate the DokuWiki pages and spaces in XWiki.
Milestone 2 is expected to have a syntax parser for importing the page content. (release next month).
Requires the 'Filter Streams Converter Application’.
Requires the ‘data’ folder of the DokuWiki instance packaged as a TGZ, and Voila!
Would love to know your thoughts/reviews! :)
Thanks!
Shubham Jain
(slayerjain)
Hi devs,
Here’s a proposal for the new roadmap (for 2 months: 9.6 and 9.7). Note that it’s summer and several will be on holidays.
Dates
=====
* 9.6: July
* 9.6RC1: 12th July (2w + 2 days)
* 9.6Final: 20th of July but we need to start releasing on 17th to be sure we're done before the XWiki SAS seminar (it starts on the 21st till the 28th and during this period the committers from XWiki SAS won’t be very active! :))
* 9.7: August
* 9.7RC1: 21st of August (3w)
* 9.7Final: 28th of August
Topics to tackle
============
* PDF Export - we need to be able to export multiple pages into one pdf file, with no errors and the best rendering possible - Vincent?
* Livetable improvements - Who: Pierre + Marius
** Implement bulk actions on livetable items
** Allow List of Users filtering also by entering first and last name, not just the user id
** Displaying a livetable list filter for a non-static list field is not scalable
** Support LiveTable text filtering on DBListclass columns
* Administration: Default values - Marius?
** XWIKI-14157 Display the default and inherited values in the Administration
** XWIKI-9663 Show default value for date format in administration
* Save button more visible. XWIKI-14162 Position Save buttons on a fixed-bottom area. - Pierre
* Notifications - Continue work - Who: Guillaume + Clement
** Replace Watchlist (missing: realtime notifications, RSS feed, Watch this page/space/wiki)
** Replace Activity Stream
** Easy to add notifications from contrib apps
** Add notifications for the Product-team supported apps (see https://products.xwikisas.com/xwiki/bin/view/Applications/)
* Get rid of old WYSIWYG - Marius?
* Be able to remove help, tour, blog extensions - Thomas?
* Improve XWiki Upgrades
** Display a notification when there’s a newer version available - ?
** Warnings when editing extension pages (same as for delete) - https://jira.xwiki.org/browse/XWIKI-14377 - ?
If time permits
===========
* Add support for Maven `<exclusions>` in Extension Manager
* Performance work
** Finish stuff to make filesystem attachment/history content the default (automatic migration, broken deleted attachments UI, etc.)
** Store the job status in separated files (XCOMMONS-1121)
** Live storage of the job log instead of at the end of the job execution(XCOMMONS-764)
** Async macros, panels, ui extensions, etc.
** ...
* Tour improvements
** add UI to use of `reflex` atrribute (TOUR-57)
WDYT?
Thanks
-Vincent
Hi all,
This mail is regarding the status of the project Glossary Application.
I have developed the basic UI for the application which enables a user to
add a glossary application and also search the already existing glossary
item in the glossary space. The UI is still not very user-friendly as I had
decided to finish off the leftover designing part after adding more
features and just before the release of the first version.
The next part of the project was "adding transformations". I have written
the code for basic transformation but still facing some errors in it. Hope
the errors may be rectified after some code review.
The task that will be left before releasing the first basic version will be
"the ability to add glossary items from the wiki pages by selecting the
words on Wiki pages". More details on
http://design.xwiki.org/xwiki/bin/view/Proposal/GlossaryApplication
<http://design.xwiki.org/xwiki/bin/view/Proposal/GlossaryApplication>.
Also, tests are to be written for each fo the above.
Rest of the features which are to be added (See Design Page) will be
implemented after the release of the first version. :)
Thanks
Sarthak Gupta
The XWiki development team is proud to announce the availability of XWiki 9.5.
Lots of usability improvements: improved Livetable filtering (Date filters, Multilist filters, DBList filters), Page Templates can now be auto-selected based on the current location, simplified way of adding a logo to a Color Theme and a lot more. In addition, the new Notifications feature has been worked on too: grouping of related notifications, ability to send emails, configuration of locations and sending diffs in emails. Last but not least: XWiki Enterprise is dead! We now have a new XWiki distribution that asks you at startup what Flavor you'd like to use for your wiki, and we're providing a default Flavor called the Standard Flavor (the closest to the previous XWiki Enterprise distribution). In the future there should be more Flavors offered.
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.5
Thanks for your support
-The XWiki dev team
Hi devs,
Part 1
=====
I was looking at http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HTopLeve… and found the thread where it was voted in July 2014:
http://markmail.org/message/4hglttljiio5v2km
Does anyone remember the thread were we decided to not do it?
I also found this VOTEd thread from 21st June 2016: http://markmail.org/message/rb5xuex3mpzg3lsm
This new thread is not contradictory with http://markmail.org/message/4hglttljiio5v2km so it doesn’t supersedes it. Thus there really must be some other thread where we decided to not implement http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HTopLeve….
Part 2
=====
Now, about http://markmail.org/message/4hglttljiio5v2km we have almost implemented it. We’re just missing one point:
“
* The Default Flavor would have at least the same release cycle as the base
flavor but it could have more releases (if some of the bundled third-party
extensions has some important bug fixes or new features that we want to offer
quickly without waiting for the next base flavor release).
“
And later on:
“
Technically this means putting the Default Flavor in a
separate github repo (same as xwiki-enterprise being in a separate repo). We
need to discuss how we do it:
- consider it’s XE for now and just add the 2 deps of Tour and CK to XE
- introduce a new repo for the default flavor and do the build for it and
deprecate XE in favor of it. For now we probably need to hardcode the flavor id
in the platform WAR till we’re ready to have the flavor selection screen at
startup (and for HSQLDB/Jetty packaging we need a hard-coded flavor anyway).
"
Right now we’ve put the “Standard Flavor” (that’s the new name) inside xwiki-platform but we discussed back then move it to a separate repo in the xwiki github organization and have only the base flavor in platform.
Should we do what we decided?
Thanks
-Vincent
Hello,
I have written some java code on 'transformations'.
https://pastebin.com/CCHsg0hq
In order to navigate to the required page, I am using the method
'ResourceReference' (highlighted region-line 86,87). Now I want to navigate
to the page named 'Glossary.doc' which is located in XWiki. I know my
current implementation is wrong and I have been struggling for 2 days to
find the right implementation/method.
Is there any method that I can use which can return me the String
'Glossary.doc' so that I can create a linkReference to the same page in
XWiki?
Thanks
Sarthak Gupta