|
| 29 Sep 2012 02:50 PM |
Here's my idea:
So lets say you write some code and upload it to your models.
You then proceed to go to the model and go to the config. (Name, Set a category)
If you scroll down past the default stuff there is something I would like to call: "deprecated method checker"
What it does is check if the model is a script or has a script inside of it and checks for any outdated methods etc.
If it does then it says:
"METHOD: (Name) IS OUTDATED! CHANGE YOUR CODE TO FIT WITH OUR STANDARDS"
So there is my idea. Throw me any feedback you got. I welcome suggestions.
|
|
|
| Report Abuse |
|
|
TaslemGuy
|
  |
| Joined: 10 Jun 2009 |
| Total Posts: 12174 |
|
|
| 29 Sep 2012 02:50 PM |
Or you could make the deprecated methods say such things.
Which is easier and more obvious. |
|
|
| Report Abuse |
|
|
| |
|
|
| 29 Sep 2012 02:54 PM |
^ And also, I think instead of checking in the config page, it should check when you upload. Show a messagebox that says something like:
"WARNING
Model.Script: 3: Remove() is a deprecated method. Use Destroy() instead. "
-= I'm not paranoid. Why? Who's asking!? =- |
|
|
| Report Abuse |
|
|
|
| 29 Sep 2012 03:11 PM |
@TaslemGuy
Yeah, you're right...We should have it built-in to the ROBLOX code editor. And when we publish it then Techboy6601's idea comes into play. |
|
|
| Report Abuse |
|
|
stravant
|
  |
 |
| Joined: 22 Oct 2007 |
| Total Posts: 2893 |
|
|
| 29 Sep 2012 03:36 PM |
| There's too much legacy code out there that the users of can't update themselves. It would just annoy people. |
|
|
| Report Abuse |
|
|
|
| 29 Sep 2012 03:40 PM |
@stravant
But code is deprecated for a reason. It's better to have users annoyed than frustrated as to why their legacy code doesn't work anymore.
And besides, it would be pretty simple to code a checkbox in to my idea that says "Do not show this warning again" or something similar so if users really want to, they can get rid of it.
If deprecation isn't respected, what's the point of deprecating them in the first place?
-= I'm not paranoid. Why? Who's asking!? =- |
|
|
| Report Abuse |
|
|
LPGhatguy
|
  |
 |
| Joined: 27 Jun 2008 |
| Total Posts: 4725 |
|
|
| 29 Sep 2012 06:06 PM |
@techboy6601 How often does ROBLOX actually remove deprecated items, really? |
|
|
| Report Abuse |
|
|
Legend26
|
  |
| Joined: 08 Sep 2008 |
| Total Posts: 10586 |
|
|
| 29 Sep 2012 06:10 PM |
| Very very rarely. Only when they're a security risk and are absolutely sure no one uses the objects. Then again, we still have a Geometry and Timer object, neither of which do anything and yet they aren't removed. |
|
|
| Report Abuse |
|
|
|
| 29 Sep 2012 06:46 PM |
But then why do they deprecate them? It makes no sense.
-= I'm not paranoid. Why? Who's asking!? =- |
|
|
| Report Abuse |
|
|
stravant
|
  |
 |
| Joined: 22 Oct 2007 |
| Total Posts: 2893 |
|
|
| 29 Sep 2012 09:24 PM |
"But code is deprecated for a reason. It's better to have users annoyed than frustrated as to why their legacy code doesn't work anymore."
A lot of deprication is non-breaking changes, like changing the capitalization of methods. For the stuff that is depreciated with breaking changes you'll already get a notification in that the code will fail.
"And besides, it would be pretty simple to code a checkbox in to my idea that says "Do not show this warning again" or something similar so if users really want to, they can get rid of it."
I suspect that 99% of users would quickly change their setup to have this turned on, to avoid output spam, and thus adding the feature would not have been useful in the first place.
"If deprecation isn't respected, what's the point of deprecating them in the first place?"
There's not really one answer to give to that. Differs on a case by case basis. |
|
|
| Report Abuse |
|
|
|
| 29 Sep 2012 09:31 PM |
@stravant
"I suspect that 99% of users would quickly change their setup to have this turned on, to avoid output spam, and thus adding the feature would not have been useful in the first place."
Leave it enabled by default, then hardcore developers can turn it back on later. ;) |
|
|
| Report Abuse |
|
|
stravant
|
  |
 |
