Re: [Phpgroupware-developers] PhpTree as filemanager

[Chris Weiss]

here's the quick rundown...

UI = User Interface
BO = Back Office/Buisness Object
SO = Storage Object

All browser/end user interaction makes calls through the UI classes.
The UI classes then make calls to the BO classes to get a data structure useful 
for
outputing.
The BO classes make calles to the SO classes to retrieve the data from the 
storage
mechninisms and agregate/filter the data so that it pass it on to the UI layer.
The SO classes handle getting data from SQL/Filesystem/IMAP/WebDav or whereever 
data
might be stored and makes it into a non-datastore dependant structure for the BO
class to deal with.

Only your app's BO classes should call your app's SO classes.  Any ACL or
permissions restriction should be done in your BO classes.  Any other app that 
would
do something with your app's feature set would make calls to your apps BO 
classes in
the same way your UI layer does.  Other apps can also make calls to reusable UI
components in your app.

Most of the time the BO functions will nothing more than a passthough to the SO
functions, this is needed for abstraction, this way an XMLRPC interface can also
just call your BO functions and get the data in the same way as your HTML UI
classes.  On more complex functions, the BO functions will make several SO 
calls.
More complex UI functions can also make several BO calls.

Examples of non-datastore dependant structures:
An array that represents a resultset.  The array will end up the same no matter 
what
database is being used.
A "messageball" that represents a email message and folder list.  The 
messageball is
the same no matter if your using IMAP or POP3 or whatever comes down the road 
next.

For a simple concept example, look at how the Notes app works.  Also, would it 
make
more sense to implement the phpTree as a UI layer on top of the phpgwapi VFS, 
sort
of like phpWebHosting does now?

Sam Przyswa (address@hidden) wrote:
>
>Hi,
>
>I noticed that severals companies, as our, using PHPGW have make the choice of
>PhpTree as filemanager because it's more flexible to share files and 
>directories
>trough theirs users, and for the MySQL files storage (Postgres not yet
>implemented).
>
>I have ported PhpTree bye Jason Read <address@hidden> on PHPGW but I
>know it don't respect exactly the PHPGW guide line, does anybody can help me 
>to do
>that to respect the class.bo class.ui scheme.
>
>It will be nice then to use the API to attach files on mail from PhpTree...
>
>Any comments...
>
>Sam.
>
>
>
>
>
>_______________________________________________
>Phpgroupware-developers mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>