March 2017 - xwiki-devs@xwiki.org

[xwiki-devs] Error while building
by Sarthak Gupta 30 Mar '17

30 Mar '17

Hi, I am getting this error while building application-ckeditor. What to do? [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] CKEditor Integration Parent POM .................... SUCCESS [02:07 min] [INFO] CKEditor Integration Base .......................... FAILURE [15:46 min] [INFO] CKEditor Integration Plugins ....................... SKIPPED [INFO] CKEditor Integration Test Modules .................. SKIPPED [INFO] CKEditor Integration Test Page Objects ............. SKIPPED [INFO] CKEditor Integration WebJar ........................ SKIPPED [INFO] CKEditor Integration UI ............................ SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 19:54 min [INFO] Finished at: 2017-03-30T15:39:01+05:30 [INFO] Final Memory: 20M/121M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (build-ckeditor) on project application-ckeditor-base: Command execution failed. Cannot run program "C:\Users\SARTHAK GUPTA\.m2\XWiki\application-ckeditor-master\base\target\ckeditor-dev-4.6.2\dev\builder\build.sh" (in directory "C:\Users\SARTHAK GUPTA\.m2\XWiki\application-ckeditor-master\base"): CreateProcess error=193, %1 is not a valid Win32 application -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :application-ckeditor-base

2 1

[xwiki-devs] (RESEND) Nesting within Annotated XHTML
by ktc 30 Mar '17

30 Mar '17

EDITED: Resending this message to fix some escaping issues when the email went out the first time. I have a use case where I need to nest macros to 2+ levels deep using XWiki's Annotated XHTML syntax. We are using this syntax as an input to a transformation process that utilizes XWiki's rendering engine to convert the Annotated XHTML into XWiki-native markup, similarly to how CKEditor does its work. The problem is that with Annotated XHTML, macros are encoded as HTML comments -- but HTML comments cannot be nested within other HTML comments. Here is a demonstrative example: (NOTE: in all examples below I have added extra spaces around the ! chars to prevent these from getting stripped out in this email) < ! --startmacro:outermacro|-||-|outer text before < ! --startmacro:innermacro|-||-|inner text-->< ! --stopmacro--> outer text after-->< ! --stopmacro--> The intention is for this to be convertible to this XWiki syntax: {{outermacro}}outer text before {{innermacro}}inner text{{/innermacro}} outer text after{{/outermacro}} However, this doesn't work because the HTML parser sees the first "-->" it encounters as the "end of comment" marker, thus breaking the intended nesting. Thus, when converted to XWiki syntax, this is what comes out instead: {{outermacro}}outer text before <==startmacro:innermacro|-||-|inner text{{/outermacro}} outer text after ~-~-> We have considered a couple possible solutions: 1. Mimic what CKEditor does in this scenario, which is to use an HTML comment for the outermost macro-block, but have any nested macros (embedded inside the HTML comment) be rendered as XWiki-native syntax. Like this: < ! --startmacro:outermacro|-||-|outer text before {{innermacro}}inner text{{//innermacro}} outer text after-->< ! --stopmacro--> This approach seems to work, but it's not ideal because our Annotated XHTML generation code will now need to support two varieties of output depending on the current nesting level -- Annotated XHTML for the outermost depth, and XWiki-native for anything nested deeper. 2. Implement a variation of the existing Annotated XHTML parsing logic which, instead of expecting macros encoded in HTML comments, will expect the use of an XHTML structure that models the same information, but doesn't suffer from the nesting restrictions of HTML comments. Something like this: <xannotation name="startmacro:outermacro"> outer text before <xannotation name="innermacro"> inner text </xannotation> outer text after </xannotation> I am looking for input from XWiki experts regarding what approach would make the most sense. Option 2 above seems like the most elegant solution overall, but I'm not sure how difficult this would be to get working in the current XWiki codebase, or what file(s) would need to be extended, etc. Is there another approach that might solve this problem more efficiently? Note: For brevity, I've referred to "nested macros" above, but for our use case we will actually need to handle all the different comment types recognized in XWikiCommentHandler.java. References: AnnotatedXHTMLRenderer.java: https://github.com/xwiki/xwiki-rendering/blob/master/xwiki-rendering-syntax… XWikiCommentHandler.java: https://github.com/xwiki/xwiki-rendering/blob/master/xwiki-rendering-syntax… -- View this message in context: http://xwiki.475771.n2.nabble.com/RESEND-Nesting-within-Annotated-XHTML-tp7… Sent from the XWiki- Dev mailing list archive at Nabble.com.

