[Proto-Scripty] Re: When does Prototype 1.7 fire Element.Methods.replace (IE)?
Hi, (I can't provide an example, because the script is not standalone). But it sounds as though you've debugged this to the point you could *create* a standalone test case replicating the problem fairly easily, whereas anyone else is going to be guessing at the things you already know. Can you give it a try? Sounds like it _may_ be a bug in Prototype in that specific situation, with that specific browser. A simple, standalone test case is the first step to getting that resolved. -- T.J. Crowder Independent Software Engineer tj / crowder software / com www / crowder software / com On Nov 25, 11:17 am, mindVex simon.sat...@googlemail.com wrote: Hi, I'm using the .replace()-Method to replace HTML content. I need the previous element that gets replaced so I'm using the return value of this function. In IE8 this returns an empty string in a specific case (I can't provide an example, because the script is not standalone). I did some research and found out that IE8 calls Element.Methods.replace in line 2770 (Prototype 1.7), where Mozilla does call replace in line 2059. Element.Methods.replace does some stuff and finally replaces the original elements outerHTML with the new content which gets stripped somehow (line 2791). Finally it seems to me it returns the orginal element that should be replaced, but already modified with the new content in line 2791, where it becomes an empty string. So I basically have two questions: 1. To dig a little bit further why this happens, can someone explain when exactly this method is called? IE doesn't seem to fire it on every replace() call. 2. It seems wrong to me that this function returns the modified original element instead of just returning the original element. Is this expected behaviour here? -- 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-scriptacul...@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: When Ajax Insert Expands Page Downward...
Yea, that is what I ended up doing. Thanks. On Dec 7, 12:24 pm, Rick Waldron waldron.r...@gmail.com wrote: Yes and it drives me nuts. I'm sure there is a correct way of fixing this, but i'm ok with just setting somekind of footer content below the fold so that I always have scroll bars -- Sent from my Palm Prē Dave L wrote: I am having an issue: when inserting a number of elements that end up push the page downward so that the scroll bar has to be adjusted, all of the css shifts to the left. I am using firefox 3.0 and have noticed this occurance before. Has anyone else come across this or know what might be causing this? -- You received this message because you are subscribed to the Google Groups Prototype amp; script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/prototype-scriptaculous?hl=en. -- 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-scriptacul...@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: When to expect code changes to be added to Prototype.
It has been closed by lighthouse robot.
It seems normal that there is not much activity on this ticket :((
--
david
On 8 sep, 12:28, FigglesKoy figgles...@gmail.com wrote:
I managed to find the lighthouse ticket (had to Google
it):https://prototype.lighthouseapp.com/projects/8886/tickets/318-wiktor-...
. The page lists the link I have above for the code itself and the
last milestone change was to 1.6.1. I checked the 1.6.1 milestone and
ticket 318 is there and listed as resolved.
On Sep 5, 12:17 pm, Rick Waldron waldron.r...@gmail.com wrote:
I wasn't previously aware of this enhancement (which is most def. is)...
however re: TJ's reply, I think support for something like this is quite
appropriate, as i know the jQuery does support the use of multiple selector
expressions sep. by commas.
Rick
On Fri, Sep 4, 2009 at 11:49 AM, T.J. Crowder
t...@crowdersoftware.comwrote:
Hi,
The Lighthouse ticket should still be there. If you filed the ticket,
you should be able to see it by searching for all tickets created by
you. Hopefully that would shed light on the issue.
You've said there's a fix to Prototype...but what you describe is an
enhancement, isn't it? Very big difference between enhancements and
fixes. It may well be that the Core team didn't think that supporting
multiple expressions in that way was appropriate for the project.
--
T.J. Crowder
tj / crowder software / com
www.crowdersoftware.com
On Sep 4, 3:10 pm, FigglesKoy figgles...@gmail.com wrote:
There's a fix to Prototype that I've been waiting for a while to see.
Specifically, that the Element.match method would support commas to
support checking for multiple rules in a single call i.e. match
('DIV.aClass, DIV.bClass'). Thing is, this has been fixed online for
a while, but it has never made it to a Prototype release and I'm not
sure why. The github commit is here (http://github.com/sstephenson/
prototype/commit/afd74ce1c72a17666d8c9d86131463ad73cafe9e) and if I'm
reading it correctly, its been there since November of last year.
However, even in the latest 1.6.1 release, it is not present. I can
no longer find it on the lighthouse page though I did at one time. I
believe it was attached to milestone 1.6.0.4, which seems to not exist
any more. I can manually add the code in for now but if this won't be
in subsequent releases, then I will have to remember to add it back in
each time I upgrade. So I guess I'm just looking for some explanation
on how to know when/if some code commit will be added to a future
release. 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
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: When to expect code changes to be added to Prototype.
@FigglesKoy:
Looks like a missed pull, or after Andrew committed that (which
automatically closed the ticket) there was a good reason found to
leave it out (whatever that might be). You might want to reopen the
ticket to put it back on the radar.
@Rick:
I wasn't saying *I* thought it was a bad idea. :-)
-- T.J.
On Sep 8, 12:28 pm, david david.brill...@gmail.com wrote:
It has been closed by lighthouse robot.
It seems normal that there is not much activity on this ticket :((
--
david
On 8 sep, 12:28, FigglesKoy figgles...@gmail.com wrote:
I managed to find the lighthouse ticket (had to Google
it):https://prototype.lighthouseapp.com/projects/8886/tickets/318-wiktor-...
. The page lists the link I have above for the code itself and the
last milestone change was to 1.6.1. I checked the 1.6.1 milestone and
ticket 318 is there and listed as resolved.
On Sep 5, 12:17 pm, Rick Waldron waldron.r...@gmail.com wrote:
I wasn't previously aware of this enhancement (which is most def. is)...
however re: TJ's reply, I think support for something like this is quite
appropriate, as i know the jQuery does support the use of multiple
selector
expressions sep. by commas.
Rick
On Fri, Sep 4, 2009 at 11:49 AM, T.J. Crowder
t...@crowdersoftware.comwrote:
Hi,
The Lighthouse ticket should still be there. If you filed the ticket,
you should be able to see it by searching for all tickets created by
you. Hopefully that would shed light on the issue.
You've said there's a fix to Prototype...but what you describe is an
enhancement, isn't it? Very big difference between enhancements and
fixes. It may well be that the Core team didn't think that supporting
multiple expressions in that way was appropriate for the project.
--
T.J. Crowder
tj / crowder software / com
www.crowdersoftware.com
On Sep 4, 3:10 pm, FigglesKoy figgles...@gmail.com wrote:
There's a fix to Prototype that I've been waiting for a while to see.
Specifically, that the Element.match method would support commas to
support checking for multiple rules in a single call i.e. match
('DIV.aClass, DIV.bClass'). Thing is, this has been fixed online for
a while, but it has never made it to a Prototype release and I'm not
sure why. The github commit is here (http://github.com/sstephenson/
prototype/commit/afd74ce1c72a17666d8c9d86131463ad73cafe9e) and if I'm
reading it correctly, its been there since November of last year.
However, even in the latest 1.6.1 release, it is not present. I can
no longer find it on the lighthouse page though I did at one time. I
believe it was attached to milestone 1.6.0.4, which seems to not exist
any more. I can manually add the code in for now but if this won't be
in subsequent releases, then I will have to remember to add it back in
each time I upgrade. So I guess I'm just looking for some explanation
on how to know when/if some code commit will be added to a future
release. 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
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: When to expect code changes to be added to Prototype.
I wasn't previously aware of this enhancement (which is most def. is)...
however re: TJ's reply, I think support for something like this is quite
appropriate, as i know the jQuery does support the use of multiple selector
expressions sep. by commas.
Rick
On Fri, Sep 4, 2009 at 11:49 AM, T.J. Crowder t...@crowdersoftware.comwrote:
Hi,
The Lighthouse ticket should still be there. If you filed the ticket,
you should be able to see it by searching for all tickets created by
you. Hopefully that would shed light on the issue.
You've said there's a fix to Prototype...but what you describe is an
enhancement, isn't it? Very big difference between enhancements and
fixes. It may well be that the Core team didn't think that supporting
multiple expressions in that way was appropriate for the project.
--
T.J. Crowder
tj / crowder software / com
www.crowdersoftware.com
On Sep 4, 3:10 pm, FigglesKoy figgles...@gmail.com wrote:
There's a fix to Prototype that I've been waiting for a while to see.
Specifically, that the Element.match method would support commas to
support checking for multiple rules in a single call i.e. match
('DIV.aClass, DIV.bClass'). Thing is, this has been fixed online for
a while, but it has never made it to a Prototype release and I'm not
sure why. The github commit is here (http://github.com/sstephenson/
prototype/commit/afd74ce1c72a17666d8c9d86131463ad73cafe9e) and if I'm
reading it correctly, its been there since November of last year.
However, even in the latest 1.6.1 release, it is not present. I can
no longer find it on the lighthouse page though I did at one time. I
believe it was attached to milestone 1.6.0.4, which seems to not exist
any more. I can manually add the code in for now but if this won't be
in subsequent releases, then I will have to remember to add it back in
each time I upgrade. So I guess I'm just looking for some explanation
on how to know when/if some code commit will be added to a future
release. 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
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: When to expect code changes to be added to Prototype.
Hi,
The Lighthouse ticket should still be there. If you filed the ticket,
you should be able to see it by searching for all tickets created by
you. Hopefully that would shed light on the issue.
You've said there's a fix to Prototype...but what you describe is an
enhancement, isn't it? Very big difference between enhancements and
fixes. It may well be that the Core team didn't think that supporting
multiple expressions in that way was appropriate for the project.
--
T.J. Crowder
tj / crowder software / com
www.crowdersoftware.com
On Sep 4, 3:10 pm, FigglesKoy figgles...@gmail.com wrote:
There's a fix to Prototype that I've been waiting for a while to see.
Specifically, that the Element.match method would support commas to
support checking for multiple rules in a single call i.e. match
('DIV.aClass, DIV.bClass'). Thing is, this has been fixed online for
a while, but it has never made it to a Prototype release and I'm not
sure why. The github commit is here (http://github.com/sstephenson/
prototype/commit/afd74ce1c72a17666d8c9d86131463ad73cafe9e) and if I'm
reading it correctly, its been there since November of last year.
However, even in the latest 1.6.1 release, it is not present. I can
no longer find it on the lighthouse page though I did at one time. I
believe it was attached to milestone 1.6.0.4, which seems to not exist
any more. I can manually add the code in for now but if this won't be
in subsequent releases, then I will have to remember to add it back in
each time I upgrade. So I guess I'm just looking for some explanation
on how to know when/if some code commit will be added to a future
release. 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
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: When are is final 1.6.1 going to be released?
On Jun 3, 4:09 am, KHelal karim.he...@gmail.com wrote: Hi all, Do you have any ETA on the final version of 1.6.1? IE8 is being force- fed by Microsoft and is starting to show usage for some of our customers. Hopefully, within a week or two. -- kangax --~--~-~--~~~---~--~~ 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: When?
On Feb 26, 7:28 am, Lox gecka.comp...@gmail.com wrote: [...] then prototype is becoming the mature and stable platform for standardised/cross platform javascript development. I understand that, and quite second that, but Peppy or Sizzle are much more faster at selecting elements by css selector witch, these days where javascript apps a getting bigger, is a must have. Don't get to wrapped-up in javascript CSS selectors. Most browsers have a host getElementsByClassName that has the benefit of being a live collection (get it once, update the DOM all you like, the collection is automatically updated for you). When combined with getElementById, getElementsByTagName and standard DOM collections, you can do an awful lot easily and quickly. Further, complex CSS selectors tie your code to the page layout - isn't the idea to separate the two? Lastly, they encourage rubbish like: tagName#someID, which is used in style rules because it helps the developer, but using it in a script selector is just plain dumb. I can understand the use of selectors for prototyping or small things where speed is irrelevant, but using them as a fundamental strategy to get large sets of elements doesn't make sense. Write a function to do it using standard host methods, it will perform much faster and be easier to work with. -- Rob --~--~-~--~~~---~--~~ 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: When?
On Feb 26, 9:15 am, RobG rg...@iinet.net.au wrote: Further, complex CSS selectors tie your code to the page layout - isn't the idea to separate the two? I don't agree. As a rule it ties your code to the *classes*, and possibly to the hierarchical (and, one would hope, logical) structure of the page. As long as you are using HTML and not XML, this seems to me to be an extremely good way of expressing the semantics of elements. Agreed, classes were originally devised for CSS, but they've come far beyond that. In any case, I don't see what you are contrasting this with: if you use getElementByTag and it's friends you've still to traverse the structure in the DOM, i.e. the page layout. Lastly, they encourage rubbish like: tagName#someID, which is used in style rules because it helps the developer, but using it in a script selector is just plain dumb. No disagreement. I can understand the use of selectors for prototyping or small things where speed is irrelevant, but using them as a fundamental strategy to get large sets of elements doesn't make sense. Write a function to do it using standard host methods, it will perform much faster and be easier to work with. Ummm... isn't that like saying Use high level languages by all means, but for serious work, you should write assembler functions? I use prototype because for me it turns Javascript from a dog I would never want to subject myself to into a usable language. I have recently had unwrap a CSS selection (select by class name) because I found that while it ran well on FF, it took a ridiculous amount of time on IE6. (As far as I can tell, IE hasn't got a 'find by class name'). But to me that is like having to descend to low-level programming to get round a hardware bug. Colin --~--~-~--~~~---~--~~ 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: When?
2009/2/25 Lox gecka.comp...@gmail.com: Is there some particular development you are waiting for? What does more modern means? Well Peppy or Sizzle means that to me Also I'll be happy to have it optimized in size and speed. (Scriptaculous is much more concerned by the size matter: the number of Ko to load to have a sliding effect is impressing! ) Some other things missed me in my last javascript project but sorry I can't remember exactly what (shame on me) but I promise to post them here next time I notice them. Opensource communities need something to eat quite often! And I, as others, are getting more and more hungry! See how Ubuntu is successful with their 6 months release cycle! Jquery has more updates and so a growing community... Concerning the well know smashingmagazine I consider a shame no being listed in the 50 Useful JavaScript Tools whereas Jquery UI is... Anyway I love how prototype is, and how it works. Using it is so logical to me that I don't have to look a the doc very often. Great works devs! Regards (excuse my poor english) As I see things, prototype.js is a background toolkit. Unless there are more inconsistencies found amongst the browsers or there are some radically new ways of processing CSS, getting hold of elements, processing arrays/hashes, etc., then prototype is becoming the mature and stable platform for standardised/cross platform javascript development. Scripty (for example), which uses prototype is always going to expand as new effects or user orientated functionality becomes available. I think of prototype as a runtime library. You need it to be small, efficient and stable. This is so I, as a developer, can take it, use it in knowledge that if it works today, it will work tomorrow. Upgrading the lowest level libraries in a project nearly always breaks SOMETHING (not always major, but ...) Maybe one reason for JQuery and others like it having such a frequent release schedule is simply because they are not mature and stable enough. Yet. Keeping backend and frontend functionality separate is a great way to go. If prototype started handling user interaction (rather than just DOM/AJAX interaction), then it would bloat VERY quickly. Richard. -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498r=213474731 Standing on the shoulders of some very clever giants! --~--~-~--~~~---~--~~ 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: When?
[...] then prototype is becoming the mature and stable platform for standardised/cross platform javascript development. I understand that, and quite second that, but Peppy or Sizzle are much more faster at selecting elements by css selector witch, these days where javascript apps a getting bigger, is a must have. Someone talked about a lot of patches floating around. What are they? Where are they? To me prototype can be optimized without changing its functionalities. I recently had a case where, in a well formed dom, it didn't find something like '#mydiv span.class' witch was anoying. I remember I had to find a workaround and also that Peppy found it --~--~-~--~~~---~--~~ 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: When?
Scripty (for example), which uses prototype is always going to expand as new effects or user orientated functionality becomes available. Is Scripty Scriptaculous ? --~--~-~--~~~---~--~~ 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: When?
On Feb 25, 4:28 pm, Lox gecka.comp...@gmail.com wrote: [...] then prototype is becoming the mature and stable platform for standardised/cross platform javascript development. I understand that, and quite second that, but Peppy or Sizzle are much more faster at selecting elements by css selector witch, these days where javascript apps a getting bigger, is a must have. Someone talked about a lot of patches floating around. What are they? Where are they? Which patches? To me prototype can be optimized without changing its functionalities. Optimized how? The bug tracker is public and anyone is free to suggest optimizations, patches, tests, etc. I recently had a case where, in a well formed dom, it didn't find something like '#mydiv span.class' witch was anoying. I remember I had to find a workaround and also that Peppy found it Submitting bug is a good way to let developers know about it. Otherwise, the chances of it being found and fixed are much lower, as you can probably guess. In which browser did that query not work? -- kangax --~--~-~--~~~---~--~~ 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: When?
2009/2/25 Lox gecka.comp...@gmail.com: Scripty (for example), which uses prototype is always going to expand as new effects or user orientated functionality becomes available. Is Scripty Scriptaculous ? Yes. Sorry for the abbrev. -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498r=213474731 Standing on the shoulders of some very clever giants! --~--~-~--~~~---~--~~ 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: When?
On Feb 24, 6:14 am, Lox gecka.comp...@gmail.com wrote: Hello, When is prototype.js new release scheduled? Current version feature is getting old. Other JavaScript frameworks are going faster and are getting more modern Prototype.js does not even appear on that article:http://www.smashingmagazine.com/2009/02/08/50-extremely-useful-javasc... OpenSource projects are alive because of there community, and prototype's is getting smaller. I use prototype a lot and don't really want to change but if no release coming soon, I will as many others I know have already. Is there some particular development you are waiting for? Because if not, what's your hurry? What does 'more modern' mean? The idea that there has to be a new 'modern' version of everything is a lie fostered by an industry that has to sell you a new version or they won't make any money. This does not apply in the Open source world. I am not arguing against either improving or extending systems; but 'falling behind' is a nonsense unless you detail specific things that you are waiting for. Colin Regards --~--~-~--~~~---~--~~ 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: When using sortable how do you get the id of the dragged item
It seems like this doesn't work with a droppable. Anyone else done something like this? On Feb 1, 5:31 pm, Matthew Tullett ouratel...@googlemail.com wrote: It's the id of the list container. I'm just wondering if you could use the droppable function as well on the same list. Sent from my iPhone On 1 Feb 2009, at 17:24, Walter Lee Davis wa...@wdstudio.com wrote: Sortable.create has a similar callback called onChange. It gets called whenever the sort order changes while dragging. According to the docs, it gets the affected element as its parameter, but I'm not sure if that's the list or the item you dragged into it. You'll have to test. Walter On Feb 1, 2009, at 12:12 PM, Matthew Tullett wrote: Can this be done with the sortable.create? Or combinded with. --~--~-~--~~~---~--~~ 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: When using sortable how do you get the id of the dragged item
In your Droppable, you have the onDrop callback function to play with.
http://wiki.github.com/madrobby/scriptaculous/droppables
From that page:
Droppables.add('shopping_cart', {
accept: 'products',
onDrop: function(element) {
$('shopping_cart_text').update('Dropped the ' + element.alt + '
on
me.');
}
});
You could make this:
Droppables.add('shopping_cart', {
accept: 'products',
onDrop: function(element) {
element.addClassName('foo');
}
});
Walter
On Feb 1, 2009, at 8:22 AM, ouratel...@googlemail.com wrote:
when you create a sortable list when dragging an item how do you get
the id of the item that has been dragged then dropped?
What i'm trying to do is add a css class to the item that has been
dropped?
Is that even possbile?
--~--~-~--~~~---~--~~
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: When using sortable how do you get the id of the dragged item
Can this be done with the sortable.create? Or combinded with.
Sent from my iPhone
On 1 Feb 2009, at 16:35, Walter Lee Davis wa...@wdstudio.com wrote:
In your Droppable, you have the onDrop callback function to play with.
http://wiki.github.com/madrobby/scriptaculous/droppables
From that page:
Droppables.add('shopping_cart', {
accept: 'products',
onDrop: function(element) {
$('shopping_cart_text').update('Dropped the ' + element.alt +
' on
me.');
}
});
You could make this:
Droppables.add('shopping_cart', {
accept: 'products',
onDrop: function(element) {
element.addClassName('foo');
}
});
Walter
On Feb 1, 2009, at 8:22 AM, ouratel...@googlemail.com wrote:
when you create a sortable list when dragging an item how do you get
the id of the item that has been dragged then dropped?
What i'm trying to do is add a css class to the item that has been
dropped?
Is that even possbile?
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
