I don't understand what you mean when you say that contactUpdated and groupUpdated should be in the core and not in the UI... I think you didn't understand the design correctly, in that case, please read my previous emails about the design. About having a UIManager, yes, it's definitely the way to go.
On Wed, Jun 24, 2009 at 10:56 AM, Luca Dariz <luca.da...@gmail.com> wrote: > > Hi all, > > I agree that there could be many common tasks that could be implemented > in the > base UI, another that comes im my mind are the events registration > (contactUpdated, groupUpdated etc..); all this things could surely be > done in > the core, like KaKaRoTo said, but i feel like there would be a lot of > methods of > this kind, so my idea is: > why not create an UImanager that would do precisely this kind of work? I > think > that the core, that is the glue between all the other pieces, should not > contain > too many methods (to make it simpler, at least something really general), i > think that it should basically coordinate the whole stuff using various > managers, like it is done right now. > This is just an idea, any comment is appreciated :) > > Finally, i think that some common variable defined in the gui/base/*.py > class > are not necessary, if the common stuff like choosing and retrieving > accountviews > is managed through an UImanager, the common variables could simply live > there > and, most important(but it could be a bad idea), could be created or not > according to UI needs. > > Regards > > Luca > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel >
------------------------------------------------------------------------------
_______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