2 3

[xwiki-devs] [ANN] XWiki 9.2 released
by Guillaume Delhumeau 28 Mar '17

28 Mar '17

The XWiki development team is proud to announce the availability of XWiki 9.2. This release introduces the Notification menu to follow wiki activity more easily. The Administration has been re-organized with a collapsible menu. The Menu Application becomes responsive with burger menus. For the advanced users, the CKEditor integration adds support for dedicated Insert Macro tool bar buttons and the Extension Manager adds support for conflict resolution configuration when installing an extension. As usual, the release also brings many bug fixes and other small improvements. 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.2 Thanks for your support -The XWiki dev team

1 0

[xwiki-devs] RedPen Integration
by oussema hidri 28 Mar '17

28 Mar '17

Hello XWIKI developers: My name is Oussema Hidri and I am software engineer student. For GSoC I am interested about the http://dev.xwiki.org/xwiki/bin/view/ GoogleSummerOfCode/RedPenIntegration2017. Few days ago I discussed with one of the members in IRC and he advised me to download and install both XWIKI and RedPen, understand them and write a proposal to you =) I did that and I read the documentations, and as I understood the project is about making an extension that involves validating the content entered by the user. What should be my next step be? Should I start writing my proposal, or send Pull Requests to the JIRA issues? With Love, Oussema Hidri.

2 1

[xwiki-devs] Nesting within Annotated XHTML
by ktc 27 Mar '17

27 Mar '17

I have a use case where I need to nest macros to 2+ levels deep using XWiki's Annotated XHTML syntax. We are using this syntax as an input to a transformation process that utilizes XWiki's rendering engine to convert the Annotated XHTML into XWiki-native markup, similarly to how CKEditor does its work. The problem is that with Annotated XHTML, macros are encoded as HTML comments -- but HTML comments cannot be nested within other HTML comments. Here is a demonstrative example: outer text after--> The intention is for this to be convertible to this XWiki syntax: {{outermacro}}outer text before {{innermacro}}inner text{{/innermacro}} outer text after{{/outermacro}} However, this doesn't work because the HTML parser sees the first "-->" it encounters as the "end of comment" marker, thus breaking the intended nesting. Thus, when converted to XWiki syntax, this is what comes out instead: {{outermacro}}outer text before <==startmacro:innermacro|-||-|inner text{{/outermacro}} outer text after ~-~-> We have considered a couple possible solutions: 1. Mimic what CKEditor does in this scenario, which is to use an HTML comment for the outermost macro-block, but have any nested macros (embedded inside the HTML comment) be rendered as XWiki-native syntax. Like this: This approach seems to work, but it's not ideal because our Annotated XHTML generation code will now need to support two varieties of output depending on the current nesting level -- Annotated XHTML for the outermost depth, and XWiki-native for anything nested deeper. 2. Implement a variation of the existing Annotated XHTML parsing logic which, instead of expecting macros encoded in HTML comments, will expect the use of an XHTML structure that models the same information, but doesn't suffer from the nesting restrictions of HTML comments. Something like this: <xannotation name="startmacro:outermacro"> outer text before <xannotation name="innermacro"> inner text </xannotation> outer text after </xannotation> I am looking for input from XWiki experts regarding what approach would make the most sense. Option 2 above seems like the most elegant solution overall, but I'm not sure how difficult this would be to get working in the current XWiki codebase, or what file(s) would need to be extended, etc. Is there another approach that might solve this problem more efficiently? Note: For brevity, I've referred to "nested macros" above, but for our use case we will actually need to handle all the different comment types recognized in XWikiCommentHandler.java. References: AnnotatedXHTMLRenderer.java: https://github.com/xwiki/xwiki-rendering/blob/master/xwiki-rendering-syntax… XWikiCommentHandler.java: https://github.com/xwiki/xwiki-rendering/blob/master/xwiki-rendering-syntax… -- View this message in context: http://xwiki.475771.n2.nabble.com/Nesting-within-Annotated-XHTML-tp7603270.… Sent from the XWiki- Dev mailing list archive at Nabble.com.

