[Proto-Scripty] space dust particles flying like fireflies?
Hi, I just found this amazing looking technique that utilizes jquery library to produce this kind of effect: http://cliframework.com/ The technique is explained here: http://net.tutsplus.com/articles/news/the-firefly-effect-the-new-plus-tutorial/ Unforutnately the whole tutorial can be accessed with payment only. Is there a nice way to produce this particle effect with prototype scriptaculous? Thanks for all answers! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Prototype Selector Speed
Hi, Is there any plans in the future to improve on prototype's speed? Yes. The core team are working on integrating the Sizzle selector engine[1] (which is what the latest version of jQuery uses). (This is more of a challenge than it sounds; switching selector engines touches a lot of things besides just the $$ and Element#select methods.) I *think* that's slated for the next release, but don't quote me. [1] http://sizzlejs.com/ HTH, -- T.J. Crowder tj / crowder software / com www / crowder software / com On Sep 21, 5:06 am, Andy Daykin daykina...@gmail.com wrote: Hello, I have been using prototype for a few months now, and so far I have enjoyed the functionality that it brings. However, I have noticed that it's speed is lacking. This makes me tentative to use prototype for a rather large project that I have been planning. To confirm this, I ran the tests fromhttp://mootools.net/slickspeed/by checking out the project from SVN, and used the latest versions of all of the frameworks listed. Prototype and mootools consistently finished at the bottom, which concerns me a little. After looking at the results I have been seriously considering switching to JQuery, although I am disappointed at their lack of OOP support. Is there any plans in the future to improve on prototype's speed? Also has there been a tentative release date set for scripty2? I'm reluctant to develop anything that heavily uses scriptaculous, since it appears scripty2 is in alpha state, although it has been that way since June. Thanks, -Andy --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Prototype Selector Speed
On 21.9.2009, at 11.04, T.J. Crowder wrote: Hi, Is there any plans in the future to improve on prototype's speed? Yes. The core team are working on integrating the Sizzle selector engine[1] (which is what the latest version of jQuery uses). (This is more of a challenge than it sounds; switching selector engines touches a lot of things besides just the $$ and Element#select methods.) I *think* that's slated for the next release, but don't quote me. Sam just tweeted [1] that they're using it already on Highrise, so I'd guess it's pretty much in a working condition. //jarkko [1] http://twitter.com/sstephenson/status/439058 -- Jarkko Laine http://jlaine.net http://dotherightthing.com http://www.railsecommerce.com http://odesign.fi --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox
I used up() and didnt work, it is the same error.
Here is the test page
http://pts.raidenenergy.com/index.php?option=com_contentview=categorylayout=blogid=8Itemid=14lang=en
and this is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
//alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 18, 5:27 am, david david.brill...@gmail.com wrote:
HiJuan,
IE has much trouble with table. So not surprinsing that IE doesn't
work as expected.
--
david
On 17 sep, 19:10,JuanDiegojuandieg...@gmail.com wrote:
Thanks.
One more thing, I am doing this inside a joomla so those divs are
inside a table inside thecontent module of joomla. When ever I use
alert(e2) I thought i was getting the table, because it said something
about table element, so for some reason in internet explorer it goes
directly to the body. That is what it is happening right? I am going
to try with teh up() function.
Ken I am using [2] because there is some text with p/p that i
though it wasnt important. But thanks for noticing.
Juan
On Sep 17, 6:08 am, david david.brill...@gmail.com wrote:
Hi Kev,
the getOffSetParent() return the closest positioned ancestor, and if
not found return the body !
That's why for some element, parent is not positionned (CSS position
property) and it return the body element.
As you say, up() is much more appropriate in this case.
--
david
On 17 sep, 10:38, Kevin Porter k...@9ballpool.co.uk wrote:
HiJuan,
For me, I get the error at e2.childElements()[2].setStyle
e2 at that point is the body element. Is that what you want?
I guess you want the LI element? If so, maybe .up() would be a better
choice than .getOffSetParent()?
Also, you probably want to use [1] instead of [2] to reference the
second element of the LI. (it's
a zero-indexed array).
regards,
- Kev
JuanDiegowrote:
Ok, so I cleaned up my code. I used each instead of a For loop, so
now it works in every Browser except IE8. I havent tested it in other
versions of IE. Like 6 o 7.
So here is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
var e2 =element.getOffsetParent();
alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
var e2 =element.getOffsetParent();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
I get an error on Line 14. The object does not accept this property
or method So the problem seems to be in this line var e2
=element.getOffsetParent();
With getOffsetParent function.
This code works in opera, konqueror, safari, firefox.
Thanks
On Sep 17, 12:36 am,JuanDiegojuandieg...@gmail.com wrote:
By the way i just found out that
var lista_izq=$$('div.lista_izq')[i].childElements()[0].childElements
();
is the problem in IE explorer. In opera works but in IE8 is a problem
On Sep 17, 12:19 am,JuanDiegojuandieg...@gmail.com wrote:
Hi I havent use javascript and prototype in a while so maybe i am
doing something really wrong.
So here is what I am trying to do with prototype
I have a a few places in my page with a set of to divs divs,
lista_izq
and lista_der, with a list inside list_izq
div class=lista_izq
ul
lidiv class=texttext1/div
div class=hidden_texthidden1/div
/li
lidiv class=texttext2/div
div class=hidden_texthidden2/div
/li
/ul
/div
div class=lista_dernbsp/div
So when ever the mouse is over the text1 or
[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox
First things first - you've got four up()s in a row, which is likely to
return you the document or window object.
If you want the LI element you only need one up() from the div.
regards,
- Kev
Juan Diego wrote:
I used up() and didnt work, it is the same error.
Here is the test page
http://pts.raidenenergy.com/index.php?option=com_contentview=categorylayout=blogid=8Itemid=14lang=en
and this is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
//alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 18, 5:27 am, david david.brill...@gmail.com wrote:
HiJuan,
IE has much trouble with table. So not surprinsing that IE doesn't
work as expected.
--
david
On 17 sep, 19:10,JuanDiegojuandieg...@gmail.com wrote:
Thanks.
One more thing, I am doing this inside a joomla so those divs are
inside a table inside thecontent module of joomla. When ever I use
alert(e2) I thought i was getting the table, because it said something
about table element, so for some reason in internet explorer it goes
directly to the body. That is what it is happening right? I am going
to try with teh up() function.
Ken I am using [2] because there is some text with p/p that i
though it wasnt important. But thanks for noticing.
Juan
On Sep 17, 6:08 am, david david.brill...@gmail.com wrote:
Hi Kev,
the getOffSetParent() return the closest positioned ancestor, and if
not found return the body !
That's why for some element, parent is not positionned (CSS position
property) and it return the body element.
As you say, up() is much more appropriate in this case.
--
david
On 17 sep, 10:38, Kevin Porter k...@9ballpool.co.uk wrote:
HiJuan,
For me, I get the error at e2.childElements()[2].setStyle
e2 at that point is the body element. Is that what you want?
I guess you want the LI element? If so, maybe .up() would be a better
choice than .getOffSetParent()?
Also, you probably want to use [1] instead of [2] to reference the
second element of the LI. (it's
a zero-indexed array).
regards,
- Kev
JuanDiegowrote:
Ok, so I cleaned up my code. I used each instead of a For loop, so
now it works in every Browser except IE8. I havent tested it in other
versions of IE. Like 6 o 7.
So here is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
var e2 =element.getOffsetParent();
alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
var e2 =element.getOffsetParent();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
I get an error on Line 14. The object does not accept this property
or method So the problem seems to be in this line var e2
=element.getOffsetParent();
With getOffsetParent function.
This code works in opera, konqueror, safari, firefox.
Thanks
On Sep 17, 12:36 am,JuanDiegojuandieg...@gmail.com wrote:
By the way i just found out that
var lista_izq=$$('div.lista_izq')[i].childElements()[0].childElements
();
is the problem in IE explorer. In opera works but in IE8 is a problem
On Sep 17, 12:19 am,JuanDiegojuandieg...@gmail.com wrote:
Hi I havent use javascript and prototype in a while so maybe i am
doing something really wrong.
So here is what I am trying to do with prototype
I have a a few places in my page with a set of to divs divs, lista_izq
and lista_der, with a list inside list_izq
div class=lista_izq
ul
lidiv class=texttext1/div
div
[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox
I dont want the LI elements. Here is how it is setup,
div class=lista_izq
ul
lidiv class=texttext1/div
div class=hidden_texthidden1/div
/li
lidiv class=texttext2/div
div class=hidden_texthidden2/div
/li
/ul
/div
div class=lista_dernbsp/div
I want display my message in lista_der. So that is why i use all
those up(), i guess I can use 4 up and one next.
On Sep 21, 3:50 am, Kevin Porter k...@9ballpool.co.uk wrote:
First things first - you've got four up()s in a row, which is likely to
return you the document or window object.
If you want the LI element you only need one up() from the div.
regards,
- Kev
JuanDiegowrote:
I used up() and didnt work, it is the same error.
Here is the test page
http://pts.raidenenergy.com/index.php?option=com_contentview=categor...
and this is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
//alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 18, 5:27 am, david david.brill...@gmail.com wrote:
HiJuan,
IE has much trouble with table. So not surprinsing that IE doesn't
work as expected.
--
david
On 17 sep, 19:10,JuanDiegojuandieg...@gmail.com wrote:
Thanks.
One more thing, I am doing this inside a joomla so those divs are
inside a table inside thecontent module of joomla. When ever I use
alert(e2) I thought i was getting the table, because it said something
about table element, so for some reason in internet explorer it goes
directly to the body. That is what it is happening right? I am going
to try with teh up() function.
Ken I am using [2] because there is some text with p/p that i
though it wasnt important. But thanks for noticing.
Juan
On Sep 17, 6:08 am, david david.brill...@gmail.com wrote:
Hi Kev,
the getOffSetParent() return the closest positioned ancestor, and if
not found return the body !
That's why for some element, parent is not positionned (CSS position
property) and it return the body element.
As you say, up() is much more appropriate in this case.
--
david
On 17 sep, 10:38, Kevin Porter k...@9ballpool.co.uk wrote:
HiJuan,
For me, I get the error at e2.childElements()[2].setStyle
e2 at that point is the body element. Is that what you want?
I guess you want the LI element? If so, maybe .up() would be a better
choice than .getOffSetParent()?
Also, you probably want to use [1] instead of [2] to reference the
second element of the LI. (it's
a zero-indexed array).
regards,
- Kev
JuanDiegowrote:
Ok, so I cleaned up my code. I used each instead of a For loop, so
now it works in every Browser except IE8. I havent tested it in other
versions of IE. Like 6 o 7.
So here is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
var e2 =element.getOffsetParent();
alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
var e2 =element.getOffsetParent();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
I get an error on Line 14. The object does not accept this property
or method So the problem seems to be in this line var e2
=element.getOffsetParent();
With getOffsetParent function.
This code works in opera, konqueror, safari, firefox.
Thanks
On Sep 17, 12:36 am,JuanDiegojuandieg...@gmail.com wrote:
By the way i just found out that
var lista_izq=$$('div.lista_izq')[i].childElements()[0].childElements
();
is the problem in IE explorer. In opera works but in IE8 is a problem
On Sep 17, 12:19 am,JuanDiegojuandieg...@gmail.com wrote:
Hi I havent use javascript and prototype in a while so maybe i am
doing something really wrong.
So here is what I am trying to do with prototype
[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox
I cleaned up a little my code it still doesnt work in IE8
this is the code
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
//alert(e2);
e2.setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
e2.innerHTML= ;
e2.setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 21, 3:59 am, Juan Diego juandieg...@gmail.com wrote:
I dont want the LI elements. Here is how it is setup,
div class=lista_izq
ul
lidiv class=texttext1/div
div class=hidden_texthidden1/div
/li
lidiv class=texttext2/div
div class=hidden_texthidden2/div
/li
/ul
/div
div class=lista_dernbsp/div
I want display my message in lista_der. So that is why i use all
those up(), i guess I can use 4 up and one next.
On Sep 21, 3:50 am, Kevin Porter k...@9ballpool.co.uk wrote:
First things first - you've got four up()s in a row, which is likely to
return you the document or window object.
If you want the LI element you only need one up() from the div.
regards,
- Kev
JuanDiegowrote:
I used up() and didnt work, it is the same error.
Here is the test page
http://pts.raidenenergy.com/index.php?option=com_contentview=categor...
and this is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
//alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 18, 5:27 am, david david.brill...@gmail.com wrote:
HiJuan,
IE has much trouble with table. So not surprinsing that IE doesn't
work as expected.
--
david
On 17 sep, 19:10,JuanDiegojuandieg...@gmail.com wrote:
Thanks.
One more thing, I am doing this inside a joomla so those divs are
inside a table inside thecontent module of joomla. When ever I use
alert(e2) I thought i was getting the table, because it said something
about table element, so for some reason in internet explorer it goes
directly to the body. That is what it is happening right? I am going
to try with teh up() function.
Ken I am using [2] because there is some text with p/p that i
though it wasnt important. But thanks for noticing.
Juan
On Sep 17, 6:08 am, david david.brill...@gmail.com wrote:
Hi Kev,
the getOffSetParent() return the closest positioned ancestor, and if
not found return the body !
That's why for some element, parent is not positionned (CSS position
property) and it return the body element.
As you say, up() is much more appropriate in this case.
--
david
On 17 sep, 10:38, Kevin Porter k...@9ballpool.co.uk wrote:
HiJuan,
For me, I get the error at e2.childElements()[2].setStyle
e2 at that point is the body element. Is that what you want?
I guess you want the LI element? If so, maybe .up() would be a better
choice than .getOffSetParent()?
Also, you probably want to use [1] instead of [2] to reference the
second element of the LI. (it's
a zero-indexed array).
regards,
- Kev
JuanDiegowrote:
Ok, so I cleaned up my code. I used each instead of a For loop, so
now it works in every Browser except IE8. I havent tested it in other
versions of IE. Like 6 o 7.
So here is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
var e2 =element.getOffsetParent();
alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
var e2
[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox
It works for me in IE8!
Kill IE8, re-open it and try again.
If it still doesn't work, what error are you getting?
regards,
- Kev
Juan Diego wrote:
I cleaned up a little my code it still doesnt work in IE8
this is the code
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
//alert(e2);
e2.setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
e2.innerHTML= ;
e2.setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 21, 3:59 am, Juan Diego juandieg...@gmail.com wrote:
I dont want the LI elements. Here is how it is setup,
div class=lista_izq
ul
lidiv class=texttext1/div
div class=hidden_texthidden1/div
/li
lidiv class=texttext2/div
div class=hidden_texthidden2/div
/li
/ul
/div
div class=lista_dernbsp/div
I want display my message in lista_der. So that is why i use all
those up(), i guess I can use 4 up and one next.
On Sep 21, 3:50 am, Kevin Porter k...@9ballpool.co.uk wrote:
First things first - you've got four up()s in a row, which is likely to
return you the document or window object.
If you want the LI element you only need one up() from the div.
regards,
- Kev
JuanDiegowrote:
I used up() and didnt work, it is the same error.
Here is the test page
http://pts.raidenenergy.com/index.php?option=com_contentview=categor...
and this is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
//alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 18, 5:27 am, david david.brill...@gmail.com wrote:
HiJuan,
IE has much trouble with table. So not surprinsing that IE doesn't
work as expected.
--
david
On 17 sep, 19:10,JuanDiegojuandieg...@gmail.com wrote:
Thanks.
One more thing, I am doing this inside a joomla so those divs are
inside a table inside thecontent module of joomla. When ever I use
alert(e2) I thought i was getting the table, because it said something
about table element, so for some reason in internet explorer it goes
directly to the body. That is what it is happening right? I am going
to try with teh up() function.
Ken I am using [2] because there is some text with p/p that i
though it wasnt important. But thanks for noticing.
Juan
On Sep 17, 6:08 am, david david.brill...@gmail.com wrote:
Hi Kev,
the getOffSetParent() return the closest positioned ancestor, and if
not found return the body !
That's why for some element, parent is not positionned (CSS position
property) and it return the body element.
As you say, up() is much more appropriate in this case.
--
david
On 17 sep, 10:38, Kevin Porter k...@9ballpool.co.uk wrote:
HiJuan,
For me, I get the error at e2.childElements()[2].setStyle
e2 at that point is the body element. Is that what you want?
I guess you want the LI element? If so, maybe .up() would be a better
choice than .getOffSetParent()?
Also, you probably want to use [1] instead of [2] to reference the
second element of the LI. (it's
a zero-indexed array).
regards,
- Kev
JuanDiegowrote:
Ok, so I cleaned up my code. I used each instead of a For loop, so
now it works in every Browser except IE8. I havent tested it in other
versions of IE. Like 6 o 7.
So here is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox
It is still not working. I am going to try in another machine. I get
this error because the browser is in spanish. El objeto no acepta
esta propiedad o metodo. Which means the object does not accept this
property or method in the lines 15 and 28.
On Sep 21, 4:23 am, Kevin Porter k...@9ballpool.co.uk wrote:
It works for me in IE8!
Kill IE8, re-open it and try again.
If it still doesn't work, what error are you getting?
regards,
- Kev
Juan Diego wrote:
I cleaned up a little my code it still doesnt work in IE8
this is the code
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
//alert(e2);
e2.setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
e2.innerHTML= ;
e2.setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 21, 3:59 am, Juan Diego juandieg...@gmail.com wrote:
I dont want the LI elements. Here is how it is setup,
div class=lista_izq
ul
lidiv class=texttext1/div
div class=hidden_texthidden1/div
/li
lidiv class=texttext2/div
div class=hidden_texthidden2/div
/li
/ul
/div
div class=lista_dernbsp/div
I want display my message in lista_der. So that is why i use all
those up(), i guess I can use 4 up and one next.
On Sep 21, 3:50 am, Kevin Porter k...@9ballpool.co.uk wrote:
First things first - you've got four up()s in a row, which is likely to
return you the document or window object.
If you want the LI element you only need one up() from the div.
regards,
- Kev
JuanDiegowrote:
I used up() and didnt work, it is the same error.
Here is the test page
http://pts.raidenenergy.com/index.php?option=com_contentview=categor...
and this is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
//alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 18, 5:27 am, david david.brill...@gmail.com wrote:
HiJuan,
IE has much trouble with table. So not surprinsing that IE doesn't
work as expected.
--
david
On 17 sep, 19:10,JuanDiegojuandieg...@gmail.com wrote:
Thanks.
One more thing, I am doing this inside a joomla so those divs are
inside a table inside thecontent module of joomla. When ever I use
alert(e2) I thought i was getting the table, because it said something
about table element, so for some reason in internet explorer it goes
directly to the body. That is what it is happening right? I am going
to try with teh up() function.
Ken I am using [2] because there is some text with p/p that i
though it wasnt important. But thanks for noticing.
Juan
On Sep 17, 6:08 am, david david.brill...@gmail.com wrote:
Hi Kev,
the getOffSetParent() return the closest positioned ancestor, and if
not found return the body !
That's why for some element, parent is not positionned (CSS position
property) and it return the body element.
As you say, up() is much more appropriate in this case.
--
david
On 17 sep, 10:38, Kevin Porter k...@9ballpool.co.uk wrote:
HiJuan,
For me, I get the error at e2.childElements()[2].setStyle
e2 at that point is the body element. Is that what you want?
I guess you want the LI element? If so, maybe .up() would be a better
choice than .getOffSetParent()?
Also, you probably want to use [1] instead of [2] to reference
the
second element of the LI. (it's
a zero-indexed array).
regards,
- Kev
JuanDiegowrote:
Ok, so I cleaned up my code. I used each instead of a For loop,
so
now it works in every Browser except IE8. I havent tested it in
other
versions of IE. Like 6 o 7.
So here is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element =
[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox
Damn IE. Ok thanks. I am going to take away elements from the page
where is the conflict. Thanks for your time.
Juan Diego
On Sep 21, 4:49 am, Kevin Porter k...@9ballpool.co.uk wrote:
Sorry, I didn't try your page, I was just using the test page I built to
test your code.
You're right, IE8 gives an error on your page.
It's complaining about this line:
var e2 = element.up().up().up().next();
You'll just have to debug - please find out exaclty what you get for
element.up(), element.up().up() etc. At some point
it's behaviour is differing from Firefox - when you find out what that
is we'll try and figure why the behaviour is different.
One thing I would suggest trying (from previous IE LI difficulties) is
to remove all whitespace from the UL/LI markup. However, the docs for
next() and up() say that whitespace nodes are totally ignored by these
functions, so that may not be the problem but it's probably worth a
minute to try.
Alternatively, you could try using a css rule in up()
(http://www.prototypejs.org/api/element/up) , eg:
var e2 = element.up('div.lista_izq').next();
Let me know how you get on. If those alternative suggestions don't work,
we really need you to debug to find out at exactly which point the IE8
behaviour is differing from that of normal browsers.
regards,
- Kev
Juan Diego wrote:
It is still not working. I am going to try in another machine. I get
this error because the browser is in spanish. El objeto no acepta
esta propiedad o metodo. Which means the object does not accept this
property or method in the lines 15 and 28.
On Sep 21, 4:23 am, Kevin Porter k...@9ballpool.co.uk wrote:
It works for me in IE8!
Kill IE8, re-open it and try again.
If it still doesn't work, what error are you getting?
regards,
- Kev
Juan Diego wrote:
I cleaned up a little my code it still doesnt work in IE8
this is the code
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
//alert(e2);
e2.setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
e2.innerHTML= ;
e2.setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 21, 3:59 am, Juan Diego juandieg...@gmail.com wrote:
I dont want the LI elements. Here is how it is setup,
div class=lista_izq
ul
lidiv class=texttext1/div
div class=hidden_texthidden1/div
/li
lidiv class=texttext2/div
div class=hidden_texthidden2/div
/li
/ul
/div
div class=lista_dernbsp/div
I want display my message in lista_der. So that is why i use all
those up(), i guess I can use 4 up and one next.
On Sep 21, 3:50 am, Kevin Porter k...@9ballpool.co.uk wrote:
First things first - you've got four up()s in a row, which is likely to
return you the document or window object.
If you want the LI element you only need one up() from the div.
regards,
- Kev
JuanDiegowrote:
I used up() and didnt work, it is the same error.
Here is the test page
http://pts.raidenenergy.com/index.php?option=com_contentview=categor...
and this is the code.
function listas(){
$$('div.texto').each(function(s) { Event.observe(s, 'mouseover',
reemplazarX)});
$$('div.texto').each(function(s) { Event.observe(s, 'mouseout',
borrar)});
};
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
//alert(e2);
e2.childElements()[2].setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.childElements()[2].innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().up();
e2.childElements()[2].innerHTML= ;
e2.childElements()[2].setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 18, 5:27 am, david david.brill...@gmail.com wrote:
HiJuan,
IE has much trouble with table. So not surprinsing that IE doesn't
work as expected.
--
david
On 17 sep, 19:10,JuanDiegojuandieg...@gmail.com wrote:
Thanks.
One more thing, I am doing this inside a joomla so those divs are
inside a table inside thecontent module of joomla. When ever I use
alert(e2) I thought i was getting the table, because it said
something
about table element, so for some reason in internet explorer it
goes
directly to the body. That is what it is happening right? I am
going
to try with teh up() function.
Ken I am using [2] because
[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox
Hi Juan,
I've only skimmed this, so apologies if this comment is completely off-
base, but you mentioned tables in there somewhere although I don't see
any tables in the HTML snippets. Do all of your tables have the
appropriate TBODY elements in them? I can see that being a difference
between browsers, particularly depending on what your DOCTYPE is.
It's a surprisingly well-kept secret that TR cannot appear directly
within TABLE, you must have a TBODY (or THEAD or TFOOT) in between:
table
tr
tdThis/td
/tr
tr
tdis/td
/tr
tr
tdWRONG/td
/tr
/table
table
tbody
tr
tdThis/td
/tr
tr
tdis/td
/tr
tr
tdright/td
/tr
/tbody
/table
Firefox will silently insert one for you; I don't know what IE's
behavior is (whether it inserts one or just doesn't worry about it).
Again, apologies if this is completely off-base.
Oh, and separately: If you find yourself writing:
someElement.up().up()
you can use
someElement.up(1)
...instead. (Yes, really 1, not 2 -- up() equals up(0), so up().up()
equals up(1). *Terrible* API choice, but there we are. Details in the
old API docs[1].)
[1] http://prototypejs.org/api/element/up
Good luck,
--
T.J. Crowder
tj / crowder software / com
www.crowdersoftware.com
On Sep 21, 11:08 am, Juan Diego juandieg...@gmail.com wrote:
Damn IE. Ok thanks. I am going to take away elements from the page
where is the conflict. Thanks for your time.
Juan Diego
On Sep 21, 4:49 am, Kevin Porter k...@9ballpool.co.uk wrote:
Sorry, I didn't try your page, I was just using the test page I built to
test your code.
You're right, IE8 gives an error on your page.
It's complaining about this line:
var e2 = element.up().up().up().next();
You'll just have to debug - please find out exaclty what you get for
element.up(), element.up().up() etc. At some point
it's behaviour is differing from Firefox - when you find out what that
is we'll try and figure why the behaviour is different.
One thing I would suggest trying (from previous IE LI difficulties) is
to remove all whitespace from the UL/LI markup. However, the docs for
next() and up() say that whitespace nodes are totally ignored by these
functions, so that may not be the problem but it's probably worth a
minute to try.
Alternatively, you could try using a css rule in up()
(http://www.prototypejs.org/api/element/up) , eg:
var e2 = element.up('div.lista_izq').next();
Let me know how you get on. If those alternative suggestions don't work,
we really need you to debug to find out at exactly which point the IE8
behaviour is differing from that of normal browsers.
regards,
- Kev
Juan Diego wrote:
It is still not working. I am going to try in another machine. I get
this error because the browser is in spanish. El objeto no acepta
esta propiedad o metodo. Which means the object does not accept this
property or method in the lines 15 and 28.
On Sep 21, 4:23 am, Kevin Porter k...@9ballpool.co.uk wrote:
It works for me in IE8!
Kill IE8, re-open it and try again.
If it still doesn't work, what error are you getting?
regards,
- Kev
Juan Diego wrote:
I cleaned up a little my code it still doesnt work in IE8
this is the code
function reemplazarX(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
//alert(e2);
e2.setStyle({
backgroundColor: '#020506',
opacity: 1.0,
borderLeft:'1px #FFF solid'
});
e2.innerHTML= element.next().innerHTML;
}
function borrar(){
var element = this;
//var e2 =element.getOffsetParent();
var e2 =element.up().up().up().next();
e2.innerHTML= ;
e2.setStyle({
backgroundColor: '#000',
opacity: 0.0
});
}
On Sep 21, 3:59 am, Juan Diego juandieg...@gmail.com wrote:
I dont want the LI elements. Here is how it is setup,
div class=lista_izq
ul
lidiv class=texttext1/div
div class=hidden_texthidden1/div
/li
lidiv class=texttext2/div
div class=hidden_texthidden2/div
/li
/ul
/div
div class=lista_dernbsp/div
I want display my message in lista_der. So that is why i use all
those up(), i guess I can use 4 up and one next.
On Sep 21, 3:50 am, Kevin Porter k...@9ballpool.co.uk wrote:
First things first - you've got four up()s in a row, which is likely
to
return you the document or window object.
If you want the LI element you only need one up() from the div.
regards,
- Kev
JuanDiegowrote:
I used up() and didnt work, it is the same error.
Here is the test page
http://pts.raidenenergy.com/index.php?option=com_contentview=categor...
and this is the code.
[Proto-Scripty] Re: Dynamic test after ajax call
Hi Tj - Thanks for the prompt response. It really amazed me, when I heard that I can see source code of the original document and not the later things that got updated through the Ajax updater. We have this dependency where we need to make series of Java script calls based on the dynamic response created by the Ajax updater. That includes the dynamically generated element id's and stuff. If these are not going to be visible in generated source, how am I supposed to make advantage. Is there a way, though prorotype Ajax ? Thanks On Sep 19, 8:21 am, T.J. Crowder t...@crowdersoftware.com wrote: Hi, View source will only show you the original source of the document, not any later modifications you make to the DOM (e.g., via Ajax.Updater or any of several other means). Why does it matter? What is it you're trying to achieve looking at the source? If it's just that you're trying to debug the markup or something, you can use Firefox with the Firebug[1] add-on, which will show you the current DOM tree rather than the original source. [1]http://getfirebug.com/ HTH, -- T.J. Crowder tj / crowder software / comwww.crowdersoftware.com On Sep 18, 11:27 pm,Kumarkumar.k.re...@gmail.com wrote: Hi All - I am using prototype Ajax updater. The main intenntion of using updater is to show users a loading icon, but in background we are making a series webservice calls to wide variety of systems, then collabarate all the data to users at one go. The page loads and calls ajax updater. Updater inturn updates a div tag with a search results. (results are processed in another jsp page). Here is the problem. After the entire page gets loaded with results, when I see the source I do not see the results grid in the source page. I know its just the code that got loaded while making ajax calls. How can I induce the code in to the same source file after the ajax call. Did any one face this issue before. if you have any thoughts, please share it across. Please shoot me an email, if you are still not clear with the issue. Thanks- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Prototype ajax history
Hey Everyone, I've finished a project that handles the problems of browser history when implementing ajax solutions. It's built to integrate with prototype perfectly and borrows a lot of the same concepts. The idea is an event driven system where all XHRs go through a single 'service' object which deals with server communications. This way we can register each request with the browser's history module and be able to accommodate the user as he/she traverses the history array. Take a look when you have a minute, its surely worth the time. http://positionabsolute.net/blog/2009/09/ajax-history-wars.php#number=6 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: .select on a combo
speedpac...@gmail.com wrote:
Hi Federico,
the readattroibute isn't giving the issues; that works fine, and the
alert does indeed return the expected value.
The line in the code no longer working is
selectedItem = orderOptions.select('[value=' + orderOptions.getValue
() + ']');
Hi David,
Element.select() returns a list of elements, so you may want to try down
instead:
selectedItem = orderOptions.down('[value=' + orderOptions.getValue()
+ ']');
Furthermore, I'm not sure that .select() on a SELECT element is not
something very different from Element.select() (a SELECT being somewhat
akin to an INPUT -- but I don't know really).
So I hope and feel rather confident that the .down() will help.
Have fun
Daniel
where orderOptions is the combo, and the selectedItem should be an
option element which has additional attributes set to it...
Thanks for the feedback though.
Any more ideas, as I'm lost with this issue.
David.
On Sep 19, 5:03 pm, jacknife federico.bore...@gmail.com wrote:
hi,
have you tried to use the Element class methods readAttribute/
writeAttribute instead that ordinary getAttribute/setAttribute?
i recently experienced some issues using getAttribute to retrieve
setted parameters.
Federico
On Sep 18, 7:33 pm, speedpac...@gmail.com speedpac...@gmail.com
wrote:
Hi Marko,
Great idea on combining the different attributes into one value
attribute with the pipe character. I'll consider it for a later
version, because this obviously also requires changes on the
serverside as we'll end up with other values being sent to the
server...
The class tihngy I knew and was on my todo list to change to that...
Unfortunately it doesn't fix my issue at this time (unless I'm
misinterpreting what you are saying...)
Have you gotten a chance to look into that biyt of code not giving me
the result I believed I should have received (and did before I
upgraded...)
Thanks again for the feedback - I really do appreciate it!
David.
On Sep 18, 7:01 pm, Marko gm.ma...@gmail.com wrote:
Hi,
Instead of adding attributes on element you can rewrite it like this:
option value=N15 domain=hjkhhjh.ch prepaid_total=18.50 EUR
postpaid_total=23.15 EURRegistreer voor 1 Jaar/option
=
option value=code|domain|pre_total|post_totalRegistreer voor 1
Jaar/option
=
option value=N15|hjkhhjh.ch|18.50 EUR|23.15 EURRegistreer voor 1
Jaar/option
You can get value like this:
selectedItem = orderOptions.select('[value=' +
orderOptions.getValue() + ']');
=
As this is equal to orderOptions you can do:
selectedItem = $F(this)
Then you can split it and get array:
selectedItem.split(|)
You can also rewrite your selects like this:
Instead of: td f=prepaid
write just: td class=prepaid
tdPrepaid = rec[0].select('[f=prepaid]');
=
tdPrepaid = rec[0].select('.prepaid');
This way you will preserve valid HTML
I think you get idea how to rewrite it.
- Marko
speedpac...@gmail.com wrote:
Hello,
I'm trying my secod post here - I never got my first to end up on the
list, so l'ts try it through the google groups website directly now...
I'm having an issue that I hope someone here can help me with...
I have the following code:
HTML:
--
select id=orderOption[hjkhhjh.ch] domain=hjkhhjh.ch
name=orderOption[hjkhhjh.ch]
option value=N15 domain=hjkhhjh.ch prepaid_total=18.50 EUR
postpaid_total=23.15 EURRegistreer voor 1 Jaar/option
option value=N16 domain=hjkhhjh.ch prepaid_total=36.30 EUR
postpaid_total=45.40 EURRegistreer voor 2 Jaar/option
option value=N19 domain=hjkhhjh.ch prepaid_total=53.40 EUR
postpaid_total=66.60 EURRegistreer voor 3 Jaar/option
option value=N17 domain=hjkhhjh.ch prepaid_total=87.00 EUR
postpaid_total=109.00 EURRegistreer voor 5 Jaar/option
option value=N18 domain=hjkhhjh.ch prepaid_total=170.50 EUR
postpaid_total=213.50 EURRegistreer voor 10 Jaar/option
/select
What I'm trying to do is when a user selects an option from the list,
the prepaid_total and postpaid_total price should show on a different
div...
this is the javascript that worked up until a few weeks ago when I
upgraded to the new release of prototype:
JAVASCRIPT:
orderOptions.observe('change', function(event) {
alert('clicked for ' + orderOptions.getAttribute
('domain'));
rec = $('domainSearchResult').select('[domain=' +
orderOptions.getAttribute('domain') + ']');
tdPrepaid = rec[0].select('[f=prepaid]');
tdPostpaid = rec[0].select('[f=postpaid]');
alert(orderOptions.getValue());
selectedItem = orderOptions.select('[value=' +
orderOptions.getValue() + ']');
alert(selectedItem);
tdPrepaid[0].update(selectedItem[0].getAttribute
('prepaid_total'));
tdPostpaid[0].update(selectedItem[0].getAttribute
('postpaid_total'));
});
The two first
[Proto-Scripty] Re: Prototype ajax history
thanks for sharing this! i would love to contribute to this project if any help is needed .. let me know cheers -- mona On Mon, Sep 21, 2009 at 7:00 PM, Matt Foster mattfoste...@gmail.com wrote: Hey Everyone, I've finished a project that handles the problems of browser history when implementing ajax solutions. It's built to integrate with prototype perfectly and borrows a lot of the same concepts. The idea is an event driven system where all XHRs go through a single 'service' object which deals with server communications. This way we can register each request with the browser's history module and be able to accommodate the user as he/she traverses the history array. Take a look when you have a minute, its surely worth the time. http://positionabsolute.net/blog/2009/09/ajax-history-wars.php#number=6 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: .select on a combo
Hi again!
Thanks for the feedback. It's very much appreciated! (what would we
all do without those around here giving their spare time to help
others out... I hope one day I'll be able to help some people out on
this fantastic list!)
Nevertheless, I tried doing what you suggested, but I'm going
completely CRAZY here, I think...
This is what I got so far:
alert(orderOptions); // == returns my combobox html element perfectly
alert(orderOptions.getValue()); // == returns the current value
perfectly
alert(orderOptions.down('[value=' + orderOptions.getValue() +
']')); // == returns undefined
The combo itself has the following HTML:
select id=orderOption[qsfqsfqsf.cn] domain=qsfqsfqsf.cn
name=orderOption[qsfqsfqsf.cn]
option value=N15 domain=qsfqsfqsf.cn prepaid_total=20.20
EUR postpaid_total=25.25 EURRegistreer voor 1 Jaar/option
option value=N16 domain=qsfqsfqsf.cn prepaid_total=39.60
EUR postpaid_total=49.50 EURRegistreer voor 2 Jaar/option
option value=N19 domain=qsfqsfqsf.cn prepaid_total=58.20
EUR postpaid_total=72.75 EURRegistreer voor 3 Jaar/option
option value=N17 domain=qsfqsfqsf.cn prepaid_total=95.00
EUR postpaid_total=118.75 EURRegistreer voor 5 Jaar/option
option value=N18 domain=qsfqsfqsf.cn prepaid_total=186.50
EUR postpaid_total=233.00 EURRegistreer voor 10 Jaar/option
/select
I have no idea what is causing this behaviour, as it used to work
perfectly before...
Is anyone else having ideas?
David.
On Sep 21, 7:22 pm, Daniel Rubin dru...@dimedis.de wrote:
speedpac...@gmail.com wrote:
Hi Federico,
the readattroibute isn't giving the issues; that works fine, and the
alert does indeed return the expected value.
The line in the code no longer working is
selectedItem = orderOptions.select('[value=' + orderOptions.getValue
() + ']');
Hi David,
Element.select() returns a list of elements, so you may want to try down
instead:
selectedItem = orderOptions.down('[value=' + orderOptions.getValue()
+ ']');
Furthermore, I'm not sure that .select() on a SELECT element is not
something very different from Element.select() (a SELECT being somewhat
akin to an INPUT -- but I don't know really).
So I hope and feel rather confident that the .down() will help.
Have fun
Daniel
where orderOptions is the combo, and the selectedItem should be an
option element which has additional attributes set to it...
Thanks for the feedback though.
Any more ideas, as I'm lost with this issue.
David.
On Sep 19, 5:03 pm, jacknife federico.bore...@gmail.com wrote:
hi,
have you tried to use the Element class methods readAttribute/
writeAttribute instead that ordinary getAttribute/setAttribute?
i recently experienced some issues using getAttribute to retrieve
setted parameters.
Federico
On Sep 18, 7:33 pm, speedpac...@gmail.com speedpac...@gmail.com
wrote:
Hi Marko,
Great idea on combining the different attributes into one value
attribute with the pipe character. I'll consider it for a later
version, because this obviously also requires changes on the
serverside as we'll end up with other values being sent to the
server...
The class tihngy I knew and was on my todo list to change to that...
Unfortunately it doesn't fix my issue at this time (unless I'm
misinterpreting what you are saying...)
Have you gotten a chance to look into that biyt of code not giving me
the result I believed I should have received (and did before I
upgraded...)
Thanks again for the feedback - I really do appreciate it!
David.
On Sep 18, 7:01 pm, Marko gm.ma...@gmail.com wrote:
Hi,
Instead of adding attributes on element you can rewrite it like this:
option value=N15 domain=hjkhhjh.ch prepaid_total=18.50 EUR
postpaid_total=23.15 EURRegistreer voor 1 Jaar/option
=
option value=code|domain|pre_total|post_totalRegistreer voor 1
Jaar/option
=
option value=N15|hjkhhjh.ch|18.50 EUR|23.15 EURRegistreer voor 1
Jaar/option
You can get value like this:
selectedItem = orderOptions.select('[value=' +
orderOptions.getValue() + ']');
=
As this is equal to orderOptions you can do:
selectedItem = $F(this)
Then you can split it and get array:
selectedItem.split(|)
You can also rewrite your selects like this:
Instead of: td f=prepaid
write just: td class=prepaid
tdPrepaid = rec[0].select('[f=prepaid]');
=
tdPrepaid = rec[0].select('.prepaid');
This way you will preserve valid HTML
I think you get idea how to rewrite it.
- Marko
speedpac...@gmail.com wrote:
Hello,
I'm trying my secod post here - I never got my first to end up on the
list, so l'ts try it through the google groups website directly now...
I'm having an issue that I hope someone here can help me with...
I have the following code:
HTML:
--
select id=orderOption[hjkhhjh.ch] domain=hjkhhjh.ch
name=orderOption[hjkhhjh.ch]
option value=N15 domain=hjkhhjh.ch prepaid_total=18.50
[Proto-Scripty] Re: .select on a combo
Hi,
Before you go totally crazy please create self-contained-test-page
http://proto-scripty.wikidot.com/self-contained-test-pageand I will
return you working version.
- Marko
speedpac...@gmail.com wrote:
Hi again!
Thanks for the feedback. It's very much appreciated! (what would we
all do without those around here giving their spare time to help
others out... I hope one day I'll be able to help some people out on
this fantastic list!)
Nevertheless, I tried doing what you suggested, but I'm going
completely CRAZY here, I think...
This is what I got so far:
alert(orderOptions); // == returns my combobox html element perfectly
alert(orderOptions.getValue()); // == returns the current value
perfectly
alert(orderOptions.down('[value=' + orderOptions.getValue() +
']')); // == returns undefined
The combo itself has the following HTML:
select id=orderOption[qsfqsfqsf.cn] domain=qsfqsfqsf.cn
name=orderOption[qsfqsfqsf.cn]
option value=N15 domain=qsfqsfqsf.cn prepaid_total=20.20
EUR postpaid_total=25.25 EURRegistreer voor 1 Jaar/option
option value=N16 domain=qsfqsfqsf.cn prepaid_total=39.60
EUR postpaid_total=49.50 EURRegistreer voor 2 Jaar/option
option value=N19 domain=qsfqsfqsf.cn prepaid_total=58.20
EUR postpaid_total=72.75 EURRegistreer voor 3 Jaar/option
option value=N17 domain=qsfqsfqsf.cn prepaid_total=95.00
EUR postpaid_total=118.75 EURRegistreer voor 5 Jaar/option
option value=N18 domain=qsfqsfqsf.cn prepaid_total=186.50
EUR postpaid_total=233.00 EURRegistreer voor 10 Jaar/option
/select
I have no idea what is causing this behaviour, as it used to work
perfectly before...
Is anyone else having ideas?
David.
On Sep 21, 7:22 pm, Daniel Rubin dru...@dimedis.de wrote:
speedpac...@gmail.com wrote:
Hi Federico,
the readattroibute isn't giving the issues; that works fine, and the
alert does indeed return the expected value.
The line in the code no longer working is
selectedItem = orderOptions.select('[value=' + orderOptions.getValue
() + ']');
Hi David,
Element.select() returns a list of elements, so you may want to try down
instead:
selectedItem = orderOptions.down('[value=' + orderOptions.getValue()
+ ']');
Furthermore, I'm not sure that .select() on a SELECT element is not
something very different from Element.select() (a SELECT being somewhat
akin to an INPUT -- but I don't know really).
So I hope and feel rather confident that the .down() will help.
Have fun
Daniel
where orderOptions is the combo, and the selectedItem should be an
option element which has additional attributes set to it...
Thanks for the feedback though.
Any more ideas, as I'm lost with this issue.
David.
On Sep 19, 5:03 pm, jacknife federico.bore...@gmail.com wrote:
hi,
have you tried to use the Element class methods readAttribute/
writeAttribute instead that ordinary getAttribute/setAttribute?
i recently experienced some issues using getAttribute to retrieve
setted parameters.
Federico
On Sep 18, 7:33 pm, speedpac...@gmail.com speedpac...@gmail.com
wrote:
Hi Marko,
Great idea on combining the different attributes into one value
attribute with the pipe character. I'll consider it for a later
version, because this obviously also requires changes on the
serverside as we'll end up with other values being sent to the
server...
The class tihngy I knew and was on my todo list to change to that...
Unfortunately it doesn't fix my issue at this time (unless I'm
misinterpreting what you are saying...)
Have you gotten a chance to look into that biyt of code not giving me
the result I believed I should have received (and did before I
upgraded...)
Thanks again for the feedback - I really do appreciate it!
David.
On Sep 18, 7:01 pm, Marko gm.ma...@gmail.com wrote:
Hi,
Instead of adding attributes on element you can rewrite it like this:
option value=N15 domain=hjkhhjh.ch prepaid_total=18.50 EUR
postpaid_total=23.15 EURRegistreer voor 1 Jaar/option
=
option value=code|domain|pre_total|post_totalRegistreer voor 1
Jaar/option
=
option value=N15|hjkhhjh.ch|18.50 EUR|23.15 EURRegistreer voor 1
Jaar/option
You can get value like this:
selectedItem = orderOptions.select('[value=' +
orderOptions.getValue() + ']');
=
As this is equal to orderOptions you can do:
selectedItem = $F(this)
Then you can split it and get array:
selectedItem.split(|)
You can also rewrite your selects like this:
Instead of: td f=prepaid
write just: td class=prepaid
tdPrepaid = rec[0].select('[f=prepaid]');
=
tdPrepaid = rec[0].select('.prepaid');
This way you will preserve valid HTML
I think you get idea how to rewrite it.
- Marko
speedpac...@gmail.com wrote:
Hello,
I'm trying my secod post here - I never got my first to end up on the
list, so l'ts try it through the
[Proto-Scripty] Re: .select on a combo
Hi Marko,
This should do it, I believe:
---
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN http://www.w3.org/
TR/html4/strict.dtd
html
head
!-- TODO: Obviously, change this if you're using a different encoding
--
meta http-equiv=Content-type content=text/html;charset=UTF-8
titleTest Page/title
script type='text/javascript' src='prototype.js'/script
script type='text/javascript'
document.observe('dom:loaded', function() {
// TODO: Delete this and the button below if you don't need them
// for what you're trying to replicate
orderOptions = $('orderOption[test.com]');
orderOptions.observe('change', function(event) {
alert('Combobox selected: ' + orderOptions.identify());
alert('Current value for the combo is ' +
orderOptions.getValue());
alert('Selected Item: ' + orderOptions.down('[value=' +
orderOptions.getValue() + ']'));
}
});
/script
/head
bodydiv
select id=orderOption[test.com] domain=test.com name=orderOption
[qsfqsfqsf.cn]
option value=N15 domain=test.com prepaid_total=20.20 EUR
postpaid_total=25.25 EURRegistreer voor 1 Jaar/option
option value=N16 domain=test.com prepaid_total=39.60 EUR
postpaid_total=49.50 EURRegistreer voor 2 Jaar/option
option value=N19 domain=test.com prepaid_total=58.20 EUR
postpaid_total=72.75 EURRegistreer voor 3 Jaar/option
option value=N17 domain=test.com prepaid_total=95.00 EUR
postpaid_total=118.75 EURRegistreer voor 5 Jaar/option
option value=N18 domain=test.com prepaid_total=186.50 EUR
postpaid_total=233.00 EURRegistreer voor 10 Jaar/option
/select
/div/body
/html
---
Just change the combo...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype script.aculo.us group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: Prototype Selector Speed
Ok I'm glad to hear that the selector speed will improve with the sizzle, that's what Dojo uses too. Dojo and JQuery always finished first/second in the slickspeed tests. Is there a release date planned for scripty2? How active is that project? -Andy -- From: Jarkko Laine jarks...@gmail.com Sent: Monday, September 21, 2009 3:16 AM To: prototype-scriptaculous@googlegroups.com Subject: [Proto-Scripty] Re: Prototype Selector Speed On 21.9.2009, at 11.04, T.J. Crowder wrote: Hi, Is there any plans in the future to improve on prototype's speed? Yes. The core team are working on integrating the Sizzle selector engine[1] (which is what the latest version of jQuery uses). (This is more of a challenge than it sounds; switching selector engines touches a lot of things besides just the $$ and Element#select methods.) I *think* that's slated for the next release, but don't quote me. Sam just tweeted [1] that they're using it already on Highrise, so I'd guess it's pretty much in a working condition. //jarkko [1] http://twitter.com/sstephenson/status/439058 -- Jarkko Laine http://jlaine.net http://dotherightthing.com http://www.railsecommerce.com http://odesign.fi --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Prototype ajax history
You asked for it Mona, I've set you up as a contributor for the project http://code.google.com/p/agileajax/ On Sep 21, 1:39 pm, Mona Remlawi mona.reml...@gmail.com wrote: thanks for sharing this! i would love to contribute to this project if any help is needed .. let me know cheers -- mona On Mon, Sep 21, 2009 at 7:00 PM, Matt Foster mattfoste...@gmail.com wrote: Hey Everyone, I've finished a project that handles the problems of browser history when implementing ajax solutions. It's built to integrate with prototype perfectly and borrows a lot of the same concepts. The idea is an event driven system where all XHRs go through a single 'service' object which deals with server communications. This way we can register each request with the browser's history module and be able to accommodate the user as he/she traverses the history array. Take a look when you have a minute, its surely worth the time. http://positionabsolute.net/blog/2009/09/ajax-history-wars.php#number=6 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Masked Input in Prototype
Thanks you very much. This was very useful. On Sep 20, 3:41 am, bjartekv bjart...@gmail.com wrote: On Jul 29, 11:27 pm, Alex McAuley webmas...@thecarmarketplace.com wrote: why not just port the jquery one... wont take long ! Sorry for resurrecting this topic after two months. In case anyone comes to this thread looking for masked input for prototype (I know I did :-). I thought I'd mention that I've ported the jQuery version to prototype. You can get the code here:http://bjartekv.github.com/MaskedInput/ Regards, Bjarte --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Prototype (1.6.1) doesn't work with firefox 3 or 3.5!!
Hi, Prototype (1.6.1) doesn't work with firefox 3 or 3.5!! Not to put too fine a point on it, but ask yourself: How likely is that, *really*? ...it throws a ton of errors (all innocuous like toJSON does not always return a value) and it won't run any other code! Look at your add-ons list, you appear to have some kind of lint style add-on installed. This is not default Firefox behavior. (And I suspect it *does* run further code, unless the add-on in question is seriously broken.) It's perfectly valid for a JavaScript function to have code paths that issue a return statement with a value and also have code paths that either don't issue a return (just letting the execution path fall out of the function) or do so with no explicitly- defined value; all it means is that the return value is `undefined` (literally). This is per spec. I don't happen to be fan of this style of code, but it's perfectly valid. HTH, -- T.J. Crowder tj / crowder software / com www.crowdersoftware.com On Sep 21, 7:57 pm, Don Rhummy donrhu...@gmail.com wrote: I'm trying to use the prototype framework (prototype.js) with firefox but it throws a ton of errors (all innocuous like toJSON does not always return a value) and it won't run any other code! All I'm doing is: 1. Including the prototype.js file 2. alert( some code was called ); it never runs the alert statement (I had other stuff before but have distilled it just to this) It DOES run in Opera 10. What might be wrong? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Dynamic test after ajax call
Sounds like your situation is very out of the norm. Usually being able to
manipulate the DOM via JS is sufficient except in debugging situations (in
which case an extension is fine). Good luck figuring out something
different to do.
On Mon, Sep 21, 2009 at 9:57 AM, Kumar kumar.k.re...@gmail.com wrote:
Thanks Bill. I am already using IE Developer Toolbar with Internet
Explorer. I dont want to just see the DOM source, but indeed want to
use. It was part of design to use it. Thanks for your reponse though.
Thanks
On Sep 21, 11:38 am, bill will...@techservsys.com wrote:
Kumar wrote:
Hi Walter -
I completely understood what you meant. I have a strange situation
here. My enitre design sits on top of the DOM for lateral processing.
As soon as the DOM gets updated, there will be sequence of java script
calls based on the elements generated on this DOM for form processing.
After I heard that I cannot get the DOM state at the source code
level, I will probably take a look at other design issue. This is
something I never expected...
You can look at the dom source code as it exists at any point in time,
just not by clicking view source. As was pointed out below, Firefox +
Firebug gives you a elegantly laid out picture (in source) of the dom.
Thanks
On Sep 21, 9:48 am, Walter Lee Davis wa...@wdstudio.com wrote:
There's a fundamental difference between the source code and the
current state of the DOM. The former is fixed at the time that your
server sends it. And once that source is sent to the browser, the
browser interprets it and generates the DOM, which it uses to create
the on-screen display of the **current** state of the DOM.
Anything you do later to modify the DOM causes the DOM itself to
change, and thus the screen to update, but does not update the source
you see in your browser. Think of the source as the score, and the DOM
as the orchestral performance. The conductor and orchestra is
JavaScript, then, to stretch the metaphor.
When you request an element by its ID, you are asking the DOM, not
the source. When you modify an element on screen, or update it to
contain entirely new content, you are modifying the DOM, not the page
source.
HTML:
div id=foosomething here/div
JavaScript:
$('foo').addClassName('bar');
console.log($('foo').hasClassName('bar')) //= true
$$('.bar').invoke('insert',' with classname bar');
console.log($('foo').innerHTML) //= something here with classname bar
At no point above, if you looked in the source, would you see that
#foo now was #foo.bar, or that its content had changed, unless you
were using a tool such as Firebug to inspect the current state of the
DOM.
Walter
On Sep 21, 2009, at 9:22 AM, Kumar wrote:
Hi Tj -
Thanks for the prompt response. It really amazed me, when I heard
that
I can see source code of the original document and not the later
things that got updated through the Ajax updater. We have this
dependency where we need to make series of Java script calls based on
the dynamic response created by the Ajax updater. That includes the
dynamically generated element id's and stuff. If these are not going
to be visible in generated source, how am I supposed to make
advantage. Is there a way, though prorotype Ajax ?
Thanks
On Sep 19, 8:21 am, T.J. Crowder t...@crowdersoftware.com wrote:
Hi,
View source will only show you the original source of the
document,
not any later modifications you make to the DOM (e.g., via
Ajax.Updater or any of several other means). Why does it matter?
What is it you're trying to achieve looking at the source? If it's
just that you're trying to debug the markup or something, you can
use
Firefox with the Firebug[1] add-on, which will show you the current
DOM tree rather than the original source.
[1]http://getfirebug.com/
HTH,
--
T.J. Crowder
tj / crowder software / comwww.crowdersoftware.com
On Sep 18, 11:27 pm,Kumarkumar.k.re...@gmail.com wrote:
Hi All -
I am using prototype Ajax updater. The main intenntion of using
updater is to show users a loading icon, but in background we are
making a series webservice calls to wide variety of systems, then
collabarate all the data to users at one go.
The page loads and calls ajax updater. Updater inturn updates a div
tag with a search results. (results are processed in another jsp
page). Here is the problem. After the entire page gets loaded with
results, when I see the source I do not see the results grid in the
source page. I know its just the code that got loaded while making
ajax calls. How can I induce the code in to the same source file
after
the ajax call.
Did any one face this issue before. if you have any thoughts,
please
share it across. Please shoot me an email, if you are still not
[Proto-Scripty] Re: .setStyle does not consistently work
Hi Ali, This is a common mistake with scriptaculous, when launching an effect (mouseout or mouseover), you did not verify if there is the opposite effect in execution. So both effect will launch concurrently and it's fliker !! To see that this is the problem, wait some time to mouseover / mouseout the element, and the problem did not appear. You could use the queue to handle that or withcallbacks. -- david On 21 sep, 19:06, ali aliboswo...@gmail.com wrote: I am having trouble with an animation, and I am hoping that someone can help me out. I have one box that triggers a mouseover event.observe event when you move your mouse over it. When this mouseover occurs, I want to have another box (which is absolutely positioned) appear, while also moving up slightly. When you 'mouseout' the second box fade's out. Obviously, after the above animation, the second box is positioned slightly higher than it was positioned initially. I thought that I could use .setStyle to always 'reset' the second boxes position right before it animates, but this is not working consistently. It works fine if you leave your mouse 'off' the first box for at least 5 seconds, but if you trigger the mouseover quickly within a few seconds it doesn't 'reset' the position and it flickers. Here is a bare-bones example: http://dl.getdropbox.com/u/128280/prototype-test.html I am having this trouble in both FF 3.5 and Safari 4. Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
