Hi folks.. This winter i'm going to build a webshop system to let people sell physical goods using my seductiveapps framework.. This starts at a complete financial administration in JSON. The problem i have with table data architectures like SQL is that you have to model everything into tables. I find JSON in javascript land a whole lot more useful, so I have built something i call "treeDB" in PHP that puts a bunch of JSON (folder-like) data into a single file on the server, and can search (per "path" like some.data.subStrucutre as some/data/subStructure) this data for what's needed on the javascript side. Should be fairly easy to reproduce / carry to SQL. The reason i'm about to post my complete javascript code, with updates following in this thread days, weeks or months later, is that I want to enable other programmers on the web to mimick my own system, allowing for easier intergration of all javascript banking systems that are modelled after this. So, getting to it, first there's the fact that every jurisdiction has their own accountancy laws. This is modelled into the very base of the datastructure (in JSON) that we'll use for the user-interfaces that use this accountancy/banking subsystem. Translations of financial terminology (for display in the UI) are handled by google translate, described at https://cloud.google.com/translate/v2/getting_started?hl=nl#translate, and a reverse function (to be written) for php.net::ucwords() that'll put javascript-compatible phrases from the base JSON (in hungarianNotation) into plain english phrases (=== "hungarian notation"), to be translated from English into (thus not failing translation) another language that the end-user wants to operate his/her webshop in, and then stored in a seperate treeDB file on the server (and in a seperate javascript variable-"path"). The UI code that uses this accountancy/banking subsystem is tied to the jurisdictional rules stored in the base layers of the JSON data & javascript code by naming the financial account that is used (from a template definition that the end-user is tied to) exactly the same as in the per-jurisdiction rules stored in the base JSON describing the accountancy rules for the entire world (per code collection written). So, I actually have a book in Dutch about accountancy, title of which translates as "accounting for dummies" , and I've put this book into code sorta say, at http://jsfiddle.net/x2t1tw7x/ I welcome any suggestions you might have.
My customer that wanted this webshop with shoppingcart may be satisfied with only a digital brochure, without shopping cart. As there is more money in building games for my website, I'll be focussing on that instead I think. I may do work on this accounting subsystem this winter, i may not. No way to tell now.