So, given that:
* There hasn't been a blog post on the website in ... ever (according
to the front of the site; in reality there was a post back in 2008)
* There hasn't been a release since 2008
* This mailing list gets a post (with no response) once every other
month or so, if that
* MochiKit is
I'll be brief, as Arnar seems intent on his plans despite my warnings.
Basically I'd just like to clarify my previous criticisms: my primary
concern is NOT that MochiKit is unpopular, NOT that it has certain
really long function names, and NOT that I expect someone else to
implement code for me.
PROTECTED] wrote:
Hi Jeremy,
On Wed, Aug 27, 2008 at 16:46, machineghost [EMAIL PROTECTED] wrote:
I'll be brief, as Arnar seems intent on his plans despite my warnings.
Sorry, what warnings? Are you referring to using Sizzle in the Selector
module?
I must have missed something :/ and I
Amit, you're barking up the wrong tree ...
http://groups.google.com/group/mochikit/browse_thread/thread/2c19e8632820270e/6d18b9075c9050f9?lnk=gst
Mochikit is VERY resistant to change, and if you try to suggest
changes people will basically tell you why don't you go use that
other library if you
First off, I do 3 Mochikit. I wasn't trying to bash it, I just
wanted to share my opinion of it with someone who seemed to be in a
similar position.
part of the reason changes are looked at with suspicion is because
a lot of suggestions are not in keeping with the intent of MochiKit.
Hey All,
I use a couple of alias functions in every project where I use the
DOM library:
/*
Shorten getElementsByTagAndClassName, because we know that we're
getting elements (nothing else has a tag/class) and we know we're
doing it by the name of the class or tag, because there is no other
way
, machineghost [EMAIL PROTECTED] wrote:
Hey All,
I use a couple of alias functions in every project where I use the
DOM library:
/*
Shorten getElementsByTagAndClassName, because we know that we're
getting elements (nothing else has a tag/class) and we know we're
doing it by the name of the class
Why wouldn't you just use $$(.someClass)
As Arnar said, the performance isn't the same (in fact, I've pretty
much avoided $$ altogether because of bad CSS selector performance
experiences in the past; maybe I should give it another try
though ...).
I think using aliases is nice, but your
addElementClass(close_run_btn, 'hidden');
This line is basically the same as saying:
close_run_btn.classNames += hidden;
removeElementClass(close_info_div, 'hidden');
This line uses a method that is the reverse of the last one:
close_info_div.classNames.replace(hidden, );
You probably only need one file: Mochikit.js. This file contains most
of the MochiKit libraries (but not all; I forget exactly which ones it
leaves out) in a compacted form. The compacting isn't perfect though,
so if you really need to remove every last k possible you could
probably shrink it a
structure is:
/ - Changes, LICENSE.txt, MANIFEST, META.json
/doc
/examples
/include
/lib
/packed
/tests
I'd prefer not to use the packed version, so I believe the only folder
I need is lib. Do I what does include to?
On Jun 18, 10:32 am, machineghost [EMAIL PROTECTED] wrote:
You probably
(and if so perhaps others might be able to do the same).
Jeremy
On Jun 17, 1:35 am, troels knak-nielsen [EMAIL PROTECTED] wrote:
On Tue, Jun 17, 2008 at 6:23 AM, machineghost [EMAIL PROTECTED] wrote:
So before I waste a bunch of time trying to fix such issues, I thought
it might help to ask
After looking at jQuery recently, I became interested in the idea of
adding core object prototype functions. Imagine if, instead of the
normal MochiKit syntax, you could do:
var a = someObject.clone(); // var a = clone(someObject);
var b = [].isArrayLike(); // var b = isArrayLike([]);
var c =
12, 2008 at 11:15 PM, machineghost [EMAIL PROTECTED] wrote:
When I first looked at your function I completely missed the
significance of this line:
myAttrs[args[pos]] = arguments[pos];
and thought that argument was only for specifying which attributes are
required. Having looked
], { type: checkbox });
Either way, I'd like to push this to MochiKit 1.5. I'm currently
mostly doing bug fixes in svn trunk so that we can get to a release of
1.4 as soon as possible.
Cheers,
/Per
On Tue, Jun 10, 2008 at 10:37 PM, machineghost [EMAIL PROTECTED] wrote:
I mentioned the idea
at 6:13 PM, machineghost [EMAIL PROTECTED] wrote:
I really like your idea of making the creation of the input functions
more generalized. However, if we wanted to preserve the:
CHECKBOX(myNameIsBox1) ==
input type=checkbox name=myNameIsBox1/
functionality we'd need a slight modification
I mentioned the idea of a createINPUT function awhile ago, but no one
seemed terribly interested so I've been slacking on submitting it.
However, I think a lot of createDOM fans could find createINPUT
similarly useful, and with the recent flurry of submissions I figured
now was as good of a time
Anyone know why the DOM API page (http://www.mochikit.com/doc/html/
MochiKit/DOM.html) is down? I feel just a little silly using the
Google Cache (http://64.233.167.104/search?
q=cache:Ox2RKuR1TlQJ:mochikit.com/doc/html/MochiKit/DOM.html+mochikit
the browser is just caching a previous 404?
/Per
On Sun, Jun 1, 2008 at 7:42 PM, machineghost [EMAIL PROTECTED] wrote:
Anyone know why the DOM API page (http://www.mochikit.com/doc/html/
MochiKit/DOM.html) is down? I feel just a little silly using the
Google Cache (http://64.233.167.104
That Animation library looks pretty cool to me. I don't use Visual
much myself, largely because my experiences with it have been negative
(I had serious performance problems and strange glitches the last time
I tried using it). However, if it was as slick as the Animation
library appears to be
As I understand things (and I am by no means a JS event sequence
expert), the ordering is as follows:
1. Browser reads page line by line; every time it reads enough lines
to complete a JS statement, it executes that statement; meanwhile, non-
JS content is loaded in to the DOM as it is read
2.
]
connect(window, 'ondomready', function () {
alert('now i know kung fu');});
[/code]
Felipe Alcacibar Buccioni
Developer of systems and solutions
On 6 mayo, 17:47, machineghost [EMAIL PROTECTED] wrote:
Hey All,
In trying to explain why he liked
Hey All,
In trying to explain why he liked jQuery, a co-worker of mine clued me
in to a fairly cool method in that library: ready(someFunc);. For
those who aren't familiar with jQuery, you can think of this method as
something like:
partial(connect, document, DOMContentLoaded)
In other word,
http://www.w3.org/International/
http://www.i18nguy.com/
http://www.xencraft.com/training/webstandards.html
Those three sites came up from a quick Google search of
internationalization web, and they will be much more helpful to you
than this list.
Mochikit can help with certain, *specific*,
First off, I'm not going to say RTFM or anything, but seriously the
docs are you friend ;-) If you take a look at the documentation for
zip:
zip(p, q, ...):
Returns an array where the n-th element is an array of the n-th
elements from each of the arrays p, q, ...
The last words are the most
The fact that IE treats names as if they were IDs is a known IE JS
issue (one of many, many known IE issues *sigh*). If Mochikit were to
mention every known IE JS issue, half the documentation would be
nothing but (and I'm only half joking when I say that; IE's JS
handling is REALLY buggy).
So,
I don't mean to be rude, but asking people to give you code is not
going to be very fruitful; I can assure you that most everyone on this
list is too busy to write your code for you.
That being said, it sounds from your post like you need a better
understanding of the core technologies. A login
throw it all away in favor of YUI or ExtJS.
/Per
On Sun, Feb 17, 2008 at 2:28 AM, machineghost [EMAIL PROTECTED] wrote:
About a year ago I found myself in a similar situation, and began
looking in to other libraries besides Mochikit for all of my widget
needs. I ultimately went
About a year ago I found myself in a similar situation, and began
looking in to other libraries besides Mochikit for all of my widget
needs. I ultimately went with the YUI (Yahoo User Interface) library,
and discovered that it in fact works very well with Mochikit. Not
seamlessly mind you, but
= createINPUTFunc(text);
/** @id MochiKit.DOM.SUBMIT */
this.SUBMIT = createINPUTFunc(submit);
On Dec 18 2007, 9:27 am, machineghost [EMAIL PROTECTED] wrote:
Thanks Kevin and Bob (I totally forgot about merge), but I agree that
trying to use Mochikit to further simplify this pretty simple function
is a bit
Sounds like a problem in your server-side code (ie. your jsp). The
responseText property of an XmlHttpRequest just Retrieves the
response body as a string. (from MSDN). So, the reason you're seeing
the entire jsp is because you're returning the entire jsp :-)
If you're working in the jsp
thought it would look more like MochiKit, as machineghost asked, but
sometimes you use a hammer so much everything begins to look like
nails.
Thanks, Bob, for the great toolkit!
- Kevin
On Dec 17, 2007 2:11 PM, Bob Ippolito [EMAIL PROTECTED] wrote:
It still wouldn't work because
I recently found myself doing this a lot:
var a = INPUT({type:textbox});
var b = INPUT({type:checkbox});
var c = INPUT({type:hidden});
etc.
So I wanted to make short-hand functions like CHECKBOX and HIDDEN
which would work exactly like INPUT, only with a pre-specified type.
At
Would something like this work?
function recursiveDigForText(someElement){
if(someElement.firstChild.tagName)
return someElement.innerHTML;
else
return recursiveDigForText(someElement.firstChild);
}
On Dec 10, 7:53 am, JS [EMAIL PROTECTED] wrote:
Hi:
I'm quite new to
I'm not familiar with TurboGears (more of Django fan myself), but glad
I could help :-)
Jeremy
On Nov 1, 8:07 am, shday [EMAIL PROTECTED] wrote:
On Oct 26, 12:00 pm, machineghost [EMAIL PROTECTED] wrote:
Is the error occurring when the page loads, because of this:
conn(window, 'onload
What if you did something like:
style.nodisplay{display:none}/style
body id=body classnodisplay
and then in your callback added something like
removeElementClass('body', 'nodisplay'); at the end?
Jeremy
On Nov 1, 4:25 am, Felipe Alcacibar B [EMAIL PROTECTED] wrote:
Hi.
I am using jsCalendar
)
will automatically do the $() for you if you pass a string as an
argument when it's expecting an element.
On Oct 25, 9:49 am, shday [EMAIL PROTECTED] wrote:
I should have mentioned it. Line 24 is:
var model_id = event.target().value;
On Oct 25, 12:30 pm, machineghost [EMAIL PROTECTED] wrote:
Stupid
Stupid question: which line is line 24? (or more specifically, which
line caused the error, as line 24 in your reduced version might be
different than 24 in the original)
Jeremy
On Oct 25, 6:55 am, shday [EMAIL PROTECTED] wrote:
For the page below, I get the following error message:
Line: 24
While I haven't mastered all the finer points of Javascript (and
therefore can't exactly explain why your code didn't work), I do have
a suggestion: try using the wonderful Mochikit function keys():
for (var x in keys(o.p))
document.write 0.p[x]
Jeremy
On Oct 3, 11:34 am, delsur [EMAIL
cloneNode is part of core Javascript, not Mochikit; I imagine this is
the reason why it's not in the documentation ...
Jeremy
On Oct 1, 4:01 pm, tphyahoo [EMAIL PROTECTED] wrote:
I wanted to embed a table in a form, and it took me a long time to
figure out how to do it.
If cloneNode had
., 19:32, machineghost [EMAIL PROTECTED] wrote:
Short answer: I think you want e.src(), not e.target()
Longer answer: The target of an event is the element that triggered
the event. This is NOT the same as the element the event was attached
to.
For instance, let's say you had:
p id
Short answer: I think you want e.src(), not e.target()
Longer answer: The target of an event is the element that triggered
the event. This is NOT the same as the element the event was attached
to.
For instance, let's say you had:
p id=myPimg id=myImg src=whatever.jpg//p
and you hooked up an
As Jason said, example code would help a lot, but here's a quick
guess: do you have console.log(something) anywhere in your
callback's code? I often use console.log for debugging my code, and
if I forget to take it out afterward then my code breaks for anyone
without Firebug (because in their
).
Jeremy
On Aug 30, 8:49 am, Leo Soto M. [EMAIL PROTECTED] wrote:
On 8/29/07, machineghost [EMAIL PROTECTED] wrote:
The Mochikit Style function showElement works as follows:
codethis.showElement = m.partial(this.setDisplayForElement,
'block');/code
In other words, it sets the display
The Mochikit Style function showElement works as follows:
codethis.showElement = m.partial(this.setDisplayForElement,
'block');/code
In other words, it sets the display style of the element to block.
I suspect the reason it does this is because whoever wrote the
function figured we can't know
I didn't actually look at your code (sorry, I'm lazy), but the general
way to solve this is to add something like:
onSubmit=return myFunction();
to your form tag, and then define a function:
function myFunction(){
doSomething();
doSomethingElse();
if( validateData() validateSomeMore()){
31, 12:14 am, machineghost [EMAIL PROTECTED] wrote:
The other day I noticed that there is no createDOM shorthand function
for any of the definition list tags (DL, DT, and DD). Anyone know why?
--~--~-~--~~~---~--~~
You received this message because you
The other day I noticed that there is no createDOM shorthand function
for any of the definition list tags (DL, DT, and DD). Anyone know why?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post
Several people have responded (both in group and out) that MochiKit IS
updated regularly. This is great and ... not really news to me; I've
lurked in this list for a few months now. My point however, still
remains, because a few Google groups posts saying development is
active does not obviously
I'm just looking at the source code, but it seems to me that it does
check whether or not the element is initially displayed:
code
MochiKit.Style.getStyle(element, 'display') != 'none'
v.PAIRS[effect][1] :
v.PAIRS[effect][0]
/code
In other words, if the element's display style
I have an object:
function myObject(e){
connect(document, 'onclick', this.someFunction);
}
myObject.prototype.someFunction = *STUFF*
The object is initialized as the onClick action of an HTML Input
element:
connect(myInput, 'onclick', function(e){var myObjectInstance =
51 matches
Mail list logo
