Macrobyte Resources Conversant Developer Central
Internet groupware development platform
RE: Plug-in architecture

Subject RE: Plug-in architecture
Posted 5/23/2002; 7:09 PM by Philippe Martin
Last Modified 5/23/2002; 7:09 PM by Philippe Martin
In Response To RE: Plug-in architecture (#246)
Label None. Read 968
<Previous Next> Thread: Edit Reply
Just some addition to Greg's and Seth's answers.

At 18:35 -0400 23/05/02, David Davies wrote:
>I'm familiar with the website fragment approach of Manila plugins whereby you create essentally a mini website within the plugin that's easily viewable via the web browser. How do I start making 'pages' for my Conversant plugin?

There is no website table, like in Manila plugins, because a Conversant plugin doesn't have to have associated pages. For instance, the email interface is implemented as a plugin. It has preference pages, because it has a "preferenceInfo" table that defines its prefs at system level, conversation level, and so on, but it doesn't have a "sub-site" à la Manila. Similarly, some other plugins are used to implement features called from macro calls, like the Bookmarks box, for example.

So Conversant plugins don't really have a required structure. Some tables are always there (like callbacks or tools, but I think only callbacks is required). Some are optional, and are used when present (like preferenceInfo). And you can create your own tables.

One thing to note, is that most plugins we've done are driven through callbacks. There are lots of callbacks available to plug in, as you can see if you look in the "callbacks" table of the plugins that came with Conversant.

Hope this helps at least a bit.

Philippe MARTIN (a.k.a. Flip)
<Previous Next> Thread: Edit Reply



© 2002 Macrobyte Resources. All rights reserved.