> Incidentally, the opinion of the RIA devs where I am is that Flex is
> only really any good for prototyping.
That's silly. That's not to say, though, that Flex in general doesn't have
another year or so to go through development, spit and polish. But it's just
the nature of the biz.
> The final application still need to be coded in ActionScript to allow full
> control over things like video elements.
Don't know what that means. There's no "level" or "stage" where one has to
automatically resort to AS. There are places (rather few actually) where
it's either more efficient or plain mandatory to work in AS. Again, the app
is evolving. But that's not unexpected.
The point I was making between Axure and Thermo is that the former pretty
much assumes design and development are separate and won't need to be
bridged. Thus your penny never dropped.
Thermo assumes it all starts or can start with design and continue under
design leadership without a mandatory layer of translation and ambiguity
Thermo is thus more subversive of the balance between design and development
where as Axure doesn't even try. That of course doesn't mean Axure doesn't
have a role to play. But if you wanted to elevate design which one would you
choose 18 months from now?
If it didn't, you'd be out of a job.
IA Summit 2008: "Experiencing Information"
April 10-14, 2008, Miami, Florida
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments
Searchable Archive at http://www.info-arch.org/lists/sigia-l/
Sigia-l mailing list -- post to: Sigiaemail@example.com
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
Received on Fri Nov 02 10:42:22 2007