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

[xwiki-devs] Comment for the display module - velocity independance

by Vincent Massol

Hi Marius, I think the display module should be independent of the Velocity module. I see that the VelocityManager is used in DocumentContentDisplayer but I don't think that's nice. It's used to isolate the velocity context in case velocity is used. I think we can improve this for the following reasons: 1) We don't always need to render content using velocity 2) Code using the displayer shouldn't need to depend on velocity if it doesn't need to I think a better solution would be to have some generic component interface for isolating content (we might already have this) and then have the displayer call "registered" components without knowing them. This would mean that the code isolating the velocity namespace would be located in the velocity module itself for ex (or in a sub module) which makes more sense IMO. WDYT? Thanks -Vincent

13 years, 8 months

2
3
0 0

[xwiki-devs] [vote] Renaming and moving of Curriki Project

by Ludovic Dubost

Hi, As there are now more projects using the Curriki Distribution, in the Curriki mailing list we have voted for the following changes for the Curriki Project: * Rename the main project xwiki-learning-cms * Call the core: xwiki-learning-cms-core: http://svn.xwiki.org/svnroot/xwiki/xwiki-learning-cms/xwiki-learning-cms-co… * Call the curriki specific code : curriki: http://svn.xwiki.org/svnroot/xwiki/xwiki-learning-cms/curriki * Call the planete sankoré specific code : sankore: http://svn.xwiki.org/svnroot/xwiki/xwiki-learning-cms/sankore The curriki 1.8 branches would go into the curriki area, except for the latest branch which would be duplicated in xwiki-kearning-cms-core as the 1.0 branch The 2.x branches would go into xwiki-learning-cms-core We would then publish the sankore core to the repository. As you can see these plans are based on SVN. A separate discussion is undergoing to see if we can easily move to GitHub. In this case we would ask for one or more repositories in the xwiki-contrib area. It's not clear to me in this case if we should use only one or 3 different repositories. I tend to think it should be 3. Finally we would rename curriki.xwiki.org into lcms.xwiki.org. We're asking the goahead from the XWiki commiters to make these changes. Here's my +1 Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

13 years, 8 months

6
8
0 0

[xwiki-devs] [Proposal] Rendering: Move MacroContentParser.getCurrentSyntax() to MacroTransformationContext.getCurrentSyntax()

by Vincent Massol

Hi dev, I've just noticed that we have a MacroContentParser.getCurrentSyntax() API. However there's a more general need of being able to get the current syntax even without using a MacroContentParser (I have this need now in some code). Thus I'm proposing to deprecate (remove?) the MacroContentParser.getCurrentSyntax() method and add a new MacroTransformationContext.getCurrentSyntax() WDYT? Thanks -Vincent

13 years, 8 months

4
3
0 0

[xwiki-devs] [VOTE] Release XWiki Syntax 2.1 as official in Rendering 3.4

by Vincent Massol

Hi devs, I'd like to propose releasing XWiki Syntax 2.1 as official (it's currently experimental) for XWiki Rendering 3.4. Rationale ======== * It has useful expanded support for links and images compared to 2.0 * It's been "experimental" for a long time and people are already using it * It would be nice to release it in the 3.x cycle since it was started in that cycle * That would allow us to start XWiki Syntax 2.2 for the 4.x cycle (see outstanding items at http://tinyurl.com/6pdt5oa ) Migration aspects ============== * I don't think we need to mandate moving to 2.1 for users. They can keep using 2.0 if they want * We should make it the default wiki syntax starting in XE 3.4, leaving 2.0 available by default * I believe there's no conversion issue between 2.0 and 2.1 so it shouldn't be an issue for users wanting to switch. * We could provide a migration script on extensions.xwiki.org for users wanting to convert all their 2.0 pages into 2.1 pages Here's my +1 Thanks -Vincent

13 years, 8 months

9
10
0 0

[xwiki-devs] [VOTE] Improve the database migration implementation on 3.4

by Denis Gervalle

