Here's a little feature I came across. It's easy to work around it if
it comes up, so I'm just reporting it.
This happened when I was testing various Mochikit functions in the interpreter.
If you close the LoggingPane by closing the pop-up window, the
interpreter cannot seem to show a new one.
To prevent typos and to encourage implentors to document their signals in the
object that provides them.
On Saturday 25 March 2006 21:26, Beau Hartshorne wrote:
Jonathan, I think I asked you about this before, but I can't find the
thread. Why does Signal require us to registerSignals
I just added an example that shows how you could implement a simple
drag handler with Signal:
http://trac.mochikit.com/browser/mochikit/trunk/examples/draggable
Any comments? How can it be better?
Thanks!
--~--~-~--~~~---~--~~
You received this message because
On Mar 27, 2006, at 12:05 PM, Beau Hartshorne wrote:
I just added an example that shows how you could implement a simple
drag handler with Signal:
http://trac.mochikit.com/browser/mochikit/trunk/examples/draggable
Any comments? How can it be better?
Looks great! The only comment I have
I just added an example that shows how you could implement a
simple drag handler with Signal:
http://trac.mochikit.com/browser/mochikit/trunk/examples/draggable
Any comments? How can it be better?
Looks great! The only comment I have is that normally I will use
the exported names in
I'd like to write some tests for elementPosition, setElementPosition,
and setOpacity. How should I do this? Should I just create a few
absolutely positioned elements on the DOM tests page, move them
around, and then inspect?
--~--~-~--~~~---~--~~
You
On Mar 27, 2006, at 2:27 PM, Beau Hartshorne wrote:
I'd like to write some tests for elementPosition, setElementPosition,
and setOpacity. How should I do this? Should I just create a few
absolutely positioned elements on the DOM tests page, move them
around, and then inspect?
That sounds
On Mar 27, 2006, at 10:14 AM, Jonathan Gardner wrote:
On Saturday 25 March 2006 21:26, Beau Hartshorne wrote:
Jonathan, I think I asked you about this before, but I can't find the
thread. Why does Signal require us to registerSignals before we use
them? Can't we do this out in connect()?
On Monday 27 March 2006 15:09, Bob Ippolito wrote:
I'm going to have to disagree here. Unless there's some technical
reason why an explicit registerSignals is necessary, we should just
let implicit registration happen. Writing less code and more
importantly requiring less explanation
On 27 Mar 2006 at 15:57, Jonathan Gardner wrote:
Unless I can declare a signal BEFORE it is signalled, you cannot
connect to it, nor can I signal it.
In my home-rolled (before Mochikit) js library. I have an event
handling
module that is more like a party line phone.
events are broadcast on
Very good idea - I remember looking for exactly that the other
day.Useful for putting in the destructor/teardown of a
controller-object (widget).
For the sake of interoperability, I think it's better with a separate
method, rather than extending the signature of disconnect. Better to
stay close
When I do this
new.courses.course_date is the id of an INPUT of type text.
connect(getElement(new.courses.course_date), onkeypress, foo);
function foo(){}
foo.apply = function (src, e){
dbg_msg(typeof src: +typeof(srs)+ typeof e: +
typeof e);
for(var o in e){
12 matches
Mail list logo
