At 12:23 15/12/2000 -0800, brian moseley wrote:
>On Fri, 15 Dec 2000, Robin Berjon wrote:
>
>> Wing has been widely tested in the field iirc, it's
>> probably a good idea to base anything in that domain on
>> it.
>
>possibly. groupware applications aren't that complex really,
>tho (except for calendaring and scheduling); the main
>problem is that they're *large* when they become featureful,
>and in some ways it feels like a waste to build a new one
>just cos "i want to do it my way".
I agree, groupware is usually fairly easy modulo that you still have to
write a lot of easy code. It would be a waste to start from scratch.
Patching Wing could be an option.
>i'd really like to see an app with a much more outlook-ish
>interface than twig. and i don't think wing has all of the
>pim functionality that twig has. can't say if wing is a good
>starting point for that or not.
I don't like outlook but as you said earlier the code should be handled in
some place and the display elsewhere. I don't know twig but if a horrible
interface is what plagues it, then it wasn't written that way. Ideally one
would have an API for the mail logic (->list_mailboxes($user),
->list_messages($user, $mailboxes), $message->content($msg_id), etc...) and
the display would be totally separate.
if the existing modules don't allow for such things, then a rewrite would
be needed. But that doesn't exclude cannibalising code where it makes sense
to :)
-- robin b.
Being schizophrenic is better than living alone.
