[rkward-cvs] rkward ChangeLog,1.72,1.73 TODO,1.67,1.68

[Thomas Friedrichsmeier]

Update of /cvsroot/rkward/rkward
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19470

Modified Files:
	ChangeLog TODO 
Log Message:
Removing obsoleted rembed-, and rktogglewidget-files.

Index: ChangeLog
===================================================================
RCS file: /cvsroot/rkward/rkward/ChangeLog,v
retrieving revision 1.72
retrieving revision 1.73
diff -C2 -d -r1.72 -r1.73
*** ChangeLog	23 Sep 2005 14:29:46 -0000	1.72
--- ChangeLog	25 Sep 2005 18:45:44 -0000	1.73
***************
*** 1,2 ****
--- 1,3 ----
+ - reworked handling of output from R (no more file-sinks)
  - fix display of warning messages (behavior does not match plain R, yet, but is mostly sane)
  - option to change list of package repositories

Index: TODO
===================================================================
RCS file: /cvsroot/rkward/rkward/TODO,v
retrieving revision 1.67
retrieving revision 1.68
diff -C2 -d -r1.67 -r1.68
*** TODO	23 Sep 2005 17:19:30 -0000	1.67
--- TODO	25 Sep 2005 18:45:44 -0000	1.68
***************
*** 12,37 ****
  
  - "real time" display of output in the console (remember to add Mutex protection before then!)
- - check parts for correct destruction
- 
- - printutils.c->481 Rvprintf: can we get at the standard out-connection and give it a fake vprintf (or better write?!) and fake fflush?
- 	- see also: connections.c line 3246ff InitConnections
- 	- seems ok now. But maybe we could still use this to catch immediate warning messages (which go to R_Consolefile)?
- 
- - still mysterious in warning-handling: 'help (doesnotexist); print ("stuff");'. Why is the order wrong?!
- 
- 
- ##################
- 
- tryCatch (message ("a"), error=function (x) {print ("e"); x$message}, warning=function (y) {print ("w"); conditionMessage(y)}, message=function (z) {print ("m"); conditionCall (z)})
- withCallingHandlers ({message ("a"); stop ("b");}, error=function (x) {print ("e"); x$message}, warning=function (y) {print ("w"); conditionMessage(y)}, message=function (z) {print ("c"); conditionCall (z)})
- 
- Not quite correct yet:
- 	.Internal (.addCondHands (c ("error"), list (function (x) {print ("e"); print (conditionMessage (x))}), parent.frame (), NULL, TRUE))
- 
- .Internal (.addCondHands (c ("warning"), list (function (x) {print ("w"); print (conditionCall (x))}), globalenv (), NULL, TRUE))
- 
- condition handlers seem to be reset after an error!!!
- 
- #################
  
  - remove classes/files:
--- 12,15 ----
***************
*** 39,44 ****
  	- RKCommandEditor (first check for reusable functionality)
  	- RKOutputWindow (first scan for useful menu item ideas)
  
! stuff to do before 0.3.2 release
  - plugins (general)
  	- add import-filter plugins
--- 17,23 ----
  	- RKCommandEditor (first check for reusable functionality)
  	- RKOutputWindow (first scan for useful menu item ideas)
+ 	- REmbed
  
! stuff to do before 0.3.5 release
  - plugins (general)
  	- add import-filter plugins
***************
*** 104,106 ****
  Notes for x11-window capturing:
  - See deactived class-header rbackend/rkwindowcatcher.h
! 	
\ No newline at end of file
--- 83,102 ----
  Notes for x11-window capturing:
  - See deactived class-header rbackend/rkwindowcatcher.h
! 
! ################## cryptic notes ######################
! 
! - printutils.c->481 Rvprintf: can we get at the standard out-connection and give it a fake vprintf (or better write?!) and fake fflush?
! 	- see also: connections.c line 3246ff InitConnections
! 	- seems ok now. But maybe we could still use this to catch immediate warning messages (which go to R_Consolefile)?
! 
! - still mysterious in warning-handling: 'help (doesnotexist); print ("stuff");'. Why is the order wrong?!
! 
! tryCatch (message ("a"), error=function (x) {print ("e"); x$message}, warning=function (y) {print ("w"); conditionMessage(y)}, message=function (z) {print ("m"); conditionCall (z)})
! withCallingHandlers ({message ("a"); stop ("b");}, error=function (x) {print ("e"); x$message}, warning=function (y) {print ("w"); conditionMessage(y)}, message=function (z) {print ("c"); conditionCall (z)})
! 
! Not quite correct yet:
! 	.Internal (.addCondHands (c ("error"), list (function (x) {print ("e"); print (conditionMessage (x))}), parent.frame (), NULL, TRUE))
! 
! .Internal (.addCondHands (c ("warning"), list (function (x) {print ("w"); print (conditionCall (x))}), globalenv (), NULL, TRUE))
! 
! condition handlers seem to be reset after an error!!!