Hi Adam,
This might not be tenable from your perspective, but is there any chance we can run multiple versions at the same time?
I realize there are some potential problems with this scenario (tag editors/libraries will change as the product
matures, you won't want to support multiple versions, etc.)
However, there will be times where a client will want to re-visit an app after it has been in production for a long time
and make additions/enhancements that will not necessarily warrant a full version upgrade. This has happened many times
in my experience and has happened at least once since I have been using Plum (beta to version 1). A lot of folks may
work on more than one app simutaneously, one in version 1, and maybe start that new one with the new version etc.
If you are an old hand, no big deal, you can probably build what you want without the old IDE by using the tags. Newer
users might have problems. And of course, with the new version comes a new set of tag editors/libraries, and that is a
problem in itself. But I have built Plum tag libraries for Dreamweaver and PrimalScript, and it might be worth it to be
able to use 2 different editors to be able to work with two different versions of Plum simultaneously.
Your thoughts?
Jeff
Adam Churvis wrote:
How do all of you feel about migrating between Plum V1.0 and future versions
of Plum?
Before you answer this question, please consider the following:
1) Because of the extensive nature of the Plum Framework, building in
backward compatibility makes the product slower and the code significantly
more cumbersome to navigate and understand, so backward compatibility is a
non-starter.
2) Not worrying about backward compatibility enables us to concentrate
entirely on performance, better code architecture, easier to use elements of
the Plum Framework, etc.
3) Migrating a Plum V1.0 app to a later version that has lots of changes and
new capabilities should be relatively straightforward if you haven't
modified the framework (which includes the custom tag library). Basically
you'd manually migrate your Environment.cfm customizations and any
instantiations of your own components in Global.cfm to the new Plum
Framework files of the same names, and that should be that. That's the
goal, anyway.
As a side note, the new custom tag library will have *much* better
formatting flexibility and capability (no more table-based markup of fields
and labels -- all CSS-based), DatabaseBlocks.cfc is going away in favor of a
better code architecture with specific methods, the whole
tablename_columnname requirement goes away, and much more. No estimated
release date just yet, but we're putting time in where we can.
Also, we should have the new Plum Service that automatically CF_2CFMODULEs
your code as you work in Beta within the next two weeks.
Respectfully,
Adam Phillip Churvis
Member of Team Macromedia
http://www.ProductivityEnhancement.com
Download Plum and other cool development tools,
and get advanced intensive Master-level training:
* C# & ASP.NET for ColdFusion Developers
* ColdFusion MX Master Class
* Advanced Development with CFMX and SQL Server 2000
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
