Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.

222 рядки
11KB

  1. <!DOCTYPE html>
  2. <html>
  3. <meta charset="utf-8">
  4. <head>
  5. <link rel="stylesheet" href="../../style.css">
  6. </head>
  7. <body>
  8. <script data-goatcounter="https://services.opengamestudio.org:443/count" async src="//services.opengamestudio.org:443/count.js"></script>
  9. <div id="header">
  10. <div>
  11. <strong id="title">Open Game Studio</strong>
  12. <div id="lang">
  13. <a href="../../en/news/index3.html">EN</a>
  14. <a href="../../ru/news/index3.html">RU</a>
  15. </div>
  16. </div>
  17. <div class="header2">
  18. <div class="menu">
  19. <a href="../../en/news/index.html">News</a>
  20. <a href="../../en/game/index.html">Games</a>
  21. <a href="../../en/tool/index.html">Tools</a>
  22. <a href="../../en/page/about.html">About</a>
  23. </div>
  24. <a class="discord" href="https://discord.gg/3A6THQabNf">
  25. <img src="../../images/discord.png"></img>
  26. </a>
  27. <div class="clear"></div>
  28. </div>
  29. </div>
  30. <center>
  31. <h1>News</h1>
  32. <div class="news_item">
  33. <h2 class="news_item_title">
  34. <a href="mahjong-techdemo1-gameplay.html">First techdemo of OGS Mahjong 2: Gameplay</a>
  35. </h2>
  36. <p class="news_item_date">
  37. 2018-02-16 00:00
  38. </p>
  39. <div class="news_item_contents">
  40. <p><img src="../../images/2018-02-16-mahjong-techdemo1-gameplay.png" alt="End of a Mahjong party" /></p>
  41. <p>We are glad to announce the release of the first technical demonstration of OGS Mahjong 2. The purpose of this release was to verify gameplay across supported platforms.</p>
  42. <p>Get techdemo for your platform:</p>
  43. <ul>
  44. <li>Run <a href="https://ogstudio.github.io/game-mahjong/versions/013/mjin-player.html">Web version</a> in your browser</li>
  45. <li>Get <a href="https://drive.google.com/open?id=1KW8IEN8Dpz8ODeg8BctVSJyzj9-AL9hR">Android version</a></li>
  46. <li>Get <a href="https://drive.google.com/open?id=1oj0-OXSmEatttzn86u2vgP9SRAIC0ozB">Windows version</a></li>
  47. <li>Get <a href="https://drive.google.com/open?id=1EX7kLIThLiMz9_W7VmBPySms3mlrF-i6">Linux version</a></li>
  48. <li>Get <a href="https://drive.google.com/open?id=1KWnvbHzan8MpMcZPG2QC-7KWoEYbqrM2">macOS version</a></li>
  49. </ul>
  50. <p>Notes:</p>
  51. <ul>
  52. <li>iOS version is not released because it cannot be easily shared outside AppStore.. . .</li>
  53. </ul>
  54. </div>
  55. <div class="news_item_more">
  56. <a href="mahjong-techdemo1-gameplay.html">Continue reading</a>
  57. </div>
  58. </div>
  59. <div class="news_item">
  60. <h2 class="news_item_title">
  61. <a href="mahjong-recreation-start.html">Mahjong recreation start</a>
  62. </h2>
  63. <p class="news_item_date">
  64. 2018-01-26 00:00
  65. </p>
  66. <div class="news_item_contents">
  67. <p><img src="../../images/2018-01-26-mahjong-recreation-start.png" alt="Spherical tiles in a Mahjong layout" /></p>
  68. <p>This article describes the start of Mahjong game recreation.</p>
  69. <p><strong>Plan</strong></p>
  70. <p>We started Mahjong recreation endeavour by composing a brief plan to get gameplay with minimal graphics:</p>
  71. <ul>
  72. <li>Load single layout</li>
  73. <li>Place tiles in layout positions</li>
  74. <li>Distinguish tiles</li>
  75. <li>Implement selection</li>
  76. <li>Implement matching</li>
  77. </ul>
  78. <p>Just like any other plan, this one looked fine at first sight. However, once you get down to work, new details start to come out. This plan was no exception. Below are a few problems that came out during development.. . .</p>
  79. </div>
  80. <div class="news_item_more">
  81. <a href="mahjong-recreation-start.html">Continue reading</a>
  82. </div>
  83. </div>
  84. <div class="news_item">
  85. <h2 class="news_item_title">
  86. <a href="the-year-of-lessons.html">The year of lessons</a>
  87. </h2>
  88. <p class="news_item_date">
  89. 2017-12-31 22:00
  90. </p>
  91. <div class="news_item_contents">
  92. <p><img src="../../images/2017-12-31-celebration.jpg" alt="Sparkler" /></p>
  93. <p>So, the year 2017 is approaching its finale, the year's results have already been summed up. We're going to take a break from igniting the fireworks or preparation of the champagne so that we can designate our goal for the following year.</p>
  94. <p>As it may be clear from other articles on the site, half of our plans in 2017 were destined to be completed at least approximately as we assumed. The other half was changed significantly.</p>
  95. <p>During the year, people joined the team and left it. As a result, we meet the end of the year with exactly the same team as 365 days ago. It made us think. A lot. But We'll save the story for another time.. . .</p>
  96. </div>
  97. <div class="news_item_more">
  98. <a href="the-year-of-lessons.html">Continue reading</a>
  99. </div>
  100. </div>
  101. <div class="news_item">
  102. <h2 class="news_item_title">
  103. <a href="2017-summary.html">2017 summary</a>
  104. </h2>
  105. <p class="news_item_date">
  106. 2017-11-22 00:00
  107. </p>
  108. <div class="news_item_contents">
  109. <p><img src="../../images/2017-11-22-2017-summary.png" alt="Memory game in the background" /></p>
  110. <p>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.</p>
  111. <p><strong>Brief history</strong></p>
  112. <p>Opensource Game Studio project is 12 years old now.</p>
  113. <p><strong>2005.</strong> We started the project with a <a href="https://www.linuxquestions.org/questions/general-10/the-creation-of-the-best-rpg-355858/">fanatic call</a> 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). 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.. . .</p>
  114. </div>
  115. <div class="news_item_more">
  116. <a href="2017-summary.html">Continue reading</a>
  117. </div>
  118. </div>
  119. <div class="news_item">
  120. <h2 class="news_item_title">
  121. <a href="back-to-the-static.html">Back to the Static</a>
  122. </h2>
  123. <p class="news_item_date">
  124. 2017-10-16 00:00
  125. </p>
  126. <div class="news_item_contents">
  127. <p><img src="../../images/2017-10-16-back-to-the-static.png" alt="Static and dynamic unite" /></p>
  128. <p>We have been using Wordpress as our website engine for more than seven years. And now it's time to move forward. Or backward. For some time we've been tracking the development of the new breed of website engines - static site generators. It seems that this is the technology capable of changing past into future.</p>
  129. <p>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. So, we are starting our site anew with the help of the <a href="https://blog.getpelican.com/">Pelican</a>.. . .</p>
  130. </div>
  131. <div class="news_item_more">
  132. <a href="back-to-the-static.html">Continue reading</a>
  133. </div>
  134. </div>
  135. <div class="news_item">
  136. <h2 class="news_item_title">
  137. <a href="mjin-world-birth.html">The birth of MJIN world</a>
  138. </h2>
  139. <p class="news_item_date">
  140. 2017-09-10 00:00
  141. </p>
  142. <div class="news_item_contents">
  143. <p><img src="../../images/2017-09-mjin-world-birth.png" alt="An explosion giving birth to something new" /></p>
  144. <p>This article describes the birth of MJIN world in August 2017.</p>
  145. <p><strong>mjin-player</strong></p>
  146. <p>As you know, <a href="scripting-research.html">we spent July to research scripting</a>. We found a solution that satisfies the following criteria. Scripts should:</p>
  147. <ol>
  148. <li>run unchanged on all supported platforms</li>
  149. <li>allow extending C++ code</li>
  150. </ol>
  151. <p>We have verified the second criterion by writing a sample application. The first criterion was taken for granted because it SHOULD be true.. . .</p>
  152. </div>
  153. <div class="news_item_more">
  154. <a href="mjin-world-birth.html">Continue reading</a>
  155. </div>
  156. </div>
  157. <div class="news_item">
  158. <h2 class="news_item_title">
  159. <a href="scripting-research.html">Scripting research</a>
  160. </h2>
  161. <p class="news_item_date">
  162. 2017-08-16 00:00
  163. </p>
  164. <div class="news_item_contents">
  165. <p><img src="../../images/2017-08-scripting-research.png" alt="Textbook with a text" /></p>
  166. <p>This article describes scripting research in July 2017.</p>
  167. <p><strong>Our first goal of using a scripting language was to have a platform-independent code that runs unchanged on every supported platform.</strong></p>
  168. <p>OGS Editor 0.10 supports Python for such a code thanks to <a href="http://swig.org/">SWIG</a>. 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.. . .</p>
  169. </div>
  170. <div class="news_item_more">
  171. <a href="scripting-research.html">Continue reading</a>
  172. </div>
  173. </div>
  174. <div class="news_item">
  175. <h2 class="news_item_title">
  176. <a href="openscenegraph-cross-platform-guide.html">OpenSceneGraph cross-platform guide</a>
  177. </h2>
  178. <p class="news_item_date">
  179. 2017-07-17 00:00
  180. </p>
  181. <div class="news_item_contents">
  182. <p><img src="../../images/2017-07-openscenegraph-guide.png" alt="OpenSceneGraph sample application in desktop and mobile" /></p>
  183. <p>This article summarizes the work we did to produce OpenSceneGraph cross-platform guide.</p>
  184. <p>June marked the finish of <a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide">OpenSceneGraph cross-platform guide</a> with the publishing of the last (initially planned) tutorial. The tutorial describes <a href="https://github.com/OGStudio/openscenegraph-cross-platform-guide/tree/master/1.10.SampleWeb">how to build and run sample OpenSceneGraph application in Web</a> using Emscripten.. . .</p>
  185. </div>
  186. <div class="news_item_more">
  187. <a href="openscenegraph-cross-platform-guide.html">Continue reading</a>
  188. </div>
  189. </div>
  190. <div class="news_item">
  191. <h2 class="news_item_title">
  192. <a href="ios-tutorial.html">iOS tutorial</a>
  193. </h2>
  194. <p class="news_item_date">
  195. 2017-06-08 10:00
  196. </p>
  197. <div class="news_item_contents">
  198. <p><img src="../../images/2017-06-08-ios-refactoring.png" alt="Earth and a rocket" /></p>
  199. <p>This article describes problems we faced during the creation of iOS tutorial in May 2017.</p>
  200. <p><a href="https://twitter.com/OpenGameStudio/status/826816343433498627">This February</a> 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.. . .</p>
  201. </div>
  202. <div class="news_item_more">
  203. <a href="ios-tutorial.html">Continue reading</a>
  204. </div>
  205. </div>
  206. <p class="pagination_title">Page 3 of 7</p>
  207. <p>
  208. <a href="index2.html">« Newer</a>
  209. <a href="index4.html">Older »</a>
  210. </p>
  211. <div id="footer">
  212. The site has been generated by <a href="http://opengamestudio.org/pskov">PSKOV</a>
  213. from <a href="http://github.com/ogstudio/site-opengamestudio">this source code</a>.
  214. </div>
  215. </center>
  216. </body>
  217. </html>