[dev] [commits] Horde-Hatchery branch master updated.

[Gunnar Wrobel]

Hi Chuck,

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Gunnar Wrobel <p at rdus.de>:
>
>> 52e4832... Reorder the www structure in a way we might do it for
>> Horde 4. I'm probably way off here but at least it can be installed
>> via PEAR this way.
>
> Okay, well, let's talk about the structure we want. :) Are you  
> following a PEAR role here, or something else? What do you need,  
> what are you going for?

thanks for picking this up. I've been a little bit busy with the  
customer I coded koward for so I was in a rush to get a structure that  
would work for me.

My primary intention was to be able to package the application with  
the PEAR tools currently available. For the package.xml of the Koward  
package I'm solely using the standard "php" and "www" PEAR roles.

The koward package has nearly all PHP code with "php" role in the  
"lib" subdir. I even placed the scripts you located under  
app/controller and app/view within the "lib" directory  
(lib/Koward/Controller and lib/Koward/View). I intended to support  
configurable Controller and View directories as the customer is likely  
to extend the views with custom stuff. This is not in the code yet.

The only PHP script that resides outside of the "lib" directory is the  
koward.php script (koward/www/htdocs/koward/koward.php,  
http://cvs.horde.org/co.php/koward/www/htdocs/koward/koward.php?rt=horde-hatchery&r=52e4832afedf0222dec06bf659d777ca49e9a8d1).

This script - in combination with the method Koward::dispatch() in  
koward/lib/Koward.php - is comparable to rampage.php you use in the  
horde base package. In fact I believe it would be better if this basic  
handler would actually be called horde.php and would call  
Horde::dispatch(). But I did not really dare to start a "horde"  
package in the horde-hatchery. Instead I copied some basic horde stuff  
(theme support, images) into koward while that could actually be its  
own package.

The "www" directory has a basic level intended to be placed outside of  
the document root. It carries configuration, documentation or other  
stuff not intended to be accessible via HTTP. The "htdocs" directory  
contains the static elements.

  www
   |__koward
   |   |
   |   |__config
   |   |__docs
   |
   |__htdocs
       |
       |__koward
           |
           |__js
           |__themes
           |__koward.php

The current koward also has "horde" subdirectories but this would  
actually belong into a separate package.

Are there elements we could actually use for Horde 4 or am I really  
way off here? :)

Cheers,

Gunnar


>
> -chuck
>
> --
> Horde developers mailing list - Join the hunt: http://horde.org/bounties/
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>





----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.horde.org/archives/dev/attachments/20090508/6a419784/attachment.bin>