- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [Proposal] Retro-compatibility between Color Theme Application ad Flamingo

by Guillaume "Louis-Marie" Delhumeau

Hi! The current color theme editor is designed for colibri, and does not look like flamingo does. We have several options here: - create a new color theme editor, especially for Flamingo - modify the current one to detect which skin is currenlty used, and change the preview. The application will be splited in 2 sections: 1/ a live preview where you can set some variables (what we currenlty have) 2/ a free textarea where the user can fill LESS code (for example, some code downloaded on bootswatch). But a lot of applications already use the color theme as it is, via the "colorThemeInit.vm" template. So we need a retro-compatibility: a color theme computed by LESS must be usable with old color themes. Concretly, we will map the old color theme variables to the bootstrap ones, example: $theme.notificationSuccessColor = @brand-success But because of the section 2 (the free textarea), we are not able to know what will be the final value of a bootstrap variables without parsing the content of the textarea! What are the options we have: 1/ Implementing our own LESS parser/compiler in Java 2/ Trying to reuse the official LESS Parser through Rhino in a way that we can get the computed variables 3/ Do not parse the input but the ouput: parse the CSS code to get the final values of the variables I'm for 3. The idea is to create some CSS classes like this: .colortheme-bordercolor{ color: @border-color; } which will be converted by LESS to: .colortheme-bordercolor{ color: #000000; } so we can parse it and know the value of $theme.bordercolor. It is quick, simple, but it pollutes the output CSS a little. WDYT? Thanks, Guillaume

11 years, 3 months

6
13
0 0

[xwiki-devs] What XWiki Day for the 5th of June?

by vincent＠massol.net

Hi devs, We missed last week’s XWiki Day (I just forgot, shame on me!) but we quickly discussed on IRC what could be the content of the next XWiki Day: - Thomas proposed a deprecation fixing day - I proposed a Pull Request day (to review all PRs and ensure we've replied to all and merge the ones we can) And now Danilo is proposing a Doc Day (see users list). So, contributors and committers, what do you wish to do for the following Thursday (the 5th of June since tomorrow is a bank holiday in France and I won’t be able to organize it, if someone is interesting to lead it, please answer here!)? Thanks -Vincent

11 years, 3 months

1
0
0 0

[xwiki-devs] Requesting rights on xwiki-contrib

by Lyes Bandou

Hi devs. For commit the code of Macro dynamic tree i need to have rights on xwiki-contrib. Github ID : bandoulyes Thank in advance --- Best regards - Cordialement --- Lyes Bandou

11 years, 3 months

2
2
0 0

[xwiki-devs] [Brainstorming] Improving the rendered quote syntax

by vincent＠massol.net

Hi devs, It’s been raised by a user to me that it’s strange that when they use a quote (using the “>” symbol) we don’t show visually that it’s a quote and that it seems to him that it would make sense to show some quote symbols. Right now on XE it looks like: https://www.evernote.com/shard/s119/sh/5eea60a0-8110-438e-a292-47d395c386bc… On xwiki.org (junco) it looks like this: http://www.xwiki.org/xwiki/bin/view/References/Testimonials It’s true that the XE’s default doesn’t look very much like a quote… It can be confused with a box easily. So WDYT about improving that in our default XE by having something either like junco (is it clear enough that it’s a quote) or adding quotes symbols? Thanks -Vincent

11 years, 3 months

4
5
0 0

[xwiki-devs] [VOTE] Support 3 XWiki versions instead of 2

by vincent＠massol.net

Hi devs, I’d like to propose that we change our rule of supporting the last 2 versions of XWiki (ie the latest stable and the version in development) which is documented here: http://www.xwiki.org/xwiki/bin/view/Main/Support The new support rule would be that we support: * The latest release from the previous development cycle (right now that’s 5.4.5) * The latest stable release from the current cycle (right now that’s 6.0.1) * The latest development release from the current cycle (right now that’s 6.1M1) The rationale is that we need to offer a super stable release (that’s the latest from the previous dev cycle) for users in production. Here’s my +1. Thanks -Vincent PS: Note that if we really wanted to support only 2 versions, then I’d propose to drop the “latest stable from the current cycle” (ie 6.0.1 right now), thus offering only 5.4.5 and 6.1M1 ATM.

11 years, 3 months

6
6
0 0

[xwiki-devs] Unwanted revision increments

by walid yaich

Hi, I added $doc.save() in contentview.vm to save the object added to my doc, this save increment the revision. is it possible to tell the save to not increment the version ? Thanks in advance :)

