[Resolved] Non editable hidden classes

[bedi nik bzez emak]

;D

 

[linkz0r]

Well, there´s no "hidden" in fact. But, i guess you´re talking about the built-in classes right? Those ones are implemented inside the Ruby Interpreter, probably written in C so you can´t change them without recompiling RGSS (impossible thing :D) or overwriting them through scripts.

Here is the list with the main ones:

• Bitmap
• Color
• Font
• Plane
• Rect
• Sprite
• Table
• Tilemap
• Tone
• Viewport
• Window

BTW, any class can be completely rewritten. It´s one of the best things of Ruby. Languages like C++ would not allow  this kind of redefinition.

 

[bedi nik bzez emak]

;D

 

[poccil]

I am aware of one "hidden" class:  TilemapAutotiles, a restricted array which allows Tilemap to have syntax like tilemap.autotiles  

 

[bedi nik bzez emak]

;D

 

[khmp]

p Graphics.private_instance_methods

There are plenty of methods for retrieving everything inside a module or class.

It's an empty array though.  :-\

 

[poccil]

Those are the only ones.  You can get a list of all methods of Graphics using the code:

module Graphics
  class << self
    p self.instance_methods-Module.instance_methods
  end
end

You can also replace Graphics with Input (or any module name) as well.

--- I was too late... ---

 

[bedi nik bzez emak]

;D

 

[poccil]

Perhaps the only low-level classes in RGSS are Graphics, Bitmap, Sprite, and Viewport, and probably Rect, Color, and Tone.  All other classes can be replaced completely, as I, for example,
have done with Window and Tilemap.

By the way, how did you manage to rewrite the Audio module?  Supposedly that module has semantic idiosyncrasies due to the fact that it uses Direct Sound, especially in how it plays BGM and ME.

 

[bedi nik bzez emak]

;D

 

[khmp]

How do you see those hidden methods in Graphics poccil? Which module method did you use?

 

[bedi nik bzez emak]

;D

 

[linkz0r]

People keep making hard changes on RMXP and all... Why not leave RMXP at all with all its limitations and simply make a new engine and embed it into a Ruby interpreter? I know a lot of people here have enough knowledge to do so, like *maybe* you, Arbiter... After the engine is done, making the Editor will be fairly easy :D Also, if done in Ruby, keeping compatibility with RMXP won´t be so difficult at all...

 

[bedi nik bzez emak]

;D