[Prototype-core] Re: What is the reason for this?
If you really want to force the issue with regard to upgrading code with a new library, you could easily supply the library in a disabled manner. Add a simple alert saying that the library is currently disabled and the readme details how to enable it along with any recent changes. But you are right, those that just update the library and not there own code (or simply ship an upgrading library to the clients - EEK!), are asking for trouble! On 18/02/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I agree that Toggle should be removed, i have been spending alot of > time optimising the prototype library for my own projects, such as > removing bad and inefficient uses of functions and removing Toggle was > one of the first things i did. > > One thing i would like to mention is that prototype is not supplied in > a package with a readme file or the like, what percentage of people > are likely to read installation instructions when downloading a new > version. In there it could include important information such as > depreciantion notices. > > But i still have no sympathy for people who fail to upgrade their code > along with the libraries that they upgrade. > > On Feb 14, 1:57 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> > wrote: > > On 2/14/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > > > > > > > > Oh. Um. Er. There's a compatibility addon? > > > > Just an idea I tossed in previously. Removed code could simply be extracted > > to such an add-on. > > > > > -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" --~--~-~--~~~---~--~~ 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: What is the reason for this?
I agree that Toggle should be removed, i have been spending alot of time optimising the prototype library for my own projects, such as removing bad and inefficient uses of functions and removing Toggle was one of the first things i did. One thing i would like to mention is that prototype is not supplied in a package with a readme file or the like, what percentage of people are likely to read installation instructions when downloading a new version. In there it could include important information such as depreciantion notices. But i still have no sympathy for people who fail to upgrade their code along with the libraries that they upgrade. On Feb 14, 1:57 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > On 2/14/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > > > > Oh. Um. Er. There's a compatibility addon? > > Just an idea I tossed in previously. Removed code could simply be extracted > to such an add-on. --~--~-~--~~~---~--~~ 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: What is the reason for this?
Lol, nice.. I agree though, if someone doesn't care about Prototype enough to read the changelogs and blog, then why is he updating anyway? So does RoR use the Toggle.display method? Cuz I had never even seen it mentioned or used anywhere before. Colin On Feb 14, 6:51 am, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > On 2/14/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > > > > Almost - but there are many, [dramatic pause] many fools out there. > > So we're talking about a person that keeps up to latest Prototype framework, > but doesn't read the blog, isn't interested in the changelog, ignores the > deprecation notices and is unaware of the compatibility addon? Where does he > live and why is he updating then? > > In short, my heart bleeds for that guy :P --~--~-~--~~~---~--~~ 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: What is the reason for this?
> Just an idea I tossed in previously. Removed code could simply be extracted > to such an add-on. Definitely the way to go. That what jQuery does for instance - and it a great idea. Release a plugin with every new release that keeps the deprecated stuff working. It's not a lot of work, and it's really much appreciated. Just my $ .02 --~--~-~--~~~---~--~~ 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: What is the reason for this?
On 2/14/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > > Oh. Um. Er. There's a compatibility addon? Just an idea I tossed in previously. Removed code could simply be extracted to such an add-on. --~--~-~--~~~---~--~~ 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: What is the reason for this?
On 14/02/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote: > On 2/14/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > Almost - but there are many, [dramatic pause] many fools out there. > > So we're talking about a person that keeps up to latest Prototype framework, > but doesn't read the blog, isn't interested in the changelog, ignores the > deprecation notices and is unaware of the compatibility addon? Where does he > live and why is he updating then? > > In short, my heart bleeds for that guy :P Oh. Um. Er. There's a compatibility addon? -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" --~--~-~--~~~---~--~~ 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: What is the reason for this?
On 2/14/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > Almost - but there are many, [dramatic pause] many fools out there. So we're talking about a person that keeps up to latest Prototype framework, but doesn't read the blog, isn't interested in the changelog, ignores the deprecation notices and is unaware of the compatibility addon? Where does he live and why is he updating then? In short, my heart bleeds for that guy :P --~--~-~--~~~---~--~~ 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: What is the reason for this?
Almost - but there are many, [dramatic pause] many fools out there. On 14/02/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote: > On 2/14/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > I would recommend announcing the removal BEFORE the actual removal. > > Yeah, that's why I said "warn people in advance via blog posts" (only in > different words). > > People read the blog. Also, there could be deprecation notices in release > notes for minor releases, as well as API break warnings in changelog for > major releases. Coupled with the compatibility add-on this plan is (almost) > foolproof! :) > > > > > -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" --~--~-~--~~~---~--~~ 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: What is the reason for this?
On 2/14/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > I would recommend announcing the removal BEFORE the actual removal. Yeah, that's why I said "warn people in advance via blog posts" (only in different words). People read the blog. Also, there could be deprecation notices in release notes for minor releases, as well as API break warnings in changelog for major releases. Coupled with the compatibility add-on this plan is (almost) foolproof! :) --~--~-~--~~~---~--~~ 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: What is the reason for this?
I would recommend announcing the removal BEFORE the actual removal.
Give a clear indication of what is required to upgrade old but working
code to new and working code. Remember that the the user's code is NOT
wrong and that the change being made is a nicety and NOT a bug.
Introducing BC breaks are always going to cause headaches for users
("It worked last week and when I upgraded the library it didn't work
any more - can you help me fix it?" - sort of thing).
On 14/02/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
> On 2/14/07, Thomas Fuchs <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > For stuff like this, we'd need some way of marking things as deprecated,
> giving a warning that it "will be removed in next major version".
>
> I don't think it's necessary to go the Rails way with this. Simply writing
> the blog post about deprecated stuff for versions 1.6 - 2.0 and repeating
> those notices when actually releasing seems enough.
>
> $("foo").toggle is nicer (and more encouraged!), anyway. How hard will it be
> to replace? And if people really want to update fast without fixing their
> old code at the moment, we could provide a backwards-compatibility addon
> with this code we removed.
>
>
> >
>
--
-
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
--~--~-~--~~~---~--~~
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: What is the reason for this?
On 2/14/07, Thomas Fuchs <[EMAIL PROTECTED]> wrote:
>
>
> For stuff like this, we'd need some way of marking things as deprecated,
> giving a warning that it "will be removed in next major version".
>
I don't think it's necessary to go the Rails way with this. Simply writing
the blog post about deprecated stuff for versions 1.6 - 2.0 and repeating
those notices when actually releasing seems enough.
$("foo").toggle is nicer (and more encouraged!), anyway. How hard will it be
to replace? And if people really want to update fast without fixing their
old code at the moment, we could provide a backwards-compatibility addon
with this code we removed.
--~--~-~--~~~---~--~~
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: What is the reason for this?
That's in for backwards compatibility.
For stuff like this, we'd need some way of marking things as
deprecated, giving a warning that it "will be removed in next major
version".
I can imagine an optional deprecated.js file to load in while doing
development, that gives console.log warnings (or so) whenever you use
deprecated Prototype methods, so you can check your code if something
needs to be changed.
Best,
Thomas
Am 14.02.2007 um 09:01 schrieb Mislav Marohnić:
> On 2/14/07, Colin Mollenhour <[EMAIL PROTECTED]> wrote:
>
> 1686 var Toggle = new Object();
> 1687 Toggle.display = Element.toggle;
>
> What is the point of this?
>
> It's a shortcut that's supposed to look nice while writing:
>
>Toogle.display ("foo")
>
> I don't like it, though, and also agree that it pollutes the global
> namespace.
>
> +1 for removing it. That makes two of us now.
>
> >
--
Thomas Fuchs
wollzelle
http://www.wollzelle.com
questentier on AIM
madrobby on irc.freenode.net
http://www.fluxiom.com :: online digital asset management
http://script.aculo.us :: Web 2.0 JavaScript
http://mir.aculo.us :: Where no web developer has gone before
--~--~-~--~~~---~--~~
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: What is the reason for this?
On 2/14/07, Colin Mollenhour <[EMAIL PROTECTED]> wrote:
>
>
> 1686 var Toggle = new Object();
> 1687 Toggle.display = Element.toggle;
>
> What is the point of this?
It's a shortcut that's supposed to look nice while writing:
Toogle.display("foo")
I don't like it, though, and also agree that it pollutes the global
namespace.
+1 for removing it. That makes two of us now.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
