6
Quote:
24. Strict names for the distributive packages, eg.
What with paths inside packages to easy installation (without manually creating/ moving folders and reading installation.txt )?
1. simple module -> core-version_modulename-version.zip
paths:
/modulename/..other_paths ( easy copy to xoops/modules)
or
modules/modulename/..other_paths ( easy extract in main xoops directory )
or
public_html/modules/modulename/..other_paths ( xoops installation pack )
2. modules like protector
public_html/modules/modulename/..other_paths
+
public_html/xoops_lib/modules/modulename/..other_paths ( like xoops installation pack, but here is problem -> xoops_lib in other root path )
/ IMO why not force separated public_html and xoops_secure( with /xoops_lib and /xoops_dat - this is recommended ...) /
3. modules with frameworks and other paths
Frameworks/"create_new_one"/
or
public_html/Frameworks/"create_new_one"/
or ( damn ;P )
xoops_lib/Frameworks/"create_new_one"/
or (better)
xoops_secure/xoops_lib/Frameworks/"create_new_one"/ ( outside public_html )
+ other paths like
public_html/uploads/"module name"/ ( tagged by modules )
or
public_html/uploads/photos ( photos or files or other tagged by category )