Hi, i am working on the module System Info, http://drupal.org/node/48602, which includes a up-to-date function. With these function the user can check if the module files of the local drupal installation are up to date. But I need an interface at drupal.org to get infos like cvs file id and md5 checksum. For example an interface can looks like this: request: http://drupal.org/uptodate/module/systeminfo/4.7 response: <?xml version=1.0" encoding="utf-8"?> <drupal> <module name="System Info"> <name>systeminfo</name> <branch>4.7</branch> <id>1.4</id> <md5>201E0700D75E565FBD17FA95D90F99D3</md5> </module> </drupal> What do you think ? Or is already there an interface? Or another way? Or i am wrong? Thanks, Ralf
Ralf Stamm wrote:
<?xml version=1.0" encoding="utf-8"?> <drupal> <module name="System Info"> <name>systeminfo</name> <branch>4.7</branch> <id>1.4</id> <md5>201E0700D75E565FBD17FA95D90F99D3</md5> </module> </drupal>
In case someone starts thinking about formats: RDF- sorry, but I haven't seen a fully complaint RDF parser in PHP that is lightweight yet. RSS- ask again once there is an RSS parser properly abstracted out of the aggregator module and into a .inc. Also, this data actually doesn't map especially well into RSS. XML- its okay if you can stand parsing it with SAX. INI- simplest to write and parse and suitable for name-value pairs, which is what I see here. And no, the file itself wouldn't be named *.ini. I'd like to see this funtionality in Drupal core right on admin/modules. I thing nedjo might be working on this. Kieran- what were the two issue links? -- Neil Drumm http://delocalizedham.com/
Op vrijdag 3 maart 2006 23:31, schreef Neil Drumm:
INI- simplest to write and parse and suitable for name-value pairs, which is what I see here. And no, the file itself wouldn't be named *.ini.
PHP the most simple way. And yes, both we, and machines can read and write that. I thought we already agreed that a keyed array was the way to go here, and not some Yet Another Meta Language Thingy parser? Bèr -- [ End user Drupal services and hosting | Sympal.nl ] Sympal draait nu voor het grootste deel al op 4.7: http://help.sympal.nl/sympal_draait_nu_voor_het_grootste_deel_al_op_4_7
Bèr Kessels wrote:
Op vrijdag 3 maart 2006 23:31, schreef Neil Drumm:
INI- simplest to write and parse and suitable for name-value pairs, which is what I see here. And no, the file itself wouldn't be named *.ini.
PHP the most simple way. And yes, both we, and machines can read and write that. I thought we already agreed that a keyed array was the way to go here, and not some Yet Another Meta Language Thingy parser?
the problem with PHP is that you can do malicious stuff. I would like drupal.org to feel safe reading these metadata packages for module listings and so on.
On 05 Mar 2006, at 3:25 PM, Moshe Weitzman wrote:
the problem with PHP is that you can do malicious stuff. I would like drupal.org to feel safe reading these metadata packages for module listings and so on.
how about just : print serialize($modules[arg(X)]['info']); -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
Adrian Rossouw wrote:
On 05 Mar 2006, at 3:25 PM, Moshe Weitzman wrote:
the problem with PHP is that you can do malicious stuff. I would like drupal.org to feel safe reading these metadata packages for module listings and so on.
how about just : print serialize($modules[arg(X)]['info']);
-- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
i don't really understand what you are trying to say with this serialize() call.
a forum question opened up today related to this. it'd be nice if folks who care about this would comment there: http://drupal.org/node/52330 thanks, -d
participants (7)
-
Adrian Rossouw -
Bèr Kessels -
Derek Wright -
Khalid B -
Moshe Weitzman -
Neil Drumm -
Ralf Stamm