11 years, 3 months

4
4
0 0

[xwiki-devs] Approved Revision Installable with the Extension Manager

by walid yaich

Hi, When i finish this work i want to make an extension "*Installable with the Extension Manager*". Main modifications i have made : - Changes on *historyinline.vm* to add a button Approve in order to approve a revision and make it public. - Modification on *contentview.vm* to get the revision value passed in parameter from historyinline.vm and set the approved revision in the object attached to the document. - I added a *groovy listener*<http://extensions.xwiki.org/xwiki/bin/view/Extension/Create+an+XObject+By+d…>to add an object to new pages - Adding a new *class*<http://www.rendering.xwiki.org/xwiki/bin/viewrev/FAQ/How+to+implement+%22Ap…>to contains the value of the approved revision It's not finished yet, i have to make a clean and tested version of this extension and make some documentations, but i want to know if i'm on the right way to build an extension. An extension can override files like historyinline.vm ? if yes it won't work for futur version if XWIKI, right ? otherwise what's the best way to do so ? I can't find documentation about creating an installable Extension Manager. What about licenses? i asked my boss and he told me that we can make this public for free but i should mention the name of our company, and make copyright (the name of our company) in new source files, is it possible ? Thanks in advance :)

11 years, 3 months

2
3
0 0

[xwiki-devs] [ANN] XWiki 5.4.5 released

by Guillaume "Louis-Marie" Delhumeau

The XWiki development team is proud to announce the availability of XWiki 5.4.5. This release is a stabilization version that fix important bugs discovered in the 5.4.4 version. 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/ReleaseNotesXWiki545 Thanks -The XWiki dev team

11 years, 3 months

1
0
0 0

Re: [xwiki-devs] [Contrib] Create a repository for the Hierarchy Macro

by Lyes Bandou

