— DRAFT —
[2014-03-01: the new ui]
Data-Configuration Generator is a program that needs some refurbishment before I shine more lite on it. It is basically a CODE/TEMPLATE (BINDING) GENERATOR intended for binding an application’s memory to a supported database-technology such as MySQL, SQLite, Microsoft Access. Currently (not publicly) there is support for SqlServer and Access databases. I would like there to be little to no bugs and for it to be idiot proof for its initial release (let-alone an imaginary competitor rushing me).
[Added Paragraph: 2014-03] THE MAJOR GOAL OF THIS APPLICATION IS TO UNIFY BUILDING-BLOCKS AND TEMPLATES THAT CAN BE USED TO AUTOMATE OR GENERATE PLATFORM/LIBRARY SPECIFIC CODE IN JUST ABOUT ANY REALM IMAGINABLE.
Replicate or write your database-scheme (tables, views, etc…) in XML or the UI and from that point you can generate SQL and DATA model source-code with the provided templates or write your own templates.
This project will be added to the public domain (on github) in time, however not in the immediate future due to the need for consolidation and migration of other projects, and this one.
- The UI (xaml code-behind) still needs to be re-written or cleaned up.
- All in all the core of this project is a trivial transclusion-like engine.
- These screenshots featuring Fluent-Ribbon Control Suite (for NET45) experimental metro theme.
- Currently each time you preview your code in the template-editor panel, that’s it. You have to copy/paste into your source-code. It would be a lot nicer if you could have a ‘project’ specifying multiple schemas/taragets (like ‘mycsharpmodel.cs.tpl’) so in stead of copy/paste, you can just generate right in to your targeted models.
- Fringes in the UI featuring ICSharpCode’s AvalonEdit to help design and test templates with syntax-highlighting and the simple CTRL+SPACEBAR code-completion semantic.
- Allows for the elaboration of (our native xml) database schemas.
- [testing] Import database schema information from existing data sources: sqlite, access, sql-server. Note that usually a layer of user-intervention is required due to the nature of OLE/AutoTypes used by COM/OLE (Microsoft’s System.Data internals).
- [wip] see: distribution of multiple tables per view.
- Primary-Key Element Tags(source)
- System.Cor3 & System.Cor3.Data
- (perhaps more)