Hi guys.
I am starting this thread to talk about UI conventions that we should
recommend to every developer who want to write an application in XWiki.
Currently, we have some standards (see
http://platform.xwiki.org/xwiki/bin/view/DevGuide/FrontendResources) and we
need to update this documentation since it is still speaking about
PrototypeJS and Bootstrap is not even mentioned. I think it is the time to
think about what these conventions should be now.
With Vincent and Caty, we have thought …
[View More]about it and our ideas are written
there: http://design.xwiki.org/xwiki/bin/view/Proposal/UIStandards
I let you read this design page and express your ideas. I need your opinion
to know how I should implement the (color) theme application for Flamingo.
Thanks,
Guillaume
[View Less]
Hi everyone,
I'm working with an initiative similar to Google Summer of Code, called Semester of Code, and I think it would be great to have students work on XWiki. Below is more detailed information, but basically its like GSoC, except students are involved as part of their courses or industrial placements, so receive academic credit rather than money for their work.
Hopefully this is of interest to the XWiki community!
If any questions aren't answered by the FAQ[1] or invitation below, …
[View More]feel free to ask.
All the best,
- Scott
~~~
The VALS Semester of Code [1] project is working with European universities and FOSS communities to give students real-world experience working in open source software projects while receiving academic credit. The benefit to your projects will be valuable and hopefully ongoing contributions. VALS will also benefit the wider sector by helping to produce graduates with the skills and experience needed to engage with open development.
Our first Semester of Code will involve approximately 75 student placements, starting in September. We would like to invite your organisation to participate in this pilot by offering mentored placements within your projects.
If you have participated in Google Summer of Code before, you will find our process similar; we will seek placements for student projects, and will use the a system similar to Google's Melange platform to manage placements. However, VALS differs from Summer of Code in that instead of receiving money for their participation, students will receive academic credit. For this reason the mentors from your project will need to liaise with the student's academic tutor. The VALS project will support this process to ensure it runs as smoothly as possible. We also ensure the admin overhead is minimal.
The VALS initiative is a partnership of European universities and SMEs who have been working for several months to plan the pilot of Semester of Code, which will run during the next academic year. We have now reached the stage where we are signing up FOSS projects who are willing to provide mentors. We have already seen interest from smaller, single-company projects to larger software foundations, and would like to see more.
If you'd be willing to provide one or more mentored projects, we’d love to talk to you about joining Semester of Code. In return, you’ll get an enthusiastic student providing a valuable contribution to your project. The VALS team will be on hand throughout the project to answer any questions and help unblock communication issues between mentors, students and academic supervisors.
To join in the Semester of Code or to simply find out more you can email mark.johnson(a)it.ox.ac.uk, or you can sign up to our mailing list directly by using the web form [1].
More detail about the Semester of Code are available on our FAQ page [2]. If you have any other questions, don’t hesitate to ask on the mailing list, and one of the VALS team will get back to you!
1: https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=VALS-SOC&A=1
2: http://semesterofcode.com/?p=22
[View Less]
Hello,
i have an idea concerning the icons of base skin colibri or others, we
should integrate "Entypo" on the skin ans delete all image icons, the
advantage is :
1- we win the chargement time of pages
2- reduce the number of code lines in the code.
3- we can add, edit , put color and change the sise of this icons
4- the skin of this icons are in flat design and we can put it in any form
5- its free for any users
for more information http://www.entypo.com/
wordpress have just integrate this solution
Yacine
Hi devs (Thomas),
I’ve noticed Thomas mentioned the following in the mail for 6.1:
“
Finally a new loading screen with
progress displayed during XWiki initialization has been introduced and
the initialization speed itself has also been improved.
“
I’ve found that intuitively the loading speed of 6.1 seemed slower than before so I did a quick measurement between 5.4.4 and 6.1.
* On 5.4.4
** Time for the webapp to be ready: 14s
** Time to load the home page after the webapp …
[View More]is ready: 8.7s
* On 6.1
** Time for the webapp to be ready: 16s
** Time to load the home page after the webapp is ready: 12.60s
So it seems we got worse and not better.
Ofc this would need more measurements.
Would be nice Thomas if you could investigate this as part of your performance improvements to see what we’re doing now that takes longer than before.
Thanks
-Vincent
[View Less]
The XWiki development team is proud to announce the availability of XWiki 6.1.
A lot of work has been done for the new Flamingo skin and we hope to
make it the default in 6.2.
This version also comes with many improvements but also introduce many
new APIs and tools for developers like the integration of LESS
preprocessor, a new authorization API taking care of the context and
its associated script service, a new experimental Mail API, the
support of grouped and asynchronous jobs in default …
[View More]job module
executor, the possibility to log from any script, a new converter to
make easier to manipulate XDOM in Velocity, and many others.
The memory used in wikis with lots of documents like
http://myxwiki.org has also been reduced a lot (around 40% in
http://myxwiki.org for example). Finally a new loading screen with
progress displayed during XWiki initialization has been introduced and
the initialization speed itself has also been improved.
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/ReleaseNotesXWiki61
Thanks
-The XWiki dev team
[View Less]
Hi devs,
After brainstorming offline with several XWiki committers (devs from XWiki SAS mostly) here’s a proposal for the 6.2 roadmap:
Content
=======
* Guillaume with help from Caty: Make Flamingo production-ready and the default skin in XE. Specifically this means;
- Finish the AppBar implementation (with proper icons)
- Polishing everywhere
- Ensure it works fine on mobile devices
- Finish Theme Editor
- Investigation about UI standards (theme variables , css classes, html/macros, js) (…
[View More]some thoughts there: http://design.xwiki.org/xwiki/bin/view/Proposal/UIStandards)
* Thomas: Continue on improving page loading times and performances in general as much as possible in the time frame.
* Marius: Finish File Manager + javascript framework evaluation/proposal (propose angularJS with LT in angular + treeview, etc)
* Denis: Are you going to work on finishing signed scripts?
* Edy: Investigate Activity Stream v2. Goal: take the occasion of the rewrite to
- Make it performant
- Catch up and leap over the competition in term of features/usability ;)
- Need find all use cases and gather feedback from everyone
* Edy: Implement as many JIRA issues as possible from the list below, starting with the top one and going down:
- Support 2 roles for users for app within minutes: application creator and data creator XWIKI-8757
- Extension Manager add extension search should suggest only compatible versions XWIKI-9920
- New widget that extends the Suggest widget with the option to pick multiple values XWIKI-8097
- Welcome block is not easily editable XE-1389
- Watchlist activity shouldn't add a version to the page XWIKI-10332
- Wrong rendering of annotations for documents with sheets XWIKI-6328
- Delete user removal from groups is not scalable and is a potential security issue (for me the feature should be at least deactivatable) XWIKI-9641
- Importing documents with Office Importer will always generate pages in syntax 2.0 XWIKI-9074
- Unpublished blog posts are displayed in the Activity Stream XWIKI-10425
- "Current wiki" wiki macros not available in the macros list in wysiwyg in path based multiwiki XWIKI-7739
- Add the possibility in AppWithinMinutes livetables settings to select a default sort on a column XWIKI-9659
- Add a reload button for changing the CAPTCHA message at registration XWIKI-9879
- Show date and time of the install and user who installed for an installed extension XWIKI-10027
- User Directory should be configurable globally XWIKI-9170
- Creating wiki page containing / character XE-688
- The default value of a date field should be empty or today, not the date when the class has been created XWIKI-10296
- The links to pages from the ToC of the watchlist notification message don't work on Outlook XWIKI-10500
- Hard to understand which is the default value for Profile's Preferences entries (edit/view mode) XWIKI-7715
- Add an explanation next to the fields in user profile XWIKI-6307
- Add an event in the Activity Stream for when a subwiki is created or deleted XWIKI-10280
- Allow to force the installation of an extension even if dependencies are not satisfied XWIKI-9827
- Access all page information in one rest request XWIKI-9135
- Allow to "send page by email" to a group (sold to AFCEN client) XE-1403
- Allow a default space to be specified for a template provider, which will automatically create the document in that space XWIKI-8759
- Renaming a page changes the creation date XWIKI-9425
- xwiki.cfg & xwiki.properties merging XWIKI-9831
- Empty groups can still have hidden rights applied, but not displayed in the UI XWIKI-9681
- Jump to a page using Ctrl+G doesn't work XWIKI-9787
- Top Active Contributors has empty values when the current user is local XWIKI-9991
- The default value of a date field should be empty or today, not the date when the class has been created XE-1388
- The User Directory does not display html for TextArea properties XWIKI-10149
- Page Blog.CategorySheet missing translation keys XWIKI-6540
- The "Username" and "Password" input fields don't have the same size XWIKI-10192
- Cannot restore document translations from recycle bin XWIKI-9567
Note that others can also help Edy on this :)
* Caty: Usability recording analysis and conclusions (Caty made some interviews with newcomers to XWiki with some scenarios to see what we should improve) + new icon set (vectorial) investigation (needed for AppBar) + UI standards (see above) + maybe help Edy (time permitting) on the AS investigation
* Lyes: Implement sending of mail invitations in Meeting Manager using the new Mail Sender API + Publish the Hierarchy Macro he’s been working on + work on Collaborative Apps
Dates
=====
(Taking into account the XWiki SAS seminar in July)
- 6.2M1: 4th Aug
- 6.2M2: 18th Aug
- 6.2RC1: 1 sep
- 6.2Final: 15 sep
Please add the stuff you wish to work on if you’re not in the list above and with to commit to working on something for the 6.2 release! :)
WDYT?
Thanks
-Vincent
[View Less]
Hi devs,
As you know we are working on a new Flamingo skin [1] that will replace the
current default Colibri skin.
The purpose of this feedback request targets:
- Feedback in general about Skins use cases we need to make sure we follow
each time we develop a new skin;
- Raising new use cases related to our usage of Boostrap framework [2];
- Mentioning annoying customization problems found on custom skin developed
on top of XWiki that we might have a chance to fix in this new skin;
- Any other …
[View More]feedback related to Colibri, Flamingo or XWiki skins.
I will gather the conclusions on this page
http://design.xwiki.org/xwiki/bin/edit/Proposal/SkinsUseCases61
I've added some use cases, but please help me expand them and add more in
order to make sure we won't forget something and that we are covering the
important aspects.
Thanks,
Caty
[1] http://design.xwiki.org/xwiki/bin/view/Improvements/Skin4x
[2] http://getbootstrap.com/
[View Less]
Hi devs,
We had this discussion in the past but it wasn’t officially recorded on dev.xwiki.org and I can’t find the thread.
The question is to decide which docs should be hidden by default.
My take:
- all pages not containing user content. This includes application pages (for ex Dashboard.WebHome, Blog.WebHome, etc)
Rationale:
- Separate apps from content
-- Spaces list should only list spaces having pages with user content
-- Apps should be found in the Applications panel (or in the Apps …
[View More]directory in the future)
Side note:
- search suggest and search should return results for app names
WDYT?
The reason I’m raising this is because while developing the new Home Page app (http://jira.xwiki.org/browse/XWIKI-10586) I just found that the user could not select the Dashboard.WebHome page because it’s a hidden page…
Thus I have 2 options:
1) Unhide it, but this means the “Dashboard” will become visible in the spaces list
2) Change the UI I have at http://jira.xwiki.org/secure/attachment/28082/step2.png in order to allow the user to choose from both a list of apps or a list of pages. I could even show the apps with their icons, using the “org.xwiki.platform.panels.Applications” UIX.
Option 2 seems ok but it’ll make the UI a bit more complex. I could offer linking to apps by default and have the linking to page behind an “Advanced” button...
Any other idea?
Thanks
-Vincent
[View Less]