re: The Changing Picture of Code Generation

liviu — Thu, 27 Dec 2007 09:24:04 GMT

the languages and tools hide the forest behind the trees. we need ane expressive rule language, a powerfull ide and the rest are plugins for code generation...

This is visionary...but imperative.

re: The Changing Picture of Code Generation

Joseph Baggett — Wed, 17 Oct 2007 16:51:40 GMT

I've read your book, interesting approaches and terms that you have defined. I have not tried going down the brute force code generation scenario though. I've been using CodeSmith and CodeBreeze to understand the different paradigms and philosophies on what we as developers should have access to when generating and/or where we store information to be generated.

I'm still trying to find more ideas on generating the web interface though. Using XSLT has been more troublesome for me, even though it does sound like the best principle to use to meet changing business requirements. Using XSLT is that it seems hard to maintain, i.e., applying style sheets, etc. and I have the feeling like I shouldn't have tried to generate the UI using this approach at times. I've tried using custom web controls, but I have been generating only generic editors with validation that is not very customizable other than giving the user the ability to modify properties.

I'm still looking for that one last step in my mind that does code generation at the UI level and makes the maintenance easy and flexible enough to meet changing business requirements. Maybe I'm approaching the XSLT generation in the wrong way... I would appreciate any more ideas that have come across your mind. Thanks for writing the book Kathleen.