Hi Devs, In order to change the way we compute document ID to reduce the likelihood of a collision, I need to improve and secure our current data migration system. I have started this works late during 3.2, but it since this is an important refactoring, and after discussion on IRC, it have been decide to wait for 3.4 to commit it, so we have a full cycle to have it carefully test. So I would like your approval now to commit this work. The advantages of these changes are: - Ensure that the hibernate store could not be access without having it migrated in the appropriate version for the running platform - Ensure that the hibernate store is left untouched if the migration have not been allowed - Easy addition of migrations, since migrator are now components - Schema and datamigration are done only once and together - One more step in the isolation of the store from XWiki - Secure enough to allow converting document IDs The impact on API and users are: - deprecate xwiki.store.hibernate.updateschema which is enable by default - xwiki.store.migration.databases=all by default (in place of xwiki) since this is the general UC - XWikiMigrationInterface and XWikiMigratorInterface are removed and new component roles DataMigrationManager and DataMigration should be used instead These improvements consist in: - Replace Migrators by DataMigration components - Replace the MigrationManager by a DataMigrationManager component - Put a "hibernate" hint on hibernate stores (in place of default) to allow the hibernate migrator to access a correctly typed store - inject and call the HibernateDataMigrationManager from the stores (and not from XWiki) - Convert data migration like action done during schema update (yes we have some sql updates during schema update) into a LegacyDataMigration producing data version 1 from data version 0 - Join together schema update and data migration on a unique place (schema update were currently done in several places in XWiki and the store) - XWIKI-1859: Do not start migrations on a clean installation of XWiki - XWIKI-2075: Move all databases upgrades and schema updates to XWiki's initialization instead of doing it lazily (partial fix, since it is still hard to have the store initialized has needed) - data migration is moved to the first access to a store (which is still during first request, but the matter is no more here) - XWIKI-2066: Migrator fails to upgrade sub wiki databases, now properly fixed (previous fix was a hack that do not) - no more excessive synchronization required for schema update, but there is still some mandatory document added lazily - clear reporting of access error when migration does not succeed For more, read http://markmail.org/thread/l3dzx7pj32n5qlqd Here is my +1 -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

13 years, 8 months

4
4
0 0

[xwiki-devs] Name of color theme that was bundled in XE 3.3

by Vincent Massol

Hi (Sergiu), I see you've committed Caty's pull requests. Thanks for that it's very nice! :) One little detail: the name of the color theme that was bundled in XE 3.3 Right now it's "XE33Default". I think this is not correct since the colortheme application is not supposed to be linked to XE. We're actually moving it to platform. So I'd rather call it something like "XWiki33Default" with a title of "XWiki 3.3 Default" instead. WDYT? Thanks -Vincent

13 years, 8 months

3
4
0 0

[xwiki-devs] Creating the page with some name suffixed with some number does not get searched?

by mohit gupta

Hi All, I created one page named as Release4 and when i try to search Release4 does not show any results for this page but if i create another page with name ReleaseFour and now search ReleaseFour , it shows the results. *Is it an issue or i am missing some thing here?*

13 years, 8 months

1
0
0 0

[xwiki-devs] How to create sub-space in xwiki?

by mohit gupta

Hi All, i have created a space on xwiki with the name MySpace. Now i want to create one sub space under MySpace with name Releases. When i go MySpace and do add space and give the name of my new sub space i.e Releases . It does not add that space under MySpace but it adds as seperate space together. Is it possible to create sub-space ?

13 years, 8 months

1
0
0 0

[xwiki-devs] Same session is getting associated from separate IE windows while login?

by mohit gupta

Hi All, I do the login with admin credentials in one internet explorer window. Now i open one more seperate IE window and give my xwiki home url i.e http://localhost:8888/myxwiki/ . I see in this second i am directly getting logged in with admin credentials which is not correct. I should see login screen on this second window here. Then i did debugging and found out with both IE windows xwikicontext.getRequest().getSession() returning the same session( basically both sessions are having same session id). As per my understanding session is specific to browser window . so both windows(or request from diffent IE windows) should have different session attached to them. Not getting how come both request are having same session id. Thanks

13 years, 8 months

2
1
0 0

[xwiki-devs] [Proposal] Roadmap for XE 3.4

by Vincent Massol

