Comments on: Going backwards with Flash http://www.cruciallimit.com/blog/43/going-backwards-with-flash/ Rants and Commentary about Flash/WebDesign/Motion Graphics by Crucial Limit Thu, 02 Sep 2010 14:18:49 -0700 hourly 1 http://wordpress.org/?v=abc By: Maegerman Philippe http://www.cruciallimit.com/blog/43/going-backwards-with-flash/comment-page-1/#comment-11049 Maegerman Philippe Tue, 26 Dec 2006 16:44:58 +0000 http://www.cruciallimit.com/blog/?p=43#comment-11049 The site is in flash, when I navigate from a section to another, I can use the back and forward button from the browser The site is in flash, when I navigate from a section to another, I can use the back and forward button from the browser

]]> By: Crucial http://www.cruciallimit.com/blog/43/going-backwards-with-flash/comment-page-1/#comment-610 Crucial Wed, 12 Apr 2006 12:56:42 +0000 http://www.cruciallimit.com/blog/?p=43#comment-610 @Maegerman Philippe - that links takes me to a page that links me to a hybrid page, I don't see the flash/backbutton integration. Where is it? Thanks for the feedback! @Maegerman Philippe – that links takes me to a page that links me to a hybrid page, I don’t see the flash/backbutton integration. Where is it?
Thanks for the feedback!

]]> By: Maegerman Philippe http://www.cruciallimit.com/blog/43/going-backwards-with-flash/comment-page-1/#comment-606 Maegerman Philippe Wed, 12 Apr 2006 08:18:17 +0000 http://www.cruciallimit.com/blog/?p=43#comment-606 Check also http://www.yourpsp.com, very good implementation. So far it's the easier I found. Pim Check also http://www.yourpsp.com, very good implementation.
So far it’s the easier I found.
Pim

]]> By: Crucial http://www.cruciallimit.com/blog/43/going-backwards-with-flash/comment-page-1/#comment-580 Crucial Sat, 08 Apr 2006 17:13:28 +0000 http://www.cruciallimit.com/blog/?p=43#comment-580 I couldn't agree with you more JD, the back button issue definitely seems to mean something different to everyone. Having said that Macromedia did make an attempt at letting the developer/designer of the app decided what is and is not a history event when they exposed the anchor functionality. The point I was trying to make when I said "fix the back button" was more along the lines of making the anchor solution a bit more usable for sites that are much more object oriented and non-linear. Sites that exist on one frame of the timeline and have much of the functionality and page states wrapped up in classes don't benefit from the anchor solution. Articles upon articles surrounding Coding best practices, OOP design, Flash for eCommerce, etc.. all suggest that code be more modular and less timeline based. These are the sites that also usually cater to the masses and have more users of all experience levels visiting the product, using the back button, loosing any input they may have given the app and have to start over when they hit that back button expecting to see the last noticable page state. The back button should not be a crutch, or used as an undo...I agree...however there should be a consistent way to allow users to go back and forth (if they so choose) using the back and forward buttons while they learn the UI. I'm also not trying to put any blame on Macromedia/Adobe's shoulders because this problem exists, only that this would be a feature that could be used to make Flash apps, RIA's, and eCommerce sites more "usable" in the eyes of not-so-advanced users, business owners and customers. This is a feature request/enhancement if anything :) Thanks again for the feedback! I couldn’t agree with you more JD, the back button issue definitely seems to mean something different to everyone. Having said that Macromedia did make an attempt at letting the developer/designer of the app decided what is and is not a history event when they exposed the anchor functionality. The point I was trying to make when I said “fix the back button” was more along the lines of making the anchor solution a bit more usable for sites that are much more object oriented and non-linear. Sites that exist on one frame of the timeline and have much of the functionality and page states wrapped up in classes don’t benefit from the anchor solution. Articles upon articles surrounding Coding best practices, OOP design, Flash for eCommerce, etc.. all suggest that code be more modular and less timeline based. These are the sites that also usually cater to the masses and have more users of all experience levels visiting the product, using the back button, loosing any input they may have given the app and have to start over when they hit that back button expecting to see the last noticable page state.

The back button should not be a crutch, or used as an undo…I agree…however there should be a consistent way to allow users to go back and forth (if they so choose) using the back and forward buttons while they learn the UI. I’m also not trying to put any blame on Macromedia/Adobe’s shoulders because this problem exists, only that this would be a feature that could be used to make Flash apps, RIA’s, and eCommerce sites more “usable” in the eyes of not-so-advanced users, business owners and customers. This is a feature request/enhancement if anything :)

Thanks again for the feedback!

]]> By: lessrain blog » Blog Archive » Flash: Back Button and Deep Links Topic http://www.cruciallimit.com/blog/43/going-backwards-with-flash/comment-page-1/#comment-579 lessrain blog » Blog Archive » Flash: Back Button and Deep Links Topic Sat, 08 Apr 2006 16:32:31 +0000 http://www.cruciallimit.com/blog/?p=43#comment-579 [...] Other articles: - Going backwards with Flash (Via cruciallimit blog) [...] [...] Other articles: – Going backwards with Flash (Via cruciallimit blog) [...]

]]>