**** BEGIN LOGGING AT Tue Mar 18 02:59:59 2014 Mar 18 08:20:48 morning Mar 18 10:19:43 morning Mar 18 13:36:25 morning Mar 18 13:37:14 morphis: I was on a little trip this weekend, but I begun thinking about the WindowManager/CardView merge (at least mostly merged) Mar 18 13:38:18 Tofe: sounds good :) Mar 18 13:38:57 My thinking was to minimze the role of WindowManager, making it only fill lists of cards, overlays and dashboards (as ListModels), which would then be used by the CardView. All the maximize, fullscreen, card stuff would be moved to a "new" Cardview object Mar 18 13:39:49 oh, and also we would only store directly "window" objects in these lists. The wrapper would go to "userData" property. Mar 18 13:40:34 I still have to see if this list thingy is a good or if I'll fall back to sending the new object via signals Mar 18 13:40:41 good idea* Mar 18 13:41:27 I don't want to have to many lists, one model with the list of cards should be all we need Mar 18 13:43:49 right Mar 18 13:44:00 that would reduce the overhead really Mar 18 13:47:53 I'm a bit hesitant about the dashboard and overlay lists, but I'll begin with them, and if I see they really are useless I'll throw them away Mar 18 13:48:48 However I like the idea of having a model list of card windows store in the WindowManager, and used directly by the Card view Mar 18 13:48:55 stored* Mar 18 13:49:26 we add an item to the list, and hop, the card is inserted in the cardview Mar 18 13:51:05 And I will also see if I can simplify the window wrapping, because we wrap only cards right now, and having a generic window wrapper doesn't make much sense Mar 18 13:53:00 right Mar 18 13:53:09 I would also say lets remove the dashboard for now Mar 18 13:53:32 as it's not used and we still need to find out if we want to use it in the future Mar 18 13:53:33 yes, agreed Mar 18 13:54:04 imho if we see something as a card the it should belong to the CardView Mar 18 13:54:14 and the wrapped window should belong to the WindowManager Mar 18 13:54:27 maybe we don't even need the separation anymore Mar 18 13:54:38 as handling newly created windows is already done by the WindowModel Mar 18 13:55:08 so if a new Window of type card gets added to the model we will automatically notify this in the CardView and don't need to have a WindowManager doing something in between Mar 18 13:58:44 Why wouldn't we want to use Dashboard in the future? It's one of webOS signature features... Agree could use some updating but it's unintrusive ;) Mar 18 13:59:18 Herrie|Veer: right now we don't use it Mar 18 13:59:35 so I would like to drop unused code until we find the best way to reintegrate it Mar 18 13:59:47 OK ;) Mar 18 14:00:04 That makes sense, just shouldn't get off the radar ;) Mar 18 14:00:17 yes Mar 18 14:01:18 morphis: yes, that was what I thought of doing for the lightweight WindowManager: almost stateless, apart from the list of cards. Just sorting out the type of the windows, that's all. Mar 18 14:01:39 Tofe: yeah, but you don't need this Mar 18 14:01:49 just query the WindowModel for the window type you want Mar 18 14:02:31 Aha, yes, of course Mar 18 14:02:32 see the windowTypeFilter property of the WindowModel Mar 18 14:02:41 it's a ListModel, right Mar 18 14:02:50 (kindof) Mar 18 14:03:03 ok, will look at that Mar 18 14:17:55 Tofe: good Mar 18 14:18:06 Tofe: you will starting working on this now? Mar 18 15:08:10 morphis: yes Mar 18 21:22:45 morphis: I now understand better what you did with WindowModel, which I maybe overlooked in the past. Indeed my "light" window manager idea is quite useless with your new dynamic list. I'll integrate it. **** ENDING LOGGING AT Wed Mar 19 02:59:58 2014