summaryrefslogtreecommitdiffstats
path: root/client/components/main/layouts.js
Commit message (Collapse)AuthorAgeFilesLines
* Fix stupid error 💥🗯💣🕳💢☠ppoulard2018-07-031-1/+1
|
* Fix QAppoulard2018-07-031-2/+2
|
* Adding SSO CAS to Wekanppoulard2018-07-031-0/+17
|
* Fix lint errors related to language namesGhassen Rjab2018-02-261-4/+8
|
* Fix Igbo language at menu.Lauri Ojansivu2018-01-281-1/+1
|
* Fix: Frequent Subscriptions problem that make Excessive CPU usage.Lauri Ojansivu2017-11-291-4/+0
| | | | Thanks to mfshiu ! Closes #1096, Closes wekan/wekan-mongodb#2
* Add Breton labelGhassen Rjab2017-06-191-1/+1
|
* Sort available languages by their translated namesGhassen Rjab2017-06-181-3/+11
|
* Admin panel:lkisme2017-02-241-0/+2
| | | | | | | Only invited user can register in strict mode, Set mail server in admin panel, Switch strict mode in admin panel, Invite people to system in admin panel
* add: use user preferred lang for user form, and allow selectingfloatinghotpot2015-12-071-0/+33
|
* Enforce a consistent ES6 coding styleMaxime Quandalle2015-09-031-8/+8
| | | | | | | | | Replace the old (and broken) jshint + jscsrc by eslint and configure it to support some of the ES6 features. The command `eslint` currently has one error which is a bug that was discovered by its static analysis and should be fixed (usage of a dead object).
* Implement a modal systemMaxime Quandalle2015-08-261-3/+11
| | | | | | | | | | | | | | I decided to create my own and not to use a community package, because 1. it's straightforward 2. it's better integrated with our others libs such as EscapeActions 3. monitoring third-party packages evolutions (eg, CSS changes) is a lot of work. This is basically the same rationale than for our other generic UI components such as the Popup/Popover. This commit also slightly modify the general layout to remove unnecessary wrapper DOM nodes.
* Start the migration from iron-router to flow-routerMaxime Quandalle2015-08-231-0/+5
Motivations: * Iron-Router foces us to use Tracker.nonreactive black magic in order to avoid un-necessary re-renders; * There is a community consensus (supported by some MDG members) that the flow-router API is easier to reason about; * The useraccounts now supports flow router (that was a blocking element when I considered the switch ~3months ago) On the server we use the Picker router, as encouraged by the Kadira team (which develop both Flow and Picker routers). In the current state of things there are some bugs related to the missing Loading architecure. Previously onRendered callback where always called when the data the component needed was available, now we have to handle this ourselves, which we will in a following commit.