On Dec 7, 1:07 pm, Jeff Coughlin <[email protected]> wrote: > It is an awesome feature, but forcing this functionality on all clients for > all their existing image use is probably a bad idea.
Lets assume there are no bugs and we implement as currently described. Our driver to upgrade the formtool is in large part a reaction by several of our larger clients to the current formtool. It's still a bit buggy, and is a little bit awkward. Apart from the crop ui, there is a considerable amount effort going into making it just "make more sense". So the upgrade targets a variety of outstanding issues, inline uploading (a major win for our users at least), and hopes to simplify how multiple image properties bind to a single source image. The changes to the formtool UI are progressive. There is nothing dramatic about the ui change except swapping the drop down of crop options for an actual cropping tool. The drop down of crop options itself was a progressive enhancement. Lets hold judgement on the merits of it going into the maintenance branch until its finished, then we can revisit whether or not its a bad idea. > Might I propose just making it a new setting/switch that a developer can > chose to activate per cfproperty? > Example: <cfproperty type="image" ftType="enhancedImage" .../> > I think making it an ftType value is probably the better option because the > type is still image, but the formtools have changed. Developers will always be able to copy the old formtool into their projects and continue with the old formtool for the forseeable future. It's really an all or nothing affair -- the old and new formtool for image are not compatible. Keep the feedback coming! GB -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
