Just a quick note on Desktop Groups. I want to have the ability to assign members to multiple groups.

Say group A, B, etc. will have access to certain modules/apps and features in the desktop. A member can then be assigned to one or multiple groups.

I am trying to decide how to handle the login procedure when a member has been assigned to multiple groups.

1. Once member logs in they must select which group they want to be signed in under, and they will only have access to that groups modules/apps and features.
2. Once logged in they have access to all modules/apps and features of all the groups they are assigned to, not just one particular group. (I’m leaning toward this one)

I have started on the Db tables for this, but nothing is set. So if anyone has ideas also please share.

Hello, I felt it was time for a quick update on the development of the desktop.

I have been doing alot of work on the database design. Tentatively it is as can be seen here. Click for a larger view.

I plan to use XML files to install modules into the desktop. Every module will need a “module.xml” file in its folder, similar to the following:

<?xml version=”1.0″?>
<module>
    <name>QoDesk.Preferences</name>
    <apptype>desktop-preferences</apptype>
    <id>qo-preferences</id>
    <version>1.0</version>
    <author>Todd Murdock</author>
    <description>Allows users to set and save their desktop preferences.</description>
    <files>
        <css>
            <file>preferences.css</file>
        </css>
        <js>
            <file>Preferences.js</file>
        </js>
        <php>
            <file>Preferences.php</file>
        </php>
    </files>
</module>

More to follow…

Hi everyone. This blog has been started to provide information to developers wanting to use the qWikiOffice desktop. It is meant to be a continuation of my thread on the Ext Js forum.

This deskop environment is a work in progress. The “About” page will give a quick overview. Currently I am working on the API that will be available to application developers.

The API will provide a connection object that developers can use to make all ajax calls to their server scripts. No hard coding of paths to server scripts will be necessary.

Stay tuned for more…