Building a framework...
Posted: Wed Aug 16, 2006 9:09 pm
In response to the thread on Java, where feyd and myself were disscussing MFC, OWL, etc...also in regards to my other thread about CMS...
Basically I want to start development of my own CMS...but as always, not being paid is allowing me full control over how it is built
I'm convinced a full fledged template engine and DB abstraction is not a big enough deal to exclude it from a CMS application - modularity/portability I always favour, unless speed is a issue.
However, now my concern is (this is where Feyd's and mine convey comes in as MFC doesnt' follow any standard, it's dog meat sometimes) coding standards and conventions...
Deep down, they are critically important to me...I have a style which i've used for years and although could use upgrading, I feel it very important to follow a consistent coding style throughout an application. Here's the problem. TL and AdoDB lite may very well follow a coding standard, but it's different from my own and the function names are not quite what I would label them as.
I can't be bothered to sift through the code and change conventions, etc, comments and what not...
So I'm stuck at this road block...should I continue development on my own framework until it's complete (which could take a while as I have other things to do) or do I somehow bite the bullet and work with what I've got...
Refactoring code later as my own framework comes togather is *not* an option...I couldn't be bothered to muck with an complete application like that...
Silly question, perhaps as only I can truely answer this...I'm anticipating starting this CMS, but at the same time don't want a hodge podge of code libraries all with different coding conventions, standards, etc...
Interested in hearing comments, opinions, etc..
Basically I want to start development of my own CMS...but as always, not being paid is allowing me full control over how it is built
I'm convinced a full fledged template engine and DB abstraction is not a big enough deal to exclude it from a CMS application - modularity/portability I always favour, unless speed is a issue.
However, now my concern is (this is where Feyd's and mine convey comes in as MFC doesnt' follow any standard, it's dog meat sometimes) coding standards and conventions...
Deep down, they are critically important to me...I have a style which i've used for years and although could use upgrading, I feel it very important to follow a consistent coding style throughout an application. Here's the problem. TL and AdoDB lite may very well follow a coding standard, but it's different from my own and the function names are not quite what I would label them as.
I can't be bothered to sift through the code and change conventions, etc, comments and what not...
So I'm stuck at this road block...should I continue development on my own framework until it's complete (which could take a while as I have other things to do) or do I somehow bite the bullet and work with what I've got...
Refactoring code later as my own framework comes togather is *not* an option...I couldn't be bothered to muck with an complete application like that...
Silly question, perhaps as only I can truely answer this...I'm anticipating starting this CMS, but at the same time don't want a hodge podge of code libraries all with different coding conventions, standards, etc...
Interested in hearing comments, opinions, etc..
