We openly invited participation on this project over a year ago and even participated in a pod-cast with Matt Woodward to talk up the invitation. Long and short of it; nobody replied. Now, I've seen a few complaints in the forum for the project calling for cfcPowerTools to be removed because the developers aren't supporting it anymore. Hate yo break it to ya, but we were pretty clear that Tom and I were stepping back from it and openly inviting the community to step up... apparently either we didn't say it clearly enough or you weren't listening. regardless, even the individual(s) who complained about the us not actively supprting the project didn't even step up to the plate. So, where does that leave us? Well, it's up to you my friends... If you like powertools and you want to belly up to the bar then you are welcome. Otherwise quit the griping and suck it up... put up or shut up really. Ya, ya, I can hear it already... Not interested. If you're offended then I suggest you take a good look at yourselfas to why. If you're not offended and want to wade in then welcome to the club. So, what is cfcPowerTools? Well... cfcPowerTools is a productivity tool used to jump start your development effort. cfcPowerTools is a code generator that offers the following: * generate CFCs from database table* generate database table from CFC * batch generate CFCs from multiple database tables * generate HTML, FLASH, and XML data entry forms * supports round trip editing * getter/setter generation cfcPowerTools is highly scalable. cfcPowerTools is built using templates. You can modify the templates packaged with cfcPowerTools, or generate your own. cfcPowerTools comes with the following templates out of the box: * Model Controller * MACH II * Concrete * Simple * Default cfcPowerTools makes you more productive. cfcPowerTools produces consistant, reliable, predictable, and documented code. Productivity features: * Component Doc View - cfcPowerTools upsizes ColdFusion's component doc view allowing you to interact with your CFC. From the component doc view, you can add, edit, and delete methods as well as view methods. * Code Behind - you can toggle between the meta data view for a cffunction and the actual cffunction code. * ColdFusion Admin - cfcPowerTools utilizes your ColdFusion administrator login to secure access to cfcPowerTools functionality. * Managed Code - you can designate section(s) of your code as managed code. cfcpowerTools will only regenerate the managed code sections, ignoring the rest of your code.
I know. I know. "This project should be removed because it's dead" Or so said the message I go from someone one day. Well, its not dead as long as people are downloading it.
What is dead is improvements to the internals of the app. But, since Ray has enabled SVN users here's we can now add people as contributors to CFCPowertools.
If you're interested in contributing let me know. I'll add you.
Here's an invitation. We (that is Tom and I) would like to extend an open invitation to interested developers out there in the community to wade in and help develop several features for cfcPowerTools.
Well, we've had several requests that cfcPowerTools support mySQL. This is very 'do-able' in that cfcPT was designed from the ground up to support multiple database types. We just happen to have picked MS-SQL 2000/2005 as we know it very, very well and 99% of the clients we work with use it too.
That being said adding new database support to cfcPT is a case of studying the files in '\components\core\databases' and chiefly 'mssqlserver.cfc' as a way to become familiar with how cfcPT interacts with the database.
So, here's the initial list for database support:
1. Support for mySQL 2. Support for PostgreSQL 3. Support for Oracle 4. Support for Sybase 5. Support for PointBase
We'd like to see if there are developers using cfcPT along with frameworks like Mach 2, MG, FB5, (etc) and if there are any additions to cfcPT that would make it more useful.
An open invitation to suggest other improvements to cfcPT that would make the tool better in general.
We're here and we're listening and we'd love to have your active participation.
We do maintain a working copy of PT in a separate instance of SVN and anyone willing to participate will need to be set up for access in that SVN repo since the one here at RIAForge only permits read/write to the project owner; not a biggie...
Right then...on with the rest of the day.
No huge changes, some tweaks to smaller things and a few minor issues looked into.
We've had (we would be Tom and I) [Ray, let us know when we can have co-authorship on RIA forge]...now where was I? Oh yes; we've had some excellent feedback on the latest build and on PT in general. It can be a dense tool at first glance, but the magic comes once you spend some time working with it and seeing how the machinery works.
The PT machinery is a really solid example of a well coded, complex application. The code reads like poetry.
Working with Tom, Nolan, Phillip and Dan is always a pleasure and while PT is the brain-child of Tom, it's also the product of a great deal of creativity and serious thought.
We (not the Royal 'we') really think that making PT an opensource project was and is the best thing for the app. and while we (again, not the Royal 'we') as a group still maintain control of the builds, we're looking for active participation in the development and refinement of PT.
We're looking for code poets.
So, if you're into PT and you'd like to add to the epic poem that is the machinery of PT let us know.
We'd also really like to know how people are getting on with PT in various environments and how you're using it.
Well, that's it for now and remember folks; code safe.
Tom noticed that the code being produced from some processes wasn't xhtml compliant. It is now. ;)
So, please update from SVN or download the new build as a zip. Let us know how things are looking and if you have any ideas that would make PT a more beautiful thing.
We've been working on some of the little nagging issues in the CRUD generators and supporting files. The new build is in SVN and in the zip file as well.
In all honesty, the best way to keep a working copy of powertools (PT) is to use SVN. So, if you've already downloaded it and you lke it I encourage you to use SVN going forwards.
Oh, and welcome to the new blog. We're moving our communications efforts to RIAS forge as a 'one stop' thing rather than maintaining the blog on the old site.
The demo etc. will be there for a while.
Byron and Tom