On Dec 12, 2005, at 8:48 AM, Leonardo Quijano Vincenzi wrote:
You were speaking of a compiler regarding this though, not a unit
test. So currently you're using Tapestry without compilation OR
unit tests for your fragile expressions in your templates. So
you've got neither. Hmmmm.
As a matter of fact Tapestry *is* hard to test. But maybe I just
need to investigate a bit. And yes, it is a point of risk in my
application, that I'd like to see solved from a compilation point
of view. I just wonder how...
Compilation isn't the key though. Testing (not just unit testing) is.
I encourage you to check out the unit test facility that comes
with RoR then. Spend a week building a RoR app, not the hyped 10
minutes. Dig in and do some unit tests for the functionality
you're building, testing your actions, your business logic,
everything. Cleanly. This is not even comparable to the best of
breed ways of doing this in any Java application using any of the
top frameworks, I assure you.
Provide me a good real application example that use RoR and that's
not a toy, and we can talk. I'm always willing to learn new things ;)
There are several listed on the left sidebar here: http://
www.rubyonrails.com/ and substantially more listed here:
http://wiki.rubyonrails.org/rails/pages/RealWorldUsage
Not a toy?! Awww, that's no fun. The world is our toy - let's play.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
