Apropos recent AJAX topics: Do the core developers have any intention to use non-XML data representation/transfer formats such as JSON or YAML in LedgerSMB?
I prefer working with JSON data for Web UI data transfers, and of course JSON libraries are available for most languages by now. On the server-side, YAML (coincidentally a superset of JSON) is probably familiar to perl users as a CPAN package metadata format. YAML is surprisingly readable for non-programmers, which leads me to think it would be a good plain-text representation (and perhaps save-load API) for multi-entity documents, such as Invoices. I'd like to see LedgerSMB have a documented YAML representation for most entities in the LedgerSMB schema. If this were complete enough, a terrific feature would be a YAML-format 'journal' of all dataset transactions, in sequence, with alias links to all referenced entities, in a plain-text representation. As a series of YAML documents, this journal would be loadable by most scripting languages. It might make an Auditor's job much easier, and make great secondary backups. It could also be a compelling story for offering migration to other systems, if LedgerSMB doesn't work out for a particular client. ____________________________________________________________________________________ Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. http://videogames.yahoo.com/platform?platform=120121 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
