Hi and sorry if this has already been discussed. I'm new on theese
lists, and I couldn't find a way to search through them.
I have been looking at the sources of script.aculo.us and I'm rather
impressed by the Enumerable class. What I don't get is why you choose
to extend Array.prototype with this
Hi and sorry if this has already been discussed. I'm new on theese
lists, and I couldn't find a way to search through them.
I have been looking at the sources of script.aculo.us and I'm rather
impressed by the Enumerable class. What I don't get is why you choose
to extend Array.prototype with this
Well after struggling a bit with how to do it, I have a few problems.
1. I will need to determine the queue where the effect is added to (I
think I will need to set the value of Effect.queue).
2. I need to know the type of effect and see if its in the PAIR array
and find its opposite
3. Check i
Looks like Sortable already has an 'onUpdate' option that should do
exactly what I want. However, I cannot get it to fire. Has anyone had
success with it? Passing the onDrop option along to Droppables didn't
work, either. It seems that onDrop is not consistently called because
the 'last_active'
Thanks, man! I appreciate your effort a lot!
greetings,
benni.
-SDG-
Gregory Hill wrote:
Hey Greg,
just my two cents: Why don't you extend the classes and then make a
patch for Thomas to integrate in the main distribution?
Would be awesome to have those small, but needed extensions in
there
I tried getting rid of the blind up, and using the "beforeUpdate" in the blind downs to set the height of the elup element.. I figured that way on each iteration of the animation the two elements would change by the same amount.No luck.I could really use this feature though, so if someone comes up
> Hey Greg,
>
> just my two cents: Why don't you extend the classes and then make a
> patch for Thomas to integrate in the main distribution?
>
> Would be awesome to have those small, but needed extensions in
there...
>
Yeah, I can do that; the main problem is that I don't have svn access
from
Hey Greg,
just my two cents: Why don't you extend the classes and then make a
patch for Thomas to integrate in the main distribution?
Would be awesome to have those small, but needed extensions in there...
greetings,
benni.
-SDG-
Gregory Hill wrote:
These blocks in the Sortable class need
Well then maybe you can access the Sortable.options.droppables[] array,
find the object you need, and then define an onDrop function for it, and
likewise for the draggables and remove, add or otherwise override the
handlers you need for each object.
-Original Message-
From: [EMAIL PROTECT
> These blocks in the Sortable class need to be extended to provide the
> level of configurability you're looking for:
>
> // build options for the draggables
> var options_for_draggable = {
> revert: true,
> ghosting:options.ghosting,
> constraint: options.constrai
I noticed that the latest control.js disables auto complete:
this.element.setAttribute('autocomplete','off');
So I removed my inline "autocomplete='off'" from my input fields.
But Firefox still auto completes.
Using the Firefox DOM Inspector I do see that it's applied
by Ajax.Autocompleter
These blocks in the Sortable class need to be extended to provide the
level of configurability you're looking for:
// build options for the draggables
var options_for_draggable = {
revert: true,
ghosting:options.ghosting,
constraint: options.constraint,
handle
So, is there any way to specify a sortable to only do a callback when
the dragged item is dropped? As it is, the onChange is called whenever
you move the draggable to a new element (even if you don't drop it), but
I'd rather only call my function after they drop it to avoid unnecessary
additional
Hi and sorry if this has already been discussed. I'm new on theese
lists, and I couldn't find a way to search through them.
I have been looking at the sources of script.aculo.us and I'm rather
impressed by the Enumerable class. What I don't get is why you choose
to extend Array.prototype with this
I was thinking that the accordian could do one of two things.
Assuming we have panel A, B and C stacked vertically with A currentlythe 'expanded' panel and the user has clicked on B.1) Shrink A one pixel at a time while expanding B one pixel at a time. When either one hits the limit, then only modi
I was thinking that the accordian could do one of two things.
Assuming we have panel A, B and C stacked vertically with A currently
the 'expanded' panel and the user has clicked on B.
1) Shrink A one pixel at a time while expanding B one pixel at a time.
When either one hits the limit, then only
One limitation I see with the Accordian method here is that it doesn't work right if you have different height panels - they all take the height of the first panel. May have a stab at addressing this tomorrow unless someone knows of an easy solution?
___
Peepz,
I was looking into how script.aculo.us handles effect to write a
tutorial and for a current project I wanted to make transition between
PAIR effects possible. These PAIR effects are (Appear/Fade,
SlideUp/SlideDown, BlindUp/BlindDown) the effect that toggle can handle.
script.aculo.us
Hi:
I just started using IPE with an app that has a listing of FAQs that
I want to edit in place. What I've discovered as I started wiring
this up is that when I click to edit, the text areas are inserting
new lines every 70-something characters. My data doesn't have these
new lines.
Is
I have the same problem. My Solution? more filter on query and limit
results to ~50, so you always get max 50 results and if you type more
about the world, the result is more exactly.
PS: sorry my bad english :P
Cam McVey escreveu:
Ryan,
It does use this method. The problem is that it also
Hi,
thanks for the pointer.
hiding form elements on IE is yet missing, but many of the other
variants are possible just by adapting the options.
it's a good question where to draw the line and let people implement
their own flavor of tooltips instead of providing every possible case.
but an
Heya,As you said, it's certainly not a common use case for an autocompleting textbox to have 1000s of suggestions.The Autocompleter is supposed to return anything from 1 to 10 completions. If you need to support more than that, you have to come up with a modified version, probably involving using o
This would be great if you could bundle in all the functionality of
domTT (what I and many others consider the crem de la crem of tooltip
libs)... check it out
(http://www.mojavelinux.com/cooker/demos/domTT/)...
Yours needs some options like "greasy" vs. "sticky"... where they show
up relative to
Ohhh. I didn't realize that. Well I can see the solution, but it
involves overriding the reject method in the Hash object. If I were you,
I'd do that and submit the patch for inclusion in the next release.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Al
Or... if you're really desparate I guess you could make the server
hard-code the event handlers inline in each element in the returned
HTML. That would at least save the looping, but it's not ideal
obviously.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Because your solution yields
#
instead of
#
In my opinion the difference is crucial. Remember the original Hash was
#
and by using the reject function I wanted to drop all hash elements
with value 1.
In Ruby (from which the inspiration for the Enumerable Mixin stems),
the reject method sur
Ok, in that case, perform as much of the event handler attachment
asynchronously as you can. Wrap the entire event handler attachment
process into one function which gets kicked off in a setTimeout with 1
millisecond delay... and each attachment itself in another setTimeout.
You may only gain a sma
Ryan,
It does use this method. The problem is that it also loops through
those created DOM elements to add event handlers (so you can key
through the results, click on them, etc.).
Cam.
On 1/23/06, Ryan Gahl <[EMAIL PROTECTED]> wrote:
>
> Now, I don't use the AutoCompleter, but if it doesn't su
Hi,
there already had been a Tooltips implementation [1] but i wasn't to
happy with that one, not only because they didn't support simple
mouse-hover tooltips (just as they appear when you are using title
attributes)
But writting this lib was also a good way to get into script.aculo.us
and
For any large chunks of data, it is far
better to let the server do the processing rather than try to make the client
stitch together 1000s of DOM elements (and then expect it to be fast)….
You need to have the server build the HTML
string to return and simply have the client do a singl
Hi All,I am currently using script.aculo.us and Autocompleter for a project which I am dealing now. I faced a situation for which I couldnt find any solution and I could not see any reference
regarding this issue in the enhancement/bug lists of script.aculo.us either. Autocompleter component is wo
Why not just do...
var b = $H(a.reject(function(val){ return (val[1]==1) }));
? The reject method returning an array makes it flexible (arrays can be
enumerables too)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Alexander Presber
Sent: Monday, January
Hello everyone.
I am not sure if this is the right place to post, please redirect me
if there is a mailinglist more specifically dealing with prototype.js.
After playing around with the very inspiring prototype library I have
found a rather annoying thing, that makes the usefulness of the
33 matches
Mail list logo
