xwiki-devs June 2016

xwiki-devs@xwiki.org

20 participants
51 discussions

[xwiki-devs] [UX] Page templates availability

by Ecaterina Moraru (Valica)

Hi, The Template Provider allows setting the locations where the template must be available. Some applications need/encourage their pages to be located in a particular app location. Currently, if we set such a location for a template, the template will be listed in the "Create Page" step only if the user navigates to that location and clicks on the "Add" button. One behavior could be that all templates are displayed each time the user clicks on 'Add', regardless of the initial location. This would mean splitting the current Location functionality into "Template Visibility" and "Creation location restrictions": - Ideally "Template Visibility" should not be restricted, but we would need to keep this field in order to be backward compatible with the current behavior. - "Creation location restrictions" would indicate if the page needs to be created in a particular location. The user will not be allowed to create somewhere else and be warned by an error message. This mail's purpose is to debate: A. If templates should be visible everywhere or just in a particular location? B. Should we recommend applications to restrict the creation of pages to a particular location? Let me know what you think. Thanks, Caty Related: [1] http://jira.xwiki.org/browse/XWIKI-8759 [2] http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageSketches/HomepageTe…

8 years, 6 months

[xwiki-devs] [contrib][android-authenticator]About Releasing Android App Automatically and Securely

by fitz

Release Android App Automatically and Securely There are mainly two steps: (1) Generate the signed apk (2) Release to the google play store. Generate the signed apk automatically: 1. (Need Help) Generate keystore file Use Command Line: https://developer.android.com/studio/publish/app-signing.html#signing-manua… keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000 Or use Android studio: https://developer.android.com/studio/publish/app-signing.html#release-mode Maybe we should generate a new, secure and stable private key for the future android development and release. WDYT? 2. (Need Help) Define gradle global values: (Gradle user home: /home/hudsonagent/.gradle in jenkins)(http://stackoverflow.com/questions/18328730/how-to-create-a-releas…) To ensure the security of the keystore, we can’t directly put the key_password, key_alias, store_password values in the github source. So where do we define these values? The gradle global properties may be a good choice. First we should define some global properties for all Gradle builds in the USER_HOME/.gradle/gradle.properties. For the jenkins server, GRADLE_USER_HOME = /home/hudsonagent/.gradle. If no gradle.properties file, just create a new file and add the following properties. # android release key username and password RELEASE_STORE_FILE=F:\\xwiki\\AndroidAuthKey.jks RELEASE_STORE_PASSWORD=android RELEASE_KEY_ALIAS=authenticator RELEASE_KEY_PASSWORD=android I have no right to login and access the jenkins agent-1, so could you help me create the global gradle.properties file in /home/hudsonagent/.gradle and correctly set the four properties. Thanks in advance. :) 3. Add the following code to build.gradle if(project.hasProperty("RELEASE_STORE_FILE")) { signingConfigs { release { storeFile file(RELEASE_STORE_FILE) storePassword RELEASE_STORE_PASSWORD keyAlias RELEASE_KEY_ALIAS keyPassword RELEASE_KEY_PASSWORD } } } buildTypes { if(project.hasProperty("RELEASE_STORE_FILE")) { release { signingConfig signingConfigs.release } } } 4. Gradle clean build -> then we can generate app-release.apk signed by the keystore in jenkins. Release automatically in Google play store: 1. (Need Help) Setup for Google API access: Following this link: https://github.com/codepath/android_guides/wiki/Automating-Publishing-to-th…. Set the google api access and download the p12 key file. But I have no permission to configure API access. It shows in the google play console: <http://xwiki.475771.n2.nabble.com/file/n7599946/api_access.png> So could you help me configure the API access? Or maybe should download the p12 key file. Thank you in advance. :) 2. (Need Help) Jenkins plugin Settings: (1) Install the jenkins plugin "Google Play Android Publisher plugin" (2) Add Credentials and import the p12 key file downloaded during the first step of setting up Google API access. <http://xwiki.475771.n2.nabble.com/file/n7599946/add_credentials.png> 3. Add a post-build step to your existing Jenkins project. <http://xwiki.475771.n2.nabble.com/file/n7599946/post_build.png> That’s all I can think of right now. I have tried and generated the release apk in the jenkins server on my local computer. As I have no permission to configure the google play api, so now I haven’t tried the automated release. I don't know if this method is the best for the automated and secure release of the android open source project, but it should be feasible. What do you think? :) Thanks, Fitz -- View this message in context: http://xwiki.475771.n2.nabble.com/contrib-android-authenticator-About-Relea… Sent from the XWiki- Dev mailing list archive at Nabble.com.

