comparison src/browser/public/libervia.css @ 589:a5019e62c3e9 frontends_multi_profiles

browser side: big refactoring to base Libervia on QuickFrontend, first draft: /!\ not finished, partially working and highly instable - add collections module with an OrderedDict like class - SatWebFrontend inherit from QuickApp - general sat_frontends tools.jid module is used - bridge/json methods have moved to json module - UniBox is partially removed (should be totally removed before merge to trunk) - Signals are now register with the generic registerSignal method (which is called mainly in QuickFrontend) - the generic getOrCreateWidget method from QuickWidgetsManager is used instead of Libervia's specific methods - all Widget are now based more or less directly on QuickWidget - with the new QuickWidgetsManager.getWidgets method, it's no more necessary to check all widgets which are instance of a particular class - ChatPanel and related moved to chat module - MicroblogPanel and related moved to blog module - global and overcomplicated send method has been disabled: each class should manage its own sending - for consistency with other frontends, former ContactPanel has been renamed to ContactList and vice versa - for the same reason, ChatPanel has been renamed to Chat - for compatibility with QuickFrontend, a fake profile is used in several places, it is set to C.PROF_KEY_NONE (real profile is managed server side for obvious security reasons) - changed default url for web panel to SàT website, and contact address to generic SàT contact address - ContactList is based on QuickContactList, UI changes are done in update method - bride call (now json module) have been greatly improved, in particular call can be done in the same way as for other frontends (bridge.method_name(arg1, arg2, ..., callback=cb, errback=eb). Blocking method must be called like async methods due to javascript architecture - in bridge calls, a callback can now exists without errback - hard reload on BridgeSignals remote error has been disabled, a better option should be implemented - use of constants where that make sens, some style improvments - avatars are temporarily disabled - lot of code disabled, will be fixed or removed before merge - various other changes, check diff for more details server side: manage remote exception on getEntityData, removed getProfileJid call, added getWaitingConf, added getRoomsSubjects
author Goffi <goffi@goffi.org>
date Sat, 24 Jan 2015 01:45:39 +0100
parents 668bb04e9708
children a099990f77a6
comparison
equal deleted inserted replaced
585:bade589dbd5a 589:a5019e62c3e9
418 width: 100%; 418 width: 100%;
419 height: 100% 419 height: 100%
420 } 420 }
421 /* Contact List */ 421 /* Contact List */
422 422
423 div.contactPanel { 423 div.contactList {
424 width: 100%; 424 width: 100%;
425 /* We want the contact panel to not use all the available height when displayed 425 /* We want the contact panel to not use all the available height when displayed
426 in the unibox panel (grey part), because the dialogs panels (white part) should 426 in the unibox panel (grey part), because the dialogs panels (white part) should
427 still be visible. The setting max-height: fit-content would be appropriate here 427 still be visible. The setting max-height: fit-content would be appropriate here
428 but it doesn't work with firefox 24.0. TODO: check if the current setting works 428 but it doesn't work with firefox 24.0. TODO: check if the current setting works
447 border: 0; 447 border: 0;
448 padding: 0; 448 padding: 0;
449 font-size: large; 449 font-size: large;
450 } 450 }
451 451
452 .groupList { 452 .groupPanel {
453 width: 100%; 453 width: 100%;
454 } 454 }
455 455
456 .groupList tr:first-child td { 456 .groupPanel tr:first-child td {
457 padding-top: 10px; 457 padding-top: 10px;
458 } 458 }
459 459
460 .group { 460 .group {
461 padding: 2px 15px; 461 padding: 2px 15px;