Re: [rkward-devel] local
Hi, On Friday 06 August 2010, Stefan Rödiger wrote: Scenario II: Object is open for editing (my.data) in fresh started RKWard 1. Create objects 2. Invoke the plugin 3. confirm to remove and do so 4. Push accidentally no when asked Das Objekt 'meine.daten' wurde vom Workspace entfernt oder in einen anderen Objekttyp umgewandelt, aber es ist gegenwärtig zur Bearbeitung geöffnet. Wollen Sie es wiederherstellen? (sorry for German, but doesn't matter anyways) Now it should crash. If yes is chosen nothing will crash but obviously the object currently open will no be removed. This should now be fixed in SVN. Regards Thomas P.S.: Yes, I'm back from my vacation, but it will take a while to catch up on the e-mail backlog. signature.asc Description: This is a digitally signed message part. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] Atsakymas į:Re: Add Lithuanian translation
Hi, On Wednesday 11 August 2010, Stefan Rödiger wrote: Am Samstag 07 August 2010, 17:18:23 schrieben Sie: That is great. But in my translation is 3 messages untranslated: 2 related with serialization format, and 1 with pager command. Maybe you can explain the meaning of it? No not really. I translated it literally. Let's wait for the comment of the others. serialization is a computing term. See http://en.wikipedia.org/wiki/Serialization . Note that this message should only be displayed in very rare and obscure cases, and mostly in the hope that any user that sees it will contact us. Even in English the message probably isn't really intellegible to anybody without reading the code. pager command means the command used to display text (see http://en.wikipedia.org/wiki/Terminal_pager ; options (pager) in R). By default this is rkward-internal, but you can set it to another text editor, e.g. kwrite, and then e.g. use page (test) to display something. --- Oops, I see the option is broken, apparently. Will make a note to take a look. Besides, in .pot is string Settings-Configure Settings-... (and not once), but I don't see such Configure Settings menu. I translated it same as Configuse RKWard. You need fix it. Good catch. Thanks! However, the message is part of the PHP-backend, which has recently become obsolete, and should never be shown to users in RKWard 0.5.3. The PHP backend (and the message) will probably be removed shortly after 0.5.4. So I won't touch it, for now. Regards Thomas signature.asc Description: This is a digitally signed message part. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] altering rk.graph.on and rk.graph.off
Am Dienstag 31 August 2010, 05:54:41 schrieb Prasenjit Kapat:
Hi Stefan,
On Mon, Aug 30, 2010 at 8:23 PM, Stefan Rödiger stefan_roedi...@gmx.de
wrote:
Hi Prasenjit,
I simply love the stuff you do. Never thought of it, now I won't miss it.
It is so convenient, smart and useful.
Thanks ;) I wish it was implemented in a better by R. Consider this
example (nothing to do with rkward:
# print device list and the currently active device:
f - function () {print (dev.list ()); print (dev.cur ())}
x11 ()
f ()
plot (0,0)
png (file = tmpplot_dev3.png, width = 400)
f ()
plot (rnorm (100), rnorm (100))
pdf (file = tmpplot_dev4.pdf, width = 4)
f ()
dev.off () # closed pdf, x11 is now active !!
f ()
dev.off () # closes x11!! png is now active
f ()
dev.off () # closes png, FINALLY!
The problem, is that dev.prev () and dev.next () are implemented in a
cyclical numeric order. In this sense,
dev.off (which = dev.prev ())
might make more sense, than, the currently implemented:
dev.off (which = dev.next ())
yet, the main problem would persist.
But in implementing a linked list of active devices would pose some
logical problems (what happens if you close the previously active
device as opposed to closing the current device?), and hence, I think,
the simplistic dev.prev and dev.next exists. In that sense, my fix
is buggy. Hmm...
Thomas asked for feedback some weeks ago which I will try to address
later.
See if you can use the latest svn code.
One stupid question. Right now it is possible to copy the preview plot to
the output. I wonder if it is possible to embed the corresponding code
too (since the user might be used to that in RKWard behaviour in
RKWard)?
Nice idea.
glad to hear
I am guessing it should be easy to do, without the syntax
highlighting. Looking at plugin/rkstandardcomponentgui.cpp, just
sending code_property-Preprocess () + code_property-calculate () +
code_property-printout () to .rk.cat.output () would do it. Of
course, a button on the GUI somewhere.
go for it ;)
The button action will be more appropriate on the plugin dialog box
rather than on the screen device window. (All though, I have arguments
in favor of device window as well.)
why not both (at least for testing)?
I'll refrain from tinkering with that part of the code! Let Thomas come
back.
okay
Regards
Stefan
Am Samstag 28 August 2010, 03:22:44 schrieb Prasenjit Kapat:
Hi,
I've modified the rk.graph.on () and rk.graph.off () functions
slightly in trunk. Since many might be using these functions (as it is
used in a lot of plugins), here is a little explanation:
As you may know, in R, after dev.off () closes the current device,
dev.next () is set as active. This applies to RKWard as well. But,
when
rk.graph.on (); ; rk.graph.off (); # dev.off () is called inside
rk.graph.off ()
is executed (in some form or the other), dev.next () is not
necessarily the device that was active before rk.graph.on () was
called. This creates a little confusion (at least to me, see [1]
below) especially when copying a device to output via Device Copy
device to output. Hence the fix.
For those following the trunk, let me know if you see any regressions
or non-intuitive behavior. Of course, this only affects rk.graph.on
and rk.graph.off and DOES NOT alter the usual (R's) behavior of
dev.off ().
Regards,
--
Prasenjit
[1]
x11 ()
plot (0,0)
x11 ()
plot (1:10,1:10)
dev.copy (device = rk.graph.on); rk.graph.off ()
dev.off (); # closes the wrong device, w/o the fix.
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
RKWard-devel mailing list
RKWard-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkward-devel
[rkward-devel] anyone using KDE 3 version of rkward?
Hi, I would like to know how many folks still use the KDE3 version of rkward (0.4.9x). The reason I ask is this: I've, partially, ported some of the recent plot history features to it. It is not clean but satisfies my day-to-day needs (Yes, I have to use the KDE3 version in the department!). If there is a demand, we can try to release another version of it: 0.4.9d (?) (If Thomas agrees!) The KDE4 version and its bug fixes will be the top priority, of course. So, the 0.4.9d release, if done, will be at least a few weeks after the upcoming 0.5.x release. I just wanted to get a heads up! For those wondering about the plot history feature, it is a browse-able history of plots that the user creates. A screen shot is here: http://sourceforge.net/apps/mediawiki/rkward/index.php?title=Screenshots#Graphics_history_actions_.28from_trunk.29 The screen shot does not represent the final version, it is subject to change. Regards, -- Prasenjit -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