8 years, 6 months

[xwiki-devs] Question about User Query with Solr

by fitz

Hi devs, Is there a better way with solr query to fast get all the users (last modified after the date "2016-01-14T15:44:02Z") of the group XWikiAdminGroup ? For this group, http://www.xwiki.org/xwiki/rest/wikis/xwiki/spaces/XWiki/pages/XWikiAdminGr… now I just query with the following method, it's too slow. 1. get all user ids from the group http://www.xwiki.org/xwiki/rest/wikis/xwiki/spaces/XWiki/pages/XWikiAdminGr… <objects> <objectSummary> <headline>XWiki.LudovicDubost</headline> -> (id = XWiki.LudovicDubost) </objectSummary> ... ... </objects> 2. one by one check the user's modified time, if after the date, then add the id "XWiki.LudovicDubost" to the array list. For example: http://www.xwiki.org/xwiki/rest/wikis/xwiki/spaces/XWiki/pages/LudovicDubost <modified>2014-07-28T03:04:44+02:00</modified> but it takes up lots of time for checking the modified date one by one. 3. from the list above getting from the step2, we just get all the ids, but no detail information, we also should request server again to get the user's detail properties one by one! it also costs much time. If the group has 1000 users, step1 needs 1 times http request, step3 needs 1000 times http requests, step3 needs <=1000 times, all steps need 1001-2001 times requests and xml parse. Maybe the step2 is not necessary so that we can reduce half of the time. Therefore, is there a better way to query the last modified users? By the way, now I query all the users modified after the date "2016-01-14T15:44:02Z" in the wikis/xwiki. like this: wiki:xwiki and object:XWiki.XWikiUsers and date:[2016-01-14T15:44:02Z TO *] & number=10000 Query Example: http://www.xwiki.org/xwiki/rest/wikis/query?q=wiki:xwiki%20and%20object:XWi… <http://www.xwiki.org/xwiki/rest/wikis/query?q=wiki:xwiki%20and%20object:XWi…> But I don't know how to query fast the group's users(last modified after the date). Could some one help me? Thanks, Fitz -- View this message in context: http://xwiki.475771.n2.nabble.com/Question-about-User-Query-with-Solr-tp759… Sent from the XWiki- Dev mailing list archive at Nabble.com.

8 years, 6 months

[xwiki-devs] [UX] Application Index

by Ecaterina Moraru (Valica)

Hi, The problem is that the AppBar could be populated with lots of apps that might not be interesting for the user. Currently the AppBar acts like an AppIndex (for the apps that provide the panels.Applications UIX), while some users might expect it to act like a Favorites mechanism (the admin deciding what apps should be promoted there). Also the AppBar is not very scalable: having 50+ apps installed will be hard for an user to scroll in order to find his desired app. Trying to simplify the Appbar by removing apps from it, concludes that users might not be able to know if some apps are installed and available. The administrators have access to EM and AppBar configuration, but normal users don't. So it's normal to have the need of an "Application Index", just like we have for pages, users and wikis. Topics: 1. App Index page location 2. App Index launcher location 1. The first thing we should decide is where we should locate this App Index. Alternatives: 1.1 Main.AppIndex : consistent with Main.AllDocs and Main.UserDirectory, not consistent with WikiManager.WebHome. 1.2 Applications.WebHome: as a new top level space. In theory, other applications could use this space as parent. 1.3 AppWithinMinutes.AppIndex : as part of AWM, but the livetable should be extended to include all the apps UIX. The page will be included on the AWM.WebHome in addition with the ability to Create new AWM apps. 1.4 XWiki.InstalledApplications : as part of EM, but with rights visible for all users, not just Admins. It will list just apps, with the ability to 'Launch/Open/View' an app. 1.4 other? 2. App Index launcher could be placed: 2.1 in the Drawer with the rest of the Indexes 2.2 instead of the AppBar 'More applications' menu, as a link There are several aspects: A. EM lists for admins all the installed extensions, but they cannot see just the 'applications' installed on the wiki and launch them. We could create a filter to list just applications (InstalledApplications) and help the admin manage apps faster. If we were to move administrative actions inside an external AppIndex (outside of EM) it would duplicate/split EM functionality (Launch, Install, Delete, Add/Create, etc.) B. AWM allows you to create apps. For a simple user, he might not see the difference between what apps are created with AWM and which are not, and why should he care. For an user, an application is just an application. If we don't chooses 1.3 than the user might be confused why some apps are listed in AWM.WebHome, while others/all are listed in an external AppIndex (outside of AWM). C. If we transform AppBar into a Favorites, then we will need to move the UIXP to the Application Index. It's a bit strange that we are considering using a panel dedicated UIXP as a simple 'application descriptor'. There are many things to consider since AppBar, AWM and EM share applications definitions and we might want to remove duplication, but still allow both admins and users have access to information about apps. Let me know what you think. Thanks, Caty Related issues: - "Simplify the Appbar by removing some apps" http://jira.xwiki.org/browse/XWIKI-13433 - "Create an Application Index" http://jira.xwiki.org/browse/XWIKI-11423 - "Better differenciate the notion of Application inside XWiki" http://jira.xwiki.org/browse/XWIKI-7924

