some suggestions
You need to be logged in to post messages in the forums. New users may register here.
|
Gaetano Giunta
Member since:
09 January 2008
Posts: 152
|
Saturday 20 March 2010 2:43:48 am
great work! about time that somebody took up the challenge.
missing suggestions / feature requests:
- nxcExtensionSettings::executesql: it is hardcoded to mysql :(, it uses a bad directory for sql files (an eZP standard does exist for that!), it does not check if file exists, and it is a function that actually exists in ezdbschema. Last but not least, using .dba file for defining sql elements needed by an extension is now recommended - try in 4.3 the upgrade_check/db page
- class nxcextension: remove include_once, let autoload do its magic via class_exists
- dependencies should be able to specify
+ versions (eg. I need ezjscore 0.2 min and 0.99 max)
+ min/max ezp versions, too
+ possibly a specific db, or other ez feature (eg webdav). harder to implement...
- I'd recommend to specify the extension dependencies in the existing ezinfo.php file, by adding a new static method to that class - this leaves us with a dependency specification that is not ties to the way it is checked/implemented (might like to read that and code that into pear packages later, and leave pear to do the checking/handling)
|
|
|
Kristof Coomans
Member since:
09 January 2008
Posts: 66
|
Saturday 20 March 2010 6:53:33 am
Hi gaetano
Maybe off-topic but ezinfo.php sucks. IMHO the best way to define meta-information about an extension would be in a XML file with a clearly defined XML schema.
|
|
You need to be logged in to post messages in the forums. New users may register here.
