[Everydevel-opers] More DB stuff and Drupal!!

[Paul <pau...@us...>]

Hello,

As I wrote in my last email, I've been wanting to abstract out the much 
database
stuff so that we don't have to have SQL in nodeballs.  This should allow 
more flexibility in the db schema that can be used.

It should also help people who develop a nodeball in one DB and then 
want to export it.  The two most popular nodeballs were Ewiki and 
EnoteAndPreview.  These both need updating to work with the new system 
and it would be better if all development could occur on a live system 
and then be exported.

So far the development process has been:

perl -I lib t/ecore/ecore-install.pl  -d t/ecore.db ../ecore/
t/TEST -start-httpd

Point browser to localhost:8529 and make changes

perl -I lib bin/export_nodeball.pl -d t/ecore.db 'core system' ../ecore/

and then commit changes.

Rather than all this mucking around with XML, it might be far better to 
have all nodeballs, or at least ecore, as an sqlite database.  On 
installation, the nodes are then extracted from ecore.db and put into 
the production mysql or Pg database.

For one this means that we are going from SQL to 'internal 
representation' to  SQL rather than SQL to 'internal representation' to 
XML to
XML/Node 'representation' to SQL. Bugs are less likely to creep in. It's 
also simpler.

On something different, people have often compared Everything to 
blogging software.  I think a much better comparison is to Drupal. So, I 
think that's the goal...to be better than Drupal.

Cheers

Paul