8 years, 6 months

[xwiki-devs] "Project" extension type in http://extensions.xwiki.org

by Thomas Mortagne

Hi xwikiers, I just introduced a "Project" extension type on http://extensions.xwiki.org. I needed a place to put a few words about OpenId Connect in general, the goal of the project, the various modules and what is common between them, etc. It's also the parent space of the actual extensions. It does not shows up in Extension Manager of course. See http://extensions.xwiki.org/xwiki/bin/view/Extension/OpenID+Connect/ WDYT ? -- Thomas Mortagne

8 years, 6 months

[xwiki-devs] [ANN] Contrib Parent 7.4-3 has been releases

by Thomas Mortagne

I just released a new version of the Contrib parent poms which add support for automatic close and release on Nexus repository. See https://github.com/xwiki-contrib/parent. -- Thomas Mortagne

8 years, 6 months

[xwiki-devs] [UX][Proposal] Support panel

by Ecaterina Moraru (Valica)

Hi, This is a follow up for the governance changes mail, see http://markmail.org/message/mcbcvd4i5cgoebh5 This proposal aims to add a support panel inside XWiki Enterprise: http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageSketches/HomepageSu… There are 3 variants you can vote on: A, B and C. Let me know what you think. Thanks, Caty

8 years, 6 months

[xwiki-devs] [UX][Proposal] Simplifying the Homepage (content + left panels)

by Ecaterina Moraru (Valica)

Hi, This is a follow up on the initial brainstorming done, see http://markmail.org/message/hbuhhkxcjodtfxwi This proposal aims to replace the current Dashboard with a more simple wiki content page: http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageSketches/HomepageLa… I would like you to vote on the 2 versions of left panels: 1. AppBar + Pages 2. AppBar Also provide feedback on the content. I've added the content on this page: http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageSketches/HomepagePr… in order for you to see how it behaves with the editors. [1] The objective was to have an easy to edit content, very close to what we have in view mode. Let me know what you think. Thanks, Caty [1] Since we don't have CKEditor installed on design wiki, see how it would looks like http://design.xwiki.org/xwiki/bin/download/Proposal/HomepageSketches/WebHom…

8 years, 6 months

[xwiki-devs] [UX][Proposal] Homepage Tour

by Alexandru Cotiuga

Hello, This proposal is about implementing a tour guide for the Homepage of the main wiki. This is the prototype: http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageTour/Prototype/ Feedback is welcomed. Thanks, Alex and Caty

8 years, 6 months

[xwiki-devs] [XWiki Day] BFD#106

by Alexandru Cotiuga

Hi devs, This Thursday is BFD#106: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays Our current status for the 1 year period is 136 bugs behind. See: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10000#Created-vs-R… Here's the BFD#106 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13616 Happy Bug Fixing Day! Thanks, Alex

8 years, 6 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs June 2016