[mochikit] Documentation error?
In the docs at this URL:
http://mochikit.com/doc/html/MochiKit/Visual.html
there is a note (below here:
http://mochikit.com/doc/html/MochiKit/Visual.html#fn-base):
// I slide it up and then down again
slideUp('myelement', {afterFinish: function () {
slideDown('myelement');
});
It seems to be missing a close brace:
slideUp('myelement', {
afterFinish: function () {
slideDown('myelement');
}
});
As it serves as the page's template format of this motif, it should be complete.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~--~~~~--~~--~--~---
[mochikit] Re: Drag and drop table rows with handle
On 1/12/07, Matthew Kwiecien <[EMAIL PROTECTED]> wrote:
> Ah, sorry, just noticed your second reply. Yes, the ghosting thing is sadly
> a limitation. Like I said though, take a step back and ask if it is really
> tables that you need to use. If you're doing the whole sortable drag and
> drop thing (which, obviously, you are) more likely than not the answer is
> no. I doubt there are very many cases where it would be better to use
> "sortable drag and drop" on a table of data than to use "sortable tables" on
> it.
>
> For example, in a recent project I was doing, I was planning on being lazy
> and using DnD tables. But I wanted the ghosting. So I bit the bullet and
> used a list, wrapping a couple div's in each li, then sprinkled some CSS
> over it. In the end, it turned out better than the tables would ever have
> looked.
>
> Just my .02
>
>
> As for actually making ghosting work with tables, I'm not sure what would
> need to be done. I didn't even know, actually, that one of the toolkits had
> it working. Looking at the YUI example you linked, it seems, to me, a bit
> slow and clunky. Then again, I've never really liked YUI.
>
>
> On 1/12/07, Matthew Kwiecien <[EMAIL PROTECTED]> wrote:
> > Sorry if this sounds a little jerk-ish, because I don't mean it that way:
> > You have to actually define the handle for handles to work.
> >
> > Here's a working example (assuming you have everything included that you
> need to in the header):
> >
> >
> >
> >
> > Handle1
> > Asdf 1
> > Asdf 2
> > Asdf 3
> > Asdf 4
> >
> >
> > Handle2
> > Asdf 1
> > Asdf 2
> > Asdf 3
> > Asdf 4
> >
> >
> > Handle3
> > Asdf 1
> > Asdf 2
> > Asdf 3
> > Asdf 4
> >
> >
> >
> > type="text/javascript">MochiKit.Sortable.Sortable.create('line',{tag:'tr',ghosting:false,handle:'handle'});
> >
> >
> > Important note: Ghosting needs to be set to false, else things get a bit
> wonky. If that's an issue, I suggest you take a step back and ask yourself
> "Do I really NEED to be doing this with tables, or is there actually a
> better/easier way?".
> >
> > Cheers,
> > Matt
> >
> >
> >
> > On 1/12/07, Liu Fung Sin < [EMAIL PROTECTED]> wrote:
> > >
> > > Just FYI, in case any of you also want to implement something like
> > > this.
> > >
> > > I found the following example using YUI
> > >
> > >
> http://tech.groups.yahoo.com/group/ydn-javascript/messages/478?threaded=1&m=e&var=1&tidx=1
> > >
> > >
> https://secure0.forward-comp.co.uk/testtable/testtable.html
> > >
> > > The demo is rather cool!
> > >
> > > Although I have to say that Mochikit, Prototype and Dojo have a much
> > > nicer design than YUI (too verbose for my taste), it seems that they
> > > have a very active community with a lot more corner case examples.
> > >
> > > I'm not giving up on mochikit yet, if anyone can kindly help and point
> > > out what's missing in the picture :-)
I actually ran into almost exatly this problem a few months ago,
though I needed to drag cells, not rows. Still, I found it impossible
to implement with tables. So how to make fixed columns in a list?
.left, .middle, .right {
display: block;
margin: 0 20px;
float: left;
width: 30px;
text-align: center;
}
.left {
clear: left;
}
one
oneA
oneB
two
twoA
twoB
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~--~~~~--~~--~--~---
[mochikit] Re: blindDown initialization
On 1/2/07, Tom Berger <[EMAIL PROTECTED]> wrote: Hi all and Happy New Year! I am trying to use blindDown/blindUp to reveal and hide an optional section of a page. Both functions work beautifully on an element that was initially visible and fully expanded, but I'd like to start with the element hidden. I set the element's style to 'display: none', but as a result the blindDown animation does not work (the element remains non-displayed until the end of the animation and then displays at once). Any ideas on how I could initialize the element not to display and use blindDown to reveal it? Cheers, Tom Did you set display:none inline? This seems to work fine with blindDown (and the other "reveal" animations) for me. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] client side validator
So a couple of months ago I made a client side form validator script that relies on mochikit. It's littered, I admit, with artifacts of the specific implementation, but I've been able to use it elsewhere. Interested parties can go here: http://axlotl.net/wp/2006/10/27/client-side-validation-script/ You definitely need New.js. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Working with Visual
On 9/25/06, Juergen Schreck <[EMAIL PROTECTED]> wrote: > > Ok, still didn't find a good solution for this. Quick reality check > - if I want to use a slideDown effect on an item - how do I 'best' > put it in the initial UP position? > > Thanks, > Juergen I do it like this: --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Trapping Safari's ENTER key
On 8/29/06, hartshorne <[EMAIL PROTECTED]> wrote:
>
> It seems you can't cancel onkeydown events with Safari. You can cancel
> onkeypress events, but MochiKit doesn't return key().string for special
> keys in a keypress event. To prevent form submissions, just do
> something like this:
>
> connect('someForm', 'onsubmit', function(e) { e.stop(); });
>
You are indeed a tenacious investigator. But indeed your solution is
the one I eventually came to lo those 27 days ago when this thread
died.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Visual.js calling obsolete funcions?
New.js. I knew that. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Visual.js calling obsolete funcions?
On 8/24/06, chris feldmann <[EMAIL PROTECTED]> wrote: > I think I'm going to be able to work around these issues... No, I'm not. And looking at previous implementations of mine that use, say, MochiKit.Visual.blindUp, I see calls to MochiKit.DOM.getStyle() all over the place, but it works. Must be update()-ed somewhere? I'm obviously out of my league. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Visual.js calling obsolete funcions?
In (current trunk, -r 1091) MochiKit.Visual.Scale.prototype, there are calls such as : (ln. 906) var fontSize = MochiKit.DOM.getStyle(this.element, 'position'); But DOM.getStyle does not exist. Similarly, there are calls to DOM.setStyle in the vicinity. These can be aliased with new functions in MochiKit.Style, except in some instances (getStyle(this.element, 'font-size'), for instance). I think I'm going to be able to work around these issues, but is this just a danger of using a version under development? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Disconnecting signals
On 8/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Lets say I had some dynamic rows with links. Perhaps I use signal to
> connect those links to some function. Later, I remove the rows. This
> happens on a continual basis.
> Would it be important to disconnect the link's signal before
> removing/discarding the row? If I didn't, would I experience memory
> problems after a while?
> Thanks
> Dennis
You should clean up the event handlers, yes.
var hndlr = MochiKit.Signal.connect( obj, "onevent", function( e ){} );
MochiKit.Signal.disconnect( hndlr );
--- or, alternatively ---
disconnectAll( obj );
http://mochikit.com/doc/html/MochiKit/Signal.html#fn-disconnect
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Trapping Safari's ENTER key
On 7/25/06, "Alexandre A. Falcão" <[EMAIL PROTECTED]> wrote: > Hi guys, > > I had the same problem when mading keyboard shortcuts to a scroll list... > > Looks like safari call the events and you can "see" what's going on, but > it doesn't allow you to stop propagation on keyboard events. So, it will > ever run the default action for a keyboard event. (like a form submit). > > > Pigmeu > Pigmeu, I thank you for your report. Beau, do you concur? -chris --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Trapping Safari's ENTER key
> Hi Chris,
>
> Try looking for key.string == 'KEY_ENTER'. If that doesn't work,
> please post a full example for me to play with.
>
> Thanks,
> Beau
>
Hi Beau.
Thanks for your reply and also for your work on Signal.js which is one
slick chunk of code. I made this test script for my server-side guy to
test on Safari for me because I don't have my powerbook. He reports
that this (which is supposed to essentially disable the entire
keyboard) STILL submits on enter keydown on safari.:
MochiKit.Signal.VERSION
1.4
http://axlotl.dyndns.org/mochikit/packed/MochiKit/MochiKit.js";>
connect( window, "onload", function(){
connect( document, "onkeydown", function( e ){
e.stop();
var key = e.key();
for( p in key ){
logDebug( p + " : " + key[p] );
}
logDebug("\n");
if( key.code == 13 || key.code == 3 || key.string
== 'KEY_ENTER' ){
return false;
}
} );
MochiKit.LoggingPane.createLoggingPane( true );
});
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Trapping Safari's ENTER key
Hi mochinauts.
I am trying to disable form submission on enter keydown. This snippet
works on every platform except safai, which even does the visual
"submit press" animation cue and then submits. Is there some secret
sauce for safari's enter key?
connect( window, "onload", function(){
connect( document, "onkeydown", function( e ){
e.stop();
var key = e.key();
for( p in key ){
logDebug( p + " : " + key[p] );
}
if( key.code == 13 || key.code == 3 ){
return false;
}
} );
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: [Fwd: pulsate patch]
On 6/21/06, Topher Cyll <[EMAIL PROTECTED]> wrote: > > I can confirm this problem. Using the latest SVN checkout (on June > 20th), attempting to call Highlight produces the following error (via > Firebug): > > this.__init__ is not a functionMochiKit.js (line 5265) > > This is with the packed code. Is this enough info to reproduce the bug > with? > > Topher > A possibility: In some cases, you'll get this error if you call the function instead of instantiating the object. Go like this: new MochiKit.Visual.Highlight(elem); --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: new design of site is cool
On 6/21/06, troels knak-nielsen <[EMAIL PROTECTED]> wrote: > > [loading index…] stays. As does [...] > I admit it - I'm using IE, but still don't think I deserved that. > Verified, win2k, ie 6.0. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: new design of site is cool
On 6/20/06, Beau Hartshorne <[EMAIL PROTECTED]> wrote: > This has stung me before too. How's this (make sure you do a super > reload): > http://mochikit.com/doc/html/MochiKit/index.html > > Changeset: > http://trac.mochikit.com/changeset/1033 > That nails it. I think I can speak for Arnar as well in saying thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: new design of site is cool
On 6/19/06, Arnar Birgisson <[EMAIL PROTECTED]> wrote: > > Me too. :o) The site is clean and nice. > > There's one thing that bugs the h*ll out of me though. In the docs > main page, which I have bookmarked, it takes a while for the script to > build the table of contents (the expandable thingie). I click the > bookmark, move my mouse over the chapter I need and poof, between the > time my brain sends a signal to my click-finger and the time it > arrives at the finger - the "[click to expand all]" link appears and I > inadvertently click the wrong chapter, since the whole TOC is shifted > two lines down. Am I the only one with such slow responses? :o) > > Reserving the place for the "[click to expand all]" link in the first > place would get rid of this "shifting". > > Arnar Yes this caught me a few times too. I tend to use the documentation that comes with the distibution, which you can always trust to be current with the package its included with anyway. Then you can just disconnect this load event (in function global_index in doc/js/toc.js) Also, there's always greasemonkey. I third the lauding of the redesign - punchy, striking, incredibly user-friendly. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: [Fwd: pulsate patch]
> >>> poking around on trunk. patch fixes missing 'this'.
> >>>
> >>> -w
> >>> Index: Visual.js
> >>> ===
> >>> --- Visual.js (revision 1027)
> >>> +++ Visual.js (working copy)
> >>> @@ -1630,7 +1630,7 @@
> >>> duration: 3.0,
> >>> from: 0,
> >>> afterFinishInternal: function (effect) {
> >>> -d.setStyle(effect.element, {opacity: oldOpacity});
> >>> +d.setStyle(effect.element, {opacity: this.oldOpacity});
> >>> }
> >>> }, options || {});
> >>> var oldOpacity = d.getInlineOpacity(element);
> >>
> >> That patch is incorrect, it doesn't fix anything. oldOpacity is in
> >> the closure, not on "this" (and even if it was on "this", it would
> >> still be wrong because it's in a different function).
> >>
> >> -b
> > ugh...actually it just breaks more stuff. this explains why I got
> > different errors after my edit. my bad for hastily misdiagnosing.
> >
> > I originally got this error on the packed version, and after
> > changing the the variable oldOpacity in the closure to match the
> > variable that is created for oldOpacity during packing, I get no
> > errors and pulsation as expected (see patch).
> > Hope this helps.
>
> Patches against the packed version are no good. If you want a patch
> applied, we're going to need a patch for the source, not generated
> code. I'm also especially hesitant to take a patch that fixes
> "something" when we don't have an example that reproduces the
> problem. How do we know if it actually resolves the issue?
>
> -bob
>
I'd say, from my experience on this list (a hesitant, quiet
experience), that one would be well served by checking twice, thrice,
four times before declaring a bug in mochikit.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: A Designer Lost In Programming
On 6/10/06, Jon <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> I'm having trouble using MochiKit (I'm more of a designer than a
> developer).
> Anyway, I hope this is the right place to post, and I hope someone can
> help me.
>
> Basicly what I want is this:
> When someone mouseover a object with the id "siste", there will be
> generated a div, containing a h2 element and an image. And when they
> mouseout of it, it will disappear.
>
> What I've managed so far:
>
> sisteinfo = ["Header", "image.png"];
>
> boks = DIV({'id': 'siste-utgivelse'},
> H2(null, sisteinfo[0]),
> IMG({'src': sisteinfo[1]}));
>
> div = toHTML(boks);
>
> (Don't pay attention to the names, they are mostly in Norwegian, and
> you really don't have to understand them.)
>
> Can anyone help me with the script/give me any pointers?
>
> Thanks a lot!
> Jon
You'll need to create functions for inserting and removing the div and
them connect them to $('siste') on mouseover and mouseout.
sisteStuff = function(){
insert = function(){
//alter this depending on where you want to insert the node
appendChildNodes('siste', 'siste-utgivelse');//a mochikit function
}
remove = function() {
siste = $('siste');
siste.parentNode.removeChild(siste);//removeElement isn't mainline until 1.4
}
connect('siste', "onmouseover", insert);
connect('siste', "onmouseout", remove);
}
Then the whole think will need to be wrapped in an window.onload
handler so the elements are there to be acted on:
connect (window, "onload", sisteStuff);
Another possibility is to load the element with the page but make it
invisible with css (display:none;) and then instead of inserting and
removing it, you toggle visibility with, say showElement(); But see :
http://mochikit.com/doc/html/MochiKit/Style.html#element-visibility
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Quick AJAX hint?
Oops: Of course. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Quick AJAX hint?
On 5/29/06, Grzegorz Staniak <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I've just started using Mochikit, and not having used a JavaScript
> framework before, I am a bit lost about how I should proceed with
> a little AJAX trick I want to use - sorry to bother you before reading
> all of the docs (a quick search of the mailing list didn't help much),
> but this is urgency of a kind: after I've done this, I guess I'll be
> able to relax, read the docs, play and experiment.
>
> Here's the "problem": I need to perform a short asynchronous check for
> a condition in a database before accepting user input from a form, and
> succeed/fail the form depending on the result of the check. It would be
> best to present a "please wait" div with a nice animated gif, then
> either proceed to the next screen, or fail the form, display a div with
> an error message, and let the user edit the entered values. What is the
> best way to do this? I found the AJAX demo in the wiki - assuming that
> an URL on the server is able to send jsonified objects, would it be
> enough to call loadJSONdoc on it? What best practice or easiest way to
> do the above would you suggest?
>
> Sorry if I'm asking a FAQ, and thanks for your time,
>
1:12 pm (9 hours ago)
Although I suppose you've now had an opportunity to read the docs, it
doesn't sound like you're really asking about mochikit, as opposed to
the general user experience flow. You could disable the submit button
or hide it until the check takes place, I suppose; I'd put a note
saying why it wasn't there and try to save people from ever noticing
the form was originally unsubmittable by checking the field in
question on the onblur event on the field in question so by the time
they finished the form, the button was enabled. Maybe. Here's a rough
sketch of the way to do the "hiding the button" version
connect("fieldtobechecked", "onblur", checkVal);
checkVal = function(){
url="example.com";
var req = doSimpleXMLHttpRequest(url, {"val" :
document.form.textfield.value});
req.addCallback(reqReturn);
req.addErrback(reqErr);
}
reqReturn = function(){
if(req.allgood){
setElementPosition('submit', {x : 99, y : 99});
} else {
//notify user
}
}
reqErr = function(){
alert("fixme");
}
There are other ways to hide things:
http://mochikit.com/doc/html/MochiKit/Style.html#element-visibility
I like this idea less every time I think about it, but I'll toss it out there.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Help with Example...
On 5/24/06, drbigfresh <[EMAIL PROTECTED]> wrote: > > I am trying to work thru some of the examples in the hopes of getting > more acquainted with the mochiKit, but I am having some problems > figuring out the ajax, loading an xml document example How would I > change the example to load a different XML document when the page first > loads? I see that it's hard coded in the ajax_tables.js files to load > the domains.json, but is it possible on the page to specify a different > xml/json file to load by default, or does it need to be hard coded into > the js file? > > Thanks. Well, it has to be coded *somewhere*. Or received as input. But it doesn't have to be hard coded in that specific file. Where would you like the url to come from? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] webserver down?
mochikit.com appears to be dead: $ wget mochikit.com --19:21:26-- http://mochikit.com/ => `index.html' Resolving mochikit.com... 216.200.21.214 Connecting to mochikit.com[216.200.21.214]:80... failed: Connection timed out. Retrying. (in Eastern time) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Signal.js question
On 5/9/06, chris feldmann <[EMAIL PROTECTED]> wrote: > Is one "mouseouting" an element if one enters another element within > that element? > Or is the event being wrongly propagating down the tree? I'm looking > at the signal code, and it's dense enough to be confusing. But > consider this testcase (with HTML, sorry, it needs to be rendered as > it concerns mouse events - the body tags are for the logging pane): Never mind; I figured out that this is expected behavior, with or without mochikit and I feel sort of dumb now. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: How can I to use MochiKit in my bew-page?
> ok... > in effects I have inserted the file system path in tag "src" becuase I > have tried to run the script in local environment... > thanks for all the feed-back , I promise that I study hard javascript > with the book of David Flanagan... but - as curiosity - this remain a > good text for understand the new technologies as Mochikit and, more > generally, Ajax or maybe this is a few old? Before we can fly we must crawl, grasshopper! Flanagan is an essential reference. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Signal.js question
Is one "mouseouting" an element if one enters another element within
that element?
Or is the event being wrongly propagating down the tree? I'm looking
at the signal code, and it's dense enough to be confusing. But
consider this testcase (with HTML, sorry, it needs to be rendered as
it concerns mouse events - the body tags are for the logging pane):
createLoggingPane(true);
var al = function(){logDebug("hi");};
var con = function(){
connect('o', "onmouseout", al);
}
connect(window, "onload", con);
Mouse in and out of the inner div and get a signal both ways.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: How can I to use MochiKit in my bew-page?
On 5/8/06, Johan Sundström <[EMAIL PROTECTED]> wrote: > > > If I good understand you say me that I must write a thing as... > > //mochikit > > > > src="absolute_path_to/MochiKit.js" > > type="text/javascript"> > [...] > > in this order. This is ok? > > You consistently seem to get the script tag syntax wrong. Try this instead: > >