From: Brendon D. <bda...@ma...> - 2002-03-06 07:31:01
|
On Wed, 2002-03-06 at 01:26, Till Adam wrote: > # Quoting Christian Kreibich (kre...@in...): > > > > - user opens new view > > > - we start monitoring the associated dir > > > - we ask efsd for metadata and get position, size and location of > > > .e_layout dir to use back > > > - as soon as we have that, we realize > > > - we start monitoring the provided .e_layout dir too > > > - something changes in the dir, efsd tells the model about it > > > - dispatch to views and update them > > > - same with the layout dir > > > > > > Like this? > > > > *hug* :) > > > > The only drawback I see with the metadata pointer is that we're > > basically screwed when that file is removed for some reason, so there > > should be a good fallback mechanism. > > Well, there's the case of a dir we dont have metadata for anyway. New > dirs for example. So sensible defaults are a must anyway. Efsd will > hopefully tell us about the file vanishing, so we can take appropriate > action. Just like when a background is deleted from the dir now. > > One thing with sharing layouts. An E_Layout would need to keep a list of > attached views, not unlike the E_Model. They have quite a bit in common, > actually. Maybe a common base class for them would make sense? Or > deriving one off the other? I'll have to think about that today. Heh... It's 1:30AM here :) > > Cheers, > > Till > > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel |