Comments on: Designer/Developer Workflow as a Common Goal http://scalenine.com/blog/2008/04/11/designerdeveloper-workflow-as-a-common-goal/ The latest about ScaleNine Thu, 28 Aug 2008 18:08:06 +0000 http://wordpress.org/?v=2.6 By: juan http://scalenine.com/blog/2008/04/11/designerdeveloper-workflow-as-a-common-goal/#comment-55258 juan Mon, 14 Apr 2008 21:55:22 +0000 http://scalenine.com/blog/2008/04/11/designerdeveloper-workflow-as-a-common-goal/#comment-55258 I still think there is still merging going on between Adobe/Macromedia in the way of applications. From what I'm hearing, there's going to be a much more fluid merging in CS4. As far as creating features for RIAs, I think there's more to it than a UI. I'd like to have a tool I can work with through every part of the process, from interaction diagrams, to wireframes, to interactive mockups, to final product. Each of those steps has their own integral parts that could be made much smoother if there was a tool to support and join those steps together. Of course, what's created would have to integrate with the development side of things too. I still think there is still merging going on between Adobe/Macromedia in the way of applications. From what I’m hearing, there’s going to be a much more fluid merging in CS4. As far as creating features for RIAs, I think there’s more to it than a UI. I’d like to have a tool I can work with through every part of the process, from interaction diagrams, to wireframes, to interactive mockups, to final product. Each of those steps has their own integral parts that could be made much smoother if there was a tool to support and join those steps together. Of course, what’s created would have to integrate with the development side of things too.

]]> By: RJ http://scalenine.com/blog/2008/04/11/designerdeveloper-workflow-as-a-common-goal/#comment-55236 RJ Mon, 14 Apr 2008 20:50:02 +0000 http://scalenine.com/blog/2008/04/11/designerdeveloper-workflow-as-a-common-goal/#comment-55236 What if Adobe made all of their apps a little more fluid? What if they could replace all of these apps with a single thing who had different views for different features? It seems like they already duplicate a lot of functionality - instead of duplicating more, let's just merge them all and give people different views for different tasks. That way you the super-specialized developer can customize it however you want. Just an idea - I'm not signing up to do this. :) What if Adobe made all of their apps a little more fluid? What if they could replace all of these apps with a single thing who had different views for different features? It seems like they already duplicate a lot of functionality - instead of duplicating more, let’s just merge them all and give people different views for different tasks. That way you the super-specialized developer can customize it however you want.

Just an idea - I’m not signing up to do this. :)

]]> By: Judah http://scalenine.com/blog/2008/04/11/designerdeveloper-workflow-as-a-common-goal/#comment-54741 Judah Sat, 12 Apr 2008 11:41:25 +0000 http://scalenine.com/blog/2008/04/11/designerdeveloper-workflow-as-a-common-goal/#comment-54741 Well said. I know I will get flack for this but I think it would be nice to have all these features in one program. Sorry Matt, hire more Flex developers. ;) Add the photoshop, fireworks or illustrator layers panel. Add premiere's time line. Add flash's filters. Add photoshop and illustrators selection and subselection tools. Add illustrator and flash drawing tools. Add flash's property inspector so we can have rich text editing in the FB design view. Add flash cs4 or thermo timeline effects. That or have Flex Builder host ps, ai, fw, fl plugins. So when you are in Flex and you want to edit a skin made in photoshop you can bring up a "photoshop" design view in Flex Builder with photoshop panels that won't mess up your layout. The reason I would say make an all in one Flex Builder tool is that every version of photoshop, fireworks, illustrator or flash will have to be updated to support the new features in Flex. Plus they aren't built for the layouts and containers Flex uses. Does photoshop support a constraint based layout? Do the designers even know what this means? What about horizontal or vertical layout or a mixture of all the layouts, absolute positioning, box layout and constraint, scale 9 etc? What about states and viewstacks? I'd rather have a designer use Flex Builder to design an application maybe pulling in assets from those other tools. Dreamweaver gave you a design view that it let you do what you want but it would not stop you from making a design that would break in different browsers. In the same way the design tools will not stop a designer from making a design that won't translate over to a Flex application. Flex Builder is constantly marketed as a "developer's" tool but it erks me to hear it described like that. To me Flex Builder is, as you described it best, a tool to create "...ground-breaking user experiences". It should support tools inherent to the creation of that goal. Well said. I know I will get flack for this but I think it would be nice to have all these features in one program. Sorry Matt, hire more Flex developers. ;) Add the photoshop, fireworks or illustrator layers panel. Add premiere’s time line. Add flash’s filters. Add photoshop and illustrators selection and subselection tools. Add illustrator and flash drawing tools. Add flash’s property inspector so we can have rich text editing in the FB design view. Add flash cs4 or thermo timeline effects.

That or have Flex Builder host ps, ai, fw, fl plugins. So when you are in Flex and you want to edit a skin made in photoshop you can bring up a “photoshop” design view in Flex Builder with photoshop panels that won’t mess up your layout.

The reason I would say make an all in one Flex Builder tool is that every version of photoshop, fireworks, illustrator or flash will have to be updated to support the new features in Flex. Plus they aren’t built for the layouts and containers Flex uses. Does photoshop support a constraint based layout? Do the designers even know what this means? What about horizontal or vertical layout or a mixture of all the layouts, absolute positioning, box layout and constraint, scale 9 etc? What about states and viewstacks? I’d rather have a designer use Flex Builder to design an application maybe pulling in assets from those other tools.

Dreamweaver gave you a design view that it let you do what you want but it would not stop you from making a design that would break in different browsers. In the same way the design tools will not stop a designer from making a design that won’t translate over to a Flex application. Flex Builder is constantly marketed as a “developer’s” tool but it erks me to hear it described like that. To me Flex Builder is, as you described it best, a tool to create “…ground-breaking user experiences”. It should support tools inherent to the creation of that goal.

]]>