[rkward-devel] typo: type or types?

[meik michalke]

hi,

am Mittwoch 28 September 2011 (09:47) schrieb Thomas Friedrichsmeier:
> naturally, this should be corrected. But I simply suggest to delay the fix
> for another while (at least until after 0.5.7). Then, we will have some
> time to experiment with a few concepts.

ok, it obviously didn't hurt anyone in the past.

> True. However, what I'm worried about is cases, where developers _think_ a
> certain restriction makes sense, but in reality it is too strict, and
> prevents the user from doing something absolutely "legal".

my guess would be that in such cases users would file a bug report if there's 
something really wrong.

i totally get your point too, though, that's why i meant we probably can't 
solve it generally for all cases. because if users can easily feed nonsense to 
functions and *then* file bug reports because they get errors (of course), 
that's pretty annoying, too. this goes especially for users who do not really 
understand R, but are able to play with GUIs.

> Yes, showing the "offending" object in the varslot, along with some visible
> form of warning and explanation, will certainly be a big step in the right
> direction. From there, I think we basically have these options:
> - Always allow the user to proceed (like required="false")
> - Allow the developer to specify, whether the user should be allowed to
> proceed (something like a new attribute strict="true/false")
> - Don't allow the user to proceed by default, but give them some means to
> override this.

i think the first two options would be a little confusing, because it looks 
like something is wrong, but you can just go on nontheless. so we should stick 
to the implicit message of error visibility, which i'd translate to "here's 
something not as it should be, some form of action is required on your side!"

the action could be like the third, "override" option. i would combine 2+3, so 
a developer can decide if an override is permitted or forbidden. we could 
treat strict="false" as the default, though, to keep that to cases where one's 
really sure about that.


viele grüße :: m.eik

p.s.: every possible tag in the plugin XML is now fully covered by rkwarddev, 
including snippets:
 o http://rkward.sourceforge.net/R/pckg/rkwarddev/rkwarddev.pdf
-- 
dipl. psych. meik michalke
institut f"ur experimentelle psychologie
abt. f"ur diagnostik und differentielle psychologie
heinrich-heine-universit"at d-40204 d"usseldorf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20110928/4cfd07ab/attachment.sig>