[rkward-devel] Importing text/csv plugin modification...
Thomas Friedrichsmeier
thomas.friedrichsmeier at ruhr-uni-bochum.de
Wed Oct 31 12:45:17 UTC 2007
Hi,
On Tuesday 30 October 2007, Prasenjit Kapat wrote:
> I have been thinking to modify this plugin slightly to provide a
> "quick" mode using read.csv/csv2/delim/delim2. I don't remember who
> had written this initially, anyway I will take some liberty to do the
> following changes:
>
> 1. Quick mode (as described above)
> 2. Combine the Rows and Columns tab into one: a lot of space seems to
> be wasted in there....
> 3. Combine the Strings and Further Options tab: same reason as above..
>
> In this regard, one quick question: (I have gone rusty) Suppose there
> are two radio sections in a plugin. If I remember correctly there is
> no way to set the "option" on one radio based on the "option" of the
> other radio... Am I right?
you can do that, but only in a very limited way. You can connect
some "governor" to the radios "string" or "number" properties. Now, if the
governor value matches the value of one of the option, that option will be
selected.
The problem is, that the governor will most likely be a "convert" logic
element, and that is limited to the values "true"/"false" (or 0/1, if you use
the "numeric" modifier). So that's not too useful, when you want to set e.g.
the third option in a radio.
One way around this would be to allow specification of the string values of
a "convert" property. However, for now you can only connect a
single "governor" to each property, so this will not help much, if you need
to select between several options based on several conditions, either.
Another option would be to add a property "selected" to each option in the
radio, similar to the property "enabled" that already exists for single
options (so you can disable some options in a radio). However, what happens,
if the current option is changed to not selected? Theoretically no option is
selected, now, and that would make for an invalid choice in the radio. Or
does it only work one way, i.e. you can set an option to be selected, but not
to not-selected?
I'm just not sure how to do this, yet. Suggestions (if the above sounds too
technical, perhaps post some pseudo-plugin-xml, that shows how it could look
like, and I'll see how this can be implemented)?
> I hope the initial author feels comfortable with this. Kindly, let me
> know you preferences/objections. I will try to incorporate them.
I had to look it up in the SVN logs. This was originally created by Adrien
Hardemare, and while it has undergone a substantial number of revisions since
then, the basic layout has remained the same.
On your points 2 and 3, I guess I'll need to see what it looks like when done.
I'm somewhat afraid that it will not be so easy to find the options of
interest, anymore. However, I have not really thought this through, and
layout changes are easy to do and undo, so just go ahead and give it a try.
Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20071031/8dafb9a8/attachment.sig>
More information about the Rkward-devel
mailing list