Development news thread (Editor 0.3.1.15, Engine 0.3.1-alpha)

[Veudekato]

oh,miracle . This is best programm i ever seen in SMBX , no more words.

[Christian07]

oh,miracle . This is best programm i ever seen in SMBX , no more words.

Isn't SMBX a program aswell?
Anyways, glad to see PGE out.

[DeuxEx]

Good evening community!
Woshland you did a great job! Great job!
I hope to see the engine as soon as possible!

[Wohlstand]

Middle mouse button features

phpBB [youtube]

Original link: http://www.youtube.com/watch?v=_-Pu0MQKdxE

To enable these features open the [Tools -> Application] settings menu and open the "Editing" tab.
Duplicated items will be placed relative to left-top corner under mouse cursor

[tb1024]

When are you going to start the development of the engine?
Is the engine planned already?

[Wohlstand]

When are you going to start the development of the engine?
Is the engine planned already?

I should to fix some issues in the editor before start engine part. Yes, Engine is planned

[Veudekato]

oh,miracle . This is best programm i ever seen in SMBX , no more words.

Isn't SMBX a program aswell?
Anyways, glad to see PGE out.

i meaning FOR SMBX.

[Mikepjr]

So stop and correct me if i am wrong, but if something is in Beta.. does that not mean it's getting closer to an official release?

[Wohlstand]

So stop and correct me if i am wrong, but if something is in Beta.. does that not mean it's getting closer to an official release?

Yea, Editor is closer to release, but it is part of project. Project version IS NOT application version. because project have multiple applications. First - is an editor, and second - engine part, and third - useful tools

[sky2]

So stop and correct me if i am wrong, but if something is in Beta.. does that not mean it's getting closer to an official release?

I don't know, but first there's some like Test 0.0.0.1 or something. Then it goes to unstable Alpha, and when it acquire many functions it turns into Beta, which is almost final but uncomplete product. When it's about to be released, it's something like "Pre-release" or "Release Candicate". After fixing all bugs, it turns to "Full" or "Release" version. Updates are less often than before, but the game is still being updated adding small things and bugfixes.

Also, Editor is in Beta, but Engine haven't started yet. I think after getting Engine to beta, project will focus on both Editor and Engine.

[Mikepjr]

Ah i see.
I was only curious.

[sky2]

No problem. As now there is editor, Wohlstand and other developers can focus on engine adding new functions, abilities to modify the "game" somehow. (:

[Luigifan2010]

Something else I'm curious about, what exactly do you need to get the OS X version running? I tried running in a VM yesterday under 10.8.3 and it mentioned something about a library not being loaded (QtMultimedia iirc). I tried installing Qt but due to me running a slightly older build of Mountain Lion and not being able to update due to the Vm hacks, it didn't exactly complete correctly.

Also, some of the OS X design guidelines state that all the app's resources should be contained within the bundle. I noticed the Unix compatible executable was in Contents>MacOS, maybe the configs, languages, etc should be placed in there too. It's not like its exactly difficult to get into the app bundle, you can literally just right click on the app, and click "Show Package Contents" and you can modify everything.

[CaptainSwag101]

Yes, when I was building the Mac versions for 0.1 Alpha, I had to place all the configs, data, etc. inside the bundle, inside "Contents/MacOS". However, I left the configs in their original locations for the new Beta build, because the folder organization had been changed. It would be easier to tell the editor where the configs were if you could create a QFilePath which was relative to the bundle instead of the executable, but to do that, you have to set the path to "../../../*Config folders*" to manually look outside of the app bundle. However, changing that would break the Windows version, where there is no app bundle.

It's complicated, but to make a long story short, I didn't move the configs for my 0.2 Beta build because I thought it would break everything.

[Luigifan2010]

I really do think they should be moved back into Contents/MacOS, like I said previously it complies better with the OS X design guidelines and its not difficult to right click>show package contents. If need be, I'll write a step by step tutorial.

Anyways you can have #ifdef's for MacOS probably, are said QFilePath's defined inside the application? If so then yeah, we could go the #ifdef macos method. Or could these be defined in the plist..?

Anyway what do you have to install to just run it? Because I'm still getting an error about a not loaded library, probably because you're not building static.

[Wohlstand]

I really do think they should be moved back into Contents/MacOS, like I said previously it complies better with the OS X design guidelines and its not difficult to right click>show package contents. If need be, I'll write a step by step tutorial.

Anyways you can have #ifdef's for MacOS probably, are said QFilePath's defined inside the application? If so then yeah, we could go the #ifdef macos method. Or could these be defined in the plist..?

Anyway what do you have to install to just run it? Because I'm still getting an error about a not loaded library, probably because you're not building static.

To find config directory I was used QApplication::applicationDirPath() method which return the path to the directory where was placed the executable file.
This finding not only "configs" directory: even data directory for some internal graphics and help directory to open the html help in your browser on the F1.

I think, I will add special modifier which will add into applicationPath call the "/../../../" string which should be defined if OS is MacOS.
And, just in case, will add reChecker which will check REAL placement of folders and will calculate configs path accurately (or together with application, or in the ../../../ dir)

[CaptainSwag101]

I haven't had any issues with running the editor, though that may be because I have Qt Creator, etc. installed already, for the obvious reason of compiling the builds, so perhaps you need to install Qt Creator to run the editor, because there isn't really any way to make redistributable Qt libraries like you can for Windows. Also, what do you mean by "building static"?

And of course, I can re-upload the build with the configs, etc. inside the package contents, although moving the files does have to be done manually every time you need to build a clean version of the editor. I'll have to research on how to use preprocessor commands like #ifdef, I'm not very experienced with them, but hopefully I can set something up in the near future.

[Wohlstand]

Also, what do you mean by "building static"

You shuld to download Qt's source codes, unpack them and build them
http://download.qt-project.org/official_releases/ ... re-opensource-src-5.3.2.tar.gz

For example, commands to build on Linux (remove some trash values and change the prefix - is a target Qt's build path)

Code: Select all

./configure -static -release -nomake examples -nomake tools -prefix /opt/Qt-5.3.1_static -qt-xcb -qt-libpng -qt-libjpeg -qt-zlib -qt-pcre -opensource -confirm-license -opengl -qt-freetype
make
make install


When you build them, you can create config in the Qt Creator for your static build of the Qt.
This means, you can build application which will don't ask you for library if you haven't installed Qt library package

[CaptainSwag101]

Ah, I see. I will do that when building Mac OS versions from now on

[Wohlstand]

Ah, I see. I will do that when building Mac OS versions from now on

Oh, because my PC is too slow (AMD Athlon 64, 2.4 Ghz 1-core), I was built full Qt sources for Windows at 12 hours but my server was built same Qt sources but for Linux at 2.5 hours (Server's CPU is AMD A8, 4-cores, 3.6 Ghz)