I was trying to make a iframe thickbox window to show a google map with
a marker but for some reason the tile with the overlay doesn't get
displayed in FF at first and the centering of the map is wrong in IE and FF.
The example can be found at http://www.lworld.be/jquery/ . On the page
you see
David schrieb:
> I was trying to make a iframe thickbox window to show a google map with
> a marker but for some reason the tile with the overlay doesn't get
> displayed in FF at first and the centering of the map is wrong in IE and FF.
>
> The example can be found at http://www.lworld.be/jquery
Ⓙⓐⓚⓔ schrieb:
> I think we're on the right track but now I get a firefox exception.
>
> http://cigar.dynalias.org/js/rolly.js
>
Try this:
$.fn.rolly = function(options) {
var settings = $.extend({
speed: 'fast',
delay: 1
}, options || {});
Stephen Woodbridge schrieb:
> John,
>
> Thank you for looking at this. Removing the '//' helps a little. Now
> both the alerts work in FF, and in IE6 it no longer throws an error, but
> both of the searches in IE6 appear to return a null string (ie: '')
>
> Also changing the first alert to:
>
> a
Klaus Hartl schreef:
> David, how (when) do you initialize the map in the iframe?
I initialze the map on body load with the example code from the google
api. I've tried to initialze it using the jquery ready function but that
doesn't show the map at all.
> You could try to simply recenter the map
Jörn Zaefferer schrieb:
> Stephen Woodbridge schrieb:
>> John,
>>
>> Thank you for looking at this. Removing the '//' helps a little. Now
>> both the alerts work in FF, and in IE6 it no longer throws an error, but
>> both of the searches in IE6 appear to return a null string (ie: '')
>>
>> Also
David schrieb:
> Klaus Hartl schreef:
>> David, how (when) do you initialize the map in the iframe?
> I initialze the map on body load with the example code from the google
> api. I've tried to initialze it using the jquery ready function but that
> doesn't show the map at all.
>> You could try
> Ah, wait a moment, I have seen it already working with jQuery and
> thickbox, have a look here:
>
> http://www.nytsweeps.com/openhouse/
>
i changed the script to the nytsweeps way of working. They center the
google map by the marker coordinates and add the marker to the center of
the map b
Hi everyone, I've noticed while poking around in other people's jQuery code that there is a common misunderstanding of .blur(). As far as I can tell, the blur() function acts the same way as any other event handler in that allows something to happen when the event ( in this case leaving an element)
> But what I've seen is that people are trying to use it to /do/ the
> actual blurring. So, it might appear in a .click() function like so:
> $('a.clickme').click(function() {
>$(this).next('div').show();
>$(this).blur();
> });
>
> Presumably this is to move the focus off of the "a" tag
Nilesh Patel wrote:
> hey Jquery users,
>
> send some feedback this way, New Cheat sheets for Jquery edits are under
> way.
>
> feedback on what you like to see this time around.
>
> small description would be nice ya?,
> anyone have any ideas how to cut down the size of it ?
>
> take a look a
Stephen Woodbridge schrieb:
> 2. it looks like you have a typo on all of the {on}event you have
> {one}event, also you have ununload(fn) is this correct (i'm not familiar
> with the interface plugin?)
Stephen, that is no typo, that is jQuery's superuseful feature to have
an event only fired onc
Klaus Hartl wrote:
> Stephen Woodbridge schrieb:
>> 2. it looks like you have a typo on all of the {on}event you have
>> {one}event, also you have ununload(fn) is this correct (i'm not familiar
>> with the interface plugin?)
>
> Stephen, that is no typo, that is jQuery's superuseful feature to h
Jörn -
> #164 is not yet resolved, see my latest comment there.
> http://jquery.com/dev/bugs/bug/164/
> IE reacts really weird when using getAttribute on an XML element. Looks
> like we need some more workarounds.
That code has already been changed in SVN. Please make sure that
you're current. I
On Oct 15, 2006, at 7:58 AM, Klaus Hartl wrote:
> $('a.clickme').click(function() {
> $(this).next('div').show();
> this.blur();
> });
>
Thanks a lot, Klaus! This works in my test. So, it's a matter of
using the built-in JavaScript variable "this" instead of the jQuery
object "$(this
Hey,I'm the one that did nytsweeps. You're right that the magic is in the PHP (but it's really simple magic). Are you sure you're only able to use plain HTML? That complicates things a bit. How many separate maps will you need to display?
-- YehudaOn 10/15/06, David <[EMAIL PROTECTED]> wrote:
> Ah,
Karl Swedberg schrieb:
> On Oct 15, 2006, at 7:58 AM, Klaus Hartl wrote:
>
>> $('a.clickme').click(function() {
>> $(this).next('div').show();
>> this.blur();
>> });
>>
> Thanks a lot, Klaus! This works in my test. So, it's a matter of
> using the built-in JavaScript variable "this" in
On Oct 15, 2006, at 11:51 AM, Klaus Hartl wrote:
> Yes, the keyword this refers to the element and you call the
> build-in method blur on it.
>
> Consider the following:
>
> $('a').blur(function() {
> this.blur();
> });
>
> $('a.clickme').click(function() {
> $(this).next('div').show();
John Resig wrote:
> Jörn -
>
>> #164 is not yet resolved, see my latest comment there.
>> http://jquery.com/dev/bugs/bug/164/
>> IE reacts really weird when using getAttribute on an XML element. Looks
>> like we need some more workarounds.
>
> That code has already been changed in SVN. Please mak
Karl Swedberg schrieb:
> On Oct 15, 2006, at 11:51 AM, Klaus Hartl wrote:
>
>> Yes, the keyword this refers to the element and you call the
>> build-in method blur on it.
>>
>> Consider the following:
>>
>> $('a').blur(function() {
>> this.blur();
>> });
>>
>> $('a.clickme').click(function()
Yehuda Katz schreef:
> Hey,
>
> I'm the one that did nytsweeps. You're right that the magic is in the
> PHP (but it's really simple magic). Are you sure you're only able to
> use plain HTML? That complicates things a bit. How many separate maps
> will you need to display?
>
Yes it's some ISP fre
No I'm not from Texas :)
Texrep is a plugin to dynamically replace text by images using a font
file. It's based on the A list apart article : dynamic text
replacement. i just jqueried (is it a verb already) it.
The code can be found at http://dlinck.d.googlepages.com/jquerytexrep .
I'm going
> Just grabbed svn and $(document).ready(function(){alert("hello")}); does
> not fire on IE.
Sorry about that, it's now fixed in SVN rev 442.
--John
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
John Resig wrote:
>> Just grabbed svn and $(document).ready(function(){alert("hello")}); does
>> not fire on IE.
>
> Sorry about that, it's now fixed in SVN rev 442.
NP, thanks for the updates.
OK, this is good in FF, in IE6 no errors, but returns a '' for the xpath
queries instead of the corre
Hi folks,
I'd like to discuss the jQuery API in general and the current event API
in detail:
The main problem is the ambiguity of events, unevents and DOM methods.
Some examples:
$().unload() - Removes load event handlers AND triggers unload event
$().submit() - Triggers the submit event, but d
Hi plugin writers,
I'd like to point to a small change I made recently to the jQuery
Plugins Authoring article, for all those who take others code as
reference. The "reference code" to define defaults and parse options now
looks like this:
jQuery.fn.pluginMethod = function(options) {
var set
> $().unload() - Removes load event handlers AND triggers unload event
It actually doesn't do both, it just the last one that was created
(which, I think, is unload). The easiest way of fixing this would be
to rename stuff like 'click' to 'onclick' - that would remove all
namespace collisions. Bac
John Resig schrieb:
> Jörn -
>
>
>> #164 is not yet resolved, see my latest comment there.
>> http://jquery.com/dev/bugs/bug/164/
>> IE reacts really weird when using getAttribute on an XML element. Looks
>> like we need some more workarounds.
>>
>
> That code has already been changed in SV
On Oct 15, 2006, at 20:38, Jörn Zaefferer wrote:
> I'd like to point to a small change I made recently to the jQuery
> Plugins Authoring article, for all those who take others code as
> reference. The "reference code" to define defaults and parse
> options now
> looks like this:
>
> jQuery.fn.p
> I have revision 442, but there are still severe problems in IE6. There
> is an error on first page load, the second attr(String, Object) test
> fails completely, find dies at test #34. Third $.load and third $.ajax
> tests die, too. I'll try to get that MS Script Debugger, but until then,
> I hav
> Authoring guidelines say "Always use jQuery instead of $ inside your
> plugin code - that allows users to change the alias for jQuery in a
> single place." Does this mean only the first line jQuery.fn... or
> should also extend be jQuery.extend()?
That means everywhere inside. So if you did $.ex
> jQuery.fn.pluginMethod = function(options) {
> var settings = $.extend({
> stuff: [5, 3, 6, 1],
> name: "pete",
> speed: 5
> }, options || {});
> // other plugin code
> };
>
> So far this is the shortest way to write that particular snippet, and
> I'd like to see it in your plug
Dzone.com's AJAX section picked up ThickBox by Cody Lindley:
http://www.dzone.com/rsslinks/thickbox_21_slick_ajax_version_of_lightbox_functi.html
Rey...
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
John Resig schrieb:
>> jQuery.fn.pluginMethod = function(options) {
>> var settings = $.extend({
>> stuff: [5, 3, 6, 1],
>> name: "pete",
>> speed: 5
>> }, options || {});
>> // other plugin code
>> };
>>
>> So far this is the shortest way to write that particular snippet, and
>
John Resig schrieb:
>> $().unload() - Removes load event handlers AND triggers unload event
>
> It actually doesn't do both, it just the last one that was created
> (which, I think, is unload). The easiest way of fixing this would be
> to rename stuff like 'click' to 'onclick' - that would remove
First, I don't see how just splitting things up into optional plug-
ins really helps the problem. At most, it means that in some rare
cases, collision will be less frequent. But the majority of people
will not want to use jQuery without dom attributes or events. It can
also result in the ugl
Hello @ all,
first i wanna thank you guys from jquery for the absolutly definitly
amazing lib!!!
I was looking for a simple autocompletor in the plugins section and
found the one from the Interface plugin,
but this one isnt working right now cause of the update of jquery to
1.0.2. Overall it n
I feel there are too many names for the ajax functions they can
all be coded ajax.. and some share names with non ajax function (as
John mentioned)... perhaps new names for these weirdly overloaded
functions?
Which brings up the matter of deprecating... it would be helpful if
you use a functio
> I wouldn't mind loading a script 'jquery-junior-developer-edition.js'
> while writing new code!
I'm actually work on this right now. It'll have full type checking for
all jQuery methods along with full console logging. Hopefully this
will also include more-understandable error messages (we'll ha
> This is cool, but as plugin developer I cannot assume the latest jQuery
> SVN version, right?
Right - once this feature comes out (say, 1.0.3) then it would be more
acceptable to require it. I guess you could always just be on the safe
side and do || {}, at least until the release of 1.1 (to whi
> First, I don't see how just splitting things up into optional plug-
> ins really helps the problem. At most, it means that in some rare
> cases, collision will be less frequent. But the majority of people
> will not want to use jQuery without dom attributes or events. It can
> also result in the
There's also http://www.dyve.net/jquery?autocomplete
Feel free to use it.
On 10/15/06, stargate <[EMAIL PROTECTED]> wrote:
> Hello @ all,
>
> first i wanna thank you guys from jquery for the absolutly definitly
> amazing lib!!!
>
> I was looking for a simple autocompletor in the plugins section an
Wow, fast reply :)
But Where're the Docs for possible Options ?
Greets,
Ralf
Dylan Verheul schrieb:
> There's also http://www.dyve.net/jquery?autocomplete
> Feel free to use it.
>
> On 10/15/06, stargate <[EMAIL PROTECTED]> wrote:
>
>> Hello @ all,
>>
>> first i wanna thank you guys from jqu
> I'd like to point to a small change I made recently to the jQuery
> Plugins Authoring article, for all those who take others code as
> reference. The "reference code" to define defaults and parse options now
> looks like this:
I like this push for consistency. Does it make sense to do this now
Sorry, the link should be in the page but seems to be missing:
http://www.dyve.net/jquery/autocomplete.txt
On 10/15/06, stargate <[EMAIL PROTECTED]> wrote:
> Wow, fast reply :)
>
> But Where're the Docs for possible Options ?
>
> Greets,
>
> Ralf
>
> Dylan Verheul schrieb:
> > There's also http:/
Mike Alsup wrote:
>> I'd like to point to a small change I made recently to the jQuery
>> Plugins Authoring article, for all those who take others code as
>> reference. The "reference code" to define defaults and parse options now
>> looks like this:
>
> I like this push for consistency. Does it
Hi,
> The easiest way of fixing this would be
> to rename stuff like 'click' to 'onclick' - that would remove all
> namespace collisions. Back when jQuery was first released, all events
> were mapped to 'onclick' - but I changed this so that backwards
> support with Prototype would be easier.
>
>
On Oct 15, 2006, at 21:02, John Resig wrote:
>> Authoring guidelines say "Always use jQuery instead of $ inside your
>> plugin code - that allows users to change the alias for jQuery in a
>> single place." Does this mean only the first line jQuery.fn... or
>> should also extend be jQuery.extend()
>> Authoring guidelines say "Always use jQuery instead of $ inside your
>> plugin code - that allows users to change the alias for jQuery in a
>> single place."
> Does using jQuery instead of $ concern absolutely every case of $.
> For example code such as:
>
> $(this).html() should be jQuer
Hi John!
> And this is even shorter, plus there's one less variable being defined:
>
> jQuery.fn.pluginMethod = function(settings) {
> settings = jQuery.extend({
> // stuff
> }, settings);
> };
>
> As noted previously - make sure that you use jQuery.extend() instead
> of $.exten
No prob, thank you.
But anyway, it doesnt work @ me
styles are defined(copied from your page as first test, except the input
class), .js is included and loaded
and i did this code:
$("#sfield").autocomplete("usersearch.cgi", {
inputClass:searchfield });
after loading the
Steven Wittens schrieb:
> However, I think we do need to look at actual jQuery use here, as
> this is all about convenience. In my own jQuery code (which I'll
> admit is not that fancy), I mostly use jQuery objects to bind event
> handlers. When I change CSS or DOM properties, it is almost al
> There are two issues at play here:
> 1) The collision of method names.
> 2) The sheer number of methods attached to the jQuery object.
> #1 will only be solved through a change in the name of the methods
> (for example, from .load() to .onload() or .event.load()).
> #2 can only be solved by bre
Ⓙⓐⓚⓔ schrieb:
> I feel there are too many names for the ajax functions they can
> all be coded ajax.. and some share names with non ajax function (as
> John mentioned)... perhaps new names for these weirdly overloaded
> functions?
>
Good point. Having a common prefix for all ajax related met
Dave Methvin schrieb:
> Still, if you're writing a plugin only for your personal (well, non-public)
> use and you're not using prototype.js, then you can freely use $() in
> plugins because there will be no conflict.
>
I like the idea of using $ for prototyping. When you go back and
refactor an
Put them in the table footer and sort only the table body?
bmckenzie wrote:
>
> What's an efficient way to keep column totals at the bottom of a table
> sorted with the tableSorter plugin?
>
> Thanks.
>
> --
> Bruce
> http://www.2MinuteExplainer.com
>
>
Hi Mike,
if I use the following snippet:
var formIdSelector = '#hijax-me';
$(formIdSelector).ajaxForm(formIdSelector);
on a form with GET method it still posts the data. I changed ajaxSubmit
to this to make it work:
(http://stilbuero.de/demo/jquery/hijax.html
http://stilbuero.de/demo/jquery/fo
> > Authoring guidelines say "Always use jQuery instead of $
> > inside your plugin code - that allows users to change the
> > alias for jQuery in a single place." Does this mean only
> > the first line jQuery.fn... or should also extend be
> > jQuery.extend()?
> That means everywhere inside. So
Let's assume you are going to do 'something' that makes jQuery better but changes the API.
What is the suggested way to bind a click function or a toggle function NOW so we don't have to change later?
I'd rather change now before things go live. :)
Glen
On 10/15/06, Jörn Zaefferer <[EMAIL PROT
deprecated('1.0.2', "such and such is deprecated') ... and it gets
removed from the packed/production version, and left in to log in the
junior-developer-edition.
On 10/15/06, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Ⓙⓐⓚⓔ schrieb:
> > I feel there are too many names for the ajax functions
>
> Texrep is a plugin to dynamically replace text by images using a font
> file. It's based on the A list apart article : dynamic text
> replacement. i just jqueried (is it a verb already) it.
>
> The code can be found at http://dlinck.d.googlepages.com/jquerytexrep .
> I'm going to try to fi
As I read differences in DOM of IE vs. Moz I realized a possible problem
with accessing $(elm).css('float').
Because accessing inline style props in Moz can be accessed by elm.style
way but when we need a value of computed style (like IE .currentStyle) we
need
to reach it via getComputedStyle().
Hi everyone,
i'm using vim for my developing most of the time but that makes problems
with highlighting if have have many different language blocks (jquery
insode of javascript that is inside of php/html). So i'm searching for
an editor to have better jquery support (or find a way to extend vim?)
> > $().unload() - Removes load event handlers AND triggers unload event
>
> It actually doesn't do both, it just the last one that was
> created (which, I think, is unload).
Well of course it's unload. So is the first one - that's the problem! :-)
Here's the actual code from event.js in the or
try out http://aptana.com
no php support yet, but its a start.
i use jEdit, http://jedit.org
On 10/15/06, Truppe Steven <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> i'm using vim for my developing most of the time but that makes problems
> with highlighting if have have many different language
Klaus,
Thanks for catching that! I totally missed that the 'get's weren't
working and that the 'get' was not augmenting the url. I'll have to
improve my unit tests!
I'll be committing the form plugin to svn within the next day or two.
Thanks again.
Mike
> jQuery.fn.ajaxSubmit = function(tar
Thanks Rix. This is now fixed in SVN and here is a test page.
http://brandonaaron.net/jquery/193/test.html
Hopefully thats the end of this one.
--
Brandon Aaron
On 10/15/06, Rix Beck <[EMAIL PROTECTED]> wrote:
> As I read differences in DOM of IE vs. Moz I realized a possible problem
> with acc
On Oct 15, 2006, at 5:55 PM, Matt Stith wrote:
> try out http://aptana.com
>
> no php support yet, but its a start.
>
> i use jEdit, http://jedit.org
>
> On 10/15/06, Truppe Steven <[EMAIL PROTECTED]> wrote:
>> Hi everyone,
>>
>> i'm using vim for my developing most of the time but that makes
>>
Here is a first run at fixing the issues with appending a string of
HTML to select elements. It isn't very pretty and I could use some
testers. I've tested the little demo I made in Safari 2.0.4, IE6,
Firefox 1.5 on Win and Mac. But testing/using it in your own use-cases
will be very helpful.
The
Olaf,
How about:
var layer = '';
___
SEAN O
Olaf wrote:
>
> Hi at all,
> i works not so long with JS. I will a var to gif in Jquery, the Snippet:
>
>
> var layer = '2';
> $(document).ready(function(){
> $('#menu-layer0').tabs({on: (layer)});
> });
>
>
> The 2 is generated with PHP a
Folks:
I'm looking at using the jCarousel plugin on my site, but just viewing
the examples on the author's site fails in FF(Linux) and Konqueror.
In FF(1.5.0.4), the carousel container is visible but nothing else. And
in Konqueror (KDE-3.5.2), the carousel container is not even visible.
Is th
hey all, anyone else seen this too?
http://ajaxian.com/archives/benchmark-prototype-and-jquery
Claudio Cicali thinks benchmarks are boring and useless, so he decided
to conduct a series of micro-benchmarks of CSS selector tests with both
Prototype and jQuery. He decided to do this after he saw
Looks like jquery and prototype both win and lose nearly the same amount
of tests.
They also didn't factor in the initial loading size of the prototype
library, or the time saved by writing jquery syntax. This is about as
fair as a political debate.
Will
> hey all, anyone else seen this too?
>
I'm find a bug in jQuery's Cookie plugIn.
When you write more than 2 cookies, from the second, you could not read it value correctly.
It's because read document.cookie is "cookie1=val1; cookie2=val2", behind ";", there is a blank. So the source code line 72 cause error "if (
cookie.substring(0, n
still doesn't work.. I simplified the plug in to:
$.fn.rolly = function(options) {
var settings = $.extend({
speed: 'fast',
delay: 1
}, options || {});
var self = this;
var rollover = function() {
self.children().e
If you run into problem, I suggest you start out with the example code
(which works), replace the dummy php file with your cgi, and slowly
work towards your own implementation.
I haven't tested this with jQuery 1.0.2 yet, so you might want to try
it with an earlier version.
Also, load Firefox wit
Sean O wrote:
>
> How about:
> var layer = '';
>
Oh, i stupid
This works great :)
$(document).ready(function(){
$('#menu-layer0').tabs({on: $layer});
});
Thank you
--
View this message in context:
http://www.nabble.com/Variable-from-PHP-to-Jquery-tf2448700.html#a6829282
Sent from the JQu
Hi there,I still don't know what plugin it causes..however, it's not too important, it's only a prototype. But if you want to look at it yourself:http://paul.jquery.com/plugins/demo_mk/
Save it and uncomment this line:$(drag).children().removeClass("highlighted");then try to drag a row around and d
Olaf schreef:
> Oh, i stupid
> This works great :)
>
>
> $(document).ready(function(){
> $('#menu-layer0').tabs({on: $layer});
> });
>
>
It's a bit scary to see it like that. If you are going to mix two
programming languages try to seperate them visualy. It will save you
much debugging time
79 matches
Mail list logo
