Hi,
On Mon, Sep 6, 2010 at 11:10 AM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> On Monday 06 September 2010, Stefan Rödiger wrote:
>> The dropdown menu ("What next? c") would be really helpful. Indicating the
>> number of the plot and the fist bit of the commands used would be
>> sufficient for me.
Hi,
On Tue, Sep 7, 2010 at 3:17 AM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> On Monday 06 September 2010, Prasenjit Kapat wrote:
>> Can we get the last command from history?
>
> in theory, yes, but not currently. (We do not support the R history
> mechanisms, yet, but it's in the feature tracker s
On Thursday 02 September 2010, Prasenjit Kapat wrote:
> BTW, Thomas:
> When / if time permits, can you download R-2.11-1.tar.gz and browse through
>
> src/library/grDevices/src/devWindows.c
>
> Of particular interest is the string "xd->needsave" (and also the
> "displayList" member)
>
> Can you
Hi,
On Monday 06 September 2010, Prasenjit Kapat wrote:
> Can we get the last command from history?
in theory, yes, but not currently. (We do not support the R history
mechanisms, yet, but it's in the feature tracker somewhere).
> Remember we are only interested in the primary plotting function
Am Montag 06 September 2010, 13:10:26 schrieb Thomas Friedrichsmeier:
> Hi,
>
> On Monday 06 September 2010, Stefan Rödiger wrote:
> > The dropdown menu ("What next? c") would be really helpful. Indicating
> > the number of the plot and the fist bit of the commands used would be
> > sufficient for
Am Montag 06 September 2010, 19:39:11 schrieb Prasenjit Kapat:
> Hi,
>
> On Sun, Sep 5, 2010 at 11:38 PM, Stefan Rödiger
wrote:
> > Am Dienstag 31 August 2010, 03:43:57 schrieb Prasenjit Kapat:
> >> Hi,
> >>
> >> Following this thread from Thomas:
> >> http://www.mail-archive.com/rkward-devel@l
HI,
On Mon, Sep 6, 2010 at 11:10 AM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> On Monday 06 September 2010, Stefan Rödiger wrote:
>> The dropdown menu ("What next? c") would be really helpful. Indicating the
>> number of the plot and the fist bit of the commands used would be
>> sufficient for me.
Hi,
On Sun, Sep 5, 2010 at 11:38 PM, Stefan Rödiger wrote:
> Am Dienstag 31 August 2010, 03:43:57 schrieb Prasenjit Kapat:
>> Hi,
>>
>> Following this thread from Thomas:
>> http://www.mail-archive.com/rkward-devel@lists.sourceforge.net/msg00872.htm
>> l
>>
>> I would like to get some feedbacks,
Hi,
On Monday 06 September 2010, Stefan Rödiger wrote:
> The dropdown menu ("What next? c") would be really helpful. Indicating the
> number of the plot and the fist bit of the commands used would be
> sufficient for me. Something like:
>
> 1 plot(rnorm(...
> 2 hist(data...
> ...
I've ad
Am Dienstag 31 August 2010, 03:43:57 schrieb Prasenjit Kapat:
> Hi,
>
> Following this thread from Thomas:
> http://www.mail-archive.com/rkward-devel@lists.sourceforge.net/msg00872.htm
> l
>
> I would like to get some feedbacks, especially bugs.
I used the latest SVN and found no bugs (I use the
Hi,
On Sun, Sep 5, 2010 at 7:23 AM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> On Saturday 04 September 2010, Prasenjit Kapat wrote:
>> Indeed. I'll need to go back to drawing board and try to implement
>> things differently. Before getting into specific cases, I am
>> suggesting, in the interest of
On Sunday 05 September 2010, Thomas Friedrichsmeier wrote:
> But perhaps it's not that hard after all? I just tried this with the
> X11Cairo device:
> plot(1, 1)
> a <- recordPlot()
> dev.off()
> replayPlot (a)
> b <- recordPlot()
> identical (a, b) # TRUE
> title ("som
Hi,
On Saturday 04 September 2010, Prasenjit Kapat wrote:
> Indeed. I'll need to go back to drawing board and try to implement
> things differently. Before getting into specific cases, I am
> suggesting, in the interest of the upcoming release, that let us
> ignore this plot history feature comple
On Sat, Sep 4, 2010 at 1:49 PM, Prasenjit Kapat wrote:
>
> So, what next?
> * One simpler strategy is to use separate history for individual
> devices, the way it is implemented on Mac OSX's quartz device. This
> way replaying / updating across devices is totally avoided.
> * Provide only first /
On Sat, Sep 4, 2010 at 9:17 AM, Thomas Friedrichsmeier
wrote:
> On Saturday 04 September 2010, Prasenjit Kapat wrote:
>> BTW, (for later) could some of the message boxes be run asynchronously?
>
> This was simple enough. rk.show.message() has a "wait" parameter, now. Of
> course rk.show.question()
Hi,
Thanks for the quick inputs, Thomas.
To everyone: find if there is any "high-level-primary" plot function
which does not get recorded (technically, which does not call plot.new
()). For example: persp () does not call plot.new (), but we have
taken care of it by putting in a hook. Are there o
On Saturday 04 September 2010, Prasenjit Kapat wrote:
> BTW, (for later) could some of the message boxes be run asynchronously?
This was simple enough. rk.show.message() has a "wait" parameter, now. Of
course rk.show.question() is inherently synchronous.
Regards
Thomas
signature.asc
Descriptio
Hi,
gee, this whole affair sure is more complex than I would have imagined!
I did not have a look at everything, so far, but here are a few issues and
comments:
On Saturday 04 September 2010, Prasenjit Kapat wrote:
> All right, the current implementation records and replays liberally.
> In some
Hi,
On Thu, Sep 2, 2010 at 2:55 AM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> 2) *Always* save to the history on plot.new, prev/next, etc. without the whole
> newPlotExists mechanism. The advantage is again that it offers much less
> potential for surprises. It does seem pretty wasteful, since most
On Thu, Sep 2, 2010 at 1:05 PM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> On Tuesday 31 August 2010, Prasenjit Kapat wrote:
>> 6. The "Show info" action currently uses kdialog (recently changed it
>> from readline ()), but as soon as Thomas returns (and finds time to
>> implement a dialog box connec
Hi,
On Thu, Sep 2, 2010 at 1:05 PM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> On Tuesday 31 August 2010, Prasenjit Kapat wrote:
>> 6. The "Show info" action currently uses kdialog (recently changed it
>> from readline ()), but as soon as Thomas returns (and finds time to
>> implement a dialog box c
Hi,
I was playing around with the plot history feature of Windows (windows
()) and Mac OS X's (qaurtz ()), something that I shuold've done much
earlier. They are both very minimalistic, although windows' is
slightly better. I realized that we were shooting a "near ideal"
solution, which is going t
Hi,
On Tuesday 31 August 2010, Prasenjit Kapat wrote:
> 6. The "Show info" action currently uses kdialog (recently changed it
> from readline ()), but as soon as Thomas returns (and finds time to
> implement a dialog box connection on the C++ side) I plan to change it
> to a more native version. (
Hi,
On Thursday 02 September 2010, Prasenjit Kapat wrote:
> On Wed, Sep 1, 2010 at 4:31 PM, Thomas Friedrichsmeier
>
> wrote:
> > Is it really a good idea to synchronize the plot windows that show the
> > same history position? I.e. if two separate windows each show the first
> > plot in history
Hi,
On Wed, Sep 1, 2010 at 4:31 PM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> great work, overall! This is pretty sophisticated stuff, and that also means
> there's a lot of details to think about and test. I'm not sure I've seen
> everything, but I don't want to let you wait much longer. So here a
Hi,
great work, overall! This is pretty sophisticated stuff, and that also means
there's a lot of details to think about and test. I'm not sure I've seen
everything, but I don't want to let you wait much longer. So here are the
notes I have taken so far in no particular order.
I'll post again,
26 matches
Mail list logo
