[Proto-Scripty] Ajax.updater - data get merged in content when running many updaters
hi all! i have a problem with Ajax.updater. When i run the Ajax.updater in one div and then if a user clicks on link and activates another Ajax.updater in the same div before the first one is finished the data get merged in the same div. The top is showing the new content, underneath is showing the data that was not yet loaded from the first call. how can I fix this? can i stop/kill the first updater before running the second one? or should i wait until the first is finished before triggering the next one...and how do I do that? grateful for help and advice --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Cut down Prototype and DragDrop
Excellent - thanks! On Nov 28, 12:05 pm, SWilk [EMAIL PROTECTED] wrote: Matt Winward pisze: Thanks for the advice SWilk .. that was pretty detailed and very very useful! I had a little hunt around on the net and found this page (http:// blog.code-purity.com/archives/2008/10/3/ compressed_prototype_scriptaculous/) which links to a 'minified' and compressed (I think?) script containing both scriptaculous and prototype, bringing them both down to an 88kb file, which is a huge improvement. I had figured that this must be something someone somewhere had done already! I'm still concerned that it will include a lot of functions that we'll never use, but at the same time, your point about maintenance is a fair one. Take a look at proto-scripty wiki articles:http://proto-scripty.wikidot.com/scripty:tip-minimum-libraries-for-ef... andhttp://proto-scripty.wikidot.com/prototype:tip-minimizing-download-times You might find the first one helpful when deciding which script of scriptaculous you need. The second one discusses the minification and consolidation of js files, and contains some other useful links. Regards, SWilk --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Help needed
Finally it works after creating another function to update div but with a delay that was the result now its ok On Fri, Nov 28, 2008 at 1:49 PM, jason maina [EMAIL PROTECTED] wrote: Hi guys/gals, I have made a select control used by 3 different pages but create from the master page by calling the relevant function then update a div with the control. On FF it works pretty fine without any issues. On IE it only shows on the first page that calls the control then on subsequent pages it shows but no content in the select. When I check its ID its there but wont get the content right, what could be the problem (the function is not being called again other than on the main page and the holding variable is not being nullified anywhere in the pages...)? Feeling like lost gravity with very strong winds pushing me to nowhere... :-) Im at the edge now --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Help needed
Hi guys/gals, I have made a select control used by 3 different pages but create from the master page by calling the relevant function then update a div with the control. On FF it works pretty fine without any issues. On IE it only shows on the first page that calls the control then on subsequent pages it shows but no content in the select. When I check its ID its there but wont get the content right, what could be the problem (the function is not being called again other than on the main page and the holding variable is not being nullified anywhere in the pages...)? Feeling like lost gravity with very strong winds pushing me to nowhere... :-) Im at the edge now --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Simple question
On Nov 27, 10:50 pm, seasoup wrote:
On Nov 27, 7:14 am, RobG wrote:
On Nov 27, 11:32 pm, spradeepkumar wrote:
[...]
If you are particular in using this...prototype has got
bind methods with which you can control your scope
The value of a function's this keyword has nothing to do
with scope, it is set by the call.
$(selector).each(function(){
alert(this);
}.bind($(somethingElse));
sets somethingElse as the 'this' inside of the each function,
instead of the item in the array. That's what spradeepkumar
was referring to by controlling scope.
And it was referring to setting the - this - value as controlling
scope (or as having anything to do with scope at all) that was being
corrected. Scope is quite an important concept in javascript, indeed
being 'lexically scoped' is one of the defining characteristics of the
language. (With the exception of possible used of the - with -
statement) Scope is defined by the ((lexical) structure of the) source
code and not amenable to runtime modification (or control). The value
of the - this - keyword in a function is determined at runtime by how
the function is called, and can be 'controlled'. It may be
(unfortunately) common to speak of 'scope' when talking about the -
this - keyword but the two are really very different things that
should not be confused.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: Cut down Prototype and DragDrop
Something else I should mention is that I also need to extend dragdrop slightly so that when a panel is dropped, it triggers a function that saves the user's new page layout. I'll probably do this by gathering the layout info and then invoking a web method. How easy would it be to extend the 'drop' functionality slightly so that it calls a function I've defined myself? We're either going to do it this way, or take the user to a config page with moveable panels and a save button.. I'm not sure this has yet been decided. On Nov 28, 10:02 am, Matt Winward [EMAIL PROTECTED] wrote: Hi all. We've just started using Scriptaculous to allow the user to rearrange their home page content panels. At the moment we have two unordered lists (left and right) and the user can move panels around to suit their preference. This is working great and the only problem we have with it is that scriptaculous.js + prototype.js + dragdrop.js + effects.js = 192kb. That's after I stopped it from loading other js files like sound.js, for example. Seeing as all I'm using (literally) is Sortable.create(list, properties) twice at the bottom of the page, and nothing else, there must be loads that I can carve out of the js files? Ideally I was hoping to be able to normalise them all into one efficient js file that handles the Sortable business. Looking through it, though, I can see it's no simple task! There must be a more modular approach? Any help or advice would be hugely appreciated! Matt --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Cut down Prototype and DragDrop
Hi all. We've just started using Scriptaculous to allow the user to rearrange their home page content panels. At the moment we have two unordered lists (left and right) and the user can move panels around to suit their preference. This is working great and the only problem we have with it is that scriptaculous.js + prototype.js + dragdrop.js + effects.js = 192kb. That's after I stopped it from loading other js files like sound.js, for example. Seeing as all I'm using (literally) is Sortable.create(list, properties) twice at the bottom of the page, and nothing else, there must be loads that I can carve out of the js files? Ideally I was hoping to be able to normalise them all into one efficient js file that handles the Sortable business. Looking through it, though, I can see it's no simple task! There must be a more modular approach? Any help or advice would be hugely appreciated! Matt --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Cut down Prototype and DragDrop
Matt Winward pisze: Thanks for the advice SWilk .. that was pretty detailed and very very useful! I had a little hunt around on the net and found this page (http:// blog.code-purity.com/archives/2008/10/3/ compressed_prototype_scriptaculous/) which links to a 'minified' and compressed (I think?) script containing both scriptaculous and prototype, bringing them both down to an 88kb file, which is a huge improvement. I had figured that this must be something someone somewhere had done already! I'm still concerned that it will include a lot of functions that we'll never use, but at the same time, your point about maintenance is a fair one. Take a look at proto-scripty wiki articles: http://proto-scripty.wikidot.com/scripty:tip-minimum-libraries-for-effects and http://proto-scripty.wikidot.com/prototype:tip-minimizing-download-times You might find the first one helpful when deciding which script of scriptaculous you need. The second one discusses the minification and consolidation of js files, and contains some other useful links. Regards, SWilk --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Cut down Prototype and DragDrop
Hi, Matt Winward wrote: Hi all. We've just started using Scriptaculous to allow the user to rearrange their home page content panels. At the moment we have two unordered lists (left and right) and the user can move panels around to suit their preference. This is working great and the only problem we have with it is that scriptaculous.js + prototype.js + dragdrop.js + effects.js = 192kb. That's after I stopped it from loading other js files like sound.js, for example. Have you tried to consolidate all the files into one big file, then gzip it? This order works for me: prototype.js scriptaculous.js builder.js effects.js controls.js dragdrop.js slider.js sound.js my-company-internal-script.js You can also use jsmin to minimize the output file and compress it with gzip. This would reduce the script download size to some tens of KB and also all the script is served with *one* single HTTP request instead of nine. For example, we have a total output script of 381327 bytes (it has much additional code in addition to prototype and scriptacoulous). After minification it weights 257390 bytes (67%). After compresion it is only 63135 bytes, so its only 16% of the original size. Now you have: allScripts-minified.js allScripts-minified.js.gz Then, take the name of the output file, both gzipped and minified and append the prototype, scriptacoulous and your own script versions, so when you change something in scripts, you have new name. allScripts-minified-proto-1.6.3-scripty-1.8.1-internal-r3410.js allScripts-minified-proto-1.6.3-scripty-1.8.1-internal-r3410.js.gz At the end, set your http server to set Expire: header to something in 2020 year, and serve the gziped file to clients who supports it (you can also gzip it on the fly with proper settings of server) Once your visitor downloaded the script, he/she will not have do it again until you changed versions, or until the cache is cleared. On the other hand, if your script have some bug, which needs to be corrected fast, you just need to generate new file and chage it's version, then change links in your website accrodingly. Each visitor now downloads new script and do not need to refresh the page to get corrected, bug-free scripts. All this without modification of scriptacoulous, so, when new version comes out, you just recreate the compilation and compress it, without complicated analysis what can be thrown out. Seeing as all I'm using (literally) is Sortable.create(list, properties) twice at the bottom of the page, and nothing else, there must be loads that I can carve out of the js files? Ideally I was hoping to be able to normalise them all into one efficient js file that handles the Sortable business. I think modification of libraries requires to much maintenance to do it every time new version comes out. Better to optimize the download, which can and should be automated. Regards, SWilk --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Effect.Highlight corrupts the element background-color
Hi all,
I meant to reply to the Effect.Highlight and :hover stops working?
topic
http://groups.google.com/group/prototype-scriptaculous/browse_thread/thread/0c4daab49d7a6d85#
but it is closed already.
Anyway, for the record, it seems that while the workaround given in
the above thread worked for Safari and Firefox, it did not seem to
work for IE6. To get it to work across browsers (at least Firefox and
IE), only a small change needed: use backgroundColor instead of
background:
var element = $('');
element.highlight({ afterFinish: function(effectObject) {
effectObject.element.style.backgroundColor = ;
}});
PS: I guess this is related to bug the following bug:
http://prototype.lighthouseapp.com/projects/8887/tickets/11-remove-inline-style-on-element-when-effect-highlight-finishes
--
Yves-Eric
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Re: Cut down Prototype and DragDrop
Thanks for the advice SWilk .. that was pretty detailed and very very useful! I had a little hunt around on the net and found this page (http:// blog.code-purity.com/archives/2008/10/3/ compressed_prototype_scriptaculous/) which links to a 'minified' and compressed (I think?) script containing both scriptaculous and prototype, bringing them both down to an 88kb file, which is a huge improvement. I had figured that this must be something someone somewhere had done already! I'm still concerned that it will include a lot of functions that we'll never use, but at the same time, your point about maintenance is a fair one. Thanks again for the reply! Matt On Nov 28, 11:12 am, SWilk [EMAIL PROTECTED] wrote: Hi, Matt Winward wrote: Hi all. We've just started using Scriptaculous to allow the user to rearrange their home page content panels. At the moment we have two unordered lists (left and right) and the user can move panels around to suit their preference. This is working great and the only problem we have with it is that scriptaculous.js + prototype.js + dragdrop.js + effects.js = 192kb. That's after I stopped it from loading other js files like sound.js, for example. Have you tried to consolidate all the files into one big file, then gzip it? This order works for me: prototype.js scriptaculous.js builder.js effects.js controls.js dragdrop.js slider.js sound.js my-company-internal-script.js You can also use jsmin to minimize the output file and compress it with gzip. This would reduce the script download size to some tens of KB and also all the script is served with *one* single HTTP request instead of nine. For example, we have a total output script of 381327 bytes (it has much additional code in addition to prototype and scriptacoulous). After minification it weights 257390 bytes (67%). After compresion it is only 63135 bytes, so its only 16% of the original size. Now you have: allScripts-minified.js allScripts-minified.js.gz Then, take the name of the output file, both gzipped and minified and append the prototype, scriptacoulous and your own script versions, so when you change something in scripts, you have new name. allScripts-minified-proto-1.6.3-scripty-1.8.1-internal-r3410.js allScripts-minified-proto-1.6.3-scripty-1.8.1-internal-r3410.js.gz At the end, set your http server to set Expire: header to something in 2020 year, and serve the gziped file to clients who supports it (you can also gzip it on the fly with proper settings of server) Once your visitor downloaded the script, he/she will not have do it again until you changed versions, or until the cache is cleared. On the other hand, if your script have some bug, which needs to be corrected fast, you just need to generate new file and chage it's version, then change links in your website accrodingly. Each visitor now downloads new script and do not need to refresh the page to get corrected, bug-free scripts. All this without modification of scriptacoulous, so, when new version comes out, you just recreate the compilation and compress it, without complicated analysis what can be thrown out. Seeing as all I'm using (literally) is Sortable.create(list, properties) twice at the bottom of the page, and nothing else, there must be loads that I can carve out of the js files? Ideally I was hoping to be able to normalise them all into one efficient js file that handles the Sortable business. I think modification of libraries requires to much maintenance to do it every time new version comes out. Better to optimize the download, which can and should be automated. Regards, SWilk --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] prototype weight
hello please help me about a question my prototype.js has 128kb in server. the http://ajax.googleapis.com/ajax/libs/prototype/1.6.0.3/prototype.js has 30 kb. if is the same, what is wrong? is there any shrink version of prototype and 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] shrink prototype and scriptaculous weight
hi people i think that something sounds bad: my prototype.js site 128kb and http://ajax.googleapis.com/ajax/libs/prototype/1.6.0.3/prototype.js has 30 kb. why? what do I do for reduce this size? thank --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: prototype weight
Well, best advise would be to gzip it. Tobie On Nov 28, 5:01 pm, Diodeus [EMAIL PROTECTED] wrote: You can get a compressed version here: http://groups.google.com/group/prototype-core/browse_thread/thread/40... On Nov 28, 9:35 am, gmourasilva [EMAIL PROTECTED] wrote: hello please help me about a question my prototype.js has 128kb in server. thehttp://ajax.googleapis.com/ajax/libs/prototype/1.6.0.3/prototype.js has 30 kb. if is the same, what is wrong? is there any shrink version of prototype and 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Allowing overlap with slider handles
Hi, I'm trying to augment my slider.js code in order allow sliders with two handles to have the sliders overlap when the restricted option is set to true. In the current version of script.aculo.us, if restricted is set to true, then when the user drags a slider down such that the slider's lower edge runs into the upper edge of the other slider, the user is unable to drag the slider lower. I would like to change the code so that instead of the edges being the boundary, the new restriction is that the upper slider's midpoint cannot go below the lower slider's midpoint. This would allow for more precision in sliders with two handles. I've had trouble changing the code in order to accomplish this. Does anyone know how to do this? What approach should I take? Thanks very much for your help, Jack --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Prototype with XML/XSLT, working in FF not in IE
Hi everyone. I'm a new developer with Prototype and Scriptaculous and hope someone can help me. I have a page that uses XSLT to render up an XML file - I then use Prototype to manipulate the XSLT-delivered page. I have some functionality that works in FF/Mozilla-based browsers and Safari, but that I just cannot get to work in IE6 or IE7. http://www.dix6.fsnet.co.uk/bibi/v9/stores.xml presents a page with a dropdown list and a text entry field. Essentially this page filters a bunch of retail store locations, either by region (via the dropdown) or by postcode (via the text entry field). Postcode filtering seems to work OK in all browsers, but region-selection doesn't work in IE and I can't figure out why (IE always reveals the entire bunch of stores, not just those specific to the selected region). I'm suspicious that the DOM structure created by the XSLT in IE is broken, so that Prototype functions built to operate on arrays of elements in the DOM do not work; I try to build a collection of stores to be revealed when a change event occurs on the dropdown, but it just isn't happening in IE; whenever I insert alert() statements to illuminate what's actually happening, IE tells me that the list of stores it is trying to reveal has zero length (I think the alerting around this, even in FF/Mozilla, is a bit buggy as it always returns number of stores in selected region = 66, which is actually the complete number of stores across ALL regions). I suppose it could be a problem with the way I've structured my XML and XSLT... but it's relatively straightforward on that score. I'm becming increasingly frustrated at my inability to solve this puzzle, so I wonder if anyone out there can offer any advice? All of the source code is available at http://www.dix6.fsnet.co.uk/bibi/v9/ if anyone wishes to take a look. I wonder if anyone has experienced anything similar? 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Problems with Scriptaculous Scrollbar
Hi, i develope a mask in Struts and include the Scriptaculous framework for the function 'Autocomplete'. Additionally i adopt a scrollbar with the css 'overflow:auto', but when i click on the arrows of the scrollbar in the internet Explorer, the Suggestion disappear. In FF i haven´t problems. It works... What can i do? Thank you for you 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Pause an Effects.Queue and restart, also looping
I know there is not a pause() function for the effects, but is there
any easy way of retaining the current queue and picking it back up? I
have this code to make a semi-floating image like a boat on water:
function Float(element){
new Effect.Move(element, { x: 6, y: -3, mode: 'relative', duration:
1.2, queue: { position: 'end', scope: element } });
new Effect.Move(element, { x: -4, y: 5, mode: 'relative', duration:
1.2, queue: { position: 'end', scope: element } });
new Effect.Move(element, { x: 5, y: 2, mode: 'relative', duration:
1.2, queue: { position: 'end', scope: element } });
new Effect.Move(element, { x: -7, y: -4, mode: 'relative', duration:
1.2, queue: { position: 'end', scope: element } });
}
But I want it to be interruptable if the mouse moves out. I have
several of these images, so I will have several scopes. Ideas?
Also I want the movement to loop as long as the mouse is over, so can
I just add AfterFinish: Float(element) in the parameters?
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
[Proto-Scripty] Fwd: O sol saiu!!
Encaminhando --- Hoje 27 de novembro de 2008 o sol saiu e conseguimos voltar a trabalhar. A despeito de brincadeiras e comentários espirituosos normais sobre esta folga forçada a verdade é que nunca me senti tão feliz de voltar ao trabalho. Não somente pelo trabalho, pela instituição e pela própria tranqüilidade de ter aonde ganhar o pão, mas também por ser um sinal de que a vida está voltando ao normal aqui na nossa Itajaí. As fotos que circulam na internet e os telejornais já nos dão as imagens claras de tudo que aconteceu então não vou me estender narrando e descrevendo as cenas vistas nestes dias. Todos vocês já sabem de cor. Eu quero mesmo é falar sobre lições aprendidas. Por mais que teorias e leituras mil nos falem sobre isso ainda é surpreendente presenciar como uma tragédia desse porte pode fazer aflorar no ser humano os sentimentos mais nobres e os seus instintos mais primitivos. As cenas e situações vividas neste final de semana prolongado em Itajaí nos fizeram chorar de alegria, raiva, tristeza e impotência. Fizeram-nos perder a fé no ser humano num segundo, para recuperar-la no seguinte. Fez-nos ver que sempre alguém se aproveitará da desgraça alheia, mas que também é mais fácil começar de novo quando todos se dão as mãos. Que aquela entidade superior que cada um acredita (Deus, Alá, Buda, GADU etc.) e da forma que cada um a concebe tenha piedade daqueles: - Que se aproveitaram a situação para fazer saques em Supermercados, levando principalmente bebidas e cigarros - Que saquearam uma farmácia levando medicamentos controlados, equipamentos e cofres e destruindo os produtos de primeira necessidade que ficaram assim como a estrutura física da mesma. - Que pediam 5 reais por um litro de água mineral. - Que chegaram a pedir 150 reais por um botijão de gás. - Que foram pedir donativos de água e alimentos nas áreas secas pra vender nas áreas alagadas. - Que foram comer e pegar roupas nos centros de triagem mesmo não tendo suas casas atingidas. - Que esperaram as pessoas saírem das suas casas para roubarem o que restava. - Que fizeram pessoas dormir em telhados e lajes com frio e fome para não ter suas casas saqueadas. - Que não sentiram preocupação por ninguém, algo está errado em seu coração. - Que simplesmente fizeram de conta que nada acontecia, por estarem em áreas secas. Da mesma forma, que essa mesma entidade superior abençoe: - Aqueles que atenderam ao chamado das rádios e se apresentaram no domingo no quartel dos bombeiros para ajudar de qualquer forma. - Os bombeiros que tiveram paciência com a gente no quartel para nos instruir e nos orientar nas atividades que devíamos desenvolver. - A turma das lanchas, os donos das lanchinhas de pescarias de fim de semana que rapidamente trouxeram seus barquinhos nas suas carretas e fizeram tanta diferença. - À equipe da lancha, gente sensacional que parecia que nos conhecíamos de toda uma vida. - Aos soldados do exército do Paraná e do Rio Grande do Sul. - Aos bravos gaúchos, tantas vezes vitimas de nossas brincadeiras que trouxeram caminhões e caminhões de mantimentos. - Aos cadetes da Academia da Polícia Militar que ainda em formação se portaram com veteranos. - Aos Bombeiros e Policias locais que resgataram, cuidaram , orientaram e auxiliaram de todas as formas, muitas vezes com as suas próprias casas embaixo das águas. - Aos Médicos Voluntários. - Às enfermeiras Voluntárias. - Aos bombeiros do Paraná que trabalharam ombro a ombro com os nossos. - Aos Helicópteros da Aeronáutica e Exercito que fizeram os resgates nos locais de difícil acesso. - Aos incansáveis do SAMU e das ambulâncias em geral, que não tiveram tempo nem pra respirar. - Ao pessoal do Helicóptero da Polícia Militar de São Paulo, que mostrou que longo é o braço da solidariedade. - Ao pessoal das rádios que manteve a população informada e manteve a esperança de quem estava isolado em casa. - Aos estudantes que emprestaram seus físicos para carregar e descarregar caminhões nos centros de triagem. - Às pessoas que cozinharam para milhares de estranhos. - Ao empresário que não se identificou e entregou mais de mil marmitex no centro de triagem. - A todos que doaram nem que seja uma peça de roupa. - A todos que serviram nem que seja um copo de água a quem precisou. - A todos que oraram por todos. - Ao Brasil todo, que chorou nossos mortos e nossas perdas. - Aos novos amigos que fiz no centro de triagem, na segunda-feira. - A todos aqueles que me ligaram preocupados com a gente. - A todos aqueles que ainda se preocupam por alguém. - A todos aqueles que fizeram algo, mas eu não soube ou esqueci. Há alguns anos, numa grande enchente na Argentina um anônimo escreveu isto: *COMEÇAR DE NOVO* Eu tinha medo da escuridão Até que as noites se fizeram longas e sem luz Eu não resistia ao frio facilmente Até passar a noite molhado numa laje Eu tinha medo dos mortos Até ter que dormir num cemitério Eu tinha
[Proto-Scripty] Re: New Script.aculo.us combination effect: Fisheye (beta), I need help with callback
You probably want to do something like:
mouseClick:. arguments[1].onClick || function(){}
and then, in your code, you hook up the click like so:
myelement.on(click, options.mouseClick);
which hooks the click event to the passed in function. If you need to do
other processing first, try:
myelement.on(click, function(evt){
dostuff();
options.mouseClick(evt);
});
Jerod Venema
Frozen Mountain Software
http://www.frozenmountain.com/
919-368-5105
On Fri, Nov 28, 2008 at 4:32 PM, Diodeus [EMAIL PROTECTED] wrote:
I am building a Scriptaculous-based fisheye menu, which is coming
along well. The thing I can't figure out is how to fire what is in the
onClick callback I created.
new Effect.FishEye('demo',{onClick:function(){alert(##)}})
In the initialization I have:
options = Object.extend({
mouseClick: arguments[1].onClick || '' ...
})
...which then goes to this method:
mouseClick: function(event) {
alert(u...I dunno)
},
I've been looking at other effects code to try and figure it out, but
I'm not getting anywhere.
Here's the demo: jameslab.moveable.com/fisheye
Thank you.
- James.
--
Jerod Venema
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---
