So I'm deciding to write a framework. I've written one at work, and it does pretty well, but they don't pay for me to play, only to continue development of what I've written there already. So instead, I plan on writing my own framework from scratch. This website is running off of Community Server. It's an ok framework, but I would certainly have coded it a lot differently. Needless to say, I want to build a framework that provides a robust library, but also leaves room for a lot of flexibility for a developer to extend the code; as well as be flexible across multiple platforms and back end data servers. It really isn't all that hard. So to start, I will be releasing individual namespace libraries, which by themselves can be used individually, but as a whole can be considered a robust document management application framework.
As it stands right now these are the following namespaces I plan to build:
Just because I think it's a cool name, we'll call this project Andromeda (yes, I just saw the TNT movie series) lol
| Andromeda.Core | Will contain all base classes; those classes that will be used throughout other namespaces. |
| Andromeda.Data | Will contain all data access classes for accessing ADO.net easily, but also interface classes for access to other database systems besides those out of the box systems of ADO.net. |
| Andromeda.UI.Forms | Will contain form classes that provide built in objects and properties for the framework developer. |
| Andromeda.UI.Controls | Contains several control classes for custom web controls. All will be Ajax enabled. |
| Andromeda.Configuration | Will contain classes relating to configuration files |
| Andromeda.Security | Contains classes and interfaces for security and permissions management. |
| | |
Share this post: 
|
|
|
|
|
|
