Re: publicweb role

My point with "app" is "any file which isn't a lib, doc, test or extension, that needs to be located at a custom place by the person who installs the package". Either if it is a standalone application or (as you said) it's used by an application. We manage packages with no distiction between them. You know that a PEAR package may contain php files, only doc files, C extensions, etc., so a package with one or more files marked as "app" are still PEAR packages. Tomas V.V.Cox On Saturday, September 6, 2003 15:18, Greg Beaver wrote: > Hi Tomas, > I think we have a different understanding of what publicweb is, here is > a few examples. > HTML_TreeMenu is not an application by any standard. It contains both > image files and .js files that are static. Currently it is impossible > to locate them without intimate knowledge of how pear installs things, > and if you attempt to run the example, it will successfully display the > dropdown menu, but no JS example is displayed, and no error either. My > Error_Handler package displays a few images in the HTML logger, and > currently, the only way to guarantee that they will display properly is > to hack in a base64decode of the image data and echo it - which makes no > sense, since it is static image data. > Neither one of these examples is a standalone application, but both can > be used by applications. So, I don't think publicweb has anything to do > with applications, at least not any more than any other role does.