Hi devs and everyone, Here's a proposal for the XE 3.4 roadmap. The idea is to have a short release focused on stabilization and polishing exclusively. This is meant to be the first of 2 stabilization releases (with XE 3.5). Reminder: XE 3.5 is the last release of the 3.x cycle and after it's released we'll start the 4.x cycle. Dates: ===== 3.4M1: 19 December 3.4RC1: 26 December 3.4Final: 5 January (not putting 2 january since it's just after new eve and people might be a bit tired and not in the mood of releasing ;)) Plan for 3.5: 3.5RC1: 23 January 3.5Final: 30 January Must have: ========= * Finish UI for extension manager - Sergiu - more polishing (js, etc) - support for XAR merges and conflicts - whatever is missing (I'm not sure about its exact status - Sergiu, could you give us a precise status of what's missing?) * Fix bugs and continue improving Extension Manager backend and the XWiki Repository application (XR) - Thomas - Thomas, can you list important stuff to do here? * Finish App with Minutes - Marius - Polishing - New auto title/page name feature - Maris, can you list other things that we need to finish in 3.4? * LDAP Admin UI - Jerome Nice to have: =========== Backend: * LDAP group sync need to test group membership before adding user to group XWIKI-7063 Unassigned * Page creation date should be the date of the installation XWIKI-7058 Unassigned * Accessing a store that is not migrated to the lastest data version should not be allowed XWIKI-7006 Denis Gervalle * Reduce the likelihood of having same (hibernate) document id for different documents XWIKI-6990 Denis Gervalle * When using filesystem attachments with attachment versioning disabled, deleted attachments are duplicated on the hard disk. XWIKI-6951 CalebJamesDeLisle * Deleted attachments duplication in recycle bin while File Storage is on XWIKI-6917 CalebJamesDeLisle * Renaming a page should also rename the title of it XWIKI-6743 Unassigned * Be able to rename a space from the UI XWIKI-6722 Unassigned * Be able to delete a space from the UI XWIKI-6687 Marius Dumitru Florea * Use a predefined Space Template like Dashboard, Livetable when creating a new space XWIKI-6684 Unassigned * Problems displaying the correct attachment version when using a proxy XWIKI-6569 Unassigned * Performance of blog category panel is still not enough XWIKI-6363 Unassigned * Change stylesheet and javascript extension filename when a modification is done on those XWIKI-6073 Unassigned * Auto-create Space.WebHome when creating a page in an underfined space XWIKI-5399 Unassigned Front end: * Add more/all configuration parameters in the wiki administration XWIKI-7066 Unassigned * Unable to add users to a group on IE9 XWIKI-7061 Unassigned * When editing a User Profile category, after saving the changes, preserve the category tab XWIKI-7059 Unassigned * Strange behaviour when pressing back and forward on a page that has 2 WYSIWYG editors displayed XWIKI-7028 Marius Dumitru Florea * Log-in automatically on registration XWIKI-6892 Unassigned * Tree from document index does not expand on IE9 XWIKI-6752 Marius Dumitru Florea * Have an auto-complete for the User and Group visibility inputs for the Message Stream XWIKI-6728 Unassigned * Limit dragable width of textareas in FF4 and Chrome XWIKI-6304 Unassigned * WebSearch should only display spaces with view right XWIKI-6227 Unassigned * Auto-suggest doesn't work for global users XWIKI-6207 Unassigned * New floating action menu hides titles in the content of the page when jumping to an anchor XWIKI-6018 Unassigned * Activity Stream doesn't show Image Profile change XWIKI-5930 Unassigned * Cannot filter using "/" on a Date column in the livetable XWIKI-5889 Unassigned * Better placement of the documentation link XE-1031 Unassigned * Cannot access the object editor for documents with XWikiRights objects on wikis with many users XE-1015 Unassigned * New XWiki Syntax Guide XE-880 Unassigned * Occasionally the livetable fails to load on index pages XE-844 Unassigned * Add option to 'show more entries' on displaying the Activity Stream XE-748 Unassigned Please review the items where your name is indicated to make sure you're planning to implement them! Of course if there are some other items that you're planning to do, make sure to add them to the list. WDYT? Thanks -Vincent

13 years, 8 months

7
22
0 0

[xwiki-devs] First alpha version of the GitHub App

by Ludovic Dubost

Hi devs, As we have moved to GitHub, I've started coding an equivalent of the SVNApp (http://extensions.xwiki.org/xwiki/bin/view/Extension/SVN+Application) for GitHub, which should ease up commiting pages from XWiki to GitHub, and because the GitHub SVN bridge is unfortunately not compatible with SVNKit. The bad news is that it's not a GitApp which seems very difficult to do as it relies on a local clone of the repository which is quite overkill when in an XWiki. The good news is that thanks to the GitHub API and a java wrapper from Eclipse, it seems fully possible to have the same functionnality as the SVNApp. I've made some good progress, as I've been able to check a repository against the Wiki AND I've been able to commit non existant files in an existing repository. The life proof is the commit of the GitHubApp itself which was done with GitHubApp: https://github.com/ldubost/application-githubapp/tree/master/src/main/resou… It's still a prototype as there is a lot of work left. For now every file is commited separately and I've not yet tested updating and other complexities, especially as the GitHub api is not that easy to work with (many times I had no errors but my updates were not showing up. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

