xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [UX][Proposal] Application: Meetings

by Ionut Maxim

Good day, One of the objectives of 6.0 is to review the existing applications on extensions.xwiki.org, improve them and see how they would integrate in the upcoming Flamingo skin (while also considering improvements suggestions). This mail covers the Flamingo integration for the Meetings Application<http://design.xwiki.org/xwiki/bin/view/Proposal/MeetingApplication>. You are welcomed to review the proposal at: <http://design.xwiki.org/xwiki/bin/view/Proposal/MeetingApplicationDesignII> *http://design.xwiki.org/xwiki/bin/view/Proposal/MeetingApplicationDesignII* Any feedback is welcomed. Thank you, have a good day! -- Ionut MAXIM - - - - - - - - - - - - - - - - - - - - - - - - Web Designer @ XWiki SAS - - - - - - - - - - - - - - - - - - - - - - - - +40755120711 | www.xwiki.com

10 years, 8 months

[xwiki-devs] [Proposal] Use HTML5 in Flamingo

by Guillaume "Louis-Marie" Delhumeau

(There is already a JIRA issue about this topic, see http://jira.xwiki.org/browse/XWIKI-7552 ). The new skin, Flamingo, uses the Bootstrap Framework, which is designed to be used with HTML5. For example, the drop down buttons [1] use the attributes "data-*" that was introduced recently and that are not valid in XHTML 1.0 Strict. Since HTML5 is becoming the new standard, I think it's time to switch to HTML5, at least for Flamingo. With the help of Thomas, I have already added an HTML5 validator in our build tools, based on validator.nu [2]. In the future, we need to change the enterprise tests suite to use this validator and the flamingo skin. ------------------------- What are the blockers ? ------------------------- ----- Meta tags ----- In Colibri headers, we used to define some meta tags used by some javascript components. These tags are: - <meta name="document" content="Main.WebHome"/> - <meta name="wiki" content="xwiki"/> - ... and so on. In my opinion, they are useless, because we also defines some variables: - XWiki.currentWiki = "xwiki"; - XWiki.currentSpace = "Main"; - XWiki.currentPage = "WebHome"; - ... and so on. The problem is: these tags are not valid in HTML5 because the specification mentions that custom meta names should be registered on http://wiki.whatwg.org/wiki/MetaExtensions. See http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#… . Other problem: if we simply remove them, we will break some javascript codes. ----- Internet Explorer meta tag ----- Bootstrap defines the following meta-tag: <meta http-equiv="X-UA-Compatible" content="IE=edge"> It is used to prevent Internet Explorer from using the compatibility mode (which is the default setting on intranet sites). As before, this meta tag is not valid. It is interresting to notice that even the bootstrap site is not valid, because of that. In my opinion, we need this meta-tag and we should ignore this HTML5 violation. ----- Use HTML5 or XHTML5? ----- XHTML5 is only a subset of HTML5 so that it is XML compliant. If we want to use it, we need to change the MIME type of our pages to "application/xhtml+xml" or "application/xml" [3]. But then, the browser is not error-tolerant anymore (I have only tested with Firefox and I hit the issue). ----- Update HTMLCleaner ----- HTML Cleaner generates this code: <img src="..."></img> which is not valid. ------------------------ Proposal ------------------------ 1. Break the javascript compatibility and remove invalid <meta> tags, except the Internet Explorer specific one. 2. Update the HTML Cleaner. 3. Use HTML5 to avoid the XML specific problems. We can change this in the future. 4. Do not touch the XWiki Rendering code because it generates XHTML, which is still valid in HTML5 [4]. Same for the WYSIWYG editor. 5. Update the enterprise test suite to also tests pages with the flamingo and the new HTML5 validator. WDYT? Louis-Marie ---------------------- Links ---------------------- [1] http://getbootstrap.com/components/#btn-dropdowns [2] http://jira.xwiki.org/browse/XWIKI-10249 [3] http://en.wikipedia.org/wiki/HTML5#XHTML5_.28XML-serialized_HTML5.29 [4] http://en.wikipedia.org/wiki/Polyglot_markup

10 years, 8 months

[xwiki-devs] Introduce a dependency on xwiki-commons-context into xwiki-rendering-api

by Denis Gervalle

Hi devs, In order to manage authorization access based on the signature of scripts, I need to have better knowledge on which rendering is being processed at any moment. The rendering is the one who knows the better the current rendering status, so it is also the best place to feed the ExecutionContext with the TransformationContext and the MacroTransformationContext. Therefore, I would like to introduce a dependency on xwiki-commons-context into xwiki-rendering-api. Since xwiki-commons-context does not have any transitive dependencies, and is part of commons, it should not be an issue. This is not a proposal to remove the current usage of the rendering contexts, it will not impose existing user of the rendering project to embrace the EC at all. If nobody complains, I am starting working on this now, so please comment ASAP if you are against. Thanks -- Denis Gervalle SOFTEC sa - CEO

10 years, 9 months

[xwiki-devs] [Proposal] Location of ApplicationResources.properties in the corresponding project/jar

by Clemens Klein-Robbenhaar

Hi, as I have been pointed to in chat by Vincent, it is possible to place ApplicationResources*.properties files containing translation keys in the src/main/resources directory of any maven "jar"-packaged project and get them used as translations, instead of adding keys to the xwiki-platform-oldcore/src/main/resources/ApplicationResources*.properties This is already documented as a "best practice" for application development: http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra… However it is missing for the platform development practices, so I would have missed it if not been pointed to explicitly. If nobody objects, I would like to add a line recommending this at e.g. http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HTransla… Or are there any reasons against this practice / or is there a better one? Clemens

10 years, 9 months

[xwiki-devs] Compiling Error on RealTime Wiki Editor

by Lawson Long

Hi, I tried to compile the project but there are error messages shown as follows: [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] XWiki Platform - Realtime - Parent POM ............ SUCCESS [0.251s] [INFO] XWiki Platform - Realtime - Editor - Parent POM ... SUCCESS [0.110s] [INFO] XWiki Platform - Realtime - Editor - GWT Client ... FAILURE [10.361s] [INFO] XWiki Platform - Realtime - Editor - GWT Server ... SKIPPED [INFO] XWiki Platform - Realtime - Editor - User Interface SKIPPED [INFO] XWiki Platform - Realtime - Editor - GWT Client And Server SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 11.948s [INFO] Finished at: Thu Apr 10 11:10:46 EDT 2014 [INFO] Final Memory: 29M/236M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.6.0:compile (default) on project xwiki-platform-realtime-editor-client: Command [[ [ERROR] C:\Program Files\Java\jdk1.7.0_45\jre\bin\java -Xmx512m -classpath C:\Users\Long\xwiki-platform-realtime-master\xwiki-platform-realt ime-editor\xwiki-platform-realtime-editor-client\target\classes;C:\Users\Long\xwiki-platform-realtime-master\xwiki-platform-realtime-editor\ xwiki-platform-realtime-editor-client\src\main\java;C:\Users\Long\xwiki-platform-realtime-master\xwiki-platform-realtime-editor\xwiki-platfo rm-realtime-editor-client\target\generated-sources\gwt;C:\Users\Long\.m2\repository\org\xwiki\commons\xwiki-commons-component-api\5.4.3\xwik i-commons-component-api-5.4.3.jar;C:\Users\Long\.m2\repository\org\xwiki\commons\xwiki-commons-stability\5.4.3\xwiki-commons-stability-5.4.3 .jar;C:\Users\Long\.m2\repository\org\xwiki\commons\xwiki-commons-text\5.4.3\xwiki-commons-text-5.4.3.jar;C:\Users\Long\.m2\repository\org\a pache\commons\commons-lang3\3.2\commons-lang3-3.2.jar;C:\Users\Long\.m2\repository\org\slf4j\slf4j-api\1.7.5\slf4j-api-1.7.5.jar;C:\Users\Lo ng\.m2\repository\javax\inject\javax.inject\1\javax.inject-1.jar;C:\Users\Long\.m2\repository\org\xwiki\platform\xwiki-platform-gwt-user\5.4 .1\xwiki-platform-gwt-user-5.4.1.jar;C:\Users\Long\.m2\repository\org\xwiki\platform\xwiki-platform-gwt-dom\5.4.1\xwiki-platform-gwt-dom-5.4 .1.jar;C:\Users\Long\.m2\repository\com\google\gwt\gwt-user\2.6.0\gwt-user-2.6.0.jar;C:\Users\Long\.m2\repository\javax\validation\validatio n-api\1.0.0.GA \validation-api-1.0.0.GA.jar;C:\Users\Long\.m2\repository\javax\validation\validation-api\ 1.0.0.GA\validation-api-1.0.0.GA-sou rces.jar;C:\Users\Long\.m2\repository\org\json\json\20090211\json-20090211.jar;C:\Users\Long\.m2\repository\com\google\gwt\gwt-user\2.6.0\gw t-user-2.6.0.jar;C:\Users\Long\.m2\repository\com\google\gwt\gwt-dev\2.6.0\gwt-dev-2.6.0.jar com.google.gwt.dev.Compiler -logLevel INFO -sty le PRETTY -war C:\Users\Long\xwiki-platform-realtime-master\xwiki-platform-realtime-editor\xwiki-platform-realtime-editor-client\target\gwt- output\gwt -localWorkers 4 -XnoclassMetadata -XnocheckCasts -XfragmentCount -1 -sourceLevel auto -gen C:\Users\Long\xwiki-platform-realtime- master\xwiki-platform-realtime-editor\xwiki-platform-realtime-editor-client\target\.generated fr.loria.score.Rt [ERROR] ]] failed with status 1 [ERROR] -> [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 :xwiki-platform-realtime-editor-client ------------------------------------------------------------------------ My directory is in C:\Users\Long\ Does any one knows how to solve this problem? The editor is in the following link: http://extensions.xwiki.org/xwiki/bin/view/Extension/RealTime+Wiki+Editor

10 years, 9 months

[xwiki-devs] [ANN] XWiki 6.0 Release Candidate 1 released

by Thomas Mortagne

The XWiki development team is proud to announce the availability of XWiki 6.0 Release Candidate 1. First and hopefully last release candidate before 6.0 final. This release contain mostly improvements on Distribution Wyzard and new experimental Flamingo skin. 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/ReleaseNotesXWiki60RC1 Thanks -The XWiki dev team

10 years, 9 months

[xwiki-devs] [Proposal] Hidden wikis & template wikis

by Guillaume "Louis-Marie" Delhumeau

Hi devs. In the coming 5.3 milestone 2, all wikis are displayed in the Wiki Index, including the templates, which was not the case before. >From the user point of view, maybe these templates should not be listed in the Wiki Index. But on the other hand, if you want to see a template, you will not be able to access through the wiki index. We also have introduced the "hidden" flag for wikis (in the WikiDescriptor, not in the UI yet). If we consider template wikis are "technical" wikis, we may use this flag to hide them. Then, in the Wiki Index, we don't care if a wiki is a template or not, we only care about the "hidden" flag. If the user does not want to see the templates in the list, she can mark them as hidden, exactly as we do for documents. But what about the template list in the wiki creation wizard? Should we list all templates, or only the visible ones? My proposition: - all wikis are visible though the wiki index (template or not). - if we want to hide templates to the users, we use the hidden flag in the wiki descriptor. - in the wiki creation wizard, we display all the templates, even these which are tagged as hidden. WDYT? Thanks, Louis-Marie

10 years, 9 months

[xwiki-devs] [Proposal] Active Installs v2

by vincent＠massol.net

Hi devs, I’d like to propose to implement version 2 of Active Installs: http://design.xwiki.org/xwiki/bin/view/Proposal/ActiveInstalls2 The main goal of Active Installs 2 is the ability to graph installs over time. Please make sure to read the backward compat section at the end. Let me know what you think. Thanks -Vincent

10 years, 9 months

[xwiki-devs] [UX][Proposal] Application: Forum

by Ecaterina Moraru (Valica)

Hi, One of the objectives of 6.0 is to review the existing applications on extensions.xwiki.org, improve them and see how they would integrate in the new Flamingo skin (while also making improvements suggestions). This mail covers the Flamingo integration for the Forum Application. You can see the proposal at: http://design.xwiki.org/xwiki/bin/view/Proposal/ForumApplicationDesign Any feedback is welcomed. Thanks, Caty

10 years, 9 months

[xwiki-devs] [ANN] XWiki 5.4.4 released

by Guillaume "Louis-Marie" Delhumeau

The XWiki development team is proud to announce the availability of XWiki 5.4.4. This is a bugfix release, with some improvements in the wiki creation. 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/ReleaseNotesXWiki544 Thanks -The XWiki dev team

10 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs