Hmm… I didn't think of either of those. I knew I was missing something obvious! A case of missing the wood for the trees, I think. :-)

Thanks, Colin and Steve! 

/Carolyn

On Nov 22, 2012, at 4:51 AM, Steve Clarke <steve@sclarkes.me.uk> wrote:

I think that discussions about validation of user entered data need to consider how you provide feedback to the user on what happened.  

Have you thought about how validation errors are integrated with Cocoa frameworks?  I don't know anything about Virtus or SmartProperties but I would be surprised if they buy you anything when used in conjunction with a Cocoa user interface.  Cocoa provides formatters.  Take a look at "Text Field with Number Formatter" in the Xcode controls.

Steve

On 22 Nov 2012, at 06:47, Colin Thomas-Arnold <colinta@gmail.com> wrote:

What happens if you use BOTH attr_accessor and attribute - the first for the IB outlet, and the other for validation. Just a thought. 


On Nov 21, 2012, at 11:08 PM, david kramf <dakr.012@gmail.com> wrote:

"Basically, I need to make sure that when I ask for an integer, I get an integer. And when I want a string - I can reject anything but strings."
Can't you use Ruby services like is_a? to force it ?
Thanks, David Kramf
On Nov 21, 2012, at 10:04 PM, Carolyn Ann Grant wrote:

Basically, I need to make sure that when I ask for an integer, I get an integer. And when I want a string - I can reject anything but strings.

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macruby-devel
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macruby-devel