13 years, 8 months

3
5
0 0

[xwiki-devs] [Proposal] Move Selenium2 platform PageObjects to platform

by Vincent Massol

Hi devs, I'd like to move Selenium2 PO classes for platform in xwiki-platform. The rationale is that: 1) it belongs to platform 2) it allows us to write functional tests in platform More precisely here's what I propose: * Move current unit test fwk currently in xwiki-platform-test to xwiki-platform-test-unit * Add a new xwiki-platform-test-functional module and move the PO objects + functional test classes in it FTM (in some future we'll move POs for a given module in that module but we're not quite there yet) I'm starting to work on this in few minutes so please let me know ASAP what you think. Thanks -Vincent

13 years, 8 months

4
4
0 0

[xwiki-devs] [VOTE] Add DocumentAccessBridge#getDefaultDocument(DocumentReference)

by Marius Dumitru Florea

Hi devs, The default implementation of DocumentAccessBridge#getDocument(DocumentReference) has been modified a few months ago [1] to return the translated document. As a consequence, currently there's no way to access the default translation of a document from a component without depending on the old core (i.e. without using XWiki.getDocument()). Thus I'm proposing to add: /** * Retrieves the default translation of a document specified by its reference. * * @param documentReference a document reference * @return the default translation of the specified document * @throws Exception when the storage cannot be accessed * @since 3.4M1 */ DocumentModelBridge getDefaultDocument(DocumentReference documentReference) throws Exception; to DocumentAccessBridge. The default implementation will do exactly what DocumentAccessBridge#getDocument(DocumentReference) was doing before [1]. Note that the default translation of a document is important because it is the only one that provides the document objects. So if you want to access the objects of a document you have to do it through the default translation. Thanks, Marius [1] https://github.com/xwiki/xwiki-platform/commit/f1188a7be56600aa975d7ccc747a…

13 years, 8 months

4
4
0 0

[xwiki-devs] brief message

by Ricardo.Julio.Rodriguez.Fernandez＠sergas.es

I know it could be a bit silly to jump into the list after a long silence only of this, but I would like to let you know that I keep following, using and promoting XWiki as much as possible! I've learnt, and keep learning, a lot from this community. Not only about software and collaborative environments. Mainly about how a great working team is created kept growing. Happy Christmas and all the best for 2012! Saúde! Ricardo -- Ricardo Rodríguez Research Management and Promotion Technician Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es ________________________________ Nota: A información contida nesta mensaxe e os seus posibles documentos adxuntos é privada e confidencial e está dirixida únicamente ó seu destinatario/a. Se vostede non é o/a destinatario/a orixinal desta mensaxe, por favor elimínea. A distribución ou copia desta mensaxe non está autorizada. Nota: La información contenida en este mensaje y sus posibles documentos adjuntos es privada y confidencial y está dirigida únicamente a su destinatario/a. Si usted no es el/la destinatario/a original de este mensaje, por favor elimínelo. La distribución o copia de este mensaje no está autorizada. See more languages: http://www.sergas.es/aviso_confidencialidad.htm

13 years, 8 months

2
1
0 0

[xwiki-devs] [Proposal] Write a Distribution Maven Plugin

by Vincent Massol

