First steps

By
At the beginning I have started to rewrite the basics blocks of the game such as logging system, filesystem management, Library (.slf files) management, Image (Surface) management. The easiest one was the loging management. Log manager uses 3 level of verbosity: full, normal, critical. Critical level is used only for errors logging. Normal level is used for logging the same information as critical level + warnings and some usefull information. When full level is used, everything is logged.

File management was rewritten. boost::filesystem is used for multiplatform file handling.

Image management is done via clanlib. Image (surface) is represented by Texture class. So far ".stci" and ".pcx" image loading is working. And also bitmap Fonts are working.


On the screenshot you can see some text rendered in ja2 with clanlib engine.

The next task is to design classes for game management (game loops, game screens, ...), new image loading support (".pcx", ".png", ".tga"), animation support.

Comments

Post a Comment

Popular posts from this blog

Main menu updates

By
Image
W ell, another "long time no see". I'm still working on the project as much as I can. But it's not a steady work. During summer I was doing some other things (like bike touring) and mostly work. So, what's new? Well the main menu is working. While working on it the need arise for some sort of "mockups" components for various asset and mockup manager. Let me explain why. Because the assets of JA2 are proprietary, it means that you need to extract and build the asset bundles by yourself. Therefor all the assets in the GameObjects needs to be referenced indirectly (because they may not exist yet). This is where mockup come on scene. The mockups are just references to the real assets (like pointers in C++). And when the scene is loaded, the mockup manager primary role is to load the real assets from the mockups. Also, the main menu is implemented using Aspid.MVVM package (MIT licensed). Some other minor changes is custom Script edImporter for .pcx and .st...
Read more

Project reborn

By
W ell, after a long time of inactivity I started to work on this project again. It's been a long time since I touched the project. I've got a lot of other work to do, and also other "spare time" projects to work on. This time, I'll be using Unity engine. So, the basic infrastructure is almost done. At moment I'm working on the UI stuff. The project would be using uGUI (Unity GUI) with some MVVM library. The one big difference from the previous project is, that original JA2 data would be needed only in build time, not in a runtime. There would be editor utils, that will convert the original JA2 data to the format Unity could work with. This means, that every user would need to do this step manually as I don't think it would be legal to distribute it. After the working main menu I would post a github link to the project as I need to also update readme.md so anyone would know where to start.
Read more

Changes to string handling - UTF-8

By Siver. T
So after some time here are some minor updates on project. As first, std::wstring was replaced by std::string (as UTF-8 as default) as it somehow wrong approach to use std::wstring anywhere. For more details see [1], [2], [3]. All std::string now by default hold UTF-8 valid string. As next I will change all projects to use unicode by default and use wide WinApi functions (with help of core::ConvertClass). As second some changes were made in whole game state/screen/handling management. There was added some new classes for init screen handling and so. As usual you could see changes in google code project site. For the near future I'm planning to implement MouseRegion class and the go to GameManager::run(). And happy new year :) [1] - boost.devel thread about strings, UTF-8, ... [2] - boost.devel tread about strings and future [3] - stackoverflow question about UTF-16
Read more