Rails spinoffs - Oct 2007 - The "Deprecated" section of http://prototypejs.org/assets/2007/10/16/prototype.js

Hi.

First of all, "Thank you".

If you don''t get enough thanks from your users, then read that line
several times, until your self-worth is higher that the highest thing
you can think of.

Your efforts make my life easier.

And on to the question at hand.

In http://prototypejs.org/assets/2007/10/16/prototype.js, there is a
"Deprecated" section.

If this was removed would that help me make sure my code was compliant
to this release?

Sure, something may be easy to find (getElementByClassName for
example), but others may not be so easy.

Obviously, we all test our code before releasing it, so, why are the
deprecated features actually present?

Ideally, the deprecated feature should report that this is deprecated
and maybe give alternative. Like $continue.

Maybe just commented out - allowing us to uncomment if needed until we
work out what to fix.

Regards,

Richard.
-- 
-----
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
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

On 10/17/07, Richard Quadling
<rquadling-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
wrote:
> First of all, "Thank you".
> ...
>
> Your efforts make my life easier.
+1!

> ...
> In http://prototypejs.org/assets/2007/10/16/prototype.js, there is a
> "Deprecated" section.
> ...
> Ideally, the deprecated feature should report that this is deprecated
> and maybe give alternative. Like $continue.
I like this concept as well.  Over three releases I picture this: mark
as deprecated => warn of deprecation => remove from library


- Ken Snyder

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi Richard,

do not forget that deprecation is ONLY tagging.
It means that this STILL works as before. What it could do is that it
perhaps logs to firebug but that''s it.
And that''s the issue will all protocols and languages that do not
support
deprecation well.
Actually noone manages this good enough. Java tooling is quite good that it
will notify you quite obvious that you are using deprecated code.
However, as said: The code shall work without modification as before.

If it wouldn''t this would not be deprecation.

If anybody has a good idea how to deprecate things I am open to this. I am
still having the issue how to deprecate a certain xml section in a schema :)

So actually I like the approach of having the deprecated section there .
Ideally this should be at the beginning of the file and not at the end to be
more prominent.


.: Fabian

-----Original Message-----
From:
grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@googlegroups.c
om
[mailto:grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@google
groups.com] On Behalf Of Richard Quadling
Sent: Mittwoch, 17. Oktober 2007 16:56
To: rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: [Rails-spinoffs] The "Deprecated" section of
http://prototypejs.org/assets/2007/10/16/prototype.js


Hi.

First of all, "Thank you".

If you don''t get enough thanks from your users, then read that line
several times, until your self-worth is higher that the highest thing
you can think of.

Your efforts make my life easier.

And on to the question at hand.

In http://prototypejs.org/assets/2007/10/16/prototype.js, there is a
"Deprecated" section.

If this was removed would that help me make sure my code was compliant
to this release?

Sure, something may be easy to find (getElementByClassName for
example), but others may not be so easy.

Obviously, we all test our code before releasing it, so, why are the
deprecated features actually present?

Ideally, the deprecated feature should report that this is deprecated
and maybe give alternative. Like $continue.

Maybe just commented out - allowing us to uncomment if needed until we
work out what to fix.

Regards,

Richard.
-- 
-----
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
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

On 17/10/2007, Ken Snyder
<kendsnyder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> On 10/17/07, Richard Quadling
<rquadling-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote:
> > ...
> > In http://prototypejs.org/assets/2007/10/16/prototype.js, there is a
> > "Deprecated" section.
> > ...
> > Ideally, the deprecated feature should report that this is deprecated
> > and maybe give alternative. Like $continue.
>
> I like this concept as well.  Over three releases I picture this: mark
> as deprecated => warn of deprecation => remove from library
I think RCs should give quite obvious errors. I would go with
firebug''s console as this is available for FF (via a full blown
extension) and for other browsers via the firebuglite.js
(http://www.getfirebug/firebug/firebug.js)

But only in RCs.

So, a ...

console.info(''This is a deprecated feature'');

maybe?

OOI. I just commented out the entire block and all my code is working
except for the getElementByClassName which I just changed as per the
release notes. So I''m back in business.

Another option is to put all the deprecated stuff in a test ...

if (Prototype.allowDeprecated) { ... }

Now, in your own library, you have to add ...

Prototype.allowDeprecated = true;

to access that really old stuff which you should have stopped using
MANY years ago and may quite suddenly be taken away from you as you
have been truly warned!!!!

This means a 1 line short-term fix to use the new library (assuming
the feature is still present).

Richard.

-- 
-----
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
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---