... You should try, Trevor. I got very found of this approach myself after hearing David hint me on the way getprop and setprop could be used this way and...
336
Mark Wieder
ahsoftware
Mar 31, 2006 6:17 pm
Marielle- ... Not strictly true at all. I have an xml-tree component where I pass it data by "set the DisplayXMLData of field xyz to myData", where myData is...
337
Mark Wieder
ahsoftware
Mar 31, 2006 6:20 pm
Marielle- Friday, March 31, 2006, 6:36:31 AM, you wrote: "It is the potential for a gradual increase in the quality of the functions and widgets available...
338
Trevor DeVore
trevor_devore
Mar 31, 2006 7:00 pm
... Umm, I do. The text quoted above was from a post from Ken <http:// groups.yahoo.com/group/revInterop/message/298>. I use virtual getProp/setProps in my...
339
Trevor DeVore
trevor_devore
Mar 31, 2006 7:13 pm
... Well Mark, technically you are only passing in one parameter :-) You are passing one parameter that you have to parse. If you go this route for data...
340
Mark Wieder
ahsoftware
Mar 31, 2006 7:17 pm
Trevor- ... Yes, exactly the point. The reason we're having this discussion here (well, the reason "*I'm* having it here) is to promote the interoperability of...
341
Alain Farmer
alain_farmer
Mar 31, 2006 7:23 pm
Hello Mark Wieder, Marielle, and y'all ... Marielle does indeed express herself coherently, clearly, and persuasively. Her above sentence is well-formed, but,...
342
Trevor DeVore
trevor_devore
Mar 31, 2006 7:26 pm
... I like the approach of common handlers shared among libs and using custom props to decide if the lib should act on object. That way I could do this: ...
343
Mark Wieder
ahsoftware
Mar 31, 2006 7:29 pm
Trevor- Yes, I realize that was kind of cheating... but yes, if you can package the data correctly then you can get around the single parameter hurdle. -- ...
344
Mark Wieder
ahsoftware
Mar 31, 2006 7:31 pm
Alain- ... Yes, I think you may have gotten the wrong idea from my post. I wasn't trying to be flippant here. Marielle did indeed get right to the core of what...
345
Mark Wieder
ahsoftware
Mar 31, 2006 7:45 pm
Trevor- ... ...and I forget whether or not there was a buy-in from rev on the idea... At any rate, my idea for the "RegisterEvent" or whatever handler is that...
346
Trevor DeVore
trevor_devore
Mar 31, 2006 7:54 pm
... Mark Waddingham didn't have an objection either way. I imagine it isn't at the top of the priority list though since people get along fine the current...
347
Mark Wieder
ahsoftware
Mar 31, 2006 8:02 pm
Trevor- ... ROTFL - I wonder if Dar's coming... anyway, I understand a reticence to change engine behavior - it's not something that should be undertaken...
348
Ken Ray
kennanray
Mar 31, 2006 8:07 pm
... But what it also means is that we need to agree on a common set of handlers that do the expected thing; that is, I can no longer use "RegisterEvent" as a...
349
Ken Ray
kennanray
Mar 31, 2006 8:11 pm
... Agreed - it's a catch-22; you either use more typing to get the same effect: get (the RegisterEvent["mouseUp"] of stack "myStack") vs. RegisterEvent...
350
Mark Wieder
ahsoftware
Mar 31, 2006 8:11 pm
Ken- ... Yes - I didn't mean to say otherwise. What I'd like to see us work out as a standard is a minimal set of handlers required for interoperable ...
351
Ken Ray
kennanray
Mar 31, 2006 8:40 pm
... Actually, Marielle, I said that... although it has its advantages, it jus seems awkward to me to execute a command like "RegisterEvent" using a custom ...
352
Richard Gaskin
fourth_world
Mar 31, 2006 9:15 pm
... This is exactly the sort of thing the Rev Interoperability Project was established for. The ECMI draft was a small but necessary first step, and there are...
353
Richard Gaskin
fourth_world
Mar 31, 2006 9:22 pm
... I've also suggested the same thing to him, esp. since RunRev has started adding non-engine messages without the "rev" prefix (see savingStandalone and...
354
Richard Gaskin
fourth_world
Mar 31, 2006 9:41 pm
I just noticed a lot of revInterop messages in my spam bin, put there by false positives from the vigilante service SpamCop. According to SpamCop, all of Yahoo...
355
Mark Wieder
ahsoftware
Mar 31, 2006 10:13 pm
Ken- ... Nope - it's not just you. It *is* awkward and goes against the grain of the naturalness of xtalk. But it *is* very powerful. I regard it as a kludge...
356
Trevor DeVore
trevor_devore
Mar 31, 2006 10:55 pm
... Great. I'll get you your own bag of Skittles at RevCon West then. -- Trevor DeVore Blue Mango Learning Systems - www.bluemangolearning.com ...
357
Trevor DeVore
trevor_devore
Mar 31, 2006 11:02 pm
... get is just like send in that you can't pass arrays, right? For that reason, I would love to see that small switch in the engine so no "stub" required. ...
358
Mark Wieder
ahsoftware
Apr 1, 2006 2:03 am
Trevor- ... Something was bothering me about this and I went back and looked at it again. I'm actually passing the entire xml *text* to my setProp handler,...
359
David Bovill
fortyfoxes
Apr 1, 2006 3:30 pm
... Yes - I do the same Mark! Actually as I "try" to view setprop and getprop handlers as "user friendly syntax interfaces" - they tend to be simplifications...
360
David Bovill
fortyfoxes
Apr 1, 2006 4:02 pm
... In both case you need to know which view you are registering - no? You may - I often do - wish to make a palette of act on the component from some...
361
David Bovill
fortyfoxes
Apr 1, 2006 4:37 pm
... Great point Richard! Inspired from the RoR story perhaps? I agree full heartedly with this - but just to play devils advocate - I was having nightmares...
362
David Bovill
fortyfoxes
Apr 1, 2006 5:14 pm
... A related problem is trying to pass a reference to an object - say the long id of some field - the reference evaluates to the text of the field....
363
Richard Gaskin
fourth_world
Apr 1, 2006 5:44 pm
... What does that entail? Are you using Rev's Geometry Manager or handling resizeStack messages yourself? -- Richard Gaskin Managing Editor, revJournal ...
364
Mark Wieder
ahsoftware
Apr 1, 2006 6:02 pm
David- ... I cheat. I use the short id and [optionally] the stack. put the id of control tControl, \ the short name of stack tStack \ into tParam1 set the...
