Ed Leafe wrote:
> On Feb 27, 2008, at 8:45 AM, Paul McNett wrote:
>
>> Eval'ing them would make them strings when they are strings, ints when
>> they are ints:
>>
>> eval("'201-555-1234'") -> "201-555-1234"
>> eval("201-555-1234") -> -1588
>> eval("23.5") -> 23.5
>> eval("'33'") -> "33"
>> eval("None") -> None
>> eval("'None'") -> "None"
>
>
> The issue, though, is that this would force people to enclose every
> single string (which will be the majority of entries, at least in my
> experience, in quotes. IMO, it is exceedingly poor design to require
> extra stuff for the default case.
OTOH, a simple solution that provides for all cases can be a good
starting point.
> This may be a specific solution for the Class Designer use cases, but
> in every situation I can think of, the options entered in the dialog
> will all be the same type. Adding a selector to specify the type that
> the entries should be might be a workable solution.
You'd have to allow None in all cases. Anyway, I think saving the
strings to be eval'd in the XML should be considered, even if you aren't
showing the extra quotes in the designer.
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
