MODx basic archtecture question

I am used to, and would like to continue, doing my development with eclipse with integrated editors, version management, and bug tracking. Basically, I would like to avoid (if possible) any steps requiring hand coding within the MODx environment other than filling in content for TVs. I would also like to avoid copy/paste of code into the MODx environment. For any PHP, JS, or xHTML coding required I want to access the files directly through eclipse but have tried and failed to understand the file structure used by MODx. For instance, where is chunk code stored? Is all snippet code located in the assets/snippets directory? Is all javascript in the various *.js files strewn throughout the assets and manager directories?

I guess my biggest concern is that some code used by MODx may be storred in DB tables or otherwise modified by MODx when it is entered through the MODx manager interface.

On a related note... rather than copy pasting code into the MODx editor interface, is it possible to just point to a file location and say "use this"?

Thanks in advance,
joe

MODx managed content is in the database, period. In the future we may enable direct protocol access to the database managed content (via FTP, WebDAV, SVN, etc.) so developers who want to edit the content through local client on their desktop can do so without limiting the ability for manager users to edit it through the manager interface itself. One of the major points of a content management system is to enable web-based editing of it’s resources, and so without this database-managed content, you might as well be developing a custom web site with PHP, XHTML, JS, and Eclipse or Dreamweaver, or whatever your tool of choice is.

That said, I include all my snippets as external PHP files and develop them in Eclipse (i.e. all my snippet content in the database are one-line consisting of a `return include(...);` or `return include_once(...);`, depending on what I’m doing). The css and js files are not an issue, as I put those also in the file-system and link to them from my database managed template. That leaves the (X)HTML, which I copy and paste in the manager or quick-edit happily, at least until someone pays me to develop the protocol access... or someone develops it out of the kindness of their heart for the rest of us to enjoy...