module xml feature request

[Johnny Robeson <johnny (at) xaraya.com>]

linoj wrote:
> Hi,
> 
> I've been meaning to add this feature request to the 2.0 agenda.
> 
> I think all modules should be required to provide an xml interface for
> import and export of items, itemtypes, blocks, and configuration data.
> 

well dynamicdata can already do most of that if you were to use the objects
as dyn_example does 

the only thing it doesn't handle is blocks , but that could be fixed if 
we were to provide overlay objects of the blocks tables

it already handles configuration data like modvars via a config object
and of course export of itemtypes and items

it's not exactly the most efficient process atm, but that is certainly
going to change as marc has recently started on the data object master class
refactoring :)
> This will facilitate a lot of features that I have been wanting/needing,
> including
> 
> - conversion of items from one item type to another
 dd has an interface to this, but it's not available programatically
nor does it work completely .. seems fixable for most common usage
> - moving items from one site to another
well if you were to use objects, that shouldn't be difficult
> - installation wizards for modules and pre-packaged websites
marc has already started the installation stuff in some of his modules
> - synchronizing websites, especially a staging site vs a live one
hmm.. have to think about how this would work in practice
certainly something worth considering

> For example, lets say I have a live community site. And at the same time
> I have a development or staging site where I'm adding improvements. When
> I'm ready to move the staging site to live, I need to diff and merge the
> databases. Right now I do this "by hand" (and hope I got it right).
> 
> 
> linoj
_______________________________________________
Xaraya_devel mailing list
Xaraya_devel (at) xaraya.com
http://xaraya.com/mailman/listinfo/xaraya_devel