[binarycloud-dev] r1 -> r2 code migration

[Alex B. <en...@tu...>]

One of the things I've tried to incorporate into the design of Dispatch (the
new, correct name for core_template) is the ability to use r1 modules with
very little conversion work required.

I think that's doable:

There will be a dbobjects directory in user/db/objects (just like in r1) and
a path constant for referencing that directory.

The only conversion that would need to happen to modules is to turn them
into classes, which is easier than it sounds.

the public method of each module will be the same as the file name (just
like the module_name() functions in the current system), and you can turn
the module_name_print() functions into private methods that are called by
the public module_name().

Dispatch will now use output buffering to cache output from modules, so we
don't need to "save" the output functions so they can be called in the
master template.

I'll also try and find the time to write a "constants" conversion script
which searches module code for r1 constants and replaces them with their r2
counterparts.

So, for those of you with code in r1 installs, the migration process should
be near painless.

_alex


--
alex black, ceo
en...@tu...

the turing studio, inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093