| Joined: 22 Oct 2007 |
| Total Posts: 2893 |
|
|
| 29 Sep 2012 09:38 PM |
"Leave it enabled by default, then hardcore developers can turn it back on later. ;)"
I can't see anyone who would use it ever. The only people that would know about it and go so far as to turn it on are already avaiding depreciated methods. |
|
|
| Report Abuse |
|
|
Ice1377
|
  |
| Joined: 16 Dec 2011 |
| Total Posts: 6432 |
|
|
| 29 Sep 2012 09:52 PM |
Evading*
And uh. Yeah. This seems rather obsolete. |
|
|
| Report Abuse |
|
|
Ice1377
|
  |
| Joined: 16 Dec 2011 |
| Total Posts: 6432 |
|
|
| 29 Sep 2012 09:53 PM |
*Avoiding?
I shouldn't correct people if I have no clue what they really meant. -_-
|
|
|
| Report Abuse |
|
|
stravant
|
  |
 |
| Joined: 22 Oct 2007 |
| Total Posts: 2893 |
|
|
| 29 Sep 2012 10:14 PM |
| Turns out the spell checker was momentarily broken. I'm not used to actually proofreading my posts. (They're usually too long for me to invest the time to proofread them as well as write them) |
|
|
| Report Abuse |
|
|
SN0X
|
  |
| Joined: 24 Oct 2011 |
| Total Posts: 7277 |
|
|
| 30 Sep 2012 10:49 AM |
How about a tool that comes with the objectbrowser?
|
|
|
| Report Abuse |
|
|
|
| 30 Sep 2012 12:52 PM |
"There's too much legacy code out there that the users of can't update themselves. It would just annoy people."
There is this new great thing that someone invented! Its called "settings"! It lets you change if things happen or not!!! |
|
|
| Report Abuse |
|
|
Quenty
|
  |
| Joined: 03 Sep 2009 |
| Total Posts: 9316 |
|
|
| 30 Sep 2012 12:59 PM |
I think ROBLOX should do a XHTML sort of thing... create a secondary standard that is preferable...
|
|
|
| Report Abuse |
|
|
stravant
|
  |
 |
| Joined: 22 Oct 2007 |
| Total Posts: 2893 |
|
|
| 30 Sep 2012 01:22 PM |
"There is this new great thing that someone invented! Its called "settings"! It lets you change if things happen or not!!!"
There's a great principal known as "don't annoy users when you don't have to". If something is still working, 99% of the user base doesn't care if it's "correct" or not as long as it's not broken. |
|
|
| Report Abuse |
|
|
|
| 30 Sep 2012 03:53 PM |
@stravant
I personally don't think it'll be that annoying...because they always have a option to turn it off. |
|
|
| Report Abuse |
|
|
stravant
|
  |
 |
| Joined: 22 Oct 2007 |
| Total Posts: 2893 |
|
|
| 30 Sep 2012 04:05 PM |
"I personally don't think it'll be that annoying...because they always have a option to turn it off."
A already addressed this. Everyone will just end up turning it off (I know I would, why would I want my output spammed when running something I didn't make? And if I did make it it won't have depreciated code in it).
And if everyone ends up turning it off there's no use in wasting development time on it in the first place.
And worse yet, for those who can't turn it off it causes annoyance when trying to use Roblox, which decreases the quality of their experience. |
|
|
| Report Abuse |
|
|