[Prototype-core] Re: General global element events and prototype 1.6.0_rc0
I currently do this: Event.DOMEvents.push((Prototype.Browser.Gecko) ? 'DOMMouseScroll' : 'mousewheel'); when I define my custom signalConnect functions, so that the mousewheel event will work. Thought I'd like for this and the enter/ leave events to be integrated, so that I can remove this seemingly redundant code. On Aug 18, 8:41 pm, Somebee [EMAIL PROTECTED] wrote: Does this mean that prototype 1.6.0_rc0 does not support mousewheel/ DOMMouseScroll? Is there an easy way to implement the support (my previous plugin no longer works) Best regards Sindre On Aug 17, 12:24 pm, Mislav Marohnić [EMAIL PROTECTED] wrote: On 8/17/07, Viktor Kojouharov [EMAIL PROTECTED] wrote: However, there's still the issue of having support for global element events, like 'mousewheel', 'mouseenter', and 'mouseout', that would work with all elements, and reuse existing event names to achieve their function. In the old events branch there was support for mousewheel/enter/out. This was held back until release 1.6.1 in the future. Prototype 1.6.0 has support for domready. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: General global element events and prototype 1.6.0_rc0
On 8/20/07, kangax [EMAIL PROTECTED] wrote: I did something similar for my context menu script. Since 1.6.0_rc0 does not have 'contextmenu' event and latest build in a trunk does, I worked around it like so: Simply use trunk until the 1.6.0 final release. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: General global element events and prototype 1.6.0_rc0
On 8/20/07, kangax [EMAIL PROTECTED] wrote: Of course, but if it's a public extension Oh, didn't realize this. Well, yeah, you can do these tiny conditional hacks. I hope we release the final soon --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Error/counter-intuitive Class-inheritance?
When you push values into an array on an object, the values of the class/prototype-array is also changed. http://pastie.caboo.se/89295 - example Is this how it is supposed to work? If so, it seems very odd and counter-intuitive to me. Best Regards Sindre --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: 1.6 release; suggestion for templates
Yes, I completely agree with you. And what are you think about the edit behaviors for data to be added in prototype, the same as in Ext - http://extjs.com/ They have great inline editing for a grid. What do you think about adding this feature ? On Aug 20, 5:37 pm, Mislav Marohnić [EMAIL PROTECTED] wrote: On 8/20/07, Andriy Mykhaylyuk [EMAIL PROTECTED] wrote: And I have a feature suggestion for templates system. That will be great if templates will support some sort of cycles with internal templates or table building. Something like gridview in ASP.NET for example. For a table builder it's good if we will have supported following templates : Row, AlternatingRow, Header, Footer, EmptyData. What do you think about ? I think it would make a great Prototype add-on, but that it is not for core framework. We at core team share beliefs that major HTML fragments should be generated at the server, not on client side. Still, a table builder support classes could be of great use in some applications. Keep in mind that grid components for Prototype (and other frameworks) are almost always based on the existing table in the DOM (that is, one generated by the server). These components just add the behavioral layer. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: 1.6 release; suggestion for templates
Andriy Mykhaylyuk wrote: Hello guys, thanx for update, and my congratulations, looks like a lot of people loves new updates. And I have a feature suggestion for templates system. That will be great if templates will support some sort of cycles with internal templates or table building. Something like gridview in ASP.NET for example. For a table builder it's good if we will have supported following templates : Row, AlternatingRow, Header, Footer, EmptyData. What do you think about ? I agree that more robust templating isn't a good fit for core. I had a similar need and came up with a compiled template class that is made for using a server-side html template to repeatedly generate content in JavaScript. Now that html5 embraces innerHTML, it is time to take advantage of it's speed. I have a piece of code in production that you can see here: http://rafb.net/p/jxjGr139.html. I'm working on making it more robust, but it is completely extensible and would allow you to add simple functions to give the table functionality you mention. When I finish, I'll do a full write-up on my web site. - Ken Snyder --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: Error/counter-intuitive Class-inheritance?
On 8/20/07, Somebee [EMAIL PROTECTED] wrote: When you push values into an array on an object, the values of the class/prototype-array is also changed. You've been bitten by the fact the array is copied by reference, not by value. You should be setting the initial value for instance variables in the constructor: http://pastie.caboo.se/89338 I'm not sure if this is something we should fix or not. In a way, the framework might deal with this situations in order to follow the POLS (principle of least surprise). We need to discuss this internally. Anyway, do as I suggested for now. This might change in release 1.6.1. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: Error/counter-intuitive Class-inheritance?
On Aug 20, 2007, at 11:51 AM, Mislav Marohnić wrote: You've been bitten by the fact the array is copied by reference, not by value. You should be setting the initial value for instance variables in the constructor: http://pastie.caboo.se/89338 I'm not sure if this is something we should fix or not. In a way, the framework might deal with this situations in order to follow the POLS (principle of least surprise). We need to discuss this internally. Anyway, do as I suggested for now. This might change in release 1.6.1. There is nothing to fix here. This is the exact problem that constructors solve. I don't think it's surprising, and we won't be changing it. -sam smime.p7s Description: S/MIME cryptographic signature
[Prototype-core] Re: Fisheye control for prototype.
That is a very keen observation, well kind of, the bounce certainly catches my eyes. I believe this is in FF only. A solution is to set the Fish Eye Toolbar's position to absolute, such that its children are not equated in the document flow, thus when the animation occurs it has no factor on anything descending in the document. I'll put that into the entry as this is a concern. Cheers, Matt On Aug 20, 1:04 pm, John Barnette [EMAIL PROTECTED] wrote: On 8/20/07, Mislav Marohnić [EMAIL PROTECTED] wrote: On 8/20/07, Matt Foster [EMAIL PROTECTED] wrote: The animation is smooth and the code is very extendable. http://positionabsolute.net/blog/2007/08/prototype-fisheye.php There is another glitch, and that is if I interact with the effect (move my mouse from left to right), some random paragraphs in the below text are slightly moving also. Is anyone else observing this? Subheadings are showing a 1px vertical jog for me (FF2 on OS X). ~ j. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: Enumerable.pluck()-like setter
On Aug 17, 2007, at 12:22 AM, Mislav Marohnić wrote: It's nice to hear about how all of you solved the problem of collection attribute assignment, but the variety of solutions shows that this is very app-specific (IMO). I won't argue against not including (invoke-ing writeAttribute works just fine), but I find your reasoning extremely odd. I would think the variety of solutions actually demonstrates a wide-spread need, not an app-specific one. (If you were to call it a training/ experience issue, pointing to invoke's ability to accept multiple parameters, then I'd agree wholeheartedly, and not complain. =) I've never needed this myself; and if I have, it would only be in one or two places, which hardly justifies its inclusion in the core framework. ... and I've never needed $R, PeriodicalExecuter or Ajax.PeriodicalUpdater. At all. Not even once. Doesn't mean they're not useful. I'm being a bit argumentative ... Like I said, I have no grief over the conclusion, but I think your reasons are off. =) TAG --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@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-core?hl=en -~--~~~~--~~--~--~---