Hi devs, I'd like to propose to write a Distribution Maven Plugin that would have the following features: * Ability to generate XWiki config files. * Ability to generate a full expanded XWiki Distribution. Here are the steps it will do (since I have a first working version I'm pasting what it currently does): ** Step 1: Expand Jetty resources into the package output directory. ** Step 2: Get the WAR dependencies and expand them in the package output directory. ** Step 3: Copy all JARs dependencies to the expanded WAR directory in WEB-INF/lib ** Step 4: Copy compiled classes in the WEB-INF/Classes directory. This allows the tests to provide custom code, for example to override existing components for the test purpose. As an example the link checker might want to override the HTTP Checker component so that checks are not done over the internet since the tests need to execute in a stable environment to prevent false positives. ** Step 5: Generate and copy config files. ** Step 6: Copy HSQLDB JDBC Driver ** Step 7: Unzip the Colibri Skin ** Step 8: Import specified XAR files into the database * Ability to generate a full zipped XWiki Distribution * Ability to import XARs Use cases: * Simplify the current build (XE, XEM, etc) by using this plugin * Use it to generate custom packaging to write functional tests for platform modules * Allow xwiki developers to easily generate custom distributions by handpicking platform modules + their own modules As mentioned above I've worked on this and I'm going to commit a first working version real soon. My current goal is to write some functional tests for the linkchecker-ui module. ATM I have added a new "package" mojo as part of the packager plugin but I'd like to create a new xwiki-platform-tool-distribution-plugin in the future and deprecate the current packager plugin. Thanks -Vincent

13 years, 8 months

4
4
0 0

[xwiki-devs] Fwd: XWiki Search not happening even after giving him the proper rights|| Adding user to different group by default

by mohit gupta

Just a minor connection in ISSUE2. here it is :- * ISSUE2:-*.As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically.Actually I want to decide the default group name where user will be added by default based on some condition . i am not getting where should i make the change for this. ---------- Forwarded message ---------- From: mohit gupta <motgupta(a)gmail.com> Date: Thu, Dec 22, 2011 at 5:24 PM Subject: XWiki Search not happening even after giving him the proper rights|| Adding user to different group by default To: devs(a)xwiki.org I have two issues when i am trying to integrate my webapplication with XWiki. One is related to not able to search the content even after giving the proper rights and another is when .As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically. I want to add this user to a to a different group say AccentureUserGroup instead of XWikiAllGroup<http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup>. i am not getting where should i make the change for this. Below are the details:- * * *Issue1:- *My intention is if an user belongs to particular organisation and he is just a registered user but not admin user for that organization say Accenture he should be able to only view and search that organization spacevotherwise he should not be able to do any operation (not even search and view) on any other space *What I Did for to achieve above* :- I as admin created AccentureUser and AccentureUserGroup . Now i added AccentureUser under AccentureUserGroup. Also I created the space for this organization with Name AccentureSpace. Lets come to Rights Management. As there are two level of rights i.e at Wiki level and Space level. AT Wiki Level:- I gave only view rights to AccentureUserGroup AT Space Level:- I gave only view rights to AccentureUserGroup for AccentureSpace Now when i log in with AccentureUser credentials, i can see AccentureSpace space on a page just after log in but i am not able to search any content(space or page) for this AccentureSpace . Not Getting Why? Do i need to give any other Right too for search? I would be grateful if somebody can provide some insight about above issues on right management.Already I have gone thru below links but did not get through the issues http://platform.xwiki.org/xwiki/bin/view/Features/RightsManagement right management http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Access+Rights access and rights *ISSUE2:-*.As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically. I want to add this user to a to a different group say AccentureUserGroup instead of XWikiAllGroup<http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup>. i am not getting where should i make the change for this. Posted issue 1 on XwikiUser group also but has not got any reply yet. Looking for quick reply.Thanks in advance.

13 years, 8 months

1
0
0 0

[xwiki-devs] XWiki Search not happening even after giving him the proper rights|| Adding user to different group by default

by mohit gupta

I have two issues when i am trying to integrate my webapplication with XWiki. One is related to not able to search the content even after giving the proper rights and another is when .As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically. I want to add this user to a to a different group say AccentureUserGroup instead of XWikiAllGroup<http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup>. i am not getting where should i make the change for this. Below are the details:- * * *Issue1:- *My intention is if an user belongs to particular organisation and he is just a registered user but not admin user for that organization say Accenture he should be able to only view and search that organization spacevotherwise he should not be able to do any operation (not even search and view) on any other space *What I Did for to achieve above* :- I as admin created AccentureUser and AccentureUserGroup . Now i added AccentureUser under AccentureUserGroup. Also I created the space for this organization with Name AccentureSpace. Lets come to Rights Management. As there are two level of rights i.e at Wiki level and Space level. AT Wiki Level:- I gave only view rights to AccentureUserGroup AT Space Level:- I gave only view rights to AccentureUserGroup for AccentureSpace Now when i log in with AccentureUser credentials, i can see AccentureSpace space on a page just after log in but i am not able to search any content(space or page) for this AccentureSpace . Not Getting Why? Do i need to give any other Right too for search? I would be grateful if somebody can provide some insight about above issues on right management.Already I have gone thru below links but did not get through the issues http://platform.xwiki.org/xwiki/bin/view/Features/RightsManagement right management http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Access+Rights access and rights *ISSUE2:-*.As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically. I want to add this user to a to a different group say AccentureUserGroup instead of XWikiAllGroup<http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup>. i am not getting where should i make the change for this. Posted issue 1 on XwikiUser group also but has not got any reply yet. Looking for quick reply.Thanks in advance.

