-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Daniel,
Daniel McBrearty wrote: > one question though, for the hard of understanding (me) : is the > schema layout exposed to the client side js in any way? Not especially, no. The way LFB works is to poke at your DBIx::Class model(s) during the request handling phase, and generate a data structure with all kinds of information about the schema. This is used by templates in the View to customize the Javascript which is then sent to the browser. What the browser receives is essentially custom-written Javascript for that schema, but there's no knowledge of the schema. You can of course see the Javascript generated in the HTML source. You can also see the data structure I mentioned above by retrieving a path like /<db>/<table>/dumpmeta - this will return a blob of JSON which describes what LFB needs to know to write the UI for that table. I hope that helps, regards, oliver. - -- Oliver Gorwits, Network and Telecommunications Group, Oxford University Computing Services -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIwGs42NPq7pwWBt4RAtdEAKCwU+OLHu6QXgySNXjeO3HEZoc43gCePf5A n9/E4XgDgY8znq56uUUatBQ= =ZCZi -----END PGP SIGNATURE----- _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
