OGS-Main
/
ogs-site
2
0
複製 0
程式碼 問題 0 合併請求 0 版本發佈 0 Wiki 活動
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
54 提交
2 分支
123MB
目錄樹: ebb11bb49c
分支列表 標籤
${ item.name }
建立分支 ${ searchTerm }
從 'ebb11bb49c'
${ noResults }
ogs-site/feeds/news.atom.xml

258 line
38KB
原始文件 Blame 歷史記錄 

  1. <?xml version="1.0" encoding="utf-8"?>

  2. <feed xmlns="http://www.w3.org/2005/Atom"><title>Opensource Game Studio</title><link href="http://opengamestudio.org/" rel="alternate"></link><link href="http://opengamestudio.org/feeds/news.atom.xml" rel="self"></link><id>http://opengamestudio.org/</id><updated>2017-11-22T00:00:00+03:00</updated><entry><title>2017 summary</title><link href="http://opengamestudio.org/2017-summary.html" rel="alternate"></link><updated>2017-11-22T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-11-22:2017-summary.html</id><summary type="html">&lt;p&gt;&lt;img alt="Screenshot" src="http://opengamestudio.org/2017-11-22-2017-summary.png" /&gt;&lt;/p&gt;

  3. &lt;p&gt;It's time to step back to see our accomplishments in 2017 and how they connect to the overall goal of Opensource Game Studio project.&lt;/p&gt;

  4. &lt;p&gt;&lt;strong&gt;Brief history&lt;/strong&gt;&lt;/p&gt;

  5. &lt;p&gt;Opensource Game Studio project is 12 years old now.&lt;/p&gt;

  6. &lt;p&gt;&lt;strong&gt;2005.&lt;/strong&gt; We started the project with a &lt;a href="https://www.linuxquestions.org/questions/general-10/the-creation-of-the-best-rpg-355858/"&gt;fanatic call&lt;/a&gt; to create the best game ever. Probably right after finishing Half-Life 2 or Morrowind. 99.99% of those who wanted to participate weathered during a couple of years leaving only the two of us: Michael (coding) and Ivan (the rest).

  7. The project was in a constant turmoil because we had no clear purpose and discipline. Thus, we only got a handful of demonstrations during that period.&lt;/p&gt;

  8. &lt;p&gt;&lt;strong&gt;2010.&lt;/strong&gt; The first year for us to admit we failed big time. After accepting the failure, we have set Mahjong game as our initial target. We also realized that if we want the game out, we must work every day. We didn't get anywhere by working on weekends because they often collided with family time.&lt;/p&gt;

  9. &lt;p&gt;&lt;strong&gt;2012, 2013.&lt;/strong&gt; We released Mahjong 1.0 and Mahjong 1.1 correspondingly. We created a complete, polished game in 3-4 years after failing to provide anything of value during previous 5 years. To this date, Mahjong is the best and only game we released so far. We're still proud of it because it still feels great.&lt;/p&gt;

  10. &lt;p&gt;&lt;strong&gt;2015.&lt;/strong&gt; We showcased the first version of our game toolset. After releasing Mahjong, we decided to spend time on building toolset that would allow us to develop games faster.&lt;/p&gt;

  11. &lt;p&gt;&lt;strong&gt;2016.&lt;/strong&gt; We recreated Mahjong gameplay with our game toolset. However, we quickly realized that desktop only game toolset is a dead end. It led us to research mobile platforms.&lt;/p&gt;

  12. &lt;p&gt;&lt;strong&gt;Last year&lt;/strong&gt;&lt;/p&gt;

  13. &lt;p&gt;&lt;strong&gt;2016, October.&lt;/strong&gt; We started mobile platforms' research by making simple straightforward  OpenSceneGraph application run under Android.&lt;/p&gt;

  14. &lt;p&gt;&lt;strong&gt;2017, January.&lt;/strong&gt; We got the Android version working and started iOS and Web research.&lt;/p&gt;

  15. &lt;p&gt;&lt;strong&gt;2017, February.&lt;/strong&gt; We made the sample application work everywhere: desktop, mobile, web.&lt;/p&gt;

  16. &lt;p&gt;Researching mobile and web took us about five months. We spent that much time because there was no documentation on how to run OpenSceneGraph across platforms. We had to step in and create said documentation.&lt;/p&gt;

  17. &lt;p&gt;&lt;strong&gt;2017, July.&lt;/strong&gt; We published &lt;a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide"&gt;OpenSceneGraph cross-platform guide&lt;/a&gt;, which describes how to create a simple OpenSceneGraph application and make it run on desktop, mobile, and web. To this date, this is our most popular GitHub repository.&lt;/p&gt;

  18. &lt;p&gt;&lt;strong&gt;2017, November.&lt;/strong&gt; We published simple &lt;a href="https://ogstudio.github.io/game-memory-colors/tutorial-5.3/mjin-player.html"&gt;Memory: Colors game&lt;/a&gt; and the &lt;a href="https://bitbucket.org/ogstudio-games/memory-colors"&gt;guide&lt;/a&gt; on how to create the game from scratch. The game is powered by MJIN, our new cross-platform game toolset that we started this summer.&lt;/p&gt;

  19. &lt;p&gt;Currently MJIN toolset is in its infancy. MJIN needs a real game to flourish. That's why we are already working on cross-platform Mahjong. We'll do our best to make Mahjong faster this time.&lt;/p&gt;</summary></entry><entry><title>Back to the Static</title><link href="http://opengamestudio.org/back-to-the-static.html" rel="alternate"></link><updated>2017-10-16T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-10-16:back-to-the-static.html</id><summary type="html">&lt;p&gt;&lt;img alt="Back to the Static" src="http://opengamestudio.org/2017-10-16-back-to-the-static.png" /&gt;&lt;/p&gt;

  20. &lt;p&gt;We have been using Wordpress as our website engine for more than seven years. And now it's time to move forward. Or backward.

  21. For some time we've been tracking the development of the new breed of website engines - static site generators.

  22. It seems that this is the technology capable of changing past into future.&lt;/p&gt;

  23. &lt;p&gt;A static website is more straightforward, quicker and more secure. And with the help of generators, it is also as easy to manage, as the dynamic website.

  24. So, we are starting our site anew with the help of the &lt;a href="https://blog.getpelican.com/"&gt;Pelican&lt;/a&gt;.

  25. Right now it doesn't have all the content from our old site, but we'll add most of it soon.&lt;/p&gt;</summary></entry><entry><title>The birth of MJIN world</title><link href="http://opengamestudio.org/mjin-world-birth.html" rel="alternate"></link><updated>2017-09-10T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-09-10:mjin-world-birth.html</id><summary type="html">&lt;p&gt;&lt;img alt="The birth of MJIN world" src="http://opengamestudio.org/2017-09-mjin-world-birth.png" /&gt;&lt;/p&gt;

  26. &lt;p&gt;This article describes the birth of MJIN world in August 2017.&lt;/p&gt;

  27. &lt;p&gt;&lt;strong&gt;mjin-player&lt;/strong&gt;&lt;/p&gt;

  28. &lt;p&gt;As you know, &lt;a href="http://opengamestudio.org/scripting-research.html"&gt;we spent July to research scripting&lt;/a&gt;. We found a solution that satisfies the following criteria. Scripts should:&lt;/p&gt;

  29. &lt;ol&gt;

  30. &lt;li&gt;run unchanged on all supported platforms&lt;/li&gt;

  31. &lt;li&gt;allow extending C++ code&lt;/li&gt;

  32. &lt;/ol&gt;

  33. &lt;p&gt;We have verified the second criterion by writing a sample application. The first criterion was taken for granted because it SHOULD be true.&lt;/p&gt;

  34. &lt;p&gt;At the time, we saw two ways to verify the first criterion:&lt;/p&gt;

  35. &lt;ol&gt;

  36. &lt;li&gt;create one sample application for each platform to verify scripting only&lt;/li&gt;

  37. &lt;li&gt;create a single cross-platform application, which can run any code&lt;/li&gt;

  38. &lt;/ol&gt;

  39. &lt;p&gt;We chose the second approach because it is more beneficial in the long run. As you might have guessed, &lt;a href="https://bitbucket.org/ogstudio/mjin-player"&gt;mjin-player&lt;/a&gt; is that application.&lt;/p&gt;

  40. &lt;p&gt;mjin-player serves as a base for the rest of MJIN projects to make them run on all supported platforms. However, there's no magic trick to hide the projects from the platform, and there was no such intention. Instead, mjin-player provides a consistent set of rules how other MJIN projects should be structured to be able to run on all supported platforms.&lt;/p&gt;

  41. &lt;p&gt;&lt;strong&gt;mjin-application&lt;/strong&gt;&lt;/p&gt;

  42. &lt;p&gt;This set of rules for MJIN projects is packaged into &lt;a href="https://bitbucket.org/ogstudio/mjin-application"&gt;mjin-application&lt;/a&gt;. mjin-application is a library that provides basic functionality every MJIN project would need and nothing more. For instance, mjin-application does not and will not contain scripting or any other specific functionality.&lt;/p&gt;

  43. &lt;p&gt;&lt;strong&gt;MJIN world&lt;/strong&gt;&lt;/p&gt;

  44. &lt;p&gt;So what is &lt;a href="https://bitbucket.org/ogstudio/mjin"&gt;MJIN world&lt;/a&gt;? It's a set of projects that constitute our game development tools. mjin-player and mjin-application are the first bricks of the newly born MJIN world. A lot more to come. Stay tuned for the brighter MJIN future.&lt;/p&gt;

  45. &lt;p&gt;That's it for describing the birth of MJIN world in August 2017.&lt;/p&gt;</summary></entry><entry><title>Scripting research</title><link href="http://opengamestudio.org/scripting-research.html" rel="alternate"></link><updated>2017-08-16T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-08-16:scripting-research.html</id><summary type="html">&lt;p&gt;&lt;img alt="Scripting research" src="http://opengamestudio.org/2017-08-scripting-research.png" /&gt;&lt;/p&gt;

  46. &lt;p&gt;This article describes scripting research in July 2017.&lt;/p&gt;

  47. &lt;p&gt;&lt;strong&gt;Our first goal of using a scripting language was to have a platform-independent code that runs unchanged on every supported platform.&lt;/strong&gt;&lt;/p&gt;

  48. &lt;p&gt;OGS Editor 0.10 supports Python for such a code thanks to &lt;a href="http://swig.org/"&gt;SWIG&lt;/a&gt;. SWIG provides a way to wrap almost any C/C++ code and use it in dozens of languages like Python, Ruby, Lua, Java, C#, etc.. SWIG really helped us taste the beauty of platform-independent code. However, SWIG only works one way: from C/C++ to a target language. This means the main application must be in the target language, and C/C++ code can only be used as a library.&lt;/p&gt;

  49. &lt;p&gt;Having the main application in Python works fine for the desktop, but not so great for mobile and web, where C and C++ are the only natively supported cross-platform languages. There are projects like &lt;a href="https://kivy.org"&gt;Kivy&lt;/a&gt;, which allow you to develop cross-platform applications in Python, but they are not supported natively. This means it's a lot of headaches when Android and iOS APIs change.&lt;/p&gt;

  50. &lt;p&gt;Having the main application in C/C++ and the need to support scripting means that a scripting language should be interpreted by the application. This is what SWIG, Kivy, and similar projects are not meant to fulfill.&lt;/p&gt;

  51. &lt;p&gt;&lt;strong&gt;Our secondary goal for using a scripting language was to allow to extend C++ code.&lt;/strong&gt;&lt;/p&gt;

  52. &lt;p&gt;OGS Editor 0.10 has some modules written in C++, and some in Python. The modules are equal from the perspective of the main application; it doesn't care what language the module is written in.&lt;/p&gt;

  53. &lt;p&gt;To achieve such flexibility, we introduced a so-called Environment. Each module would register the keys it responds to, and Environment would deliver corresponding messages. 

  54. Technically such behaviour is achieved by inheriting a base class and overriding its methods in both C++ and a scripting language.&lt;/p&gt;

  55. &lt;p&gt;&lt;strong&gt;First, we evaluated Python for the role of cross-platform scripting language.&lt;/strong&gt;&lt;/p&gt;

  56. &lt;p&gt;Since we already used Python, we started to research the possibility to run Python code on every supported platform. The result was disappointing because CPython (the default Python implementation used on the desktop) does not mention mobile and web platforms. We only found some years old forks of CPython that were claimed to work either on Android or iOS. Such a disarray was not suitable for us.

  57. We also had a look at &lt;a href="http://pypy.org"&gt;PyPy&lt;/a&gt;, another Python implementation. It also did not mention support for mobile and web platforms.&lt;/p&gt;

  58. &lt;p&gt;This was a clear indication that Python community doesn't care for mobile and web platforms. Or that nobody had time to provide the information about building Python on such platforms. Either way, it was not acceptable for us.&lt;/p&gt;

  59. &lt;p&gt;&lt;strong&gt;Second, we evaluated &lt;a href="http://wren.io"&gt;Wren&lt;/a&gt; for the role of cross-platform scripting language.&lt;/strong&gt;&lt;/p&gt;

  60. &lt;p&gt;Wren was the first scripting language we stumbled upon in the long list of non-mainstream scripting languages.&lt;/p&gt;

  61. &lt;p&gt;Wren claimed to be small and easy to learn. Wren also claimed to be intended for embedding in applications. Ironically, the author &lt;a href="http://wren.io/embedding-api.html"&gt;had no time to document how to do the embedding in the first place&lt;/a&gt;. When &lt;a href="https://github.com/munificent/wren/issues/465"&gt;we asked for the time estimates of publishing&lt;/a&gt; the critical part of the documentation, &lt;a href="https://github.com/munificent/wren/issues/402"&gt;we just got a reference to another issue&lt;/a&gt; where the other guy was asking the same question half a year ago!&lt;/p&gt;

  62. &lt;p&gt;That's when we ended our relationship with Wren.&lt;/p&gt;

  63. &lt;p&gt;&lt;strong&gt;Third, we evaluated &lt;a href="http://chaiscript.com"&gt;Chai&lt;/a&gt; for the role of cross-platform scripting language.&lt;/strong&gt;&lt;/p&gt;

  64. &lt;p&gt;Chai was in the long list of non-mainstream scripting languages, too. Chai was promising because it claimed to be specifically tailored for embedding in a C++ application.

  65. We successfully managed to call a C++ function from inside Chai but failed to call a member function. &lt;a href="http://discourse.chaiscript.com/t/cannot-call-a-function-that-accepts-a-string-and-a-vector/334"&gt;We asked for help&lt;/a&gt;, but nobody replied.&lt;/p&gt;

  66. &lt;p&gt;We had to end our relationship with Chai.&lt;/p&gt;

  67. &lt;p&gt;&lt;strong&gt;Fourth, we evaluated Lua for the role of cross-platform scripting language.&lt;/strong&gt;&lt;/p&gt;

  68. &lt;p&gt;Lua is the mainstream language for embedding. So we decided to try the obvious choice. Documentation looked promising, too. However, by the end of reading the &lt;a href="https://www.lua.org/pil/24.html"&gt;C API&lt;/a&gt; chapter we had no clue how to inherit a class inside Lua.&lt;/p&gt;

  69. &lt;p&gt;This led us to search for libraries that wrap Lua C API syntax into something more meaningful for C++. That's how we found &lt;a href="http://sol2.rtfd.io"&gt;Sol2&lt;/a&gt;. Just as before, the first attempt to call a C++ member function from Lua failed. But unlike before, we asked for help and &lt;a href="https://github.com/ThePhD/sol2/issues/465"&gt;got the help&lt;/a&gt;! This was a refreshing surprise for us.

  70. Next, we tried to inherit a class in Lua and override the class methods. We failed, but &lt;a href="https://github.com/ThePhD/sol2/issues/468"&gt;the author helped us out again&lt;/a&gt;. In the end, we succeeded in inheriting a class and overriding its behaviour.&lt;/p&gt;

  71. &lt;p&gt;That's when we understood it's a start for a long and mutual relationship with Sol2/Lua.&lt;/p&gt;

  72. &lt;p&gt;&lt;strong&gt;This search for a scripting language taught us one important lesson: people matter, not technologies.&lt;/strong&gt;&lt;/p&gt;

  73. &lt;p&gt;There are lots of scripting languages that look shiny on the outside but are dead. Why? Because some authors don't have time for users. In return, users don't have time for the authors' projects.&lt;/p&gt;

  74. &lt;p&gt;That's it for describing scripting research in July 2017.&lt;/p&gt;</summary></entry><entry><title>OpenSceneGraph cross-platform guide</title><link href="http://opengamestudio.org/openscenegraph-cross-platform-guide.html" rel="alternate"></link><updated>2017-07-17T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-07-17:openscenegraph-cross-platform-guide.html</id><summary type="html">&lt;p&gt;&lt;img alt="OpenSceneGraph guide" src="http://opengamestudio.org/2017-07-openscenegraph-guide.png" /&gt;&lt;/p&gt;

  75. &lt;p&gt;This article summarizes the work we did to produce OpenSceneGraph cross-platform guide.&lt;/p&gt;

  76. &lt;p&gt;June marked the finish of &lt;a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide"&gt;OpenSceneGraph cross-platform guide&lt;/a&gt; with the publishing of the last (initially planned) tutorial. The tutorial describes &lt;a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide/tree/master/1.10.SampleWeb"&gt;how to build and run sample OpenSceneGraph application in Web&lt;/a&gt; using Emscripten.

  77. In case you missed it, here's a &lt;a href="https://ogstudio.github.io/openscenegraph-cross-platform-guide/"&gt;link to the final application&lt;/a&gt;. Open it in your web browser.&lt;/p&gt;

  78. &lt;p&gt;We started to compose the guide in February when we successfully managed to render a simple model on mobile and web.

  79. We spent 120 hours in five months to produce ten tutorials of the guide.&lt;/p&gt;

  80. &lt;p&gt;We have been doing OpenSceneGraph cross-platform guide for two main reasons:&lt;/p&gt;

  81. &lt;ol&gt;

  82. &lt;li&gt;Keep OpenSceneGraph cross-platform knowledge in easily accessible and reproducible form&lt;/li&gt;

  83. &lt;li&gt;Share the knowledge with OpenSceneGraph community to make it stronger&lt;/li&gt;

  84. &lt;/ol&gt;

  85. &lt;p&gt;We believe we succeeded in both. Here's why:&lt;/p&gt;

  86. &lt;ol&gt;

  87. &lt;li&gt;The guide repository has more &lt;a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide/stargazers"&gt;stars&lt;/a&gt; (aka "likes") than any other repository of ours&lt;/li&gt;

  88. &lt;li&gt;OpenSceneGraph project leader Robert Osfield said &lt;a href="http://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg74815.html"&gt;"Great work"&lt;/a&gt;, which means a lot&lt;/li&gt;

  89. &lt;li&gt;The guide already has &lt;a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide/issues"&gt;two issues&lt;/a&gt;&lt;/li&gt;

  90. &lt;/ol&gt;

  91. &lt;p&gt;Reaching our goal of researching OpenSceneGraph cross-platform development and providing the knowledge back to the community just made us happier.&lt;/p&gt;

  92. &lt;p&gt;However, our journey does not stop here. Using the knowledge of the guide, we now continue to work on bringing our tools to support mobile and web, just as we &lt;a href="http://opengamestudio.org/lang/en/news/2456"&gt;promised in January&lt;/a&gt;.&lt;/p&gt;

  93. &lt;p&gt;That's it for summarizing the work we did to produce OpenSceneGraph cross-platform guide.&lt;/p&gt;</summary></entry><entry><title>iOS tutorial</title><link href="http://opengamestudio.org/ios-tutorial.html" rel="alternate"></link><updated>2017-06-08T10:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-06-08:ios-tutorial.html</id><summary type="html">&lt;p&gt;&lt;img alt="iOS tutorial" src="http://opengamestudio.org/2017-06-08-ios-refactoring.png" /&gt;&lt;/p&gt;

  94. &lt;p&gt;This article describes problems we faced during the creation of iOS tutorial in May 2017.&lt;/p&gt;

  95. &lt;p&gt;&lt;a href="https://twitter.com/OpenGameStudio/status/826816343433498627"&gt;This February&lt;/a&gt; we managed to get simple model rendered under iOS in just a few days. We expected to finish iOS tutorial in no time. However, the reality reminded us: it's easy to come up with a hackish demo that works for one person, but it's hard to create a concise example that works for everyone.&lt;/p&gt;

  96. &lt;h3&gt;Native library&lt;/h3&gt;

  97. &lt;p&gt;The first question we had to answer was: should the sample application be part of Xcode project or be a separately built library?&lt;/p&gt;

  98. &lt;p&gt;We had to consider the following facts:&lt;/p&gt;

  99. &lt;ol&gt;

  100. &lt;li&gt;Xcode project can use C++ directly (thanks to Objective-C++) without stuff like JNI&lt;ul&gt;

  101. &lt;li&gt;There's no need for a separate library (+ application)&lt;/li&gt;

  102. &lt;li&gt;Creating a separate library is an additional work (- library)&lt;/li&gt;

  103. &lt;/ul&gt;

  104. &lt;/li&gt;

  105. &lt;li&gt;OpenSceneGraph builds libraries&lt;ul&gt;

  106. &lt;li&gt;It's easier to use standard build process (+ library)&lt;/li&gt;

  107. &lt;li&gt;It's harder to create custom build process just for a single platform (- application)&lt;/li&gt;

  108. &lt;/ul&gt;

  109. &lt;/li&gt;

  110. &lt;li&gt;OpenSceneGraph uses CMake build system, which is not supported by Xcode&lt;ul&gt;

  111. &lt;li&gt;Xcode project can't include CMake files (- application)&lt;/li&gt;

  112. &lt;li&gt;It's easy to create custom CMake file that includes OpenSceneGraph CMake file to build a single library (+ library)&lt;/li&gt;

  113. &lt;/ul&gt;

  114. &lt;/li&gt;

  115. &lt;li&gt;CMake can generate Xcode project&lt;ul&gt;

  116. &lt;li&gt;It's possible to create a CMake file that builds both OpenSceneGraph and the sample application (+ application)&lt;/li&gt;

  117. &lt;li&gt;Xcode is the de-facto tool to create Xcode projects; it's easier to use standard build process (+ library)&lt;/li&gt;

  118. &lt;/ul&gt;

  119. &lt;/li&gt;

  120. &lt;/ol&gt;

  121. &lt;p&gt;After evaluating the pros and cons of each approach, we decided to turn the sample application into a library and include it in Xcode project. The downside of this approach is that simulator and real device builds need separate library builds.&lt;/p&gt;

  122. &lt;h3&gt;Refactoring&lt;/h3&gt;

  123. &lt;p&gt;The second question we had to answer was: should there be a single source code base for all platforms or several ones, one for each platform?&lt;/p&gt;

  124. &lt;p&gt;While doing Android tutorial we used single source code base because it worked fine for desktop and Android. As we started to work through iOS tutorial, it became apparent that particular features may or may not work on some platforms. For example, one feature may work on desktop and iOS, but not Android. Another feature may work on iOS and Android, but not desktop. Since we didn't want to pollute the code with #ifdefs, we started to put each platform combination into a separate file. The number of files grew rapidly. The files were reusable, but it became extremely hard to see the whole picture.&lt;/p&gt;

  125. &lt;p&gt;At this point, we realized there's the second question. We reminded ourselves that the main purpose of the sample source code is to teach how to do basic OpenSceneGraph things, not create a reusable library with API that is stable across several years.&lt;/p&gt;

  126. &lt;p&gt;That's when our home grown feature tool came into play. With its help, we separated the code into several parts, which in the end produce just two files for each platform:&lt;/p&gt;

  127. &lt;ol&gt;

  128. &lt;li&gt;functions.h - contains reusable classless functions&lt;/li&gt;

  129. &lt;li&gt;main.h - contains the rest of the sample application code&lt;/li&gt;

  130. &lt;/ol&gt;

  131. &lt;p&gt;Their contents differ slightly for each platform, but it's easy to see the whole picture now.&lt;/p&gt;

  132. &lt;p&gt;That's it for describing problems we faced during the creation of iOS tutorial in May 2017.&lt;/p&gt;</summary></entry><entry><title>OpenSceneGraph sample</title><link href="http://opengamestudio.org/osg-sample.html" rel="alternate"></link><updated>2017-05-12T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-05-12:osg-sample.html</id><summary type="html">&lt;p&gt;&lt;img alt="OSG sample" src="http://opengamestudio.org/2017-05_osg-sample.png" /&gt;&lt;/p&gt;

  133. &lt;p&gt;This article describes creation of the tutorials for building sample OpenSceneGraph application under Linux, macOS, Windows, and Android in April 2017.&lt;/p&gt;

  134. &lt;p&gt;Previous tutorials described how to install OpenSceneGraph under Linux, macOS, Windows and render a model using the standard &lt;strong&gt;osgviewer&lt;/strong&gt; tool. This time we worked on a &lt;a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide-application"&gt;sample OpenSceneGraph application&lt;/a&gt; that would run under Linux, macOS, Windows, and Android.&lt;/p&gt;

  135. &lt;p&gt;The application is very basic and has the following features:&lt;/p&gt;

  136. &lt;ol&gt;

  137. &lt;li&gt;Render window creation&lt;/li&gt;

  138. &lt;li&gt;Model loading&lt;/li&gt;

  139. &lt;li&gt;Model rendering with simple GLSL shaders&lt;/li&gt;

  140. &lt;li&gt;Model motion with a mouse under Linux, macOS, Windows and a finger under Android&lt;/li&gt;

  141. &lt;/ol&gt;

  142. &lt;p&gt;Creating the tutorials for Linux, macOS, Windows was so easy and straightforward, that it only took us half a month. We spent the second half of the month creating Android tutorial.&lt;/p&gt;

  143. &lt;p&gt;Our &lt;a href="http://www.opengame.epizy.com/lang/en/news/2414"&gt;first successful Android build&lt;/a&gt; last year included hacks and non-obvious steps to make OpenSceneGraph run under Android. This time we wanted a cleaner, faster, and cheaper approach.&lt;/p&gt;

  144. &lt;p&gt;The approach we ended up with requires just a few files and a few changes to the original Android Studio project (with C++ support) to make sample OpenSceneGraph application run under Android.&lt;/p&gt;

  145. &lt;p&gt;Here's a quick rundown of the files:&lt;/p&gt;

  146. &lt;ol&gt;

  147. &lt;li&gt;GLES2 surface&lt;/li&gt;

  148. &lt;li&gt;Render activity to render to the surface&lt;/li&gt;

  149. &lt;li&gt;Native library Java interface&lt;/li&gt;

  150. &lt;li&gt;Native library C++ implementation&lt;/li&gt;

  151. &lt;li&gt;CMake file to build native library&lt;/li&gt;

  152. &lt;li&gt;Render activity layout&lt;/li&gt;

  153. &lt;li&gt;Model to display&lt;/li&gt;

  154. &lt;/ol&gt;

  155. &lt;p&gt;Here's a quick rundown of the project changes:&lt;/p&gt;

  156. &lt;ol&gt;

  157. &lt;li&gt;Update Android manifest to use GLES2 and render activity&lt;/li&gt;

  158. &lt;li&gt;Reference native library's CMake file in the project's CMake file&lt;/li&gt;

  159. &lt;/ol&gt;

  160. &lt;p&gt;OpenSceneGraph documentation suggests building OpenSceneGraph outside Android Studio with CMake. However, this approach has the following limitations:&lt;/p&gt;

  161. &lt;ol&gt;

  162. &lt;li&gt;You have to build OpenSceneGraph for each target architecture&lt;/li&gt;

  163. &lt;li&gt;You have to manually copy/reference built OpenSceneGraph libraries into Android Studio project&lt;/li&gt;

  164. &lt;/ol&gt;

  165. &lt;p&gt;Our approach includes building OpenSceneGraph for those target architectures that Android Studio project is built for. Also, OpenSceneGraph is already referenced, so no extra work is required: you just need to rebuild the project, and you're done.&lt;/p&gt;

  166. &lt;p&gt;That's it for describing the creation of the tutorials for building sample OpenSceneGraph application under Linux, macOS, Windows, and Android in April 2017.&lt;/p&gt;</summary></entry><entry><title>It's all fine</title><link href="http://opengamestudio.org/its-all-fine.html" rel="alternate"></link><updated>2017-04-07T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-04-07:its-all-fine.html</id><summary type="html">&lt;p&gt;&lt;img alt="ItsAllFine" src="http://opengamestudio.org/2017-04_its-all-fine.png" /&gt;&lt;/p&gt;

  167. &lt;p&gt;This article describes creation of the first four OpenSceneGraph tutorials in March 2017.&lt;/p&gt;

  168. &lt;p&gt;The &lt;a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide/"&gt;first four OpenSceneGraph tutorials&lt;/a&gt; explain how to create a cube model with Blender and display the model under Linux, macOS, or Windows using OpenSceneGraph tool called osgviewer.&lt;/p&gt;

  169. &lt;p&gt;The whole process of creating a single tutorial turned out to be pretty daunting because it includes several tasks:&lt;/p&gt;

  170. &lt;ol&gt;

  171. &lt;li&gt;Record original video depicting one or more steps&lt;/li&gt;

  172. &lt;li&gt;Name the steps as clear as possible&lt;/li&gt;

  173. &lt;li&gt;Select the parts of the video that display the step&lt;/li&gt;

  174. &lt;li&gt;Remove the parts of the video that bare no value, e.g., waiting in the middle of compilation&lt;/li&gt;

  175. &lt;li&gt;Select a single frame to best represent current step, e.g., typing a specific command&lt;/li&gt;

  176. &lt;li&gt;Add a detailed description to article, why current step should have been taken&lt;/li&gt;

  177. &lt;li&gt;Proof-read the article&lt;/li&gt;

  178. &lt;li&gt;Correct typos and video timing&lt;/li&gt;

  179. &lt;li&gt;Review the whole video&lt;/li&gt;

  180. &lt;li&gt;Upload the video to YouTube with timestamps of steps for easier navigation&lt;/li&gt;

  181. &lt;/ol&gt;

  182. &lt;p&gt;Some of those tasks had to be repeated multiple times until the combination of video, text, and article was clear and logical.&lt;/p&gt;

  183. &lt;p&gt;Overall, it took us 30 hours to create the tutorials. The whole process gave us a lot of experience, which will help us in shaping learning materials for our technologies in the future. We don't know how they will look like exactly, but they will definitely be better.&lt;/p&gt;

  184. &lt;p&gt;That's it for describing creation of the first four OpenSceneGraph tutorials in March 2017.&lt;/p&gt;</summary></entry><entry><title>Let's go</title><link href="http://opengamestudio.org/lets-go.html" rel="alternate"></link><updated>2017-03-16T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-03-16:lets-go.html</id><summary type="html">&lt;p&gt;&lt;img alt="Let's go" src="http://opengamestudio.org/2017-03_lets-go.png" /&gt;&lt;/p&gt;

  185. &lt;p&gt;In this article we describe our progress in January and February of 2017: rendering under iOS/Web and a new tutorial tool.&lt;/p&gt;

  186. &lt;p&gt;&lt;strong&gt;Rendering under iOS/Web&lt;/strong&gt;&lt;/p&gt;

  187. &lt;p&gt;To our surprise, we got a simple red cube rendered under &lt;a href="https://twitter.com/OpenGameStudio/status/826816343433498627"&gt;iOS&lt;/a&gt; and &lt;a href="https://twitter.com/OpenGameStudio/status/829731986264698881"&gt;Web&lt;/a&gt; pretty fast: in early February. However, this is only the beginning of this year's challenge to support Android, iOS, and Web platforms. There's a long and bumpy road ahead of us as we need a lot more on each platform before we can claim a success: visual effects, Python scripting, data archives.&lt;/p&gt;

  188. &lt;p&gt;Since it took us about four months to get to mobile and web platforms, we decided to share our knowledge and help OpenSceneGraph community with a guide that shows how to use OpenSceneGraph on desktop, mobile, and web. We believe the more widespread OpenSceneGraph is, the stronger our technology becomes. As Isaac Newton said, "If I have seen further, it is by standing on the shoulders of giants." OpenSceneGraph is our giant.&lt;/p&gt;

  189. &lt;p&gt;&lt;strong&gt;Tutorial tool&lt;/strong&gt;&lt;/p&gt;

  190. &lt;p&gt;Having conducted four live sessions before, it was clear the guide needs videos depicting every nuance. However, bare video alone is only good for showing what to do and not for explaining why do it in a certain way. That's why we decided to combine video with text in the forms of video subtitles and separate articles.&lt;/p&gt;

  191. &lt;p&gt;To combine text and video, we first tried &lt;a href="http://openshotvideo.com"&gt;OpenShot&lt;/a&gt;. It worked well, but we quickly saw its limitations:&lt;/p&gt;

  192. &lt;ul&gt;

  193. &lt;li&gt;Too much time is spent on adjusting time frames and animations&lt;/li&gt;

  194. &lt;li&gt;Project file and original resources are hard to track with VCS&lt;/li&gt;

  195. &lt;/ul&gt;

  196. &lt;p&gt;Since OpenSceneGraph cross-platform guide would consist of several tutorials, we decided to automate the process. Brief research revealed a great multimedia framework called &lt;a href="http://mltframework.org"&gt;MLT&lt;/a&gt;, which powers OpenShot itself. With MLT we got our tutorial tool in no time.&lt;/p&gt;

  197. &lt;p&gt;Currently, the tutorial tool allows anyone to combine text and video using a simple text file like this:&lt;/p&gt;

  198. &lt;div class="highlight"&gt;&lt;pre&gt;background bg.png

  199. text 5 Let&amp;#39;s install Blender

  200. video 0:6 install_blender.mp4

  201. text 5 Installing it with apt

  202. video 6:26 install_blender.mp4

  203. text 5 We&amp;#39;re still installing it

  204. video 26:56 install_blender.mp4

  205. text 5 Congratulations! We just finished installing Blender

  206. &lt;/pre&gt;&lt;/div&gt;

  207. 

  208. 

  209. &lt;p&gt;This is the actual script. See the final result &lt;a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide/tree/master/tutorial-tool"&gt;here&lt;/a&gt;.&lt;/p&gt;

  210. &lt;p&gt;That's it for describing our progress in January and February of 2017: rendering under iOS/Web and the new tutorial tool.&lt;/p&gt;</summary></entry><entry><title>The year of challenges</title><link href="http://opengamestudio.org/the-year-of-challenges.html" rel="alternate"></link><updated>2017-01-25T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2017-01-25:the-year-of-challenges.html</id><summary type="html">&lt;p&gt;&lt;img alt="The year of challenges" src="http://opengamestudio.org/2017-01_the-year-of-challenges.png" /&gt;&lt;/p&gt;

  211. &lt;p&gt;This article describes our plans for 2017.&lt;/p&gt;

  212. &lt;p&gt;Our past plans suggested we would have Android platform support by this time. However, we have a long way to go, before we can declare Android support. See for yourself:&lt;/p&gt;

  213. &lt;p&gt;&lt;img alt="Android rendering" src="http://opengamestudio.org/2017-01_mjin-android-gles.png" /&gt;&lt;/p&gt;

  214. &lt;p&gt;Some people would consider this a failure. We don't. We see a chance to start low and jump high!&lt;/p&gt;

  215. &lt;p&gt;Having only worked with liberal and forgiving desktop environments, Android was a complete surprise for us. Android punished us for everything: memory, resources, graphics. The usual Android response was either a crash, or an empty screen.

  216. At the same time, such a harsh environment highlighted weak spots in our technologies and helped us see where to go next.&lt;/p&gt;

  217. &lt;p&gt;This month we start working on iOS platform support, even though we have only scratched Android. Why? Because it's a lot easier to get those red cubes rendered on iOS without polishing Android first. We don't want to spend months polishing Android only to find out later we had to implement certain feature differently so that it works on all supported platforms.&lt;/p&gt;

  218. &lt;p&gt;And right after we get those cubes rendered on iOS, we start to work on bringing them to Web.&lt;/p&gt;

  219. &lt;p&gt;&lt;strong&gt;You got it right: we challenge ourselves with support for Android, iOS, and Web this year.&lt;/strong&gt;&lt;/p&gt;

  220. &lt;p&gt;That's it for describing our plans for 2017.&lt;/p&gt;</summary></entry><entry><title>Happy 2017</title><link href="http://opengamestudio.org/2017-happy-new-year.html" rel="alternate"></link><updated>2016-12-31T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2016-12-31:2017-happy-new-year.html</id><summary type="html">&lt;p&gt;&lt;img alt="Happy new year" src="http://opengamestudio.org/2016-12-31_happy-new-year.png" /&gt;&lt;/p&gt;

  221. &lt;p&gt;Okay. It's been a hard year for everyone in the team. And it's almost over. Praise it ends! Praise the new one!&lt;/p&gt;

  222. &lt;p&gt;It may seem, that our progress stalled. Three years ago we announced the beginning of a new project (two to be precise), and now we still working on the engine and editor, haven't even started creating the actual game.&lt;/p&gt;

  223. &lt;p&gt;If you were monitoring our news during the year, you know that we held several live sessions, showing in the real time how to use our tools to create some simple games. Each session was a step in a long road to our goal. While preparing for these live sessions, we added necessary building blocks, that will be needed to create almost any game.&lt;/p&gt;

  224. &lt;p&gt;Future live sessions and technical previews will add even more, so at some point in future (i hope not very distant), we will have everything we need to sit down and build our planned game from these blocks.&lt;/p&gt;

  225. &lt;p&gt;So, the project isn't dead; the idea was not thrown away. But there is a lot of work to be done before we can start making the game, and there are only two of us, using our spare time.

  226. So. You want our game to become a reality? Join us. Together we will rule the galaxy. Or just wait and see. We didn't stop several years ago. We won't stop now.

  227. After all, there is only one way to create a fine tool (and it's our initial goal if you remember) - we need to use it ourselves.

  228. We will. Stay tuned.&lt;/p&gt;

  229. &lt;p&gt;Happy 2017. Let it be simple.&lt;/p&gt;</summary></entry><entry><title>November 2016 recap</title><link href="http://opengamestudio.org/2016-november-recap.html" rel="alternate"></link><updated>2016-12-15T00:00:00+03:00</updated><author><name>Opensource Game Studio</name></author><id>tag:opengamestudio.org,2016-12-15:2016-november-recap.html</id><summary type="html">&lt;p&gt;&lt;img alt="November recap" src="http://opengamestudio.org/2016-12-15_2016-november-recap.png" /&gt;&lt;/p&gt;

  230. &lt;p&gt;This article describes the start of MJIN library separation into modules.&lt;/p&gt;

  231. &lt;p&gt;Once we built OpenSceneGraph for Android, it became obvious that some MJIN functionality is not suitable for Android. For example, UIQt provides a basis for OGS Editor UI. Since OGS Editor is a desktop application, we don't need UIQt for Android.&lt;/p&gt;

  232. &lt;p&gt;We decided to have a look at two approaches to separate MJIN into modules: build-time separation and run-time one. 

  233. &lt;strong&gt;Build-time&lt;/strong&gt; separation means MJIN becomes highly configurable and each platform gets specifically tailored MJIN build.

  234. &lt;strong&gt;Run-time&lt;/strong&gt; separation means MJIN is divided into smaller libraries that are connected at run-time, which makes it easy to change functionality without rebuilding.&lt;/p&gt;

  235. &lt;p&gt;&lt;strong&gt;Run-time separation research.&lt;/strong&gt;&lt;/p&gt;

  236. &lt;p&gt;Since run-time separation has more benefits, we started researching it first.

  237. The easiest way to achieve it was to use C API, because C ABI rules are much simpler than C++ one's.&lt;/p&gt;

  238. &lt;p&gt;We created a sample project consisting of the application, library, and plugin.

  239. &lt;strong&gt;The application&lt;/strong&gt; has been linked to the library and used it to load the plugin.

  240. &lt;strong&gt;The library&lt;/strong&gt; provided functions to register plugins and call their functions.

  241. &lt;strong&gt;The plugin&lt;/strong&gt; provided functions for the library and called library functions.&lt;/p&gt;

  242. &lt;p&gt;The research was successful: the sample project worked correctly under Linux and Windows. However, since MJIN is currently a single large entity, we postponed C API application until we finish build-time separation.&lt;/p&gt;

  243. &lt;p&gt;&lt;strong&gt;Build-time separation start.&lt;/strong&gt;&lt;/p&gt;

  244. &lt;p&gt;We extracted the following modules from MJIN:&lt;/p&gt;

  245. &lt;ul&gt;

  246. &lt;li&gt;

  247. &lt;p&gt;Android: provides Java Native Interface (JNI) to MJIN&lt;/p&gt;

  248. &lt;/li&gt;

  249. &lt;li&gt;

  250. &lt;p&gt;Sound: provides access to OpenAL&lt;/p&gt;

  251. &lt;/li&gt;

  252. &lt;li&gt;

  253. &lt;p&gt;UIQt: provides access to Qt UI&lt;/p&gt;

  254. &lt;/li&gt;

  255. &lt;/ul&gt;

  256. &lt;p&gt;Sound and UIQt modules are currently statically linked into MJIN library, while Android module is already a separate library due to JNI requirements.&lt;/p&gt;

  257. &lt;p&gt;In the coming year, we're going to significantly restructure MJIN so that it suits as many platforms as possible.&lt;/p&gt;

  258. &lt;p&gt;That's it for describing the start of MJIN library separation into modules.&lt;/p&gt;</summary></entry></feed>