search for: saveoptions

...the scriptaculous library and found something like the below code, but everytime I ran it I would get a constructor error. Thanks for any help; Looking for something like: MyControls.TextBox = Class.create(); MyControls.TextBox.prototype = { baseInitialize: function(loadCallback, saveCallback, saveOptions) { this.loadCallback = loadCallback; this.saveCallback = saveCallback; .... }, Save: function() { //do save operation using options } }; MyControls.EditableTextBox = Class.create(); Object.extend(MyControls.EditableTextBox.prototype, MyControls.TextBox.prototype), {...

...the package name. The options() tree would be far more readable, separating core options from others. Two weeks ago, i ended up with a list of 125 elements... PS2: an other related topic is Saving/Restore options. For my personal needs (testing within a session), I coded following functions: saveOptions <- function(file="R.options",...){ opts=options(...) save(opts,file=file) } restoreOptions <- function(file="R.options"){ bool=TRUE .tmp=new.env() if (!file.exists(file)) { warning(paste("file ", file, " does not exist"))...

Dear expeRts, Here is a minimal example with the latest version of 'tables' (questions below): require(tables) saveopts <- table_options(toprule="\\toprule", midrule="\\midrule", bottomrule="\\bottomrule", titlerule="\\cmidrule(lr)", rowlabeljustification="r")#, justification="r") ## data.frame x

R-developers: Duncan Murdoch suggested I move a post I started on r-help over here, since it is more at the developer level. Here is my question/challenge -- to my knowledge, there is not currently an official way to store a *package*'s options to a standardized location on a user's computer. Given that OS-level programs have standard preference locations, I was hoping to first assess: