SRL Archive - Reflection Development

New Reflection SVN Rules


Narcle

2009-02-05 16:20:41

The NEW Development SVN is at http://scardevreflection.googlecode.com/svn/trunk/
The stable Reflection SVN is still at http://scarreflection.googlecode.com/svn/trunk/

Please use the Dev SVN as much as you want to commit improvements etc. Improvements that are stable should be noted and will be uploaded on Hook updates.

All MAJOR changes will be discussed in detail on these forums (Reflection Development).

jakeyboy29

2009-02-05 16:42:01

could i ask why? any one done anything wrong?

Torrent of Flame

2009-02-05 17:12:54

Owners, nava2. Ones removed, nava2?


jakeyboy, they was updating the rev's without proper due care and attention, which caused quite a fiasco.

Harry

2009-02-05 17:14:34

Link to the public group .. http://code.google.com/p/scarreflection/

It is so people do not add stuff to Reflection that no one wants, or does not work good, etc.

@ToF: He was removed from the public group, but then added into the Dev group as an admin.

Narcle

2009-02-05 17:17:19

Stable commits will be heavily reviewed before being committed. Some may be re-added to speed up the process depending.

noidea

2009-02-05 19:18:09

When the hooks break. Will there be a quick fix, instead of waiting for a stable "Official" version?

Method

2009-02-05 19:58:08

From: noidea
When the hooks break. Will there be a quick fix, instead of waiting for a stable "Official" version?


Narcle suggested that I add the hooks to the Developer repository, where they can then be tested and moved to the regular repository, so that will probably be how it goes for the next update unless it moves very slowly.

Narcle

2009-02-05 20:16:40

From: Method
Narcle suggested that I add the hooks to the Developer repository, where they can then be tested and moved to the regular repository, so that will probably be how it goes for the next update unless it moves very slowly.


Yep. If its too slow it'll switch to a quick update system for hooks and updates for other stuff will be offset from hooks. We'll try to keep them together but well… we'll see what happens.

NiCbaZ

2009-02-05 20:42:12

Good update, i have been making little commits ( not to many latly ) lots when it started, i will continue you doing this in the furure, and I will never mess up the reflection include, I think the bug updated ( that is fixed now) should have been done lots slower, and talked about lots more.\

Nicbaz.

ZephyrsFury

2009-02-05 20:51:52

From: Narcle
Yep. If its too slow it'll switch to a quick update system for hooks and updates for other stuff will be offset from hooks. We'll try to keep them together but well… we'll see what happens.


We should just add hooks directly to the main svn. Theres not many ways you can make mistakes while adding hooks and even if there are mistakes its not as bad as having outdated hooks which lead to reflection completely failing.

Narcle

2009-02-05 21:42:32

From: ZephyrsFury
We should just add hooks directly to the main svn. Theres not many ways you can make mistakes while adding hooks and even if there are mistakes its not as bad as having outdated hooks which lead to reflection completely failing.


Hooks have never been a issue. Mainly I want to get new functions/updates out when the hooks are updated - reducing the reflection revisions.

ZephyrsFury

2009-02-05 21:55:55

From: Narcle
Hooks have never been a issue. Mainly I want to get new functions/updates out when the hooks are updated - reducing the reflection revisions.


But we should keep everyone waiting on the new hooks especially as they are required for reflection to work. They should be released as soon as possible meaning we commit directly to the pub svn rather than having to "test it" in the dev one.

Narcle

2009-02-05 22:02:43

From: ZephyrsFury
But we should keep everyone waiting on the new hooks especially as they are required for reflection to work. They should be released as soon as possible meaning we commit directly to the pub svn rather than having to "test it" in the dev one.


Well if you have a "test" script it would take 2 mins to test. Technically it doesn't have to be in the Dev first but just a confirmation real quick.

Really I wish we could use a online hook database instead, would be even faster and way less reflection revisions.

lordsaturn

2009-02-06 00:25:04

From: Narcle
Well if you have a "test" script it would take 2 mins to test. Technically it doesn't have to be in the Dev first but just a confirmation real quick.

Really I wish we could use a online hook database instead, would be even faster and way less reflection revisions.


That would be possible, but wouldn't it take a toll on speed if you had to connect to the internet every time you wanted to grab a hook?

Narcle

2009-02-06 01:54:53

From: lordsaturn
That would be possible, but wouldn't it take a toll on speed if you had to connect to the internet every time you wanted to grab a hook?


Not if u grab it once then save it. Then have a separate page that's real small with Runescapes client version (w/e its called) so you know they're up to date. Loading 3 numbers for version check if they don't match then it downloads and saves new hooks to a ini file.

lordsaturn

2009-02-06 02:47:28

From: Narcle
Not if u grab it once then save it. Then have a separate page that's real small with Runescapes client version (w/e its called) so you know they're up to date. Loading 3 numbers for version check if they don't match then it downloads and saves new hooks to a ini file.


So if I understand you correctly, what you're saying is save the hooks online somewhere. When a script runs, check to see if an ini doesnt exist or is outdated, if so, download it from the site. And then use that as your personal hooks file?

NiCbaZ

2009-02-06 02:52:18

I like this idea, like Worlds.Ini…. wow if methods willing, he could try and make a browser based hook getter.. and it would update by auto..

But for now i think we should just , download the ini file going, that would be great as we would not have to commit a pubic revition each time hooks update.

Narcle

2009-02-06 12:16:03

From: lordsaturn
So if I understand you correctly, what you're saying is save the hooks online somewhere. When a script runs, check to see if an ini doesnt exist or is outdated, if so, download it from the site. And then use that as your personal hooks file?


You don't look for the ini first because in scar you have to load the whole page. So load a Runescape version check that's one page and has the version number (3 numbers e.g. 543) so its a instant load even on dial-up connection. Now if the version isn't the same as yours THEN it updates from the ini page.

I would have to talk to Method in detail and figure out a stable website etc. It was tried before but was scraped for a reason I'm unaware of.

Nava2

2009-02-06 16:33:26

Frankly, a SetupReflection could do this quite easily. Load all the hooks into a TStringArray, and then place them into the correct constants. This would make updating the hooks easy.

But, this would take some work, as well as make the hooks Vars now instead of constants.

Also, as lordsaturn stated, speed would be effected, but only on start up. I'd be willing to set this up, with some help. :)

E: A simple RSBuild Check would make sure the hooks are only updated when they need to be.

Boreas

2009-02-06 18:34:14

From: NiCbaZ
wow if methods willing, he could try and make a browser based hook getter.. and it would update by auto..


If you mean something that gets new hooks automatically without a human checking them first, then no thats a bad idea.

Widget

2009-02-06 20:35:28

From: Nava2
Frankly, a SetupReflection could do this quite easily. Load all the hooks into a TStringArray, and then place them into the correct constants. This would make updating the hooks easy.


Look around rev ~20, we tried and it failed horribly.
From: Changelog
8-08-08 Widget:
- Reverting Hooks.scar back to constants. Ini file will no longer be used.
- LoadHooks/SetupReflection is no longer needed (for now)

Who really cares about the number of revision updates? Update hooks right away, and major updates whenever. When people update hooks the next time or a script doesn't work, they'll have the new reflection. Update-checking is silly unless someone wants to write a plugin.


Edit:
From: Nava2
For the record, remove Widget too. He isn't a dev. Nor is he worthy.

That's like saying WT-Fakawi shouldn't be allowed to change SRL because he doesn't do all that much anymore, look toward the bottom of the changelog, you just weren't around ;) (/feels like an old man)

Ededitit: For the record, is reflection considered "stable" yet? I've always thought of it as beta once it went public since it wasn't guaranteed that your scripts wouldn't break since we had a million new features to add back then, but it seems we have most stuff now.

NiCbaZ

2009-02-10 23:46:14

Originally Posted by Nava2 View Post
For the record, remove Widget too. He isn't a dev. Nor is he worthy.


WTF? Widget got this going, he wrote all the NPC and player stuff, and helped lots of people in development?

Kyle Undefined

2009-02-11 09:22:36

Nice. Wish I could help out with this, but I'm still getting use to reflection :p

~Camo

Nava2

2009-02-12 09:10:21

From: NiCbaZ
WTF? Widget got this going, he wrote all the NPC and player stuff, and helped lots of people in development?


Context my friend, context.

:)

I know he did that. ;)

But on that same note, although this is all done and over with. All of us moving on, did you also know that I wrote almost all of the Inventory stuff, the bank stuff, and a bunch of smaller stuff? :)

I was on a rage =/

E: I also already talked to Widget bout this.