Well, that just takes the wind outta my SAILS. Is there a way we can salvage this and start using it? What if we start trying to do use this as primary documentation, where it's appropriate? I'm going to start this week and report back. There are lots of places where it's important to show transitions that flat screenshots just can't convey (easil), where an interactive prototype fits the bill. Dave Malouf has been saying this, like, forever.
On our conversation about this on Twitter, he said that in a similar scenario with MS Expression (no integration with Visio), he found that this lack of round-tripping didn't matter in the end. Which makes me say, why not take a risk and start prototyping in Catalyst? If I'm going to do that longer term, though, we're gonna need some better drawing tools in there-- an Alignment and Spacing panel, for one, and tool behavior that more comprehensively matches Fireworks, or, hell, any other Adobe app. On that note, I wonder how much longer we need to wait until Fireworks CS5? Less than a year [1]? A boy can dream, can't he? - Nasir [1] I'm conveniently forgetting how recently CS4 came out. Try and not break it to me; it might break my heart ;-). ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
