I just finished re-tooling everything in pos/backend to pay attention to fannie's configuration, not be dependent on $_SERVER['DOCUMENT_ROOT'], and use ADOdb for an abstraction layer.
I copied instead of making in-place changes, so pos/backend/batch is in pos/fannie/batch, pos/backend/item is pos/fannie/item, etc.
The biggest changes I made were were to the actual queries. I added column polling where it makes sense and stripped out MySQL-specific things where possible (backticks, direct calls to NOW(), etc). I'm definitely biased on account of still having an MSSQL server around that I have to deal with, but writing queries in a portable way (when possible) seems like a good idea.
If you're OK with the changes - and I haven't broken anything - I think pos/fannie can replace pos/backend. Sure there'll be two tools for editing products, and two tools for batches, but at least they're paying attention to the same configuration.
I just finished re-tooling everything in pos/backend to pay attention to fannie's configuration, not be dependent on $_SERVER['DOCUMENT_ROOT'], and use ADOdb for an abstraction layer.
I copied instead of making in-place changes, so pos/backend/batch is in pos/fannie/batch, pos/backend/item is pos/fannie/item, etc.
The biggest changes I made were were to the actual queries. I added column polling where it makes sense and stripped out MySQL-specific things where possible (backticks, direct calls to NOW(), etc). I'm definitely biased on account of still having an MSSQL server around that I have to deal with, but writing queries in a portable way (when possible) seems like a good idea.
If you're OK with the changes - and I haven't broken anything - I think pos/fannie can replace pos/backend. Sure there'll be two tools for editing products, and two tools for batches, but at least they're paying attention to the same configuration.