|
that
was me too, but now i pretty much exclusively use dwmx;dont forget however you
can setup studio as your external code editor and set auto-reload on both
products so you just can alt-tab between the code view and design view. been
able to do that since cfstudio 4.5 and DW4....
look
at custom server behaviors... they rock snippets and they build dialog boxes for
you for arguments. the solution for these in cfstudio was vtml files, def a pain
in the butt. i still use snippets to, i always did in cfstudio, but im not going
to throw the baby out with the bath water.... i use dwmx to generate stubs of
code which i enhance, so i get a bunch of benefits from that too. for now i'll
deal with the fact there are no keyboard shortcuts for snippets in dwmx. they'll
add that feature for sure in the next release.
make
sure you have the _expression_ panel extension for dreamweaver. it rocks and it
provides an _expression_ dialog for building dwmx extensions, so you can quickly
learn how to customize your toolbars and the insert panel.... just like we could
do in studio... a little more effort, but for the basic needs like a
<cfdump> toolbar or insert bar item, worth the effort. i dont have a link
to the extension but will gladly email to anyone who wants
it.
reconsider how you are going to build your applications and code reuse
components in your applications:
if
you are still using cfincludes for headers and footers, i would urge you to take
a day and look at dreamweaver templates. in dwmx, templates are so awesome. you
can now create templates within other tempaltes and provide template properties
and use template expressions to conditionalize the display of content, wiothout
having to "open" up areas as editable regions. yes this is DESIGN time
_expression_ resolution, not run time, but it is very powerful none the
less. sure the code is duplicated and you'll now have a dependency on using
the dreamweaver tool, but you already have a dependecy on mm products once you
choose cf or whatever. you get a single point of maintenance (change the
template and all instances of templates are updated accordingly) and it plugs
right into contribute for maintaining design control over the content
managers. and remember with templates, the code is replicated but it is easy to
have hardcoded links, etc... cause dreamweaver will update links throughout the
site if you use the site files window to move files....
along
these same lines, although certainly less palatable for us CFers, look at some
of the code generation features of dwmx. i use "record insertion behavior" all
the time. it generates the self posting form and the query with the SQL insert.
if i am creating a cfc wrapper to my DB table, i just cut and paste the
<cfquery it generates into my cfc, modify the code to work with a struct ISO
the form scope, as well as beef up the code itself a bit, and then drag the cfc
method for the table wrapper, or a workflow facade component into the cfm page.
the entire html form is created for me and then i can just take care of my
validation rules. i litterally bang out applications so much faster and the
clients love the fact it costs so much less money.
even
in complex applications, there are often "areas" of functionality that are so
simple that using the code generation of dwmx makes development fast, cost
effective, easy to maintain and one other thing.... developed in a "Dreamweaver"
standard. relatively non sophisticated cf developers can do maintenance without
having to learn a complex framework....or how about "the new guy" who has to
maintain the old applications.... now he/she doesn't have to deal with your
"personal flare" in the code. its standardized. i think at least being aware of
this kind of functionality is worth the effort. it is like to improve over time
and become more and more reliable.
|
<<attachment: winmail.dat>>
