unsubscribe
Carl Zetterberg
Tic-Tac Mobile
www.tictacmobile.com
+46-8-660 66 41
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email to
Hi all!
Since we are past 1.6.0 final i wonder when you will remove the
deprecated portion of the source.
Best,
Kjell Bublitz
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this
On 07/01/2008, Kjell Bublitz [EMAIL PROTECTED] wrote:
Hi all!
Since we are past 1.6.0 final i wonder when you will remove the
deprecated portion of the source.
Best,
Kjell Bublitz
I do this by hand by adding comment tags around the code. That way, it
is just an uncomment when you realize
So it's save to simply delete the section myself if i begin to write a
new application using 1.6.x?
On Jan 7, 2008 1:42 PM, Richard Quadling [EMAIL PROTECTED] wrote:
On 07/01/2008, Kjell Bublitz [EMAIL PROTECTED] wrote:
Hi all!
Since we are past 1.6.0 final i wonder when you will
On Jan 7, 2008 1:48 PM, Kjell Bublitz [EMAIL PROTECTED] wrote:
So it's save to simply delete the section myself if i begin to write a
new application using 1.6.x?
Yes. It is also safe to delete the section if you fully port your old
scripts to 1.6. Consider that section as a patch that
element.update(hello)
Element.update can take a string (in which case it's set as
innerHTML), an Element object, or any object that responds to either
toElement or toHTML (and which returns accordingly either an element
or a string of html :))
(The same goes for Element.replace and
What features are the authors considering in upcoming releases? Or is
public discussion of the Prototype/SAU roadmap limited due to factors
such as competition with other frameworks?
Based on hints dropped in the lists, I can make a few guesses:
- Expand Prototype custom events to fire
On Jan 7, 2008 9:25 PM, Ken Snyder [EMAIL PROTECTED] wrote:
What features are the authors considering in upcoming releases? Or is
public discussion of the Prototype/SAU roadmap limited due to factors
such as competition with other frameworks?
We don't lay out long roadmaps for Prototype
Mislav Marohnić wrote:
On Jan 7, 2008 9:25 PM, Ken Snyder [EMAIL PROTECTED]
Some ideas
are shared with the community while some are kept private for further
discussions among core members.
Why the secrecy? This is an open source project after all.
So, the reason we don't share the exact
Mislav Marohnić wrote:
...
- Expand Prototype custom events to fire callbacks for Element methods
such as update, setStyle, remove, replace, insert, wrap,
writeAttribute,
addClassName, removeClassName, scrollTo, etc.
That is planned for the next major release. Based on
Mislav Marohnić wrote:
...
- Add Prototype support for onmouseenter and onmouseleave
This is definitely useful to the majority of users. We are still
discussing if it's going to become core and in which version.
Meanwhile, read the very insightful article by Andrew about why
I periodically share Michael's feelings as well. For me, those concerns
would be eliminated if the authors did two things:
1. Publicly disclosed the enhancements they were /considering/ (not
necessarily a formal roadmap)
2. Set up a thriving community for official and unofficial plugins
For
This is great. Kudos to Kangax for compiling it!
I'm probably dreaming too big, but it would be great if the code was
submitted so that it could be hosted on the site and required unit tests
to be certified for a certain Prototype version. Plus demos on the
site would be fantastic. I really
Ken,
http://scripteka.com/
Prototype extensions library.
maintained by Kangax
On Jan 8, 2008 10:42 AM, Ken Snyder [EMAIL PROTECTED] wrote:
I periodically share Michael's feelings as well. For me, those concerns
would be eliminated if the authors did two things:
1. Publicly disclosed the
On Monday 07 January 2008, Ken Snyder wrote:
- Expand Prototype custom events to fire callbacks for Element
methods such as update, setStyle, remove, replace, insert, wrap,
writeAttribute, addClassName, removeClassName, scrollTo, etc.
I've written about notifications for DOM changes just
Mislav Marohnić wrote:
...
- Add intuitive Prototype methods for checkbox- and radio-group form
elements ( e.g. a method to get the value of the currently checked
item(s) in based on a group name)
Hmm, we have it for select boxes and multiple selects, why not radio
Yup,
That's awsome. Very insightful remarks, too.
How does the performance feel ?
Best,
Tobie
On Jan 7, 11:26 pm, Michael Schuerig [EMAIL PROTECTED] wrote:
On Monday 07 January 2008, Ken Snyder wrote:
- Expand Prototype custom events to fire callbacks for Element
methods such as
On Jan 8, 9:33 am, Ken Snyder [EMAIL PROTECTED] wrote:
Mislav Marohnić wrote:
...
- Add intuitive Prototype methods for checkbox- and radio-group form
elements ( e.g. a method to get the value of the currently checked
item(s) in based on a group name)
Hmm, we have it
18 matches
Mail list logo