13 years, 8 months

1
0
0 0

[xwiki-devs] [Vote][Proposal] New Skin/ColorTheme Improvements for XE 3.4

by Ecaterina Moraru (Valica)

Hi, Ludovic suggested we should refresh the Default Color Theme for XE 3.4 with something new. Since (and long before) we dropped support for IE6 and IE7 (XE 3.2) I wanted to add some CSS3 enhancement to our default skin: shadows, gradients, round corners, etc. So this is a good time to make a proposal that integrates some CSS3 (gradients on menus, panels, tabs, buttons, forms; text-shadows; box-shadows; border-radius;) and a new ColorTheme into Colibri skin: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/34Proposal There are 3 directions that can be voted for this proposal: *Var A:* Integrate the proposed Skin improvements and the new ColorTheme into platform Demo at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/WebHome *Var B: *Don't integrate anything in the 3.4 timeframe and wait for a new complete skin in 4.x = Current skin + default ColorTheme (no changes) Demo at http://incubator.myxwiki.org/xwiki/bin/view/Drafts/WebHome *Var C:* Integrate just the new proposed ColorTheme that will replace the current DefaultColorTheme Demo at http://incubator.myxwiki.org/xwiki/bin/view/Standards/WebHome *Important remarks when making a decision:* *Var B* and *Var C *does not involve any changes, problems or advantages from the current Colibri skin. Advantages for *Var A*: - Tested on IE7, IE8, IE9, Opera 11, Chrome 16, Firefox 8, Safari 5 and works beautifully. - Uses CSS3 declarations that makes the skin more nice (gradients, round corners, shades, etc.) Problems for *Var A*: - The existing ColorThemes (from the ColorThemes space and extensions.xwiki.org) will become deprecated for XE 3.4 since the new skin needs shades for the gradients (this means the existing ColorThemes variables will be either used in ways they were not intended or they will not have all the variables declared). See my previous mail about "[Discussion] Problematic ColorTheme extensibility"<http://xwiki.markmail.org/thread/ex6fgou6fl6vjwfr> - The CSS will become even more invalid (right now we have a -moz-border-radius and a word-wrap non valid declarations), but the new code contains 154 declarations for the gradients (covering -moz-linear-gradient, -webkit-gradient, -webkit-linear-gradient, -o-linear-gradient, -ms-linear-gradient, linear-gradient and filter: progid:DXImageTransform.Microsoft.gradient proprietary declarations). The invalidity comes because the proprietary declarations are not yet W3C standard (and will not ever be a standard). The proposed standard W3C declaration (linear-gradient) is not yet supported consistently and correctly by browsers, but when it will become standard we can remove all the other proprietary declarations. Please cast your vote. Thanks, Caty

13 years, 8 months

8
11
0 0

[xwiki-devs] [VOTE] Create new xwiki-platform-messagestream-api and xwiki-platform-messagestream-ui modules

by Vincent Massol

Hi devs, Right now the Message Stream feature is split in several places: * xwiki-platform-messagestream/ for the API * xwiki-platform-user/xwiki-platform-user-ui for the Network tab of the user profile (XWikiUserNetworkSheet.xml) * xwiki-enterprise-ui/, in : ** Activity.xml which contains both the AS and the UI to post user messages ** MessageStreamConfig.xml: the admin page for message stream My proposal is to have instead: xwiki-platform-messagestream/ |_ xwiki-platform-messagestream-api/ |_ xwiki-platform-messagestream-ui/ Where xwiki-platform-messagestream-ui/ will contain: * XWikiUserNetworkSheet.xml as is (moved from xwiki-platform-user/xwiki-platform-user-ui) * MessageStreamConfig.xml as is (moved from xwiki-enterprise-ui/) * Creation of a new page (we need to find a name for it), for example: Main.MessageStream, which will contain the UI to post user messages and which will be included from Main.Activity Here's my +1 If you can think of a better split for Activity.xml please put it forward. Thanks -Vincent

