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

Subject RE: Plug-in architecture
Posted 5/23/2002; 6:05 PM by Seth Dillingham
Last Modified 5/23/2002; 6:05 PM by Seth Dillingham
In Response To RE: Plug-in architecture (#246)
Label None. Read 884
<Previous Next> Thread: Edit Reply

On 5/23/02, David Davies said:

>OK, I've made a plugin, restarted Conversant and activated my plugin
>via admin/system/preferences$section=Plugins
>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?

To be perfectly honest, I'm *not* familiar with how this works. I've never looked at it. Greg may have, and I'm sure Flip has, and I'm equally sure that Brian hasn't. Anyway, there's very little chance that the plugins work in the same way.

What a "page" is, in Conversant, is sort of like a CGI script in a traditional server. The objects you create in your plugin's pages table are mini-apps.

There are two page types that are very, very simple, and make for an easy place to start learning about Covnersant's "pages". They are "Bound Message" and "Redirect".

The Bound Message is the easiest one to set up. Just do this:

1. Go to a message in your browser, like http://my_sites_url/1 (and make sure you're logged in)

2. Scroll to the bottom of the page, where the Admin Functions table lives. Look for the form that says "Bind Message to URL"

3. Type "a_new_page" into the text field, then click on the "Bind" button

4. A new page opens that tells you the new page was created, and where. Click the link. You've created a "Bound Message" page, and now you're seeing it for the first time.

Now if you want to study how that page works, open up the site in Frontier (or Radio). Look for a file under the "Windows" menu named "ConvZone_[sitename].root", where [sitename] is the name of the site you created in the installer. In that window you'll see a root-level table with the name of your site, and then a further structure like this:


Open up that last "myfirstsite" table, and you'll see the contents of the web site.

Scroll down through the table until you reach the table named "a_new_page". Open it up.

When that page is requested through the browser, the #content script runs. That script was put there when the page was created. It's copied directly from the "page type's" prototype table, which you'll find here:

["MainResponder Interface"].pages.["Bound Message"].content

I know that's a long answer... I'm going to stop here, hopefully I've given you a place to start digging.

I'm *sure* you'll have more questions. Keep asking! LIke I said before, you'll helping to write the documentation.


<Previous Next> Thread: Edit Reply


RE: Plug-in architecture
5/23/2002 by David Davies
I'm *sure* you'll have more questions. So you've heard about me then ;-) Thanks

© 2002 Macrobyte Resources. All rights reserved.