On January 11th, 2008 Doug Green (not verified) says:
This looks interesting. But I'm not sure that we need to be a new language. The Drupal way seems to be to define things using arrays.
Are you proposing a new utility that is totally separate from Drupal, simply for inporting and exporting CCK types?
I'd like to see a Drupal module, with an import/export feature, where the definitions could be pasted into php. This would lend itself more to an array syntax rather than a language definition.
I've done a lot of language work in the past and I understand parsers. But we have gotten pretty far in Drupal without them. I even avoided it in coder, opting instead for lots of regex checks.
So, I'm wondering why you think that the CCK definition needs to be a language. It feels very un-Drupalish.
why create a language?
This looks interesting. But I'm not sure that we need to be a new language. The Drupal way seems to be to define things using arrays.
Are you proposing a new utility that is totally separate from Drupal, simply for inporting and exporting CCK types?
I'd like to see a Drupal module, with an import/export feature, where the definitions could be pasted into php. This would lend itself more to an array syntax rather than a language definition.
I've done a lot of language work in the past and I understand parsers. But we have gotten pretty far in Drupal without them. I even avoided it in coder, opting instead for lots of regex checks.
So, I'm wondering why you think that the CCK definition needs to be a language. It feels very un-Drupalish.
Thanks!