2003-08-01 08:23:03 Ξplease see more information on sourceforge project page for BlooGee docs. This is a sample page what BlooGee may look like.

If you want to use the advanced features, click "command shell" in the menu to the bottom right (allow popups!). If you need help, try "help" at the "CLI". If you need a user account, just try "guest" with password "guest".

If you want to add to the list of related items below, you need your own bloogee along with your weblog. If you are admin, you may edit in place.

2003-07-13 20:26:49 Just play around, dragging the panes, reordering items, try the menu (bottom right) and do not forget to test the CLI!
BlooGee establishes semantic peer-to-peer networks, stores and forwards messages, based on HTTP communication between common CMSs. Access through AJAX based interfaces or HTTP-header. Works as add-on/editor for microcontent collections like weblogs.

2003-06-30 10:17:48 Now drag and drop the item on the notepad to the right. You may resize both panes and drag them in the window. If zou click the highlighted headline, may be it can be edited.

2003-05-29 00:32:18 changed by mck: This is the first Version of BlooGee - still below 0.1 ;-) - which has the following capabilities: - a full security layer, supporting an - abstract layer of basic datbase commands. - a full featured command shell to access the - basic set of server-to-server protocoll functions; and - an AJAX based desktop for blog-style display. - Integration of ADODB. - A widely open architecture for extensions and third party plugins.

2003-05-23 17:55:01
What does BlooGee consist of?
BlooGee consists of a set of clientside scripts and a set of server side PHP scripts. It makes use of AJAX related stuff and is based on a simple object model for microcontent. To construct the wrapper interface, the common libraries Prototype and Scriptaculous are used.

Wrapper
A wrapper is the HTML part that is initially loaded into the browser. It contains references to JavaScript, CSS and basic HTML. A wrapper is used to put all elements on screen, it is the basic layout template for BlooGee. A wrapper is only loaded on initially calling a BlooGee page and ties together all elements and behaviours, also the wrapper decides which format is used for initial output.

Commands
BlooGees datasource interface accepts a basic set of shorthands to retrieve content items. These can easily be wrapped into specialised plugins or controller pages. Additionally, they can be passed via GET or POST data to BlooGee. If used with controllers, partial updates are possible (see the example controllers).  BlooGee only accepts commands, item ids or keywords as querystring.

Plugins
Plugins smply control the default behaviour of a BlooGee and are included into index.php. They may be used fo building queries on own specialised block commands. Plugins should pass their output back to index.php, so in most cases a plugin produces a full page output.

Controller
Unlike plugins, controllers update only parts of the wrapper page. They use block commands, but provide their own formatter.  Controller are called "stand alone" (not through index.php), it is up to the wrapper to properly ask for and render a controllers output. Controllers may be small and simple appications (like the search controller), or a full blown application for user registration and management.

DB adaptor
The datasource adaptor provides the interface between command language and the data. By default, BlooGee uses a MySQL database with MovableType tables. Further versions will contain adaptors for PostNuke/PHPNuke, Serendipidity, Google, Amazon and ebay. By using different adaptors in specialised controllers, several datasources may be combined into one BlooGee page. If the datasource is not on your own server, the dbadator has to provide the correct AJAX calls which will be handled through the  client sided wrapper.

///////////////////////////////////
Messaging
BlooGees block commands make it highly communicative. If you have the appropiate controller, a remote BlooGee may be queried and even updated. If you have a look at the classes, you will find a basic object which carries information on "per item" or "permalink" basis. For example, a Bloogee may qury other sites and update if something corresponds with an item - for example, if a remote URL is added to the relatives section. The other side may decide whether to store this information to the relatives section of its element, or not.  

Notice: in this version 0.01.a messaging is only "implicit", which means there is no special controller for that. Since messaging is one of the basic concepts (and features) of BlooGee, the next version will provide a RPC-like command for remote updating.  

2003-05-23 14:31:19
This is the first version of BlooGee. What is BlooGee?

First of all, BlooGee is not a full blown content management or weblog system. BlooGee is rather a  library for displaying and editing existing content from  variety of sources. Upon this library and its model you can build highly customizable interfaces to existing structured data produced by commonly used systems as mentioned above. The basic BlooGee wrapper makes extensive use of the famous libraries "Prototype" and "Scriptaculous" which are included with this distribution. You may use BlooGee to search and edit your existing content in a comfortable way, or build an additional "display and edit port" to existing structured data.

What does BlooGee need?
BlooGee needs the follwing things: a living datasource (basically MySQL with tables from MovableType or Post/PHPNuke, or use your own format, see below), a properly set up Apache, PHP are server side prepositions, the client side will need a common browser with activated JavaScript. (!!This version works properly only using Firefox!!). Just copy the files and directories in the package to a directory of your choice (it should be accessable via Apache...), you may rename index.php as needed. Set up the datasource (which is a high risk at this time, you may loose ALL your tables, or anyone may edit your content...!) , call index.php in your browser.  

How does BlooGee work?
Initially, BlooGee works like a simple weblog - it produces an array which alway has the same structure: {id, title, text, [array $relatives], [array $config]}. If no query string is specified, it takes a default action (selection) from its default plugin and passes the result (the array, see above) to the appropiate wrapper. This wrapper produces the HTML and JavaScript output which is sent to the client. If the basic controller (index.php) receives a query string, it will be examined if it contains block commands. If so, only the first is executed, if not, BlooGee treats the query string as a search term and delivers a collection to the wrapper which will format and return it to the client. BlooGee works with any datasource which has a PHP-accessable API if the appropiate dbadaptor is used. As well BlooGee may produce not only HTML output, but also XML or popular formats like RSS (if the appropiate wrapper is used).