phpgroupware-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-developers] phpgw on eyeOS


From: fallingdutch
Subject: [Phpgroupware-developers] phpgw on eyeOS
Date: Sat, 19 Aug 2006 10:24:13 +0200

Hello List,

I am playing around with getting phpgroupware applications running within eyeOS 
( http://eyeOS.org ).
I think the idea of eyeOS is pretty good and it would be good for both - eyeOS 
and phpGroupWare.

Now a list of problems i encounter and suggestions i have:
 - need for a new authtype and auth derived class
 - need for a new sessions class
 - common->phpgw_final() is registered as shutdown function and writes the 
footer which should not be done 
   within eyeOS but also cleans up => a flag 'nofooter' like the flag 
'noheader' should do the trick
 - it should be possible to have the preferences of an application within the 
application: 
   If i start eg Todo i want to be able to change its settings and dont want to 
start another "Settings"
   application to do that ... any ideas here?
 - s there any doxygen or similar documentation? @developers: yes i know its 
annoying but everyone will 
   love you for writing them :D
 - on eyeOS each application has its own directory and is started by an 
aplic.php ... but a lot of code 
   is used by all applications. Where should we store the framework? I have 
asked in the eyeOS forum 
   wether there are thoughts about supporting "libs" so we dont waste a lot of 
space by storing the 
   framework in each application directory
 - I found a bug in common->phpgw_header() (already posted #17471) that 
'noheader' is not checked
 - why is parse_navbar() called by phgw_header() and by many(or all?) apps? 
   (16, file phpgwapi/inc/class.common.inc.php Line 1144)

How eyeOS calls its applications/restriction:
 - just a aplic.php is called
 - if you want to include other files within your dir use $appinfo['appdir']
 - "Note that if the page contains HTML headers (......) or it requires css 
files, 
    you should include it from an iframe, otherwise you will disrupt the eyeOS 
    window management system."

My perfekt world would be (so far):
 - phpgroupware/index.php calls each application and "draws" the surroundings, 
like navbar, sidemenu (idots) etc.
 - the applications only "draw" themselfs nothing else, no header, footer etc - 
so using the applications 
   without navbar etc is done by just calling eg phpgroupware/todo/index.php
 - possibility to have phpgwapi in another directory (so it can be used as a 
"library" on eyeOS), can be done 
   by PHPGW_INCLUDE_ROOT, am i right?
 - in eyeOS the include directory is not set static but asked from the "os" by 
$appinfo['appdir'] so - 
   setting $SERVER_ROOT to $appinfo['appdir'] would be a good idea, i think
 - possibilty to have the application at the root so /todo instead of 
/phpgroupware/todo: then on eyeOS it would
   be /apps/todo, /apps/sshclient and /apps/project instead of 
/apps/phpgroupware/todo, /apps/phpgroupware/sshclient etc.

comments and hints are very welcome,
thanks for the great work so far!

Bas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]