I'm curious as to if anyone has used or featured XML in their FreeTrade (or
let's loosely say FreeEnergy) implementations.
I was looking at ways of opening up the setting up/configuration of
FreeTrade to the designers and clients and I posted a "why not have this
info in the database" question which I answered myself by finding Leon's
reasoning in the archives. In practice it does prove to be a good way to go.
So in order to display the editable config/language info to administration
it could be just a parsed text file but XML seems to be an appropriate
method of structuring the info. Poking around other systems e.g.
Binarycloud, SiteManager unearthed similar thinking...
So has anyone any observations, experience, advice, etc?
Thanks,
Nick
p.s. I was wondering since FreeAssociation is a not too distant cousin of
FreeTrade but seems somewhat lonely out there wouldn't it be an idea to open
up this mailing list to FreeAssociation as well? It seems a shame to let
that work gather dust and it has been discussed here more (apparently) than
it's own list. How about a generic FreeEnergy list?
----------------------
Lab2 Design-Unit
URL: http://www.lab2.com.au
e-mail: [EMAIL PROTECTED]
----------------------
_______________________________________________
FreeTrade-dev mailing list
[EMAIL PROTECTED]
http://share.whichever.com/mailman/listinfo/freetrade-dev
