Cosmin Bucur wrote:
Leonardo , I guess you bring up some very valid points , that are
irrelevant in my scenario ,. The applications i am trying to build
are ment to replace desktop apps , that don't have the users used to
bookmarking or pressing the back button . For my purpose bookmarking
and the back button should not be allowed , all we care is that the
application will work out of the box on any computer without needing
an install or any system update .
This is rather an endless debate. For example, typical newbie question:
"if back / forward buttons are not supported, then why are they there?".
Sometimes, disabling these buttons shows laziness. I know that's not
your case (don't get offended), but many times the buttons are disabled
because the programmer can't think of a way to make them work reliably.
For a typical non-ajax webapp is as simple as using Redirect-After-Post
and tokens.
As an example, I have a bank account that can be accessed online, but
the web-interface has so many limitations, it feels very awkward. I'd
rather use my web browser like it was designed to be used.
Remember, in software, all of those requirements that would never show
up, will! One day, a customer will ask for a bookmark on his complex
query he just did. Or he will say "why can't I go back to the previous
page? It had important data I don't know how to extract again!".
Ideally I'd like to see both aproaches supported , allthogh I'd like
to know if what I am going for seems stupid and unreasonable , or not
worth supporting .
As a matter of fact, your request applies the same for single and
multiple pages application. Our discussion is just for fun, because it's
using nested components is needed for both.
As for the demo app yea ... programers are needed , and nothing i can
say there since i've been promissing to help more for months and
months yet theese days if i can get one hour of coding on my own stuff
, away from the time I waste on redundant biz processes , I consider
myself happy at the end of the day .
Your app is a large test area for Tacos, and the test cases are the way
to reproduce the bugs you find in your app. At least it is going to be
that way until we have a more stable framework (though you have to
acknowledge Tacos is much more stable now that it is in beta).
Trust me, doing the small page test cases (using Selenium and the
examples in the demo) is *very* helpful. And it just takes a couple of
minutes ;).
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Tacos-devel mailing list
Tacos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tacos-devel
