Hi guys,
After i've done a lot (+8 weeks!) of work on the window class it's now
ready to be released to the public for beta testing. I'm hoping to
release this plugin at the same time jQuery 1.1 becomes available, but
all bugs have to be squised off course.
The plugin makes use of my cssHover
Fully agree! Providing a full release for newbies and as reference
for documentation on the one hand and a custom build for further
needs should be just fine. As soon as you are familiar enough with
jQuery tp use the custom build, you won't worry about missing methods
referenced in the
I'd propose something like $().fieldValue() and $().fieldSerialize
be added to the form plugin. Both could take an optional
successful only argument indicating if non-successful controls
should be ignored. fieldValue() would return the value of the
first matched element, in array form if
Personally, 19k is tiny to me compared to the others out there. Even 25k
would be tiny still. However, I think the form handling is something that
makes sense to rely on a plugin.
My personal goal for jQuery is to have it be smaller in size
(compressed) than Prototype (compressed) and
I could probably do a run through of the code and
reduce the size of the download by a couple hundred KB, no problem.
couple hundred BYTES! That'd be one heck of an optimization!
--John
___
jQuery mailing list
discuss@jquery.com
After i've done a lot (+8 weeks!) of work on the window class it's now
ready to be released to the public for beta testing. I'm hoping to
release this plugin at the same time jQuery 1.1 becomes available, but
all bugs have to be squised off course.
Well, whatever may come, you were quite
I still think that using a namespace and providing a short cut like $A
is the best way to handle this, instead of extending the element or
prototype. I think we could even get chaining to work properly if we
really wanted too. We could also probably provide a way to extend the
prototype if
That sounds like a good solution to me. It puts the form code with other
form code.
I just started using the form plugin today and noticed that it doesn't pass
along the error callback in ajaxSubmit. I've changed my local copy but I
suspect others might want that as well.
That's a great
That sounds like a good solution to me. It puts the form code with other
form code.
I just started using the form plugin today and noticed that it doesn't pass
along the error callback in ajaxSubmit. I've changed my local copy but I
suspect others might want that as well.
That's a
Hola nuevamente David y Choan:
Por más que leo y miro el código no logro entenderlo pues soy un poco novato
con jQuery y de Javascript no se mucho, lo he usado un poco en validaciones
pero con el boom de la Web2.0 veo que se pueden hacer cosas increíbles. ¿Me
pueden dar un norte para guiarme y
Hi everyone,
I've been getting increasingly frustrated by the flexibility and output from
all of the WYSIWYG editors available for the web so I want to try and build
an editor experience for our 2nd generation of CMS that will achieve the
following:
- Integrate in to our sites without
Ok, it's very simple indeed, and doesn't actually let you edit anything!!
However, the idea is that you can designate a div as the 'editor' and then
within this you can drop elements (I would imagine having a drop zone at
the
bottom?) for example:
- p tag
- h1-h4 etc
- ul
-
101 - 112 of 112 matches
Mail list logo