Hi Bas, Comments inline.
On Sat, 2006-08-19 at 10:24 +0200, fallingdutch wrote: > 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. > I have looked at the project a couple of times and found it to be a pretty cool idea. I also quite like the idea of "web desktops". > 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 We have discussed these a bit on #phpgroupware, this should be pretty easy to implement. > - 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 This already exists and works. An alternative could be creating a new template set called eyeOS which handles some of these issues. > - 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? Preferences should be a seperate app as it is. You can use the hooks as you like. So if you were to create the eyeOS template set you could detect the current app and create a "setting menu". The url after updating would need to be handled better than it is now. > - s there any doxygen or similar documentation? @developers: yes i > know its annoying but everyone will > love you for writing them :D The docs are growing. HEAD will use phpdoc as it is no longer PHP licensed, it is LGPL iirc. > - 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 Moving phpgw's path around to suit eyeOS is not something I am in favour of at this stage, as I would not want phpGW to be dependent on eyeOS to function. Maybe we can look at setting a flag in the header.inc.php to handle it. > - 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. phpgroupware/index.php acts as a dispatcher already. But the app knows if it needs to output the header/navbar/footer etc, there is not a generic solution to this as you propose. > - 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 this won't work, as phpgroupware/todo/index.php just redirects to the dispatcher with the correct method call > - 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. I am lost here. Cheers Dave -- LLLLL L*LLL LLLLL LLLLL DAVE LLLLL HALL CONSULTING Open Source Business Solutions p +61 410 47 42 55 e [EMAIL PROTECTED] w davehall.com.au _______________________________________________ Phpgroupware-developers mailing list [email protected] http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