1 0

[xwiki-devs] [GSOC-2017]
by Krzysiek Płachno 27 Mar '17

27 Mar '17

Hello! I'm last year student of Computer Science Master at AGH University of Science and Technology in Cracow, Poland. I'd like to take part in GSoC working on XWiki. I've never heard about XWiki before, and I got very interested with the idea of "Second generation wiki". And so, I'd like to contribute to this fancy idea, and get to know the project better. The task that I'd like to take is "More extension repositories". I'm a Java EE Developer with one year experience of working in real world company. Frameworks that I worked with: Spring, Hibernate and many other smaller ones. Of course I worked with REST and Http protocol, so I think I'm quite prepared to the task. I spent some time trying to build locally XWiki Platform system - on both Windows and Linux environments and there're always some problems. I followed all instructions given here: http://dev.xwiki.org/xwiki/bin/view/Community/Building. <http://dev.xwiki.org/xwiki/bin/view/Community/Building#HTroubleshooting> Do you have something like configured Virtual Machine on which I can run building seamlessly? Or do you have some troubleShooting wiki, when you post solution to common problems. (I guess mailing list is not the best place for pasting logs and asking for help, right?) Best, Krzysztof Płachno

2 6

[xwiki-devs] Know about red pen integration
by NILESH GULIA 27 Mar '17

27 Mar '17

