|There's more than one way to do things|
Hmm. Im trying really hard to remember anyone saying that. Perhaps they or you did one time in the CB or something, but I honestly dont remember. The only comments i really recall were about the Titlebar Settings that I put together. And which i havent applied here. But I dont recall anyone saying anything detailed about the personal nodelet. Beyond a few people saying that they liked it on the test server.
Regardless. If you idea of a personal nodelet is a scratchpad in a box then I think we can handle that. I will say that my thinking was mostly along the lines of "make the current stuff easier to control" not "redesign it in a totally different fashion".
If you dont like the name ill change the name. Thats ok too. I have no idea what you talking about with your s/// stuff. But yes if you want to treat the scratchpad as a single document then a lot of things do become simpler.
I will say one thing. This is the most detailed criticism ive seen of anything ive posted here, including this code about 4 months ago. So i dont feel too bad about it not fitting your exact (unsupplied) specification. In the long run i think most people will appreciate what ive given them even if you don't. And ill also work on giving you your scratchpad in a box too. :-)
I guess you didn't bother to look too much at existing data you'd have to deal with before you wrote this code.
Im unclear what you mean. I had a look at a number of peoples $VARS, and i had a detailed look at the code that encoded/decoded them. Also the current code doesnt work the way your s/// suggests. Nor is it lossy to my knowledge. Any data placed inside the text boxes will be stored and retreived faithfully.
Do you bother to test it on any existing personal nodelets? How can you consider that "fully"?
Sure i did. Several. Can you detail any errors for me wrt to encoding?
First they ignore you, then they laugh at you, then they fight you, then you win.
In reply to Re^2: Y.A.N.F: Personal Nodelet enhancements. (yuck)