[ADK-V4CC 0004885]: VField value returns not an object when the field is boolean

Ruslan Zasukhin ruslan_zasukhin at valentina-db.com
Wed Apr 28 01:57:37 CDT 2010


On 25/4/10 2:13 PM, "Erne" <ernestogiannotta at tiscalinet.it> wrote:

Hi Erne,

:-)  Thorsten have point the same in chat.

I have redesign this names 2 days ago.
Committed to SVN already.

Only I have choose more short names, exactly like class name

    mediumValue
    setMediumValue

    umediumValue
    setUMediumValue

...


> thanks always for your kind attention.
> 
>> !!! VField.value renamed to  VField.valueAsObject  !!!
> 
> Let me just make some observations about namings in V4CC
> 
> We have in the VString header:
> 
> -(NSString*)stringValue;
> -(void)setStringValue:(NSString*)inNewValue;
> 
> and in the VLong header:
> 
> -(int) value;
> -(void) setValue:(int) inNewValue;
> 
> What about having subclasses return always appropriately named values VString
> style, i.e.
> 
> -(BOOL)booleanValue for VBoolean
> -(NSInteger)integerValue for VLong and all signed numeric values
> -(NSUInteger)unsignedIntegerValue for VUlong and all unsigned numeric values
> (btw how can you currently fit an unsigned long into an int if it's too big?)
> -(NSString *)stringValue for VString and all test fields
> -(NSData *)dataValue for VBlob
> 
> etc... and just leave value to super VField class like this
> 
> -(id)value  returning always an object representation of the field's contents
> 
> 
> BTW
> 
> mmm... I really don't understand how picts are handled here :-(
> why can't we have some
> 
> -(NSImage)imageValue for VPicture?
> 
> 
> 
> Well, I talked too much as usual... :-)
> thank you all for your patience.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]




More information about the Valentina mailing list