- 05 Aug, 2014 1 commit
-
-
JC Brand authored
-
- 04 Aug, 2014 23 commits
-
-
JC Brand authored
-
JC Brand authored
Update Chinese translation PO file
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
updates #83
-
JC Brand authored
-
JC Brand authored
Conflicts: index.html
-
JC Brand authored
-
JC Brand authored
See: https://github.com/jcbrand/converse.js/issues/196 and: https://github.com/jrburke/requirejs/issues/392 updates #196
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
updates #83
-
JC Brand authored
-
JC Brand authored
updates #83
-
JC Brand authored
-
JC Brand authored
-
- 03 Aug, 2014 6 commits
- 02 Aug, 2014 3 commits
-
-
JC Brand authored
The RosterView view is now an overview of RosterGroup objects. RosterGroup objects each have their own collection of contacts which fall under that group. Additionally, the RosterView has a collection of all contacts. The comparator of RosterContacts is now used to correctly position roster contacts and we therefore no longer need to explicitly sort them afterwards. updates #83 updates #151
-
JC Brand authored
-
JC Brand authored
-
- 01 Aug, 2014 2 commits
-
-
JC Brand authored
-
JC Brand authored
This is because we can no longer assume a one to one mapping between roster contacts and their views. Roster contacts can belong to more than one group, each group needs to show the contact, which means we need a view for each group the contact belongs to. updates #83
-
- 31 Jul, 2014 4 commits
-
-
JC Brand authored
In order to make group values non-distinct, (i.e. buddies can be in multiple groups), we can't assume there's one view per roster item. This means we cannot manage the rosterview as an overview (since it makes this assumption).
-
JC Brand authored
updates #83
-
JC Brand authored
-
JC Brand authored
-
- 30 Jul, 2014 1 commit
-
-
JC Brand authored
updates #83
-