Hello I want to know more about working of red pen and its designing issues. Skills:html5,css3,js On Mar 26, 2017 10:57 PM, <devs-request(a)xwiki.org> wrote: Send devs mailing list submissions to devs(a)xwiki.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.xwiki.org/mailman/listinfo/devs or, via email, send a message with subject or body 'help' to devs-request(a)xwiki.org You can reach the person managing the list at devs-owner(a)xwiki.org When replying, please edit your Subject line so it is more specific than "Re: Contents of devs digest..." Today's Topics: 1. know about projects (NILESH GULIA) 2. Re: Glossary Application (Sarthak Gupta) 3. Re: [GSOC-2017] DokuWiki importer (Abilashini Thiyagarajah) 4. Re: Glossary Application (Vincent Massol) ---------------------------------------------------------------------- Message: 1 Date: Sun, 26 Mar 2017 17:48:33 +0530 From: NILESH GULIA <16bcs030(a)smvdu.ac.in> To: devs(a)xwiki.org Subject: [xwiki-devs] know about projects Message-ID: <CABFhrE4GwOq6xOVTtqSSwTaDafEtEduf5X8_KRDiFF+68nxy5A(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 hi there, I am Nilesh a student in comp,science and eng.. Tell me more about red pen integration and search callibrator and how to contribute to them.Is the knowledge of following skills sufficient? skills:html5,css3,javascript ------------------------------ Message: 2 Date: Sun, 26 Mar 2017 18:15:07 +0530 From: Sarthak Gupta <sarthakgupta072(a)gmail.com> To: XWiki Developers <devs(a)xwiki.org> Subject: Re: [xwiki-devs] Glossary Application Message-ID: <CAANw3tF-g+uGq3PixtTsVREqFe-jUWiyCyp4OO6X-Cx5h1QakQ(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi Vincent, I am not able to decide how would my approach be like to develop the glossary application. I have an idea what I need to do to develop this app but couldn't able to decide the milestones(that I will write in my proposal) I should set. The things I know are to be done are: - The glossary app homepage will be created by "App within minutes application". - Using rendering transformation to create links to the app and to display the words. - Developing the extension whose mechanism will be analogous to that of annotation extension. - Linking the extension with the glossary home page and to pages containing definition of words. Please guide me. Thanks -Sarthak Gupta On Fri, Mar 24, 2017 at 10:38 PM, Vincent Massol <vincent(a)massol.net> wrote: > Hi Sarthak, > > > On 24 Mar 2017, at 16:44, Sarthak Gupta <sarthakgupta072(a)gmail.com> > wrote: > > > > Hi Vincent, > > > > I have created a design page > > > > Link: http://design.xwiki.org/xwiki/bin/view/Proposal/ > GlossaryApplication > > I?ve commented on the page. > > Thanks > -Vincent > > > > > I request you to review it and please tell me if anything needs to be > > added/modified in it. > > > > Thanks :) > > > > Sarthak Gupta > > > > On Thu, Mar 23, 2017 at 12:21 AM, Sarthak Gupta < > sarthakgupta072(a)gmail.com> > > wrote: > > > >> > >> > >> On Tue, Mar 21, 2017 at 4:09 PM, Vincent Massol <vincent(a)massol.net> > >> wrote: > >> > >>> Hi Sarthak, > >>> > >>>> On 20 Mar 2017, at 20:00, Sarthak Gupta <sarthakgupta072(a)gmail.com> > >>> wrote: > >>>> > >>>> ?Hi Vincent, > >>>> > >>>> I have come up with an idea that: > >>>> 1. I will make an extension that will link to the Glossary Page. > >>> > >>> ?? > >>> The extension *is* the Glossary app. There?s no glossary page in XWiki > >>> ATM. The point of this project is to create this app/extension. > >>> > >>> > >> I was talking about the home page(I will make) of the glossary app that > I > >> proposed. :P? > >> > >> > >> > >>>> 2. The idea would be whenever a user will select a list of words in > the > >>> page, then a button will appear just above the text. > >>> > >>> Ok. We could also introduce a shortcut key as we have for annotations > >>> (ctrl+M). > >>> > >>> I guess you?re referring to creating glossary entries right? > >>> > >>> ?Yup, glossary entries will be created on clicking the 'Make entry' > >> button by admin or by shortcut key as proposed by you. > >> > >>> Because for viewing the the Rendering Transformation would simply > create > >>> standard links IMO. > >>> > >>> > >> ?I need to think how this will work. > >> ? > >> > >>>> 3. On clicking that button a dialog box will appear on the bottom > right > >>> of the screen that will specify some options as follows: > >>> > >>> I think it should appear just below the word(s) you selected. > >>> > >>> ?Yes, this would be better. The dialog box will move along the screen > as > >> we move to the next word. > >> ? > >> > >>>> (i)For a user: (a) "Word name"(one word at a time. Next word could > >>> be accessed by clicking an another button) > >>>> (b) Short description of the word, with a link > >>> for 'Read More'. Clicking on 'Read more' will direct the user to the > >>> glossary page. > >>> > >>> I think it?s enough to do display that on hover without clicking. > >>> Clicking would go to the glossary page. > >>> > >> ?Yes, I agree with this too.? > >> > >>>> (ii) For an Admin: (a) The JavaScript will scan each and every word > >>> of the selected text, and will display if a word in the selected > >>> text is in the Glossary Page or not(by the > use > >>> different color for each word that is 'in' and that is 'not in' > >>> the glossary page. > >>> > >>> That?s one way of doing it indeed. Another way (possibly better or not > - > >>> We need to list the pros and cons of each approach) is to use a > Rendering > >>> Transformation since it?s meant for that. > >>> > >>> I don?t understand why only admins would see glossary terms on the > page. > >>> IMO everyone should see them. > >>> > >>> ?I meant to say that the users will be able to see the words which have > >> entries on the glossary page. But for admin, he would be able to > see/select > >> the both the words that are 'in' and 'not in' the glossary page and make > >> changes to them.? > >> > >> > >> > >>>> (b) Add the word to the glossary page/ > >>> Make changes(which will direct the admin to the glossary page and there > >>> he could add new entries or make > changes > >>> to the original one). > >>>> 4. The glossary page will simply be created with 'Create Page' > provided > >>> in X-wiki I suppose. I need to think of interface :P. > >>> > >>> IMO there should be 2 ways: > >>> 1) same mechanism as for annotations > >>> 2) on the glossary app home page with a form > >>> > >>> ?I am not able to grasp these points. So I would try discussing it on > >> IRC?probably . > >> > >>> It would be nice if you could create a design page on design.xwiki.org > >>> so that we can record all decisions that we take. > >>> > >>> ?I have initiated a page, and going through the tutorials? on how to > use > >> the 'design page' and 'create application'. I will come out with > something > >> in few days. :) > >> > >> Thanks > >> > >> Sarthak Gupta > >> > >> > > ------------------------------ Message: 3 Date: Sun, 26 Mar 2017 21:32:06 +0530 From: Abilashini Thiyagarajah <abilashini.13(a)cse.mrt.ac.lk> To: Thomas Mortagne <thomas.mortagne(a)xwiki.com> Cc: XWiki Developers <devs(a)xwiki.org> Subject: Re: [xwiki-devs] [GSOC-2017] DokuWiki importer Message-ID: <CAFX9s621LaqY9==aVEAwiE_mb0frDXSShRPnA=L+-xo2oE8L-A(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi , I am working to understand the process in the implementation of MediaWiki-XML. Mean while I am preparing the proposal. The high level concept behind this project will be as implementing a filter which intercepts the DokuWiki input and converts into the events to be accepted by the output filter (correct me if I am wrong). So now I have the question on what are the events to be supported by the filter. I found this file [1] saying as the events related to extensions. Is these are the events to be considered? But this file does not state any explanation on each events. I don't understand what are these stand for. Can I have any available references which states about events? [1] https://github.com/xwiki/xwiki-commons/blob/master/xwiki-commons-core/xwiki- commons-filter/xwiki-commons-filter-events/xwiki-commons- filter-event-extension/src/main/java/org/xwiki/filter/event/extension/ ExtensionFilter.java Thanks and Regards, Abilashini *Thiyagarajah Abilashini* Student Department of Computer Science and Engineering University of Moratuwa, Sri Lanka On 23 March 2017 at 16:30, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: > Actually I just renamed the wrongly named (was not following contrib > rules) class to > org.xwiki.contrib.mediawiki.xml.internal.input. > MediaWikiInputFilterStreamFact. > > On Thu, Mar 23, 2017 at 11:52 AM, Thomas Mortagne > <thomas.mortagne(a)xwiki.com> wrote: > > Did you look at > > http://extensions.xwiki.org/xwiki/bin/view/Extension/ > MediaWiki/MediaWiki+XML/. > > ? Because the Dokuwiki version will have the exact same structure than > > this one. > > > > You should try to build https://github.com/xwiki-contrib/mediawiki/ > > and look at the code of > > https://github.com/xwiki-contrib/mediawiki/tree/master/mediawiki-xml. > > The main entry point is the class > > org.xwiki.filter.mediawiki.xml.internal.input. > MediaWikiInputFilterStreamFactory. > > You can also find unit tests in this project that you can execute to > > debug how things are working. > > > > On Thu, Mar 23, 2017 at 11:41 AM, Abilashini Thiyagarajah > > <abilashini.13(a)cse.mrt.ac.lk> wrote: > >> Hi Thomas, > >> > >> I went through most of the online documents to understand the > >> functionalities of xwiki. But a little bit confused on how to get stated > >> with xwiki. It would be really helpful if I get some assistance to find > out > >> the code base and the instructions to start with xwiki related to the > >> project. > >> > >> Thanks in advance, > >> Abilashini > >> > >> Thiyagarajah Abilashini > >> Student > >> Department of Computer Science and Engineering > >> University of Moratuwa, Sri Lanka > >> > >> On 22 March 2017 at 20:10, Abilashini Thiyagarajah > >> <abilashini.13(a)cse.mrt.ac.lk> wrote: > >>> > >>> Hi Thomas, > >>> > >>> Thank you for the quick reply and the reference. I will continue my > work > >>> to get familiarized with the project and let you know my progress. > >>> > >>> Best Regards, > >>> Abilashini > >>> > >>> Thiyagarajah Abilashini > >>> Student > >>> Department of Computer Science and Engineering > >>> University of Moratuwa, Sri Lanka > >>> > >>> On 22 March 2017 at 19:59, Thomas Mortagne <thomas.mortagne(a)xwiki.com> > >>> wrote: > >>>> > >>>> Hi Abilashini, > >>>> > >>>> Welcome in the XWiki community ! > >>>> > >>>> In case you did not do it already you might want to take a look at > >>>> http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Guidelines. > >>>> > >>>> For this project the goal is to write an "Input Filter" which support > >>>> Dokuwiki export format (whatever it is). The closed example you could > >>>> find for this is the MediaWiki Input Filter you can find on > >>>> > >>>> http://extensions.xwiki.org/xwiki/bin/view/Extension/ > MediaWiki/MediaWiki+XML/. > >>>> > >>>> The general idea is that the extension should parse the Dokuwiki > >>>> file/package and generate standard "events" which are sent to the > >>>> Output Filter which turns those events into another format/storage > >>>> (like a XARfile , an XWiki database, etc.). > >>>> > >>>> On Wed, Mar 22, 2017 at 2:49 PM, Abilashini Thiyagarajah > >>>> <abilashini.13(a)cse.mrt.ac.lk> wrote: > >>>> > Hi, > >>>> > > >>>> > I am Abilashini Thiyagarajah, a final year undergraduate of > Department > >>>> > of > >>>> > Computer Science and Engineering, University of Moratuwa, Sri > Lanka. I > >>>> > am > >>>> > interested to contribute to the project 'DokuWiki importer'. > Currently > >>>> > I am > >>>> > working on to understand the provided resources in the project > >>>> > description. > >>>> > I will be so glad if I get some assistance to understand the > >>>> > requirements > >>>> > of this project. > >>>> > > >>>> > Thank you, > >>>> > Abilashini > >>>> > > >>>> > *Thiyagarajah Abilashini* > >>>> > Student > >>>> > Department of Computer Science and Engineering > >>>> > University of Moratuwa, Sri Lanka > >>>> > >>>> > >>>> > >>>> -- > >>>> Thomas Mortagne > >>> > >>> > >> > > > > > > > > -- > > Thomas Mortagne > > > > -- > Thomas Mortagne > ------------------------------ Message: 4 Date: Sun, 26 Mar 2017 19:27:21 +0200 From: Vincent Massol <vincent(a)massol.net> To: XWiki Developers <devs(a)xwiki.org> Subject: Re: [xwiki-devs] Glossary Application Message-ID: <A859CF0B-A974-433B-9DBC-B3466DB7A2B9(a)massol.net> Content-Type: text/plain; charset=utf-8 Hi Sarthak, > On 26 Mar 2017, at 14:45, Sarthak Gupta <sarthakgupta072(a)gmail.com> wrote: > > Hi Vincent, > I am not able to decide how would my approach be like to develop the > glossary application. I have an idea what I need to do to develop this app > but couldn't able to decide the milestones(that I will write in my > proposal) I should set. > > The things I know are to be done are: > > - The glossary app homepage will be created by "App within minutes > application". Yes it?s fine to use AWM although it?s not required at all and another UI could be proposed/done. See http://platform.xwiki.org/xwiki/bin/view/DevGuide/ FAQTutorial/FAQTutorialManual to understand how it works. You really need to understand this rather than use the AWM which hides how it works. > - Using rendering transformation to create links to the app and to > display the words. Yes,except not direct links but on hover information + link in the on hover popup. > - Developing the extension whose mechanism will be analogous to that of > annotation extension. I don?t know what you call ?extension?. I think you mean the in-context creation of glossary entries. > - Linking the extension with the glossary home page and to pages > containing definition of words. What do you call extension? In XWiki an extension has a special meaning, see http://extensions.xwiki.org/xwiki/bin/view/Extension/ > Please guide me. I would if I knew what you?re looking for precisely :) You?ve already listed several steps above. Couldn?t that be your milestones? IMO you should also propose other features that could be implemented depending on how fast you progress on the main features. I?ll give you 2 examples (I?m not saying they?re the best but you should use your own experience/ideas by thinking about how you?d use this glossary feature and how to make it the best possible): * Provide an Admin UI to configure the Glossary application. For example to configure on which pages the transformation should execute (with regex includes/excludes) * Allow using Wikipedia (or other sources) to automatically gather information about glossary items. Thanks! -Vincent > Thanks > > -Sarthak Gupta > > On Fri, Mar 24, 2017 at 10:38 PM, Vincent Massol <vincent(a)massol.net> wrote: > >> Hi Sarthak, >> >>> On 24 Mar 2017, at 16:44, Sarthak Gupta <sarthakgupta072(a)gmail.com> >> wrote: >>> >>> Hi Vincent, >>> >>> I have created a design page >>> >>> Link: http://design.xwiki.org/xwiki/bin/view/Proposal/ >> GlossaryApplication >> >> I?ve commented on the page. >> >> Thanks >> -Vincent >> >>> >>> I request you to review it and please tell me if anything needs to be >>> added/modified in it. >>> >>> Thanks :) >>> >>> Sarthak Gupta >>> >>> On Thu, Mar 23, 2017 at 12:21 AM, Sarthak Gupta < >> sarthakgupta072(a)gmail.com> >>> wrote: >>> >>>> >>>> >>>> On Tue, Mar 21, 2017 at 4:09 PM, Vincent Massol <vincent(a)massol.net> >>>> wrote: >>>> >>>>> Hi Sarthak, >>>>> >>>>>> On 20 Mar 2017, at 20:00, Sarthak Gupta <sarthakgupta072(a)gmail.com> >>>>> wrote: >>>>>> >>>>>> ?Hi Vincent, >>>>>> >>>>>> I have come up with an idea that: >>>>>> 1. I will make an extension that will link to the Glossary Page. >>>>> >>>>> ?? >>>>> The extension *is* the Glossary app. There?s no glossary page in XWiki >>>>> ATM. The point of this project is to create this app/extension. >>>>> >>>>> >>>> I was talking about the home page(I will make) of the glossary app that >> I >>>> proposed. :P? >>>> >>>> >>>> >>>>>> 2. The idea would be whenever a user will select a list of words in >> the >>>>> page, then a button will appear just above the text. >>>>> >>>>> Ok. We could also introduce a shortcut key as we have for annotations >>>>> (ctrl+M). >>>>> >>>>> I guess you?re referring to creating glossary entries right? >>>>> >>>>> ?Yup, glossary entries will be created on clicking the 'Make entry' >>>> button by admin or by shortcut key as proposed by you. >>>> >>>>> Because for viewing the the Rendering Transformation would simply >> create >>>>> standard links IMO. >>>>> >>>>> >>>> ?I need to think how this will work. >>>> ? >>>> >>>>>> 3. On clicking that button a dialog box will appear on the bottom >> right >>>>> of the screen that will specify some options as follows: >>>>> >>>>> I think it should appear just below the word(s) you selected. >>>>> >>>>> ?Yes, this would be better. The dialog box will move along the screen >> as >>>> we move to the next word. >>>> ? >>>> >>>>>> (i)For a user: (a) "Word name"(one word at a time. Next word could >>>>> be accessed by clicking an another button) >>>>>> (b) Short description of the word, with a link >>>>> for 'Read More'. Clicking on 'Read more' will direct the user to the >>>>> glossary page. >>>>> >>>>> I think it?s enough to do display that on hover without clicking. >>>>> Clicking would go to the glossary page. >>>>> >>>> ?Yes, I agree with this too.? >>>> >>>>>> (ii) For an Admin: (a) The JavaScript will scan each and every word >>>>> of the selected text, and will display if a word in the selected >>>>> text is in the Glossary Page or not(by the >> use >>>>> different color for each word that is 'in' and that is 'not in' >>>>> the glossary page. >>>>> >>>>> That?s one way of doing it indeed. Another way (possibly better or not >> - >>>>> We need to list the pros and cons of each approach) is to use a >> Rendering >>>>> Transformation since it?s meant for that. >>>>> >>>>> I don?t understand why only admins would see glossary terms on the >> page. >>>>> IMO everyone should see them. >>>>> >>>>> ?I meant to say that the users will be able to see the words which have >>>> entries on the glossary page. But for admin, he would be able to >> see/select >>>> the both the words that are 'in' and 'not in' the glossary page and make >>>> changes to them.? >>>> >>>> >>>> >>>>>> (b) Add the word to the glossary page/ >>>>> Make changes(which will direct the admin to the glossary page and there >>>>> he could add new entries or make >> changes >>>>> to the original one). >>>>>> 4. The glossary page will simply be created with 'Create Page' >> provided >>>>> in X-wiki I suppose. I need to think of interface :P. >>>>> >>>>> IMO there should be 2 ways: >>>>> 1) same mechanism as for annotations >>>>> 2) on the glossary app home page with a form >>>>> >>>>> ?I am not able to grasp these points. So I would try discussing it on >>>> IRC?probably . >>>> >>>>> It would be nice if you could create a design page on design.xwiki.org >>>>> so that we can record all decisions that we take. >>>>> >>>>> ?I have initiated a page, and going through the tutorials? on how to >> use >>>> the 'design page' and 'create application'. I will come out with >> something >>>> in few days. :) >>>> >>>> Thanks >>>> >>>> Sarthak Gupta >>>> >>>> >> >> ------------------------------ Subject: Digest Footer _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs ------------------------------ End of devs Digest, Vol 117, Issue 33 *************************************

2 1

[xwiki-devs] [GSOC-2017] DokuWiki importer
by Abilashini Thiyagarajah 26 Mar '17

26 Mar '17

Hi, I am Abilashini Thiyagarajah, a final year undergraduate of Department of Computer Science and Engineering, University of Moratuwa, Sri Lanka. I am interested to contribute to the project 'DokuWiki importer'. Currently I am working on to understand the provided resources in the project description. I will be so glad if I get some assistance to understand the requirements of this project. Thank you, Abilashini *Thiyagarajah Abilashini* Student Department of Computer Science and Engineering University of Moratuwa, Sri Lanka

2 8

[xwiki-devs] know about projects
by NILESH GULIA 26 Mar '17

26 Mar '17

hi there, I am Nilesh a student in comp,science and eng.. Tell me more about red pen integration and search callibrator and how to contribute to them.Is the knowledge of following skills sufficient? skills:html5,css3,javascript

2 1

[xwiki-devs] GSoC proposal review
by Pawan Pal 24 Mar '17

24 Mar '17

Hi, I submitted my draft proposal for XWiki Android Authenticator on GSoC website 3 days ago. Please review it and comment the suggestions. Thanks.

2 2