Hi Vincent Thank you , and no we don't need a JIRA project yet On Mon, May 26, 2014 at 11:15 AM, vincent(a)massol.net <vincent(a)massol.net>wrote: > Hi Lyes, > > Done: https://github.com/xwiki-contrib/macro-dynamic-tree > > Do you also need a JIRA project? > > Thanks > -Vincent > > On 21 May 2014 at 19:07:24, Anca Luca (lucaa(a)xwiki.com(mailto: > lucaa(a)xwiki.com)) wrote: > > > Hello Devs, > > > > As far as I know it's not a refactoring of the old macro because some > > parameters / parameters behaviour was not kept 100%. It's missing some > > features, basically. Adding some with the cost of removing others. > > > > So if we consider it a new version of the old one, installing an > "upgrade" > > will break the behaviour. You'd tell me we could wait to release the new > > version it only when ready, but then people could not take advantage of > its > > features (which are cool). > > > > We could have it as a new extension until we implement all the features > of > > the old one, and then we mark it as implementing the same feature so that > > the old one could be upgraded to the new one. > > > > Anca > > > > > > On Wed, May 21, 2014 at 7:11 PM, vincent(a)massol.net wrote: > > > > > > > > > > > > > > > > > On 21 May 2014 at 18:08:33, Lyes Bandou (lyes.bandou(a)xwiki.com(mailto: > > > lyes.bandou(a)xwiki.com)) wrote: > > > > > > > Code of the two macros is not the same, > > > > > > This doesn’t matter much if the new code is considered a refactoring of > > > the old code. > > > > > > > The new macro has the same name and > > > > keeps most paramettres, but the behavior is not the same it uses > Ajax to > > > > load the data (using JSON) and the older macro display the documents > > > > hierarchy in a space , the new macro can uses documents list as > documents > > > > roots of the tree (plus another paramettres) > > > > > > > > > > > > I suggest "Dynamic Tree Macro" as the new name. > > > > > > The real question is: do we need the 2 macros at once? > > > > > > I guess we need to ask the question to the author of the first macro: > > > Anca, Paul, Mircea. > > > > > > Because from a user point of view, it’s a nightmare to have several > > > extensions doing the same thing, the user never knows which one to use. > > > > > > Anca/Paul/Mircea, do you have an opinion? > > > > > > Thanks > > > -Vincent > > > > > > > On Wed, May 21, 2014 at 4:40 PM, Thomas Mortagne > > > > wrote: > > > > > > > > > Same question, why is a new repository needed exactly ? If it's THE > > > > > new version then it's the same extension and it should be the same > > > > > repository, even if you rewrite half of it in a 2.0 version. > > > > > > > > > > On Wed, May 21, 2014 at 5:37 PM, vincent(a)massol.net > > > > > wrote: > > > > > > Do you really need a new extension? Couldn’t you improve the > existing > > > > > one then? > > > > > > > > > > > > Thanks > > > > > > -Vincent > > > > > > > > > > > > On 21 May 2014 at 17:35:52, Lyes Bandou (lyes.bandou(a)xwiki.com > > > (mailto: > > > > > lyes.bandou(a)xwiki.com)) wrote: > > > > > > > > > > > >> This is the new version of Hierarchy Macro ( > > > > > >> > http://extensions.xwiki.org/xwiki/bin/view/Extension/HierarchyMacro > > > ) > > > > > with > > > > > >> the addition of to many parameters > > > > > >> > > > > > >> > > > > > >> On Wed, May 21, 2014 at 4:26 PM, Thomas Mortagne > > > > > >> wrote: > > > > > >> > > > > > >> > Are you talking about > > > > > >> > > > > http://extensions.xwiki.org/xwiki/bin/view/Extension/HierarchyMacro ? > > > > > >> > > > > > > >> > If not you might want to find another name since this one > already > > > have > > > > > >> > https://github.com/xwiki-contrib/macro-hierarchy. > > > > > >> > > > > > > >> > On Wed, May 21, 2014 at 5:23 PM, Lyes Bandou > > > > > >> > wrote: > > > > > >> > > Hello devs, > > > > > >> > > > > > > > >> > > I would like a repository for the Hierarchy Macro on > > > > > >> > > https://github.com/xwiki-contrib. > > > > > >> > > > > > > > >> > > Hierarchy Macro use jQuery and jsTree ( > http://www.jstree.com) > > > to > > > > > display > > > > > >> > > dynamique tree view of wiki documents based on parent/child > > > > > relationships > > > > > >> > > > > > > > >> > > Thank you in advance. > > > > > >> > > > > > > > >> > > > > > > > >> > > Lyes Bandou > > > > > > > > > > > > _______________________________________________ > > > > > > devs mailing list > > > > > > devs(a)xwiki.org > > > > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > > > > > > > > > > > > > > > -- > > > > > Thomas Mortagne > > > > > _______________________________________________ > > > > > devs mailing list > > > > > devs(a)xwiki.org > > > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > > > > _______________________________________________ > > > > devs mailing list > > > > devs(a)xwiki.org > > > > http://lists.xwiki.org/mailman/listinfo/devs > > > _______________________________________________ > > > devs mailing list > > > devs(a)xwiki.org > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs >

11 years, 3 months

1
0
0 0

Re: [xwiki-devs] [Contrib] Create a repository for the Hierarchy Macro

by Lyes Bandou

Code of the two macros is not the same, The new macro has the same name and keeps most paramettres, but the behavior is not the same it uses Ajax to load the data (using JSON) and the older macro display the documents hierarchy in a space , the new macro can uses documents list as documents roots of the tree (plus another paramettres) I suggest "Dynamic Tree Macro" as the new name. On Wed, May 21, 2014 at 4:40 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com>wrote: > Same question, why is a new repository needed exactly ? If it's THE > new version then it's the same extension and it should be the same > repository, even if you rewrite half of it in a 2.0 version. > > On Wed, May 21, 2014 at 5:37 PM, vincent(a)massol.net <vincent(a)massol.net> > wrote: > > Do you really need a new extension? Couldn’t you improve the existing > one then? > > > > Thanks > > -Vincent > > > > On 21 May 2014 at 17:35:52, Lyes Bandou (lyes.bandou(a)xwiki.com(mailto: > lyes.bandou(a)xwiki.com)) wrote: > > > >> This is the new version of Hierarchy Macro ( > >> http://extensions.xwiki.org/xwiki/bin/view/Extension/HierarchyMacro) > with > >> the addition of to many parameters > >> > >> > >> On Wed, May 21, 2014 at 4:26 PM, Thomas Mortagne > >> wrote: > >> > >> > Are you talking about > >> > http://extensions.xwiki.org/xwiki/bin/view/Extension/HierarchyMacro ? > >> > > >> > If not you might want to find another name since this one already have > >> > https://github.com/xwiki-contrib/macro-hierarchy. > >> > > >> > On Wed, May 21, 2014 at 5:23 PM, Lyes Bandou > >> > wrote: > >> > > Hello devs, > >> > > > >> > > I would like a repository for the Hierarchy Macro on > >> > > https://github.com/xwiki-contrib. > >> > > > >> > > Hierarchy Macro use jQuery and jsTree (http://www.jstree.com) to > display > >> > > dynamique tree view of wiki documents based on parent/child > relationships > >> > > > >> > > Thank you in advance. > >> > > > >> > > > >> > > Lyes Bandou > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > -- > Thomas Mortagne > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs >

11 years, 3 months

3
3
0 0

[xwiki-devs] Infinite loop in documentation

by walid yaich

Hi, I think there is a loop when trying to read about DocumentSheetBinding<http://enterprise.xwiki.org/xwiki/bin/view/XWiki/DocumentSheetBinding>, here is the link: http://enterprise.xwiki.org/xwiki/bin/view/XWiki/SheetDescriptorClass Have a nice day :)

11 years, 3 months

2
2
0 0

[xwiki-devs] Display Revision Application

by walid yaich

Hi, I have problem to get this application works properly, In this article<http://www.xwiki.org/xwiki/bin/view/FAQ/How+to+implement+%22Approved+Revisi…>, i'm supposed to do this to test it : 1. Create a page, say Main.Test with the content "Original Content" 2. Edit the page again to change the content to "New Content" 3. Add an XObject of type Revision.RevisionClass and set the revisionfield to 1.1 (this is the version we want to display) 4. Save This works But when we change the order : 1. Add an XObject of type Revision.RevisionClass and set the revisionfield to 1.1 (this is the version we want to display) 2. Create a page, say Main.Test with the content "Original Content" 3. Edit the page again to change the content to "New Content" 4. Save it doesn't work anymore, you save the Revision object with the right revision but it won't display it. But this works for all revisions before adding the object. Once you added the object, no matter how much changes you made, you won't be able to display last revisions(created after adding the object) BTW, when i give a wrong revision, the page display just "$revDoc.getRenderedContent()" One strange usecase : 1) i create a new page, make modifications and save 3 times 2) i add the object and give 1.1 for revision and save 3) when i edit the file, in the editor, i can find the last version, i modify something and save ==> it's like, it'll save the revision 1.1 (setted to the added object) When i make "compare selected version" between the last and the first, it gives me the last change i made, but when i click on the last revision i can't find the last change i made. Any explanation please ? Thanks in advance :)

11 years, 3 months

2
2
0 0

[xwiki-devs] Display revision

by walid yaich

Hi, Please, did you remember on which XWIKI version did you test this application<http://www.xwiki.org/xwiki/bin/view/FAQ/How+to+implement+%22Approved+Revisi…>? i tried it on 5.4.4 and 6.0 but i can't get it work properly, Thanks in advance

11 years, 3 months

2
1
0 0

[xwiki-devs] historyinline.vm

by walid yaich

Hi, I'm changing historyinline.vm to add a link "Approve", in order to set the approved revision in the object added to the document. I added this tag in the foreach : do this make sens ? is it supposed to work ? <a href="" onclick="$doc.set("revision", $version)">Approve</a></td> In my html source i find : <a href="" onclick="">Approve</a> the display is fine but no action, nothing happen Thanks in advance :)

11 years, 3 months

1
1
0 0

[xwiki-devs] Add an object by default for all pages

by walid yaich

Hello, First of all, Merci bcp Vincent for this How to implement "Approved Revisions"?<http://www.xwiki.org/xwiki/bin/view/FAQ/How+to+implement+%22Approved+Revisi…> I was able to choose which revision to display by following the "how to", now i need to add the object automatically to any page in my wiki or at least any page in a given space Thanks in advance :)

11 years, 3 months

6
25
0 0

[xwiki-devs] [ANN] XWiki 6.1 Milestone 1 Released

by Marius Dumitru Florea

The XWiki development team is proud to announce the availability of XWiki 6.1 Milestone 1. This release introduces the ability to change the width of the panel columns and comes with an improved Active Installs feature (with evolution graph and many new filters). Developers can now use the LESS preprocessor for skin style sheets. A couple of bug fixes (18) and some small improvements (24) make this release worth trying. 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/ReleaseNotesXWiki61M1 Thanks -The XWiki dev team

11 years, 3 months

1
0
0 0

[xwiki-devs] [ANN] XWiki 6.0.1 released

by Thomas Mortagne

The XWiki development team is proud to announce the availability of XWiki 6.0.1. This release is a stabilization version that fix important bugs discovered in the 6.0 version. 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/ReleaseNotesXWiki601 Thanks -The XWiki dev team

11 years, 3 months

1
0
0 0

Re: [xwiki-devs] [Contrib] Create a repository for the Hierarchy Macro

by Lyes Bandou

This is the new version of Hierarchy Macro ( http://extensions.xwiki.org/xwiki/bin/view/Extension/HierarchyMacro) with the addition of to many parameters On Wed, May 21, 2014 at 4:26 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com>wrote: > Are you talking about > http://extensions.xwiki.org/xwiki/bin/view/Extension/HierarchyMacro ? > > If not you might want to find another name since this one already have > https://github.com/xwiki-contrib/macro-hierarchy. > > On Wed, May 21, 2014 at 5:23 PM, Lyes Bandou <lyes.bandou(a)xwiki.com> > wrote: > > Hello devs, > > > > I would like a repository for the Hierarchy Macro on > > https://github.com/xwiki-contrib. > > > > Hierarchy Macro use jQuery and jsTree (http://www.jstree.com) to display > > dynamique tree view of wiki documents based on parent/child relationships > > > > Thank you in advance. > > > > > > Lyes Bandou > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > -- > Thomas Mortagne > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs >

11 years, 3 months

3
2
0 0

[xwiki-devs] [Contrib] Create a repository for the Hierarchy Macro

by Lyes Bandou

Hello devs, I would like a repository for the Hierarchy Macro on https://github.com/xwiki-contrib. Hierarchy Macro use jQuery and jsTree (http://www.jstree.com) to display dynamique tree view of wiki documents based on parent/child relationships Thank you in advance. Lyes Bandou

11 years, 3 months

2
1
0 0

[xwiki-devs] VOTE: Integrate LESS in XWiki

by Guillaume "Louis-Marie" Delhumeau

Needs: As you already know, the new skin, Flamingo, is based on Bootstrap ( http://getbootstrap.com/) which use a CSS Preprocessor to have more flexibility. There is 2 majors competitors in this field: LESS ( http://lesscss.org/) and SASS (http://sass-lang.com/). Bootstrap is using LESS but they also provide an official port for SASS. We need to execute one of these preprocessors at the runtime, to recompile the Bootstrap CSS according to the current Color Theme. After a long thread [1] where we have compared the 2 preprocessors, and after some discussions on IRC, **I am proposing you to choose LESS**. Why: * It is the original preprocessor used by Bootstrap, and so the majority of Bootstrap Themes that we can find on the web provides LESS sources. If we want to be able to use all these themes, using LESS is clearly an advantage. * Caty, Denis and I have a bit of experience with it. Bluebird [2], Junco [3] and the current Flamingo skins are built with LESS. * The syntax is not too close to Velocity, meanwhile SASS is. * The Java integration, using Rhino, works quite well. Although there is an issue [4] for which I have written a patch. I hope the LESS community will handle it. * It looks a bit more popular than SASS. Here is my +1 for using LESS. For the record, this is what I am going to do: * Implement a cache to only compile LESS files when needed, because the computation is costly. The cache will be flushed only when the current color theme is modified. * Write new components and a script service to compile LESS files that are present in the skin directory, partially parsed with Velocity. In the future, we might want to integrate it directly in the Skin Action, but that means we need to change oldcore. Thanks, Guillaume (Louis-Marie) --- [1] The thread "[Proposal] Integrate LESS css in XWiki": http://markmail.org/message/hw45txkv2vk5dnqw [2] Bluebird Skin: http://extensions.xwiki.org/xwiki/bin/view/Extension/Bluebird+Skin [3] Junco Skin: http://extensions.xwiki.org/xwiki/bin/view/Extension/Junco+Skin [4] LESS issue: https://github.com/less/less.js/issues/2005

11 years, 3 months

6
8
0 0

[xwiki-devs] [History] Add links to every revision

by walid yaich

Good morning, I read the user guide and a part of developer's guide and i really really really like the philosophy and architecture of XWIKI, thanks for all XWIKI Teams and contributors for this great work :) Actually, i need some help, Now, In the page history, we have one link "delete" related to every revision I need to add for every revision next to "delete" two links, "approve" and "unapprove" like this in mediaWiki [image: Images intégrées 1] Questions : 1)how can i find the right XCLASS and/XOBJECT to modify, 2)how can i know the code behind the link "delete", is it velocity ? Thanks in advance, Have a nice day :)

11 years, 4 months

2
1
0 0

[xwiki-devs] myxwiki.org status

by Ludovic Dubost

Hi, myxwiki.org seem to crash quite a lot recently and we have also detected that it's using a lot of CPU (compared to many other services that XWiki SAS is running). I've taken a memory dump of myxwiki.org to give it a look. I see in the memory analysis 400Mb in the velocimacro structures. This could be normal as there are some caches of macros for each wiki (and there are a lot of wikis), however this is a lot and should be looked at. I've put the page http://www.myxwiki.org/xwiki/bin/view/Admin/CheckVelocityManager to check if we see any macros being cached that should not be (like the bug we had on USH). In any case, in multiwiki we have an issue with cache of velocity macros which can grow pretty big without any cleaning up when the wiki is not accessed. I've also closed registration on the main wiki (there seem to be spam users) and will run some scripts with check for open wikis and for pages with big RCS (spam suspects). We should in any case reduce the load of myxwiki (private cloud analysis shows a big CPU usage) and for this some cleaning up of unused wiki sounds like a plan. We should contact all users and closed unused wikis (I bet there are a lot). Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

11 years, 4 months

2
2
0 0

[xwiki-devs] [contrib] Move realtime-backend and realtime-wiki to xwiki-contrib

by Caleb James DeLisle

Hi, I'd like to shove these two projects over into xwiki-contrib github group. One is for the backend which supports realtime-wysiwyg and realtime-wiki and the other is the realtime-wiki (text editor). https://github.com/cjdelisle/xwiki-contrib-rtbackend https://github.com/cjdelisle/xwiki-contrib-rtwiki Thanks, Caleb

11 years, 4 months

2
3
0 0

[xwiki-devs] [IDEA] Start supporting IE10 and IE11

by Andreea Popescu

Hello all, I’m writing this e-mail because I want to propose supporting Internet Explorer 10 and Internet Explorer 11 on 6.x cycle. First of all, it’s known that Internet Explorer 8 and Internet Explorer 9 are still widely used by users, but many of them are currently choosing to update to IE10 and IE11. According to netmarketshare.com (Browsers -> Desktop Share by Version) from a total of 100%, IE10 is used by 6.85% users and IE11 by 16.61% users. It’s true that IE10 is not as popular as the older versions (IE8 - 20.85% and IE9 - 8.89%), but its usage percentage is still significant. Second of all, both versions (IE10 and IE11) have some problems rendering our content sometimes, and you will see that below: IE10 known problems (unfixed) reported on JIRA: 1. XWIKI-10269: Table edit: pressing enter inserts new line in a different table cell 2. XWIKI-10299: The last annotation for a word isn’t displayed on IE10 3. XWIKI-10300: If a text has multiple annotations after removing one of them the text looks like isn’t annotated on IE10 4. XWIKI-10192: The "Username" and "Password" input fields don't have the same size IE11 known problems (unfixed) reported on JIRA: 1. XWIKI-9933: When you press "Alt+C" in IE11 (cancel edition) in edit wiki mode, the wiki session is canceled, but it also appears the "View favourites, feeds and history" option 2. XWIKI-9787: Jump to a page using CTRL+G doesn’t work 3. XWIKI-10192: The "Username" and "Password" input fields don't have the same size Last but not least, since December - January I’ve been testing IE10 and IE11 (smoke tests or full tests) and their biggest problems were with WYSIWYG (you can see that on: XWIKI-9698, XWIKI-10282 and XWIKI-10283). So, what do you think? Andreea

11 years, 4 months

3
4
0 0

[xwiki-devs] [Proposal] Display the extension ID on e.x.o

by Denis Gervalle

Hi devs, I know this have been removed and considered too technical, but I am sure this is a bad idea because: - we display it in EM, so is it less technical there ? - this is the only way to be sure you talk about the same extension, and there are couple of extension with very similar names - it allows finding the right extension for sure (using advance search), which could avoid ambiguities while working remotely with an end user Ok, it should not be the title of the document, but it should be there somewhere to be copy pasted. Here is my +1 to put it back. -- Denis Gervalle SOFTEC sa - CEO

11 years, 4 months

4
3
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs