> My thoughts are that it is a good thing to discuss these things, > specifically in a forum that MM folks are attentive to, so that they can see > where the needs for improvement for development tools support for their > application servers are at. Knowledge and idea sharing are also good things > :)
Definitely! To be sincere, while everyone has one or more pet features still missing in DW (code collapsing, expression builder or whatever), I strongly believe that Code Trust is the number one issue (followed by performances) that affect DW nowadays and prevent a broader adoption among coders. The way DW's developing team has tried to solve so far is to build a complex heuristic and try to ensure Code Trust on a case by case basis. They are very committed to it, between MX, 6.1 and now 2004 they squashed a terrific amount of bugs but, in my opinion, they keep fighting the alligators instead of go ahead and clean up the swamps... I admire their commitment and restless efforts, but they will never be able to cover all the potential exotic combinations of code we can throw in DW. The issues related to XSL or PHP/Smarty are an example; how long we can keep going on, discovering one bug at time, report it to the DW's team and wait for next release? It's an endless, frustrating, effort. What we need is a way to completely prevent DW to mess around with the code, it doesn't matter if DW try to do it for legitimate reasons, like fixing a path or improving rendering in Design View, there must be a way to stop all of this. If the price to pay is to disable some features (translators, SBs or even more), I am more than willing to pay for it. There must be a way to enforce a "Code Trust Mode" that ensure 100% Code Trust for people that need it. The implementation details may vary, from turning it on in the application settings, on a session basis or a page basis. Whatever would be just fine for me, there is no need to have it turn on by default either; just keep the traditional DW users happy but leave an option open for coders. Right now the "Code Rewrite" setting in DW are just a joke... It's clearly something that would deeply affect DW's architecture but I don't see any other viable and effective solution. Sorry for the long post, people in the DW community are pretty much aware of my opinion on this, I just hope it help fellow CF developers getting a better picture ---------------------------- Massimo Foti Certified Dreamweaver MX Developer Certified Advanced ColdFusion MX Developer http://www.massimocorner.com/ ---------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
