[Prototype-core] Re: Roadmap
+1 on more information outside the core team on where Prototype is headed, agnostic as to what form it takes. Since this is the core mailing list, it seems like it would be here, but I don't recall mention of the new layout stuff or on here. (Could be my memory, though.) -- T.J. On Apr 8, 12:06 am, Allen Madsen bla...@gmail.com wrote: I agree that a road map would be helpful. In addition to the reasons gf3 mentioned, I think it would make it easier to contribute. Allen Madsenhttp://www.allenmadsen.com On Wed, Apr 7, 2010 at 4:53 PM, gf3 giannichiappe...@gmail.com wrote: This is a continuation of the discussion started here: http://github.com/sstephenson/prototype/commit/2f9bde3ad5a2e3dd104c81... It would be very helpful to see some sort of Prototype roadmap or at least be able to see internal discussion about the development of the library. Not only from a personal interest standpoint but I also receive a lot of questions on IRC regarding what Prototype is doing, what's happening with development, c. Unfortunately, right now, I don't really have an information that I can pass on. Tobie mentioned a public read-only interface to internal discussions – this would satisfy my needs. Although a formal roadmap may be beneficial to core devs as well. -- 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 prototype-core-unsubscr...@googlegroups.com For more options, visit this group athttp://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using remove me as the subject. -- 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 prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en
[Prototype-core] Re: Roadmap
Hi folks, I'm being dense, there's already the outline of a roadmap: http://prototype.lighthouseapp.com/projects/8886-prototype/milestones There are milestones for 1.6.0.3 (completed), 1.6.0.4, 1.6.1, and the inline documentation. I don't know what the release with the big changes is going to be called, I'm guessing 2.0.0 as it'll be an API shuffle. Perhaps we could add a milestone and links to tickets for the big things? Such as not extending native object prototypes, that sort of thing... Then a Roadmap link from the main prototypejs.org site to the Lighthouse list would give people an idea what the plans were. Dates would be nice, but with this kind of project, I don't know how realistic having dates on milestones is. -- T.J. :-) On Oct 24, 12:32 am, kangax [EMAIL PROTECTED] wrote: On Oct 23, 5:12 pm, T.J. Crowder [EMAIL PROTECTED] wrote: Hi folks, Now that 1.6.0.3 is out the door (kudos!!), is there work toward a roadmap for 1.6.1, 1.6.2, and (gasp) 2.0 in the works? Obviously there was that discussion thread recently, but it was a lot of discussion and relatively little (I think) definitive statement by Core. I know that using wrappers rather than extending native prototypes is on the cards, and inline documentation, both of which (IMHO) are very good moves. What else? Plans can change, of course, but the absense of a plan leads to meandering I'm working on replacing UA sniffing with proper feature tests (where possible). We also have bugfixes that didn't make its way into 1.6.0.3 (for various reasons). Some of those will need to be reviewed, tested and applied to 1.6.0.4. Thanks, -- T.J. Crowder tj / crowder software / com -- kangax --~--~-~--~~~---~--~~ 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: Roadmap
First and foremost: handling the bug backlog. I'm currently working on extracting and revamping the unittest (that should be out pretty soon). Ajax needs some love (for 1.6.1) Dimensions work by Andrew. ... On Oct 23, 11:12 pm, T.J. Crowder [EMAIL PROTECTED] wrote: Hi folks, Now that 1.6.0.3 is out the door (kudos!!), is there work toward a roadmap for 1.6.1, 1.6.2, and (gasp) 2.0 in the works? Obviously there was that discussion thread recently, but it was a lot of discussion and relatively little (I think) definitive statement by Core. I know that using wrappers rather than extending native prototypes is on the cards, and inline documentation, both of which (IMHO) are very good moves. What else? Plans can change, of course, but the absense of a plan leads to meandering Thanks, -- T.J. Crowder tj / crowder software / com --~--~-~--~~~---~--~~ 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: Roadmap
On Oct 23, 5:12 pm, T.J. Crowder [EMAIL PROTECTED] wrote: Hi folks, Now that 1.6.0.3 is out the door (kudos!!), is there work toward a roadmap for 1.6.1, 1.6.2, and (gasp) 2.0 in the works? Obviously there was that discussion thread recently, but it was a lot of discussion and relatively little (I think) definitive statement by Core. I know that using wrappers rather than extending native prototypes is on the cards, and inline documentation, both of which (IMHO) are very good moves. What else? Plans can change, of course, but the absense of a plan leads to meandering I'm working on replacing UA sniffing with proper feature tests (where possible). We also have bugfixes that didn't make its way into 1.6.0.3 (for various reasons). Some of those will need to be reviewed, tested and applied to 1.6.0.4. Thanks, -- T.J. Crowder tj / crowder software / com -- kangax --~--~-~--~~~---~--~~ 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: Roadmap for 1.6.1 (My take)
I don't have anything specific that I'd like to see in Prototype. The event delegation sounds excellent! I'm happy it will fix the memory leak that's been plaguing me because of it. My general feeling is that we should implement some new features that get developers excited about Prototype. The new browsers are introducing many new technologies and it would be great to expand this framework into that piece of the future (DOM storage, HTML5, webforms2, etc). Additionally, scriptaculous2 is called scripty. I'm not sure what the road map is, but I'd like to see it take advantage of the new browsers just the same by implementing CSS3 Transitions for example. There are many new things to learn with FF3, IE8, new Opera, and WebKit. It would be great to have 1 framework that brought us the advantages of all those great new things. Maybe that's better for a 1.7 or 1.8 since it's slightly ambitious. Oh, also, does anyone know where I galleries of busty teens? Is this list being moved like the other one? --~--~-~--~~~---~--~~ 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: Roadmap for 1.6.1 (My take)
Ken, wouldn't Enumerable.addMethods be just a wrapper around
Class.addMethods? Like Class.addMethods(Enumerable, methods)
On Jul 3, 7:31 am, Ken Snyder [EMAIL PROTECTED] wrote:
Yes, those escapeHTML fixes are what I was thinking.
I'm excited to see Event delegation!
Also, I wanted to suggest some more ways to extend and customize Prototype:
*Event.addMethods* to allow adding methods to Event instances
(http://prototype.lighthouseapp.com/projects/8886-prototype/tickets/203)
*Class.addMethods* to allow adding methods to every class instance for
classes created with Class.create() (http://dev.rubyonrails.org/ticket/10089
)
*Enumerable.addMethods* as a quick way to add methods to all enumerables:
Enumerable.addMethods = function(methods) {
Hash.addMethods(methods);
ObjectRange.addMethods(methods);
Object.extend(Ajax.Responders, methods);
Object.extend(Array.prototype, methods);
Element.ClassNames.addMethods(methods); // i think this is deprecated now
};
- Ken
--~--~-~--~~~---~--~~
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: Roadmap for 1.6.1 (My take)
Also utilizing element.ownerDocument more (this will help in compatibility with iframes). Maybe a Element#getDocument(), getBodyElement, getRootElement. --~--~-~--~~~---~--~~ 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: Roadmap for 1.6.1 (My take)
Is avoiding document.write() for IE dom:loaded included in 1.6.1? I think the core team concluded that doScroll was the way to go, but I'm not sure. What about fixing String#escapeHTML for IE and WebKit? What about enhancing Element#siblings to accept a selector? (http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thread/4dd057addb2b0be1/c354acd62c1fbe43?lnk=gstq=siblings+check#c354acd62c1fbe43) What are the thoughts on adding an Object.isEmpty or Object.hasProperties? (http://dev.rubyonrails.org/ticket/10356) Thanks, - Ken John-David Dalton wrote: I haven't seen the official roadmap for 1.6.1. So here is my take on it. 1.6.0.3 was a bug fix release. I see 1.6.1 as an optimization and new feature/API release. I see things like: * Use of documentFragment (Huge IE boost in spots), * Use of _each instead of each in places were we can * Remove the event onunload mechanism for IE (I have a working prototype of it) * Avoiding wrapped methods internally (Element.method(element) instead of element.method()) * Implement hasOwnProperty for Safari 2.0.4 (can finally use it in the rest of the code) * Make $H(...).include() work properly * Pass optional conditionals to methods like Element#show, Element#hide and others) * Optimize the Template class. * Make Element#getStyle automatically convert units to px and handle the inherit style. * Use of Dimensions class * Create various methods where needed: - Object.isNodeList() - Element#isOrphaned - Element#getNumericStyle [cssToNumber] * Ajax Fixes: - Network error fixes - Timeout added - Abort added - Detect when status 0 is allows (when its ftp or file protocols) I am sure I missed a few, but the good news is almost all of these listed features/modifications have already been programmed. We should be able to create the tickets and unit tests rather fast. Do yall have anything else to add? Here is a list of tickets currently marked to be addressed for 1.6.1 (not nessesarily included in 1.6.1) http://prototype.lighthouseapp.com/projects/8886-prototype/tickets?filter=page=1q=state%3Aopen+milestone%3A1.6.1 - JDD --~--~-~--~~~---~--~~ 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: Roadmap for 1.6.1 (My take)
Automagical stopObserving on update/remove? Event delegation modification in core (so you can attach delegated events to observe instead of having to write the same document.observe pattern with a series of if-s and element.match(cssSelector)? Gareth On Thu, Jul 3, 2008 at 9:51 AM, kangax [EMAIL PROTECTED] wrote: +1 for hasProperties/isEmpty I would also want to see #setProperty. Ken, which #escapeHTML fix are you talking about? We actually made few changes in a current trunk. Besides what was mentioned: - deprecate Try.these - deprecate Array#reduce (for compatibility with FF3+) - update String#isJSON -- kangax On Jul 2, 4:34 pm, Ken Snyder [EMAIL PROTECTED] wrote: Is avoiding document.write() for IE dom:loaded included in 1.6.1? I think the core team concluded that doScroll was the way to go, but I'm not sure. What about fixing String#escapeHTML for IE and WebKit? What about enhancing Element#siblings to accept a selector? (http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thr.. .) What are the thoughts on adding an Object.isEmpty or Object.hasProperties? (http://dev.rubyonrails.org/ticket/10356) Thanks, - Ken John-David Dalton wrote: I haven't seen the official roadmap for 1.6.1. So here is my take on it. 1.6.0.3 was a bug fix release. I see 1.6.1 as an optimization and new feature/API release. I see things like: * Use of documentFragment (Huge IE boost in spots), * Use of _each instead of each in places were we can * Remove the event onunload mechanism for IE (I have a working prototype of it) * Avoiding wrapped methods internally (Element.method(element) instead of element.method()) * Implement hasOwnProperty for Safari 2.0.4 (can finally use it in the rest of the code) * Make $H(...).include() work properly * Pass optional conditionals to methods like Element#show, Element#hide and others) * Optimize the Template class. * Make Element#getStyle automatically convert units to px and handle the inherit style. * Use of Dimensions class * Create various methods where needed: - Object.isNodeList() - Element#isOrphaned - Element#getNumericStyle [cssToNumber] * Ajax Fixes: - Network error fixes - Timeout added - Abort added - Detect when status 0 is allows (when its ftp or file protocols) I am sure I missed a few, but the good news is almost all of these listed features/modifications have already been programmed. We should be able to create the tickets and unit tests rather fast. Do yall have anything else to add? Here is a list of tickets currently marked to be addressed for 1.6.1 (not nessesarily included in 1.6.1) http://prototype.lighthouseapp.com/projects/8886-prototype/tickets?fi. .. - JDD --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
