|
From: Marcel M. <m.e...@st...> - 2004-04-05 13:27:59
|
> Oh, cool, I've been keen on doing this, too; would make the groupware > far more usable as a groupware (many of my current hacks to mgw, which > I haven't committed up yet, link things such as projects to contacts, > etc; it's done just by manipulating the SQL of the other module > directly, and of course, has broken slightly with module revisions. > Reason why I haven't committed them is because I consider them a hack; > an OO approach would make this far more effective). Yeah, I have also implemented something I call mgw_objects ... which is kind of a base class for any type of object (user, note, project, etc) which have properties like id,type,owner etc. This way each object has a unique id in mgw and you can very easily map obejcts to each other. Like you could have a project and map several users and todos (tasks) to it, and these tasks could have notes mapped to then, etc ... you get the idea. Another good thing is that these object can basicly be handeled in a similar way with regards to certain operations, like viewing and modifing object rights. This way we can have a more extensive api for module developers and let then work on more important things. -- Marcel |