Well that's just cumbersome, and actually not the point of my discussion. <div>I rather discuss about the ways we could use RSpec to create an application based on RubyCocoa (for example), instead of discussing about what types of software can't work on the web, alright?
<br><br><div class="gmail_quote">On Nov 17, 2007 10:51 PM, M. Edward (Ed) Borasky <<a href="mailto:znmeb@cesmail.net">znmeb@cesmail.net</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">Matthijs Langenberg wrote:<br>> Hello everybody,<br>><br>> I've been using RSpec as a tool to create web applications for some time<br>> now, in Rails, and using plain Ruby with WEBrick as well. The tool suits
<br>> my needs and the story runner is great.<br>> Now there are things that aren't solvable on the web, you'll need a<br>> _real_ desktop application for those problems.<br><br></div>Well ... given a large enough monitor and a minimal set of toolbars and
<br>menus on your browser, I'm not convinced there's much of a difference<br>between a "desktop" application and a "web" application from the point<br>of view of a user sitting at a KVM portal. Of course, there is over a
<br>decade of convergence between the two user interfaces, so that's not a<br>great surprise. What do you think you couldn't do with a browser and a<br>web application framework/database running on the same machine as the
<br>browser and contacted via "localhost"?<br><br>_______________________________________________<br>rspec-users mailing list<br><a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/rspec-users" target="_blank">
http://rubyforge.org/mailman/listinfo/rspec-users</a><br></blockquote></div><br></div>