[OGo-Discuss] OGo and asterisk, SUMMARY
Adam Tauno Williams
discuss@opengroupware.org
Fri, 24 Nov 2006 11:11:35 -0500
> > Doesn't current versions of Outlook even support a journal?
> Yes, and so do most of the linux clients as well.
I was just thinking that this is about the only feature completely
unsupported in ZideLook; maybe if it was added to OGo it might someday
get supported in ZideLook. Would be nice. But of course the ZideLook
people will decide all that on their own.
> On Mac's I dont know.
> Integration with OGo is a completely different matter OTH.
Yep. But I don't see that as a problem there are already lots of
quasi-standards relating to working with a journal.
> I think it is very important to keep things general-purpose; if
> > people need very specific functionality OGo provides to means for
> > users to construct front-ends to the general purpose functionality
via
> > an intranet or other means.
> Reading your/this discussion has been most interesting and well
thought out. I
> agree a journal (as an add on or other) is probably the correct
facility to
> accomplish this requirement as well as others.
I've got bits of journal support (LSNewJournalEntryCommand,
LSSetJournalEntryCommand, LSDeleteJournalEntryCommand, etc...) - working
out exactly how OGo put all the layers together is interesting. :) But
I'm just interested in this for ZOGI (http://code.google.com/p/zogi/) &
Consonance (http://code.google.com/p/consonance/). If someone is
interested in adding a journal application to the WebUI that would be
very cool.
> Btw, blogs are not really that bad when properly used assuming that
the editor
> has received a basic level of <snicker> training?
I wasn't dissing BLOGs with "the <cough>standard</cough> BLOG APIs" I
was referring to the standard BLOG APIs such as Blogger (already
supported to some degree in ZideStore, see ZideStore/Protocols/Blogger
in the source). Everyone implements these at least a wee-bit
differently. Of course the same charge can be leveled against XML-RPC
as well. (Blogger is theoretically replaced by ATOM -
http://code.blogger.com/archives/atom-docs.html See
http://www.blogger.com/developers/api/1_docs/ ) But that is all really
an aside to this discussion.