Original Jake's design was based on the fixed set of predefined layouts for different page sizes. I completely changed the layout of the page. What is it? There should be a key press (space bar, originally) which should drop a current tetromino to the bottom, where it still can be moved, if there is a room for that. Unfortunately, the lack of this feature is typical for most of the implementations I saw. I mentioned the lack of the feature which rendered the implementation of the game not playable. Even playing on the board of the size of some 100 x 100 blocks became quite possible (but, by the way, really irritating :-)). So, first of all, it allows to easily customize things which were totally rigid in the original work, first of all, the size of the game in blocks can be modified in reasonable limits. Instead, I designed the separation of the settings objects places in a separate file "settings.js", introduced a separate constructor with prototype methods representing Tetromino elements and other structural elements formally expressed as a set of separate JavaScript objects, such as simple FSM and layout.
FALLING BLOCKS BLENDER CODE
I did not follow the original code design with the further decomposition of the game into such parts as "constants", "variable", "logics" and so on. But I liked the basics of the solution and really wanted to fix it all, to create a really operational and well maintained product. The original Jake's work was incomplete, but some initial design feature already led the development in wrong direction, and the lack of at least one feature made the game not really playable. I re-wrote nearly 100% of the code from scratch, but I used all the low-level algorithms developed by Jake and followed most of his algorithmic ideas, as well as the general design of the application, decomposition into major blocks: basic helper methods, game with its event queue, rendering with invalidation mechanism and main application. This is the original work by Jake Gordon which caught my attention: But how can it be a problem if you have a neat source code? So I decided to rewrite it from scratch. This was mostly due to the lack of flexibility already put in the initial design and lack of important features. At the same time, it wasn't yet playable and the quality of code did not satisfy me at the level of its general design, despite of its clarity and general correctness. It was apparent that the incomplete work I found was written by quite a qualified author. So, when I, just be some chance, came across such implementation, I was much pleased. It does not require anything except a browser, should work on all platforms and always comes with source code. First of all, I would not risk anything without open source, but what I saw wasn't really playable, due to the lack of most important features and proper look and feel, making no match with the old-time implementations for DOS.Īt the same time, HTML with JavaScript using new HTML (HTML5) canvas element is the most attractive platform for simple games. No, I'm not a gamer and did not see much.
Unfortunately, I haven't seen a really playable implementation of the game for a long time. I cannot say I never tried anything in the field of pure entertainment before, but, again, nothing worth mentioning.įalling Blocks is a legendary game with unique combination of extreme simplicity and attractiveness. This is my very first complete work on JavaScript, not counting something totally trivial. Inner Functions and Event Handling: Passing "this".
FALLING BLOCKS BLENDER DOWNLOAD
0 kommentar(er)