13 years, 8 months

5
6
0 0

[xwiki-devs] [Proposal] Use the XWiki.org JIRA project more

by Vincent Massol

(I sent this mail once but it didn't make it on the list apparently so resending) Hi devs, I'd like to propose that we use the XWiki.org JIRA project more: http://jira.xwiki.org/browse/XWIKIORG The idea is to create issues in it whenever we see stuff to improve on xwiki.org. I'm also proposing to do the following actions: * Modify it in JIRA so that this project doesn't have any Affects and Fix for fields. The idea is to simple have a list of issues and no releases. * Add some documentation on the contribution page on xwiki.org to explain that creating jira issues for stuff to improve on xwiki.org is a way to contribute too * Send an email to the users list asking people to create jira issues for stuff to improve on xwiki.org * Modify the xwiki.org feedback form on xwiki.org to ask users to create jira issues for stuff they'd like to see improved * Move documentation located in JIRA Platform project (and possibly others) to the XWiki.org JIRA project Are you ok about this? Once this is all done I'll send another email to propose to start again the Doc Days (say one per month). Thanks -Vincent

13 years, 8 months

7
10
0 0

Re: [xwiki-devs] How to use WikiWords?

by Hamster

I still can't figure out how to use WikiWords. I have searched with Google on "XWiki +WikiWords", but nothing relevant came up. I have searched the XWiki-site for documentation on how to use WikiWords, but can't find any docs. Does anyone have a clue for me? Thanks! -- View this message in context: http://xwiki.475771.n2.nabble.com/How-to-use-WikiWords-tp7070568p7077791.ht… Sent from the XWiki- Dev mailing list archive at Nabble.com.

13 years, 8 months

3
11
0 0

[xwiki-devs] [VOTE] Create new User Application in platfom (and refactor Admin App)

by Vincent Massol

Hi Devs, Right now the Administration Application includes user profiles pages. I'd like to propose to move them to a new user application in platform: - in xwiki-platform-user/xwiki-platform-user-ui (the reason for this directory structure is because in the future we'll probably have an -api module for User API) - or directly in xwiki-platform-user/ FTM and refactor later on when we have the need for a user -api module The rationale for moving the user profile pages out of the Administration app is the following: * IMO we need to make the Admin app only contain technical pages making up the Admin page (i.e. http://localhost:8080/xwiki/bin/admin/XWiki/XWikiPreferences + the technical pages like ConfigurableClass, etc). * We should move specific admin pages to the extensions that bring them. For example WYSIWYG admin pages should be in the wysiwyg application and not in the administration app. * This will allow us to better document each feature. Right now the user has to know that he has to go to the Admin app to find documentation about user profile (which is missing btw ;)), wysiwyg administration, etc. More specifically here are the pages I'd like to move out in XE 3.4M1: * XWikiUserSheet * XWikiUserProfileSheet * XWikiUserPreferencesSheet * XWikiUserNetworkSheet Here's my +1 Thanks -Vincent

13 years, 8 months

6
8
0 0

[xwiki-devs] [Discussion] Problematic ColorTheme extensibility

by Ecaterina Moraru (Valica)

Hi, Since we introduces ColorThemes in XE 2.0 we've used them constantly, being a great improvement for the cases when we wanted to rapidly change the color variables used. The problem with the ColorThemes is that they contain a limited number of variables. There are places in Colibri where we've recycled and used variables that were not intended to be used there, for example: - Administration's vertical-menu is using $theme.panelCollapsedBackgroundColor (which was intended for the collapsed state of the panels); - Suggest search results is using for it's .resultContainer also $theme.panelCollapsedBackgroundColor; - etc. Also there are some variables in the ColorThemes like $theme.textPrimaryColor and $theme.textSecondaryColor or even $theme.backgroundSecondaryColor that are used quite randomly in the code (all being shades of gray in the default theme). Not knowing exactly what is the purpose and usage of a color is very easy when you create a ColorTheme to chose colors that in practice will not provide enough contrast or that will not look very nice together. Since their release, we've added just 6 new variables (2 for the "Add" menu and 4 for the notifications colors: warning, error, success and info). One of the reason behind not adding new colors was not to confuse the user with a wide range of color variations. The colortheme wizard was great at making it easy for the user to change the 36 variables, but having 50+ variables to set could be a difficult/complex task even when using a Wizard. Although when we created ColorThemes we had in mind that they will be skin independent I don't know if in practice this will be still valid. When we're going to create a new skin for XE it will have a different layout, a different semantic of the variables names and a different color pool need. These needs are not mappable on what we currently have. So I think the ColorThemes should be skin dependent and also version dependent in order to assure that is gonna look the way it was originally intended to look. For example I want to add some CSS3 gradients for the 3.4 Colibri skin, but I don't have enough variables to specify the gradient shades. To solve that I've used non semantically variables combinations like: background-image: -moz-linear-gradient(top, $theme.linkColor 0%, $theme.buttonPrimaryBackgroundColor 100%); background-image: -moz-linear-gradient(top, $theme.pageContentBackgroundColor 0%, $theme.buttonSecondaryBackgroundColor 100%); Even though the combination will work for the ColorTheme defined specially for XE 3.4, this means the other existing ColorThemes will be used in a way they were not designed for (like ColorThemes.Bordo theme, etc.) thus not being as good looking as before when applied on the new skin. The same use case will be for any other skin that we will create for the XE 4.x. IMO you can't assume that any defined colortheme will work "graciously" independent of the skin applied and version used. (they will work but the color mix will be random). So another solution would be add more colors to the ColorTheme. For variation of Colibri this will work, but for a new skin (that maybe will not have 2 sets of menus, or will not have 2 separate colors for the background and the content) all the semantic behind the variables naming will fail. We will end up with variables inside the colortheme that may never be used inside the new skin code and I don't even imagine how the ColorTheme Wizard would look like (a nice idea would be to adjust itself dynamically dependent of the enabled skin). Also I want to know what is your opinion regarding adding new variables. What is the backward compatibility strategy for that? Right now, we have a fallback ColorTheme that provides fallback colors in case the ColorTheme doesn't have those colors set. But this does not assure that installing an "old" red colortheme will look nice with the fallback blue colors. We are not telling the user anywhere that there are missing colors in the installed colortheme and also in the wizard is hard to know what colors are defined and what are the fallback ones (if you know what colors are missing than you can manual define them and you don't need to cover all wizard dialogs in order to find the inconsistencies). So IMO the only solution is to have ColorThemes designed dependent of a skin and a version, with the possibility to let the user manually enhance and reuse old colortheme to work on the new versions. Maybe you have other solutions. Thanks, Caty

13 years, 8 months

2
2
0 0

[xwiki-devs] [Announcement] XWiki Enterprise 3.3 and XWiki Enterprise Manager 3.3 Released

by Sergiu Dumitriu

The XWiki development team is proud to announce the availability of XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager 3.3. Following the goals established for the 3.x cycle, XWiki Enterprise 3.3 delivers the first usable but experimental versions of App Within Minutes and Extension Manager features. The highlights of this release are: * Experimental "App Within Minutes" feature * Improved Extension Manager * Automatic external link checker * Better support for exporting CJK documents as PDF * LDAP user membership improvements * Attachment handling improvements * Debian packages for installing XWiki See the full release notes at http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise33 for more details. -- Sergiu Dumitriu http://purl.org/net/sergiu/

13 years, 8 months

2
1
0 0

[xwiki-devs] [Proposal] Community-sourcing of our compatibility grid

by Vincent Massol

Hi devs, Here's something I'd love to see: The idea is the following: * Allow end users to install the extension and run the tests on their current XWiki Enterprise instance * At the end of the test make the extension publish the result by POSTing the result to a xwiki.org URL. The results should include: ** XE version ** DB version ** DB driver version ** Browser version ** Console logs ** Screenshots taken * Display test results on several places of xwiki.org: ** On a general compatibility page ** On the Installation page for specific Servlet Containers and Databases Note that we need to improve a bit the test suite so that: * All tests create data in a Test space * If a test requires a default page of XE we need to verify it contains what we need before the test starts and if not then mark the test as skipped instead of failing it * Tests work independently of what data already exists in the wiki I've entered it as a jira here: http://jira.xwiki.org/jira/browse/XE-1064 WDYT? Thanks -Vincent

13 years, 9 months

2
1
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