[rkward-devel] Programa de orden financiero y manejo inteligente del dinero
Hola, reciba un cordial saludo. El motivo de comunicarme con usted es para invitarlo a un Programa de Ordenamiento Financiero y control inteligente del dinero. No es un curso de contabilidad, lo que se busca es ayudar a corregir los hábitos financieros a través de un ordenamiento financiero personal. A través de este va a poder alcanzar: 1-Desarrollo de un plan para ordenar sus finanzas. 2-Desarrollo de un plan de pago de deudas. 3-Pasos para alcanzar una brecha de ahorro. 4-Diagnóstico y conciencia de su situación financiera actual. 5- Definición de parámetros mentales que definen su comportamiento. 6-Cambio de hábitos para lograr su libertad financiera. 7-Programa de Reacondicionamiento Financiero en 60 Días. Si necesita más información puede ingresar a la siguiente dirección electrónica: http://descubrelibertad.wordpress.com/testimonios Testimonio de un especialista de finanzas que tomó el programa en Perú: http://www.youtube.com/watch?v=LuqxN5W7UDY Quisiera reunirme con usted para explicarle un poco más del programa si está interesado. Por favor contáctese conmigo a la siguiente dirección electrónica: r.lind...@hotamil.com Atentamente Dr. Rosalinda Durán Celular 506-87867578 -- 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] Programa de orden financiero y manejo inteligente del dinero
sorry, hit accept instead of reject! this is spam. 2010/9/6 rosalinda duran duranrosalind...@gmail.com: Hola, reciba un cordial saludo. El motivo de comunicarme con usted es para invitarlo a un Programa de Ordenamiento Financiero y control inteligente del dinero. No es un curso de contabilidad, lo que se busca es ayudar a corregir los hábitos financieros a través de un ordenamiento financiero personal. A través de este va a poder alcanzar: 1-Desarrollo de un plan para ordenar sus finanzas. 2-Desarrollo de un plan de pago de deudas. 3-Pasos para alcanzar una brecha de ahorro. 4-Diagnóstico y conciencia de su situación financiera actual. 5- Definición de parámetros mentales que definen su comportamiento. 6-Cambio de hábitos para lograr su libertad financiera. 7-Programa de Reacondicionamiento Financiero en 60 Días. Si necesita más información puede ingresar a la siguiente dirección electrónica: http://descubrelibertad.wordpress.com/testimonios Testimonio de un especialista de finanzas que tomó el programa en Perú: http://www.youtube.com/watch?v=LuqxN5W7UDY Quisiera reunirme con usted para explicarle un poco más del programa si está interesado. Por favor contáctese conmigo a la siguiente dirección electrónica: r.lind...@hotamil.com Atentamente Dr. Rosalinda Durán Celular 506-87867578 -- 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 -- 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
Re: [rkward-devel] Request for feedback on plot history
Hi, On Sun, Sep 5, 2010 at 11:38 PM, Stefan Rödiger stefan_roedi...@gmx.de 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, especially bugs. I used the latest SVN and found no bugs (I use the feature relative intensively during my work). Thanks for the testing, Stefan. I'm re-writing the whole thing, hopefully, for the better. I'll make another call for testing once done... To my pleasant surprise it works (move through history, remove elements, ...) without problems with split.screen() too. But trouble here is that I find it You were working with version before the recent overhaul. But still, every plot () -type call after split.screen () should create a separate entry into history. Let us not worry about it, for now. hard to tell which window is open without calling Plot properties manually (this issue would be addressed in future versions for non-splitted windows if I understand you right). Either Plot properties get a more prominent position (persistent status bar as you suggested) or you could establish some kind of visual feedback (see below Visual feedback, or other active GUI elements of RKWard have a read square for example) in future version. But this has no priority in my opinion. I see that Thomas has already added a drop-down list. I haven't tested that version yet. That should help in the visual feedback. One thing I find a bit distracting is the output presented in the console and command-log when a plot is invoked (example output attached). This is an issue for me since I use to work on a 10 inch netbook from time to time and therefore need to scroll more than I used to. Yeah, sorry for that, the output is mainly there for my debugging purpose. All the non-error outputs will be suppressed in the final version. 1. Settings Configure RKWard Output has settings for the history length and size Found it finally after this hint. I which there was a help button as in the plug-ins. Even in the current stat the plot history is quite powerful and some easy accessible documentation -as users of plug-ins might be used to- would be highly appreciated. Oh, yes! once the whole thing settles, I'll write the rkh file. 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... ... This will be impossible to get for standard graphics functions (in package:graphics). But already there for the lattice functions. I have some ideas, but I don't think it is going to work. What next? a. Fix the Add to history action in a more intuitive way b. If possible, replace the info button by a persistent status bar Definitely (see above). My suggestion would include some more feedback within the plot region (red square, a plot number, ..., what ever) which would also help when working with a splitted screen. Do we need a status bar even after the plot history drop down menu? c. A drop down menu for the history? Definitely (see above) Thomas has already added that. Thanks again. BTW, hold off you plot-history related testing for a week now. I'm re-writing the whole thing. 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
Re: [rkward-devel] Request for feedback on plot history
HI, On Mon, Sep 6, 2010 at 11:10 AM, Thomas Friedrichsmeier thomas.friedrichsme...@ruhr-uni-bochum.de 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. Something like: 1 plot(rnorm(... 2 hist(data... ... I've added a drop-down menu (Prasenjit, I hope I did not get into your way Great! Now, I have all the more reason to finish up the new re-write quickly. with this; the changes in public_graphics.R are fairly straightforward, though). Of course for normal (non lattice) plots, showing the plot command is probably impossible, technically. Yes, for graphics:: () functions this will be impossible. Here is an idea, may not work though (and I am not going to try it until the main stuff is done): Can we get the last command from history? Remember we are only interested in the primary plotting functions. Unfortunately, utils::history () calls file.show () in the end, so I don't think the paged output can be assigned to any variable. I was thinking of writing another history function (almost the same as utils::history) which would search for plot ()-type patterns, eg: ^(plot|hist|boxplot|...). This function would be called from our wrapped plot.new () just before record () call. A properly crafted regex pattern, can hunt down the first line of a multiline command as well. Again, this is just an idea. What do yo think? Will it work? This is still buggy when you are navigating from a yet unsaved plot to a different position, when the history is already filled to the maximum length. It should be possible to fix this, but since it probably needs to make some assumptions about the internals of the implementation, I thought I rather wait for the next version before bothering with this. Yes, lets wait for the re-write. 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
Re: [rkward-devel] Request for feedback on plot history
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 me. Something like: 1 plot(rnorm(... 2 hist(data... ... I've added a drop-down menu (Prasenjit, I hope I did not get into your way with this; the changes in public_graphics.R are fairly straightforward, though). Of course for normal (non lattice) plots, showing the plot command is probably impossible, technically. This is still buggy when you are navigating from a yet unsaved plot to a different position, when the history is already filled to the maximum length. It should be possible to fix this, but since it probably needs to make some assumptions about the internals of the implementation, I thought I rather wait for the next version before bothering with this. Worked fine for me. I had no crashes when I was doing some boxplots, jumping between them, ... . I changed the default the settings (8 instead of 20) plot history entries out of curiosity what might happen. Even that worked with the notification that some plots need to be removed when I apply the new settings. But I wonder how do you deal with multiple opened windows? All have one history or each has an individual? All windows share a single history, currently. This has some advantages (most importantly, the plot history persists after closing the device windwow!), but it's also the root cause of most of the headaches which Prasenjit and I have been discussing the past few days. Okay. Regards Thomas Regards Stefan -- 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] plot history featrues
Hi, Since I am trying do this from scratch, let me try to chalk out the intended features and expected caveats. So please comment with your suggestion / objections. A. a global history - all managed screen devices will share it. B. ignore preview devices completely C. a STATIC global switch (checkbox) to enable / disable the plot history feature. STATIC means: toggling the checkbox will only affect new sessions of rkward, not the running ones - this global switch should be used to enable/disable the menu/toolbar actions as well Features: 1. history length restriction 2. duplicating a device: - behave as if the duplicated plot is new ie do not alter the old plot - when/if, possible to determine (reliably) that this new duplicated plot and old plot (duplicated from) are identical, do not save this new plot, otherwise always add it to the history at a new position 3. multiple plots on the screen: - check for par (mfig) and graphics:::.SSexists (sp.screens) 4. save the history list when rkward closes - not for this release - as part of the save workspace? - Windows uses .GlobalEnv::.savedPlots right from the beginning - when loading, replace the existing plot history by the loaded one? 5. Actions: a. first / prev / next / last b. remove plot (has to be implemented due to 1.) c. append plot d. insert plot e. overwrite/replace plot (insert then remove) f. clear history g. plot properties 5a. first / prev / next / last - always record - if the recorded version is not identical (see *1) to the old one and if the same plot is displayed on multiple devices, then save this recorded plot in place on the current device but set the status of the plots on all these other devices as new - if the number of these other devices 1, then no way to avoid duplicated plots (err on the conservative side!) (see *2) 5b. remove plot - if the user removes a plot from a device then replay the next available plot on this device - if this removed plot is displayed on any other device(s) then set their status to new - again, if after removal, more than one other device displays the removed plot, then set these as new - no reliable way to avoid duplicated plots in the history (see *2) 5c. append plot - no matter what the current status is, this action should always append the displayed plot to the history - this is a safe guard action, ie, if some plot does not pass through the plot.new / print.trellis etc. wrappers then the user still has a way to add it to the history w/o loosing the plot 5d. Insert plot - similar to append, but the plot will be inserted in the history - care needs to be taken to avoid copying / moving the whole/part of the recorded history 5e. Clear history - after clearing, make the plots displayed on the devices as new 5f. Plot properties - for lattice calls, truncate the call string to a fixed length - additional status bar? since drop-down menu has been implemented, this may not be needed. - for graphics::: functions extract the last plot call from history, if at all possible - last priority, may not work at all [*1] use either identical (a,b) or identical (a[[1]], b[[1]]) [*2] For plots saved via a - recordPlot () a[[1]] is all that is sufficient I think. It contains the data as well as the meta data. In that case, we can hash using digest (a[[1]]) and later (more?) reliably identify / track duplicated plots in the history? (Make digest a dependency of rkward or make it modular?) 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
