http://cegui.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Ident CEGUI Wiki - Crazy Eddie's GUI System (Open Source) - User contributions [en] 2026-04-11T23:43:48Z User contributions MediaWiki 1.24.1 http://cegui.org/wiki/index.php?title=MediaWiki:Sidebar&diff=5810 MediaWiki:Sidebar 2021-05-23T23:21:10Z <p>Ident: </p> <hr /> <div>* Main<br /> ** http://www.cegui.org.uk/wiki | Home<br /> ** http://www.cegui.org.uk/download | Releases<br /> ** http://www.cegui.org.uk/news | News<br /> ** https://github.com/cegui | Repository<br /> ** recentchanges-url | Recent Changes<br /> <br /> * Community<br /> ** http://www.cegui.org.uk/phpBB2/index.php | Forum<br /> ** https://twitter.com/ceguilib | Twitter<br /> ** https://discord.gg/NJ3fgsw | Discord<br /> <br /> * Documentation<br /> ** http://static.cegui.org.uk/docs/ | Official documentation<br /> ** Category:Tutorials |Tutorials<br /> ** Category:HowTo |HowTo<br /> ** Category:Manuals |Manuals</div> Ident http://cegui.org/wiki/index.php?title=MediaWiki:Sidebar&diff=5807 MediaWiki:Sidebar 2019-08-30T18:25:33Z <p>Ident: </p> <hr /> <div>* Main<br /> ** http://www.cegui.org.uk/wiki | Home<br /> ** http://www.cegui.org.uk/download | Releases<br /> ** http://www.cegui.org.uk/news | News<br /> ** https://bitbucket.org/cegui/ | Repository<br /> ** recentchanges-url | Recent Changes<br /> <br /> * Community<br /> ** http://www.cegui.org.uk/phpBB2/index.php | Forum<br /> ** https://twitter.com/ceguilib | Twitter<br /> ** https://discord.gg/NJ3fgsw | Discord<br /> <br /> * Documentation<br /> ** http://static.cegui.org.uk/docs/ | Official documentation<br /> ** Category:Tutorials |Tutorials<br /> ** Category:HowTo |HowTo<br /> ** Category:Manuals |Manuals</div> Ident http://cegui.org/wiki/index.php?title=MediaWiki:SideBar&diff=5806 MediaWiki:SideBar 2019-08-30T18:25:01Z <p>Ident: </p> <hr /> <div>* Main Menu<br /> ** mainpage|Home<br /> ** news|News<br /> ** downloads |Downloads<br /> ** http://www.cegui.org.uk/gallery/index.php |Screenshots<br /> ** main_links |Web Links<br /> ** recentchanges-url|Recent Changes<br /> * Community<br /> ** http://www.cegui.org.uk/phpBB2/index.php |Forums<br /> ** http://www.cegui.org.uk/mantis/index.php |Mantis Tracker<br /> ** https://discord.gg/NJ3fgsw |CEGUI on Discord<br /> ** http://skins.cegui.org.uk |Skins<br /> ** http://sourceforge.net/projects/crayzedsgui/ |Sourceforge Project<br /> ** sitesupport-url|sitesupport<br /> * Documentation<br /> ** http://www.cegui.org.uk/docs/current |Main Docs<br /> ** Tutorials |Tutorials<br /> ** FAQ |FAQ<br /> ** http://www.cegui.org.uk/mantis/roadmap_page.php?project_id=0 |Development Roadmap<br /> ** https://bitbucket.org/cegui/ |Browse Mercurial<br /> ** helppage|help<br /> * SEARCH<br /> * TOOLBOX<br /> * LANGUAGES</div> Ident http://cegui.org/wiki/index.php?title=Developer_Team&diff=5803 Developer Team 2019-03-10T19:22:14Z <p>Ident: </p> <hr /> <div>Something about the team should go here<br /> <br /> * [[User:Crazyeddie]] - project lead, project creator, programmer, wizard in his spare time<br /> * [[User:Kulik]] - programmer (focus on all parts of CEGUI, especially the CEGUI Animation features, Unix support), CEED creator, GSoC mentor<br /> * [[User:Ident]] (Lukas Meindl) - programmer (focus on the Renderers for OpenGL, OpenGL 3.2+ Core Profile, Direct3D11 and Ogre Renderer, as well as the CEED Look n' Feel Editor, Windows/Visual Studio support, the ColourPicker widget), also reviews mustard in his spare time<br /> * [[User:Timotei]] - programmer (focus on the non-focus, new input system, new model-view widgets, SDK builder)<br /> * [[User:YaronCT]] (Yaron Cohen-Tal) - programmer.</div> Ident http://cegui.org/wiki/index.php?title=Projects_Using_CEGUI&diff=5802 Projects Using CEGUI 2018-11-04T16:23:03Z <p>Ident: </p> <hr /> <div>== Introduction ==<br /> This page lists finished projects which make use of the CEGUI library. The intros are mostly quoted from the original locations.<br /> <br /> == Games ==<br /> === Open source ===<br /> * [http://wiki.worldforge.org/wiki/Ember Ember] A GPL 3d client for the Worldforge system<br /> * [http://www.ryzom.com/ Ryzom] MMORPG that recently got released under AGPL (including all art!)<br /> * [http://www.secretmaryo.org/ Secret Maryo Chronicles] A GPL 2D platform game using SDL and OpenGL.<br /> * [http://www.sumwars.org/ Summoning Wars] open source role-playing game, featuring both a single-player and a multiplayer mode for about 2 to 8 players<br /> * [http://www.orxonox.net/ Orxonox] open source spacecraft shooter that plays in the post-apocalyptic world of our future<br /> * [http://opengamestudio.org/ OGS Mahjong] is a simple mahjong solitaire game with nice 3D graphics and relaxing soundtrack<br /> * [http://sourceforge.net/projects/opendungeons/ Open Dungeons] OpenDungeons is an open source game based on the Dungeon Keeper series of games with a different story and new creatures.<br /> * [http://tnlgame.net/ Thunder&amp;Lightning] An Open Source Futuristic Action Flight Simulator Game Inspired By Carrier Command<br /> <br /> === Proprietary ===<br /> * [https://store.steampowered.com/app/788630/Gaia_Beyond/ Gaia Beyond] A handcrafted 2D Action-RPG, an exploration mix built around the core features fighting, mining and trading.<br /> * [http://store.steampowered.com/app/496460 Life is Feudal: Forest Village] A medieval strategy city-builder game<br /> * [https://www.kickstarter.com/projects/nerdkingdom/tug-1/posts TUG] TUG is a multiplayer open-world sandbox-RPG using new technology and social sciences to directly involve players in the game�s design.<br /> * [http://www.torchlightgame.com/ Torchlight] An action role-playing game by [http://www.runicgames.com/ Runic Games]<br /> * [http://www.salvationprophecy.com/ Salvation Prophecy] A military space epic. Human, mutant, and robotic factions are at war for galactic domination.<br /> * [http://www.ankh-game.com/ Ankh 3] A commercial adventure point and click game.<br /> * [http://www.jack-keane-game.de/ Jack Keane] A commercial adventure point and click game.<br /> * [http://www.shipsim.com/products/shipsimulatorextremes Ship Simulator Extremes] A commercial hardcore simulator game by [http://www.vstep.nl/ VSTEP]<br /> * [http://www.dawntide.net/ Dawntide] Open-ended sandbox MMORPG by [http://www.waisoft.com/ WAISOFT]<br /> * [http://www.venetica-game.com/ Venetica] Fantasy themed adventure game.<br /> * [http://www.matrixgames.com/products/374/details/Operation.Barbarossa.-.The.Struggle.for.Russia/ Operation Barbarossa - The Struggle for Russia] A commercial turnbased strategy game<br /> * [http://global.lunia.com/ Lunia] MMORPG featuring anime characters.<br /> * [http://en.wikipedia.org/wiki/The_Book_of_Unwritten_Tales The Book of Unwritten Tales] 3D adventure game by HMH Interactive<br /> * [http://voiddestroyer.com/ Void Destroyer] An independent (self funded) space combat simulator with real time strategy elements.<br /> * [http://www.lifeon.pl/ LifeON] A MMO Virtual Worlds 3D Game using Ogre and CEGUI<br /> * [http://www.worldofbattles.com/ World of battles] Free Online MMORTS<br /> * [http://edeneternal.aeriagames.com/ Eden Eternal] A free Anime MMORPG Game from Aeria Games<br /> * [http://www.snakeworldsgame.com/ Snakeworlds - Spherical 3D snake game] The game classic on spheres / globes.<br /> * [http://www.wiraingames.com/ Interstellar defense troops] Tower defense style game in space by Winter rain games<br /> * [http://www.ivan.org.es/showcase/gameview.php?id=2 Photopolys] A challenge for your mind in which you must compose puzzles based on your own photos.<br /> * [http://www.dancingdots-studio.com/ Ride!] An equestrian simulation by Dancing Dots.<br /> * [http://www.moonpod.com/English/about_pirateprincess.php/ Pirate Princess] Semi-casual word game based adventure in a pirate setting.<br /> * [http://www.zeroballistics.com/game_info.php?um=1&amp;lm=1 Zero Ballistics] a unique blend of multiplayer first person shooter and tank combat game<br /> * [http://store.steampowered.com/app/46520 Wasteland Angel]<br /> * [http://store.steampowered.com/app/49330/ Pirates of Black Cove]<br /> <br /> === Educational ===<br /> * [http://citycardriving.com/ City Car Driving] is designed to help users feel the car driving in ? big city or in a country<br /> * [https://www.cs.utexas.edu/~theshark/courses/cs354r/lectures/cs354r-21.pdf 2015 Lecture notes including CEGUI] - CEGUI was introduced in lecture notes of 2015: University of Texas at Austin CS 354R – Game Technology - S. Abraham<br /> <br /> === Addons ===<br /> * [http://www.mtasa.com/ Multi Theft Auto: SA] Third party mod for GTA3: San Andreas providing multiplayer<br /> * [http://www.iv-multiplayer.com/ IV:M] Third party mod for GTA4 providing multiplayer<br /> <br /> === Defunct? ===<br /> * [http://www.cubecombat.net/ Cube Combat] 3D Bomberman like game, supporting up to 4 player through lan or internet.<br /> * [http://www.opengate.ontheserver.de OpenGate] Opengate is an open source remake of the game Jumpgate©<br /> * [http://www.smootsy.com/ Smootsy] A MMO Social Network 3D Game using Ogre<br /> <br /> == Applications ==<br /> * [http://www.psychosynth.com PsychoSynth] aims to create an interactive modular soft-synth inspired by the ideas of the Reactable.<br /> * [http://www.navit-project.org/ NAVIT] is a car navigation system with routing engine.<br /> * [http://mmix.me/ MMiX.Me] 3D Media Player for Microsoft Windows.<br /> * [http://www.nightshadesoftware.org Nightshade] Nightshade is simulation and visualization software for teaching and exploring astronomy, Earth science, and related topics. Download this incredible software for free.<br /> <br /> == Engines and frameworks ==<br /> === The Delta3D Open Source Game Engine ===<br /> The Delta3D Game Engine integrates the functionality of CEGUI, allowing users to have robust user interfaces active in their applications. The Delta3D Game Engine was an early adopter of the CEGUI technology and has contributed to its development over the years.<br /> <br /> For more information, see [http://delta3d.org http://delta3d.org].<br /> <br /> === Reality factory ===<br /> Reality Factory is a program that, in conjunction with other tools, allows you to create first- and third- person perspective games - without programming!<br /> <br /> CEGUI is used in version 2.0 and upwards.<br /> More at [http://www.realityfactory.info http://www.realityfactory.info] and [http://realityfactory2.sourceforge.net/ http://realityfactory2.sourceforge.net/]<br /> <br /> == Game related tools ==<br /> === TeamSpeak 3 overlay ===<br /> TeamSpeak 3 overlay is an injection engine that displays TeamSpeak activities (e.g. when people are talking) while in-game.<br /> <br /> For more information, check [http://ts3overlay.r-dev.de ts3overlay.r-dev.de]<br /> <br /> === OGRE particle editor ===<br /> &quot;The OGRE Particle Editor is a real-time visual particle system editor. It is a tool that provides the ability to rapidly create OGRE particle system templates that can be used in any OGRE driven application. The effects are stored and loaded as templates via standard OGRE particle scripts (*.particle).&quot;<br /> <br /> It can be downloaded [http://www.ogre3d.org/index.php?option=com_remository&amp;Itemid=74&amp;func=fileinfo&amp;filecatid=35&amp;parent=category here]. <br /> <br /> And the manual can be found [http://www.game-cat.com/ogre/pe/docs/ here].<br /> <br /> === Nimble 3D ===<br /> Nimble is WMI's second realtime visualization product. Based on advanced physics models, Nimble follows in its predecessor's footsteps and delivers another first in simulation graphics- truly photorealistic 3D clouds, completely in realtime<br /> <br /> For more information, see [http://www.windwardmark.net/products.php?page=nimble&amp;sub=technology| windwardmark.net]</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5801 Ident TODO 2017-05-02T22:01:46Z <p>Ident: </p> <hr /> <div>=== CEGUI General ===<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> * CEGUI default: rename isActive() to isInFocus() or similar to be more meaningful? http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=7162<br /> <br /> === Opengl Renderers === <br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> === Renderers === <br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> === SVG === <br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> === SampleBrowser === <br /> * Separate duties (input, Renderer-related stuff, etc) in different facades. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> === CEGUI docu === <br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> === SVG Tessellator tests === <br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> === Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs === <br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> === Adapt CEGUI System/Renderer for multi-window support and write a simple demo app === <br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14<br /> <br /> === Image / Font autoscaling should be GUIContext-specific ===<br /> As brought up by Naros on #cegui, currently System has a notifyDisplaySizeChanged function, which makes no sense, as we have been supporting multiple concurrent GUIContexts at a time. The function propagates the notification to FontManager and ImageManager which use it for autoscaling. While it makes sense to share the image and font definitions, it doesnt make sense to share the final scale result between guicontexts. So these should be stored for each font and image separately per GUIContexts. To be specific, that would be the d_scaledSize and d_scaledOffset for each. The function itself should be removed. --&gt; all of this has to go into default branch. A ticket has to be created for this yet on bitbucket.<br /> <br /> = FINISHED =<br /> <br /> === Add tooltips to some demo === <br /> &lt;strike&gt;It is currently not covered anywhere. Or is it( need to check!)?&lt;/strike&gt;<br /> Added to the look n' feel demo (and fixed some bugs with inherited tooltips that I noticed ;) )<br /> <br /> === Glyph rendering and Freetype Font rework ===<br /> * Fixed: Glyph atlas creation algorithm completely overworked and simplified and made more efficient<br /> * Fixed: Kerning and raqm support added<br /> * Won't fix: Glyph atlas is RGBA despite being single-channel, but turning it to single channel requires shader changes and makes renderer support difficult...<br /> * Won't fix: We don't support LCD subpixel rendering, as it depends too much on hardware and single channel is good enough<br /> * Won't fix: Won't support subpixel positiong because small Font sizes can get blurrier than normal if moved to a subpixel position, unfortunately, and small Fonts are the main reason to do this..</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5800 Ident TODO 2017-01-28T12:35:57Z <p>Ident: /* SampleBrowser */</p> <hr /> <div>=== CEGUI General ===<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> * CEGUI default: rename isActive() to isInFocus() or similar to be more meaningful? http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=7162<br /> <br /> === Opengl Renderers === <br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> === Renderers === <br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> === SVG === <br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> === SampleBrowser === <br /> * Separate duties (input, Renderer-related stuff, etc) in different facades. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> === CEGUI docu === <br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> === SVG Tessellator tests === <br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> === Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs === <br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> === Adapt CEGUI System/Renderer for multi-window support and write a simple demo app === <br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14<br /> <br /> <br /> = FINISHED =<br /> <br /> === Add tooltips to some demo === <br /> &lt;strike&gt;It is currently not covered anywhere. Or is it( need to check!)?&lt;/strike&gt;<br /> Added to the look n' feel demo (and fixed some bugs with inherited tooltips that I noticed ;) )<br /> <br /> === Glyph rendering and Freetype Font rework ===<br /> * Fixed: Glyph atlas creation algorithm completely overworked and simplified and made more efficient<br /> * Fixed: Kerning and raqm support added<br /> * Won't fix: Glyph atlas is RGBA despite being single-channel, but turning it to single channel requires shader changes and makes renderer support difficult...<br /> * Won't fix: We don't support LCD subpixel rendering, as it depends too much on hardware and single channel is good enough<br /> * Won't fix: Won't support subpixel positiong because small Font sizes can get blurrier than normal if moved to a subpixel position, unfortunately, and small Fonts are the main reason to do this..</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5799 Ident TODO 2017-01-28T12:24:06Z <p>Ident: </p> <hr /> <div>=== CEGUI General ===<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> * CEGUI default: rename isActive() to isInFocus() or similar to be more meaningful? http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=7162<br /> <br /> === Opengl Renderers === <br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> === Renderers === <br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> === SVG === <br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> === SampleBrowser === <br /> * Separate duties (input, Renderer-related stuff, etc) in different facets. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> === CEGUI docu === <br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> === SVG Tessellator tests === <br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> === Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs === <br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> === Adapt CEGUI System/Renderer for multi-window support and write a simple demo app === <br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14<br /> <br /> <br /> = FINISHED =<br /> <br /> === Add tooltips to some demo === <br /> &lt;strike&gt;It is currently not covered anywhere. Or is it( need to check!)?&lt;/strike&gt;<br /> Added to the look n' feel demo (and fixed some bugs with inherited tooltips that I noticed ;) )<br /> <br /> === Glyph rendering and Freetype Font rework ===<br /> * Fixed: Glyph atlas creation algorithm completely overworked and simplified and made more efficient<br /> * Fixed: Kerning and raqm support added<br /> * Won't fix: Glyph atlas is RGBA despite being single-channel, but turning it to single channel requires shader changes and makes renderer support difficult...<br /> * Won't fix: We don't support LCD subpixel rendering, as it depends too much on hardware and single channel is good enough<br /> * Won't fix: Won't support subpixel positiong because small Font sizes can get blurrier than normal if moved to a subpixel position, unfortunately, and small Fonts are the main reason to do this..</div> Ident http://cegui.org/wiki/index.php?title=Building_CEED_for_Windows&diff=5798 Building CEED for Windows 2016-10-02T12:20:53Z <p>Ident: /* Installing boost binaries */</p> <hr /> <div>{{VersionBadge|0.8}}<br /> <br /> '''Written by Ident (Lukas Meindl) &amp; Nickenstein79 (Working correctly as of 11th June, 2014)'''<br /> <br /> The following instructions need to be done in the presented order and are created for the currently available version of CEED and could therefore be outdated at some point. Please notify us if you think this is outdated.<br /> <br /> <br /> == Installing the prerequisites ==<br /> <br /> When downloading/installing binaries, be sure to get the version which matches your version of visual studio, for instance choose the 32-bit and VC10 (visual studio 2010) versions of the binaries if that is what you are using to build. (or VC9 / VC11 / VC12 / ... if you are building with those.) If you use VC14 and not for example VC9 then be sure that the paths also match this. Don't get confused about the '''paths''' listed in this article, they are '''exemplatory''' and based on VC9. '''Do not mix VC9 binaries with VC10 or VC11, etc.''' We recommend using VC9 to build CEED because this one is assured to work.<br /> <br /> == Installing Python ==<br /> * Get Python 2.7.12 (32 bit version) for Windows and install it: <br /> https://www.python.org/downloads/<br /> * Add your Python install folder path to the PATH variable in your Windows environment variables, e.g.: C:Projects\Python27<br /> * Now add the Scripts folder to the PATH environment variable, e.g.: C:\Projects\Python27\Scripts &amp; C:\Projects\Python27\Tools\Scripts (depending on which of those folders exists in your install)<br /> * Open up a dos-command-prompt (cmd.exe) with admin rights and type &quot;python&quot; - See if you get something written into the console, such as &quot;Python 2.7.12 (default [...]&quot;, if this is the case then the install worked.<br /> <br /> == Installing pip ==<br /> * Install the latest pip distribution: First download get-pip.py: <br /> http://pip.readthedocs.org/en/latest/installing.html<br /> * Open up a dos-command-prompt (cmd.exe) with admin rights, change to the folder to which you downloaded &quot;get-pip.py&quot; by using the &quot;cd&quot; command, e.g.: cd &quot;A:/Downloads/Not porn&quot;<br /> * Type &quot;python get-pip.py&quot; and click enter in the dos-command-prompt<br /> * pip should now be installed<br /> * Afterwards enter &quot;pip&quot; and click enter. You should get some sort of information about pip now, if the install succeeded.<br /> <br /> <br /> == Installing pyside ==<br /> * Now you can install pyside easily with the following command: &quot;pip install -U PySide&quot;<br /> * You should get a console output notifying you of a successful install<br /> <br /> <br /> == Installing pyOpenGL ==<br /> * Install pyOpenGL on Windows with this installer: <br /> https://pypi.python.org/packages/any/P/PyOpenGL/PyOpenGL-3.0.2.win32.exe<br /> <br /> <br /> == Installing boost binaries ==<br /> * We also need to install boost. We recommend using version boost 1.55, later versions are known to cause issues. You can use an .exe file for this that will install the necessary binaries from this download page:<br /> http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0-build2/ <br /> (Be sure to get the version which matches the version of msvc you intend to build with. If use MSVC2008, then get the download with 'msvc-9.0' in the name, if you use MSVC2010 get the version with 'msvc-10.0' in the name, etc...)<br /> <br /> * Note : If you have multiple versions of MSVS on your machine, it is safe to install different versions of these boost distributions into the same root folder (e.g C:/boost_1_55_0/), as the *.h and *.hpp files are all identical, and the pre-compiled binary libs all get installed to sub-folders specific to different versions of msvc. (It is these folders and libs that we will be manually pointing cmake to in the next section.)<br /> <br /> == Configuring a PyCEGUI build with cmake == <br /> <br /> * Clone CEGUI v0-8 from the CEGUI repository to a new local folder from here:<br /> https://bitbucket.org/cegui/cegui/branch/v0-8<br /> e.g. to C:/cegui-v0-8<br /> * Check that the branch of your working directory is really v0-8 after cloning, if not then update to the latest v0-8 commit<br /> * Add the CEGUI dependencies folder into the CEGUI_v0_8 repository folder that you just cloned.<br /> * Open CMake and set the source code folder to your new local folder, e.g.: C:/cegui-v0-8 and the binaries to for example: C:/cegui-v0-8/build<br /> * Set the tick-boxes 'Advanced' and 'Grouped' to true. It makes it much easier to manage variables within cmake.<br /> <br /> ''[The following two steps are optional but will make finding boost libraries a lot more comfortable: If you, for whatever reason, can not or do not want to add or modify environment variables, you can directly specify all of the paths manually in CMake, by setting the variables to path values analogously to those used in the boost path examples below]''<br /> * Set the following windows environment variables:<br /> <br /> * 'BOOST_INCLUDEDIR' (Where the boost *.hpp files are)<br /> * 'BOOST_LIBRARYDIR' (Where the platform/compiler specific libs are)<br /> * 'BOOST_ROOT' (Set this to the root folder which contains the above two folders.)<br /> <br /> * Now click 'configure'. CMake will now auto-detect most of the build requirements. &lt;br /&gt;It 'should' now correctly auto-detect boost, However, if it failed to find any bost components, then you need to set them manually:<br /> <br /> These are directory-paths and file-paths to locations inside the boost and Python distributions that you installed in the previous steps.<br /> <br /> (Here are examples of what they are set to on my machine)<br /> <br /> === cmake Boost path examples ===<br /> ------------------------------------------------------------------------------------------------------------<br /> ** Boost_PYTHON_LIBRARY_DEBUG C:/boost_1_55_0/lib32-msvc-9.0/boost_python-vc90-mt-gd-1_55.lib<br /> ** Boost_PYTHON_LIBRARY_RELEASE C:/boost_1_55_0/lib32-msvc-9.0/boost_python-vc90-mt-1_55.lib<br /> ** Boost_SYSTEM_LIBRARY_DEBUG C:/boost_1_55_0/lib32-msvc-9.0/boost_system-vc90-mt-gd-1_55.lib<br /> ** Boost_SYSTEM_LIBRARY_RELEASE C:/boost_1_55_0/lib32-msvc-9.0/boost_system-vc90-mt-1_55.lib<br /> ** Boost_INCLUDE_DIR C:/boost_1_55_0<br /> ------------------------------------------------------------------------------------------------------------<br /> <br /> <br /> CMake may correctly auto-find the following Python variables, but it may fail. So be sure to inspect them, and if they were not found, you need to set them manually. <br /> <br /> Here are examples of mine:<br /> <br /> === cmake Python path examples ===<br /> ------------------------------------------------------------------------------------------------------------<br /> ** PYTHON_INCLUDE_DIR C:/Python27/include<br /> ** PYTHON_LIBRARY C:/Python27/libs/python27.lib<br /> ** PYTHON_EXECUTABLE C:/Python27/python.exe<br /> ------------------------------------------------------------------------------------------------------------<br /> <br /> <br /> * Unselect Building the CEGUI samples and select only OpenGL3 and OpenGL out of the available renderers to build<br /> * Select CEGUI_BUILD_PYTHON_MODULES so that this option is checked<br /> * Click 'configure' again, and then click 'generate', this should now work without errors and generate a solution-file in the binary folder that you specified as your build location.<br /> <br /> == Building PyCEGUI ==<br /> <br /> * Open the generated solution using MSVC and build the ALL_BUILDS project (You need 'Release' mode only)<br /> * Go for a very long walk along a very long beach. Building PyCEGUI &amp; PyCEGUI_OpenGLRenderer is very slow.<br /> <br /> <br /> == Setting up the PyCEGUI dll dependencies ==<br /> * Put the following dependencies of CEGUI into your build's bin folder, e.g.: C:/cegui-v0-8/build/bin<br /> ** From your CEGUI dependencies folder (e.g.: C:/cegui-v0-8/dependencies) :<br /> *** freetype.dll<br /> *** glew.dll<br /> *** pcre.dll<br /> ** From the boost binaries folder (e.g.: A:\Programs\boost_1_55_0\lib32-msvc-9.0 )<br /> *** boost_python-vc90-mt-1_55.dll (Or higher, depending on your version of MSVS &amp; the boost lib folder you are using.)<br /> <br /> <br /> == Cloning the CEED repository ==<br /> * clone the following CEED repository, and verify that you are on the v0-8 branch.<br /> https://bitbucket.org/cegui/ceed<br /> <br /> <br /> == Running CEED ==<br /> * Go to your CEED\bin folder (the bin folder inside the folder that you just cloned CEED to)<br /> * Edit runwrapper.bat so that the relative path CEGUI_BUILD_PATH matches the folder you just compiled PyCEGUI to<br /> * Run the batch file, and the CEED editor should be launched (if not, start the guide again. If it still fails, ask for help on the CEGUI forums)<br /> <br /> <br /> == Using Python-CEED-Migrate ==<br /> You can also use the ceed-migrate tool for convert your old cegui-datafiles to the newer formats. See this page for some examples of the parameters ceed-migrate takes: [[Using CEED-Migrate]]<br /> <br /> <br /> [[Using CEED-Migrate]] <br /> [[Category:HowTo]]<br /> [[Category:Tutorials]]</div> Ident http://cegui.org/wiki/index.php?title=Projects_Using_CEGUI&diff=5797 Projects Using CEGUI 2016-09-28T21:47:45Z <p>Ident: /* Proprietary */</p> <hr /> <div>== Introduction ==<br /> This page lists finished projects which make use of the CEGUI library. The intros are mostly quoted from the original locations.<br /> <br /> == Games ==<br /> === Open source ===<br /> * [http://wiki.worldforge.org/wiki/Ember Ember] A GPL 3d client for the Worldforge system<br /> * [http://www.ryzom.com/ Ryzom] MMORPG that recently got released under AGPL (including all art!)<br /> * [http://www.secretmaryo.org/ Secret Maryo Chronicles] A GPL 2D platform game using SDL and OpenGL.<br /> * [http://www.sumwars.org/ Summoning Wars] open source role-playing game, featuring both a single-player and a multiplayer mode for about 2 to 8 players<br /> * [http://www.orxonox.net/ Orxonox] open source spacecraft shooter that plays in the post-apocalyptic world of our future<br /> * [http://opengamestudio.org/ OGS Mahjong] is a simple mahjong solitaire game with nice 3D graphics and relaxing soundtrack<br /> * [http://sourceforge.net/projects/opendungeons/ Open Dungeons] OpenDungeons is an open source game based on the Dungeon Keeper series of games with a different story and new creatures.<br /> * [http://tnlgame.net/ Thunder&amp;Lightning] An Open Source Futuristic Action Flight Simulator Game Inspired By Carrier Command<br /> <br /> === Proprietary ===<br /> * [http://store.steampowered.com/app/496460 Life is Feudal: Forest Village] A medieval strategy city-builder game<br /> * [https://www.kickstarter.com/projects/nerdkingdom/tug-1/posts TUG] TUG is a multiplayer open-world sandbox-RPG using new technology and social sciences to directly involve players in the game�s design.<br /> * [http://www.torchlightgame.com/ Torchlight] An action role-playing game by [http://www.runicgames.com/ Runic Games]<br /> * [http://www.salvationprophecy.com/ Salvation Prophecy] A military space epic. Human, mutant, and robotic factions are at war for galactic domination.<br /> * [http://www.ankh-game.com/ Ankh 3] A commercial adventure point and click game.<br /> * [http://www.jack-keane-game.de/ Jack Keane] A commercial adventure point and click game.<br /> * [http://www.shipsim.com/products/shipsimulatorextremes Ship Simulator Extremes] A commercial hardcore simulator game by [http://www.vstep.nl/ VSTEP]<br /> * [http://www.dawntide.net/ Dawntide] Open-ended sandbox MMORPG by [http://www.waisoft.com/ WAISOFT]<br /> * [http://www.venetica-game.com/ Venetica] Fantasy themed adventure game.<br /> * [http://www.matrixgames.com/products/374/details/Operation.Barbarossa.-.The.Struggle.for.Russia/ Operation Barbarossa - The Struggle for Russia] A commercial turnbased strategy game<br /> * [http://global.lunia.com/ Lunia] MMORPG featuring anime characters.<br /> * [http://en.wikipedia.org/wiki/The_Book_of_Unwritten_Tales The Book of Unwritten Tales] 3D adventure game by HMH Interactive<br /> * [http://voiddestroyer.com/ Void Destroyer] An independent (self funded) space combat simulator with real time strategy elements.<br /> * [http://www.lifeon.pl/ LifeON] A MMO Virtual Worlds 3D Game using Ogre and CEGUI<br /> * [http://www.worldofbattles.com/ World of battles] Free Online MMORTS<br /> * [http://edeneternal.aeriagames.com/ Eden Eternal] A free Anime MMORPG Game from Aeria Games<br /> * [http://www.snakeworldsgame.com/ Snakeworlds - Spherical 3D snake game] The game classic on spheres / globes.<br /> * [http://www.wiraingames.com/ Interstellar defense troops] Tower defense style game in space by Winter rain games<br /> * [http://www.ivan.org.es/showcase/gameview.php?id=2 Photopolys] A challenge for your mind in which you must compose puzzles based on your own photos.<br /> * [http://www.dancingdots-studio.com/ Ride!] An equestrian simulation by Dancing Dots.<br /> * [http://www.moonpod.com/English/about_pirateprincess.php/ Pirate Princess] Semi-casual word game based adventure in a pirate setting.<br /> * [http://www.zeroballistics.com/game_info.php?um=1&amp;lm=1 Zero Ballistics] a unique blend of multiplayer first person shooter and tank combat game<br /> * [http://store.steampowered.com/app/46520 Wasteland Angel]<br /> * [http://store.steampowered.com/app/49330/ Pirates of Black Cove]<br /> <br /> === Educational ===<br /> * [http://citycardriving.com/ City Car Driving] is designed to help users feel the car driving in ? big city or in a country<br /> * [https://www.cs.utexas.edu/~theshark/courses/cs354r/lectures/cs354r-21.pdf 2015 Lecture notes including CEGUI] - CEGUI was introduced in lecture notes of 2015: University of Texas at Austin CS 354R – Game Technology - S. Abraham<br /> <br /> === Addons ===<br /> * [http://www.mtasa.com/ Multi Theft Auto: SA] Third party mod for GTA3: San Andreas providing multiplayer<br /> * [http://www.iv-multiplayer.com/ IV:M] Third party mod for GTA4 providing multiplayer<br /> <br /> === Defunct? ===<br /> * [http://www.cubecombat.net/ Cube Combat] 3D Bomberman like game, supporting up to 4 player through lan or internet.<br /> * [http://www.opengate.ontheserver.de OpenGate] Opengate is an open source remake of the game Jumpgate©<br /> * [http://www.smootsy.com/ Smootsy] A MMO Social Network 3D Game using Ogre<br /> <br /> == Applications ==<br /> * [http://www.psychosynth.com PsychoSynth] aims to create an interactive modular soft-synth inspired by the ideas of the Reactable.<br /> * [http://www.navit-project.org/ NAVIT] is a car navigation system with routing engine.<br /> * [http://mmix.me/ MMiX.Me] 3D Media Player for Microsoft Windows.<br /> * [http://www.nightshadesoftware.org Nightshade] Nightshade is simulation and visualization software for teaching and exploring astronomy, Earth science, and related topics. Download this incredible software for free.<br /> <br /> == Engines and frameworks ==<br /> === The Delta3D Open Source Game Engine ===<br /> The Delta3D Game Engine integrates the functionality of CEGUI, allowing users to have robust user interfaces active in their applications. The Delta3D Game Engine was an early adopter of the CEGUI technology and has contributed to its development over the years.<br /> <br /> For more information, see [http://delta3d.org http://delta3d.org].<br /> <br /> === Reality factory ===<br /> Reality Factory is a program that, in conjunction with other tools, allows you to create first- and third- person perspective games - without programming!<br /> <br /> CEGUI is used in version 2.0 and upwards.<br /> More at [http://www.realityfactory.info http://www.realityfactory.info] and [http://realityfactory2.sourceforge.net/ http://realityfactory2.sourceforge.net/]<br /> <br /> == Game related tools ==<br /> === TeamSpeak 3 overlay ===<br /> TeamSpeak 3 overlay is an injection engine that displays TeamSpeak activities (e.g. when people are talking) while in-game.<br /> <br /> For more information, check [http://ts3overlay.r-dev.de ts3overlay.r-dev.de]<br /> <br /> === OGRE particle editor ===<br /> &quot;The OGRE Particle Editor is a real-time visual particle system editor. It is a tool that provides the ability to rapidly create OGRE particle system templates that can be used in any OGRE driven application. The effects are stored and loaded as templates via standard OGRE particle scripts (*.particle).&quot;<br /> <br /> It can be downloaded [http://www.ogre3d.org/index.php?option=com_remository&amp;Itemid=74&amp;func=fileinfo&amp;filecatid=35&amp;parent=category here]. <br /> <br /> And the manual can be found [http://www.game-cat.com/ogre/pe/docs/ here].<br /> <br /> === Nimble 3D ===<br /> Nimble is WMI's second realtime visualization product. Based on advanced physics models, Nimble follows in its predecessor's footsteps and delivers another first in simulation graphics- truly photorealistic 3D clouds, completely in realtime<br /> <br /> For more information, see [http://www.windwardmark.net/products.php?page=nimble&amp;sub=technology| windwardmark.net]</div> Ident http://cegui.org/wiki/index.php?title=GLFW_to_CEGUI_Key_and_Mouse_Mapping&diff=5796 GLFW to CEGUI Key and Mouse Mapping 2016-09-19T18:10:12Z <p>Ident: </p> <hr /> <div>Map key and mouse button codes from [http://glfw.sourceforge.net GLFW] to CEGUI.<br /> <br /> &lt;source lang=&quot;cpp&quot;&gt;<br /> unsigned int GlfwToCeguiKey(int glfwKey)<br /> {<br /> switch(glfwKey)<br /> {<br /> case GLFW_KEY_UNKNOWN : return 0;<br /> case GLFW_KEY_ESC : return CEGUI::Key::Escape;<br /> case GLFW_KEY_F1 : return CEGUI::Key::F1;<br /> case GLFW_KEY_F2 : return CEGUI::Key::F2;<br /> case GLFW_KEY_F3 : return CEGUI::Key::F3;<br /> case GLFW_KEY_F4 : return CEGUI::Key::F4;<br /> case GLFW_KEY_F5 : return CEGUI::Key::F5;<br /> case GLFW_KEY_F6 : return CEGUI::Key::F6;<br /> case GLFW_KEY_F7 : return CEGUI::Key::F7;<br /> case GLFW_KEY_F8 : return CEGUI::Key::F8;<br /> case GLFW_KEY_F9 : return CEGUI::Key::F9;<br /> case GLFW_KEY_F10 : return CEGUI::Key::F10;<br /> case GLFW_KEY_F11 : return CEGUI::Key::F11;<br /> case GLFW_KEY_F12 : return CEGUI::Key::F12;<br /> case GLFW_KEY_F13 : return CEGUI::Key::F13;<br /> case GLFW_KEY_F14 : return CEGUI::Key::F14;<br /> case GLFW_KEY_F15 : return CEGUI::Key::F15;<br /> case GLFW_KEY_UP : return CEGUI::Key::ArrowUp;<br /> case GLFW_KEY_DOWN : return CEGUI::Key::ArrowDown;<br /> case GLFW_KEY_LEFT : return CEGUI::Key::ArrowLeft;<br /> case GLFW_KEY_RIGHT : return CEGUI::Key::ArrowRight;<br /> case GLFW_KEY_LSHIFT : return CEGUI::Key::LeftShift;<br /> case GLFW_KEY_RSHIFT : return CEGUI::Key::RightShift;<br /> case GLFW_KEY_LCTRL : return CEGUI::Key::LeftControl;<br /> case GLFW_KEY_RCTRL : return CEGUI::Key::RightControl;<br /> case GLFW_KEY_LALT : return CEGUI::Key::LeftAlt;<br /> case GLFW_KEY_RALT : return CEGUI::Key::RightAlt;<br /> case GLFW_KEY_TAB : return CEGUI::Key::Tab;<br /> case GLFW_KEY_ENTER : return CEGUI::Key::Return;<br /> case GLFW_KEY_BACKSPACE : return CEGUI::Key::Backspace;<br /> case GLFW_KEY_INSERT : return CEGUI::Key::Insert;<br /> case GLFW_KEY_DEL : return CEGUI::Key::Delete;<br /> case GLFW_KEY_PAGEUP : return CEGUI::Key::PageUp;<br /> case GLFW_KEY_PAGEDOWN : return CEGUI::Key::PageDown;<br /> case GLFW_KEY_HOME : return CEGUI::Key::Home;<br /> case GLFW_KEY_END : return CEGUI::Key::End;<br /> case GLFW_KEY_KP_ENTER : return CEGUI::Key::NumpadEnter;<br /> default : return 0;<br /> }<br /> }<br /> <br /> CEGUI::MouseButton GlfwToCeguiButton(int glfwButton)<br /> {<br /> switch(glfwButton)<br /> {<br /> case GLFW_MOUSE_BUTTON_LEFT : return CEGUI::LeftButton;<br /> case GLFW_MOUSE_BUTTON_RIGHT : return CEGUI::RightButton;<br /> case GLFW_MOUSE_BUTTON_MIDDLE : return CEGUI::MiddleButton;<br /> default : return CEGUI::NoButton;<br /> }<br /> }<br /> &lt;/source&gt;<br /> <br /> <br /> For GLFW3 you may find this useful: http://cegui.org.uk/forum/viewtopic.php?p=35297<br /> <br /> [[Category:HowTo]]</div> Ident http://cegui.org/wiki/index.php?title=For_the_team&diff=5795 For the team 2016-08-21T21:35:45Z <p>Ident: </p> <hr /> <div>Links that are relevant only for the dev team members:<br /> <br /> * [[Release_Checklist]]<br /> * [[General_Guidelines]]</div> Ident http://cegui.org/wiki/index.php?title=For_the_team&diff=5794 For the team 2016-08-21T21:35:28Z <p>Ident: </p> <hr /> <div>Links that are relevant only for the dev team members:<br /> <br /> - [Release_Checklist]<br /> - [General_Guidelines]</div> Ident http://cegui.org/wiki/index.php?title=General_Guidelines&diff=5793 General Guidelines 2016-08-21T21:34:54Z <p>Ident: Created page with &quot;== Merging == * The main branches currently have to be merged in this direction: '''v0-8 --&gt; v0 --&gt; default''' * If you push v0 or v0-8 changes and you are done with this bra...&quot;</p> <hr /> <div>== Merging ==<br /> <br /> * The main branches currently have to be merged in this direction: '''v0-8 --&gt; v0 --&gt; default'''<br /> * If you push v0 or v0-8 changes and you are done with this branch for today, you must also merge upwards to v0 and default. This ensures that there won't be a backlog of merges piling up that would make it very hard for the next one to do this. <br /> * If you push a change to the default branch and are doen with the branch for today, you have to first make sure you merged all changes from v0-8 to v0 and from v0 to default branch.</div> Ident http://cegui.org/wiki/index.php?title=For_the_team&diff=5792 For the team 2016-08-21T21:28:29Z <p>Ident: </p> <hr /> <div>Links that are relevant only for the dev team members:<br /> <br /> * [[Release_Checklist]]<br /> * [[General_Guidelines]]</div> Ident http://cegui.org/wiki/index.php?title=For_the_team&diff=5791 For the team 2016-08-21T21:28:11Z <p>Ident: </p> <hr /> <div>Links that are relevant only for the dev team members:<br /> <br /> - [[Release_Checklist]]<br /> - [[General_Guidelines]]</div> Ident http://cegui.org/wiki/index.php?title=For_the_team&diff=5790 For the team 2016-08-21T21:13:20Z <p>Ident: Created page with &quot;Links that are relevant only for the dev team members: - [Release_Checklist] - [General_Guidelines]&quot;</p> <hr /> <div>Links that are relevant only for the dev team members:<br /> <br /> - [Release_Checklist]<br /> - [General_Guidelines]</div> Ident http://cegui.org/wiki/index.php?title=User:Ident&diff=5789 User:Ident 2016-08-21T21:11:49Z <p>Ident: </p> <hr /> <div>This page is dedicated to mustard. I could not have made it this far without you.<br /> <br /> <br /> Good video about mustard-based sauce:<br /> https://www.youtube.com/watch?v=VFlcO9J9b0Y<br /> <br /> <br /> CEGUI is where the [http://www.phrases.org.uk/meanings/cut-the-mustard.html mustard is cut].<br /> <br /> <br /> Mustard-related quote:<br /> &lt;code lang=&quot;text&quot;&gt;<br /> There has been an association between the heat and piquancy of mustard and the zest and energy of people's behaviour. This dates back to at least 1672, when the term 'as keen as mustard' is first recorded. 'Up to mustard' or just 'mustard' means up to standard in the same way as 'up to snuff'. 'Cutting' has also long been used to mean 'exhibiting', as in the phrase 'cutting a fine figure'. Unless some actual evidence is found for the other proposed explanations, the derivation of 'cutting the mustard' as an alternative way of saying 'exhibiting one's high standards' is by far the most likely.<br /> &lt;/code&gt;<br /> <br /> <br /> <br /> <br /> <br /> <br /> Todo List: http://cegui.org.uk/wiki/Ident_TODO</div> Ident http://cegui.org/wiki/index.php?title=User:Ident&diff=5788 User:Ident 2016-08-21T21:11:32Z <p>Ident: </p> <hr /> <div>This page is dedicated to mustard. I could not have made it this far without you.<br /> <br /> Good video about mustard-based sauce:<br /> https://www.youtube.com/watch?v=VFlcO9J9b0Y<br /> <br /> CEGUI is where the [http://www.phrases.org.uk/meanings/cut-the-mustard.html mustard is cut].<br /> <br /> Mustard-related quote:<br /> &lt;code lang=&quot;text&quot;&gt;<br /> There has been an association between the heat and piquancy of mustard and the zest and energy of people's behaviour. This dates back to at least 1672, when the term 'as keen as mustard' is first recorded. 'Up to mustard' or just 'mustard' means up to standard in the same way as 'up to snuff'. 'Cutting' has also long been used to mean 'exhibiting', as in the phrase 'cutting a fine figure'. Unless some actual evidence is found for the other proposed explanations, the derivation of 'cutting the mustard' as an alternative way of saying 'exhibiting one's high standards' is by far the most likely.<br /> &lt;/code&gt;<br /> <br /> <br /> <br /> <br /> <br /> <br /> Todo List: http://cegui.org.uk/wiki/Ident_TODO</div> Ident http://cegui.org/wiki/index.php?title=Building_CEED_for_Windows&diff=5787 Building CEED for Windows 2016-08-21T14:11:50Z <p>Ident: /* Installing Python */</p> <hr /> <div>{{VersionBadge|0.8}}<br /> <br /> '''Written by Ident (Lukas Meindl) &amp; Nickenstein79 (Working correctly as of 11th June, 2014)'''<br /> <br /> The following instructions need to be done in the presented order and are created for the currently available version of CEED and could therefore be outdated at some point. Please notify us if you think this is outdated.<br /> <br /> <br /> == Installing the prerequisites ==<br /> <br /> When downloading/installing binaries, be sure to get the version which matches your version of visual studio, for instance choose the 32-bit and VC10 (visual studio 2010) versions of the binaries if that is what you are using to build. (or VC9 / VC11 / VC12 / ... if you are building with those.) If you use VC14 and not for example VC9 then be sure that the paths also match this. Don't get confused about the '''paths''' listed in this article, they are '''exemplatory''' and based on VC9. '''Do not mix VC9 binaries with VC10 or VC11, etc.''' We recommend using VC9 to build CEED because this one is assured to work.<br /> <br /> == Installing Python ==<br /> * Get Python 2.7.12 (32 bit version) for Windows and install it: <br /> https://www.python.org/downloads/<br /> * Add your Python install folder path to the PATH variable in your Windows environment variables, e.g.: C:Projects\Python27<br /> * Now add the Scripts folder to the PATH environment variable, e.g.: C:\Projects\Python27\Scripts &amp; C:\Projects\Python27\Tools\Scripts (depending on which of those folders exists in your install)<br /> * Open up a dos-command-prompt (cmd.exe) with admin rights and type &quot;python&quot; - See if you get something written into the console, such as &quot;Python 2.7.12 (default [...]&quot;, if this is the case then the install worked.<br /> <br /> == Installing pip ==<br /> * Install the latest pip distribution: First download get-pip.py: <br /> http://pip.readthedocs.org/en/latest/installing.html<br /> * Open up a dos-command-prompt (cmd.exe) with admin rights, change to the folder to which you downloaded &quot;get-pip.py&quot; by using the &quot;cd&quot; command, e.g.: cd &quot;A:/Downloads/Not porn&quot;<br /> * Type &quot;python get-pip.py&quot; and click enter in the dos-command-prompt<br /> * pip should now be installed<br /> * Afterwards enter &quot;pip&quot; and click enter. You should get some sort of information about pip now, if the install succeeded.<br /> <br /> <br /> == Installing pyside ==<br /> * Now you can install pyside easily with the following command: &quot;pip install -U PySide&quot;<br /> * You should get a console output notifying you of a successful install<br /> <br /> <br /> == Installing pyOpenGL ==<br /> * Install pyOpenGL on Windows with this installer: <br /> https://pypi.python.org/packages/any/P/PyOpenGL/PyOpenGL-3.0.2.win32.exe<br /> <br /> <br /> == Installing boost binaries ==<br /> * We also need to install boost. You can use an .exe file for this that will install the necessary binaries from this download page:<br /> http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0-build2/ <br /> (Be sure to get the version which matches the version of msvc you intend to build with. If use MSVC2008, then get the download with 'msvc-9.0' in the name, if you use MSVC2010 get the version with 'msvc-10.0' in the name, etc...)<br /> <br /> * Note : If you have multiple versions of MSVS on your machine, it is safe to install different versions of these boost distributions into the same root folder (e.g C:/boost_1_55_0/), as the *.h and *.hpp files are all identical, and the pre-compiled binary libs all get installed to sub-folders specific to different versions of msvc. (It is these folders and libs that we will be manually pointing cmake to in the next section.)<br /> <br /> <br /> == Configuring a PyCEGUI build with cmake == <br /> <br /> * Clone CEGUI v0-8 from the CEGUI repository to a new local folder from here:<br /> https://bitbucket.org/cegui/cegui/branch/v0-8<br /> e.g. to C:/cegui-v0-8<br /> * Check that the branch of your working directory is really v0-8 after cloning, if not then update to the latest v0-8 commit<br /> * Add the CEGUI dependencies folder into the CEGUI_v0_8 repository folder that you just cloned.<br /> * Open CMake and set the source code folder to your new local folder, e.g.: C:/cegui-v0-8 and the binaries to for example: C:/cegui-v0-8/build<br /> * Set the tick-boxes 'Advanced' and 'Grouped' to true. It makes it much easier to manage variables within cmake.<br /> <br /> ''[The following two steps are optional but will make finding boost libraries a lot more comfortable: If you, for whatever reason, can not or do not want to add or modify environment variables, you can directly specify all of the paths manually in CMake, by setting the variables to path values analogously to those used in the boost path examples below]''<br /> * Set the following windows environment variables:<br /> <br /> * 'BOOST_INCLUDEDIR' (Where the boost *.hpp files are)<br /> * 'BOOST_LIBRARYDIR' (Where the platform/compiler specific libs are)<br /> * 'BOOST_ROOT' (Set this to the root folder which contains the above two folders.)<br /> <br /> * Now click 'configure'. CMake will now auto-detect most of the build requirements. &lt;br /&gt;It 'should' now correctly auto-detect boost, However, if it failed to find any bost components, then you need to set them manually:<br /> <br /> These are directory-paths and file-paths to locations inside the boost and Python distributions that you installed in the previous steps.<br /> <br /> (Here are examples of what they are set to on my machine)<br /> <br /> === cmake Boost path examples ===<br /> ------------------------------------------------------------------------------------------------------------<br /> ** Boost_PYTHON_LIBRARY_DEBUG C:/boost_1_55_0/lib32-msvc-9.0/boost_python-vc90-mt-gd-1_55.lib<br /> ** Boost_PYTHON_LIBRARY_RELEASE C:/boost_1_55_0/lib32-msvc-9.0/boost_python-vc90-mt-1_55.lib<br /> ** Boost_SYSTEM_LIBRARY_DEBUG C:/boost_1_55_0/lib32-msvc-9.0/boost_system-vc90-mt-gd-1_55.lib<br /> ** Boost_SYSTEM_LIBRARY_RELEASE C:/boost_1_55_0/lib32-msvc-9.0/boost_system-vc90-mt-1_55.lib<br /> ** Boost_INCLUDE_DIR C:/boost_1_55_0<br /> ------------------------------------------------------------------------------------------------------------<br /> <br /> <br /> CMake may correctly auto-find the following Python variables, but it may fail. So be sure to inspect them, and if they were not found, you need to set them manually. <br /> <br /> Here are examples of mine:<br /> <br /> === cmake Python path examples ===<br /> ------------------------------------------------------------------------------------------------------------<br /> ** PYTHON_INCLUDE_DIR C:/Python27/include<br /> ** PYTHON_LIBRARY C:/Python27/libs/python27.lib<br /> ** PYTHON_EXECUTABLE C:/Python27/python.exe<br /> ------------------------------------------------------------------------------------------------------------<br /> <br /> <br /> * Unselect Building the CEGUI samples and select only OpenGL3 and OpenGL out of the available renderers to build<br /> * Select CEGUI_BUILD_PYTHON_MODULES so that this option is checked<br /> * Click 'configure' again, and then click 'generate', this should now work without errors and generate a solution-file in the binary folder that you specified as your build location.<br /> <br /> == Building PyCEGUI ==<br /> <br /> * Open the generated solution using MSVC and build the ALL_BUILDS project (You need 'Release' mode only)<br /> * Go for a very long walk along a very long beach. Building PyCEGUI &amp; PyCEGUI_OpenGLRenderer is very slow.<br /> <br /> <br /> == Setting up the PyCEGUI dll dependencies ==<br /> * Put the following dependencies of CEGUI into your build's bin folder, e.g.: C:/cegui-v0-8/build/bin<br /> ** From your CEGUI dependencies folder (e.g.: C:/cegui-v0-8/dependencies) :<br /> *** freetype.dll<br /> *** glew.dll<br /> *** pcre.dll<br /> ** From the boost binaries folder (e.g.: A:\Programs\boost_1_55_0\lib32-msvc-9.0 )<br /> *** boost_python-vc90-mt-1_55.dll (Or higher, depending on your version of MSVS &amp; the boost lib folder you are using.)<br /> <br /> <br /> == Cloning the CEED repository ==<br /> * clone the following CEED repository, and verify that you are on the v0-8 branch.<br /> https://bitbucket.org/cegui/ceed<br /> <br /> <br /> == Running CEED ==<br /> * Go to your CEED\bin folder (the bin folder inside the folder that you just cloned CEED to)<br /> * Edit runwrapper.bat so that the relative path CEGUI_BUILD_PATH matches the folder you just compiled PyCEGUI to<br /> * Run the batch file, and the CEED editor should be launched (if not, start the guide again. If it still fails, ask for help on the CEGUI forums)<br /> <br /> <br /> == Using Python-CEED-Migrate ==<br /> You can also use the ceed-migrate tool for convert your old cegui-datafiles to the newer formats. See this page for some examples of the parameters ceed-migrate takes: [[Using CEED-Migrate]]<br /> <br /> <br /> [[Using CEED-Migrate]] <br /> [[Category:HowTo]]<br /> [[Category:Tutorials]]</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5784 Vulkan Renderer Development 2016-06-20T22:05:00Z <p>Ident: /* State of development */</p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the problems/restrictions we need to consider? What should we keep in mind?<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development<br /> <br /> == References ==<br /> ===Links===<br /> <br /> * Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1<br /> * QuickRef: https://www.khronos.org/registry/vulkan/specs/1.0/refguide/Vulkan-1.0-web.pdf<br /> * Set of demos: https://github.com/SaschaWillems/Vulkan<br /> * Good old triangle demo: https://github.com/SaschaWillems/Vulkan/blob/master/triangle/triangle.cpp<br /> <br /> ===Books===<br /> * Not yet released, not sure if worth it: Vulkan Programming Guide by John M. Kessenich and Graham Sellers: https://www.amazon.co.uk/Vulkan-Programming-Guide-Official-Learning/dp/0134464540<br /> <br /> == CEGUI Vulkan Renderer : Thoughts ==<br /> <br /> === General considerations ===<br /> <br /> * As of now, CEGUI does not support any kind of internal threading. <br /> * If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.<br /> * Would any sort of threading for CEGUI's logic and rendering provide an advantage? In the end, the rendering would always have to wait for the logic to be processed but they could be started at separate times.<br /> <br /> === Points to achieve optimal performance with the CEGUI Vulkan Renderer ===<br /> * Considering that Vulkan as one of its main benefits features threading support, we want to research whether this would be worth it for CEGUI default branch.<br /> * As always, we need to keep batching low. Is there anything provided in Vulkan that allows us to batch things better? We used to make the VBOs as large as possible, which was a notable advantage even though we rendered the quads in separate draw calls. Can this be done better?<br /> <br /> == ToDo ==<br /> <br /> == State of development ==<br /> Nvidia C++ Wrapper for Vulkan will be used. This Wrapper contains of a single header file. For CEGUI this means, that the single header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer. For further building informations, please look into the repository:<br /> * Repo link: https://github.com/nvpro-pipeline/vkcpp<br /> * Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5783 Vulkan Renderer Development 2016-06-20T22:04:42Z <p>Ident: /* References */</p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the problems/restrictions we need to consider? What should we keep in mind?<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development<br /> <br /> == References ==<br /> ===Links===<br /> <br /> * Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1<br /> * QuickRef: https://www.khronos.org/registry/vulkan/specs/1.0/refguide/Vulkan-1.0-web.pdf<br /> * Set of demos: https://github.com/SaschaWillems/Vulkan<br /> * Good old triangle demo: https://github.com/SaschaWillems/Vulkan/blob/master/triangle/triangle.cpp<br /> <br /> ===Books===<br /> * Not yet released, not sure if worth it: Vulkan Programming Guide by John M. Kessenich and Graham Sellers: https://www.amazon.co.uk/Vulkan-Programming-Guide-Official-Learning/dp/0134464540<br /> <br /> == CEGUI Vulkan Renderer : Thoughts ==<br /> <br /> === General considerations ===<br /> <br /> * As of now, CEGUI does not support any kind of internal threading. <br /> * If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.<br /> * Would any sort of threading for CEGUI's logic and rendering provide an advantage? In the end, the rendering would always have to wait for the logic to be processed but they could be started at separate times.<br /> <br /> === Points to achieve optimal performance with the CEGUI Vulkan Renderer ===<br /> * Considering that Vulkan as one of its main benefits features threading support, we want to research whether this would be worth it for CEGUI default branch.<br /> * As always, we need to keep batching low. Is there anything provided in Vulkan that allows us to batch things better? We used to make the VBOs as large as possible, which was a notable advantage even though we rendered the quads in separate draw calls. Can this be done better?<br /> <br /> == ToDo ==<br /> <br /> == State of development ==<br /> Nvidia C++ Wrapper for Vulkan will be used. This Wrapper contains of a single header file. For CEGUI this means, that the single header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer. For further building informations, please look into the repository:<br /> <br /> - Repo link: https://github.com/nvpro-pipeline/vkcpp<br /> <br /> - Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5782 Vulkan Renderer Development 2016-06-20T22:01:14Z <p>Ident: /* Links */</p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the problems/restrictions we need to consider? What should we keep in mind?<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development<br /> <br /> == References ==<br /> ===Links===<br /> <br /> *Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1<br /> *QuickRef: https://www.khronos.org/registry/vulkan/specs/1.0/refguide/Vulkan-1.0-web.pdf<br /> <br /> ===Books===<br /> *Vulkan Programming Guide by John M. Kessenich and Graham Sellers: https://www.amazon.co.uk/Vulkan-Programming-Guide-Official-Learning/dp/0134464540<br /> <br /> == CEGUI Vulkan Renderer : Thoughts ==<br /> <br /> === General considerations ===<br /> <br /> * As of now, CEGUI does not support any kind of internal threading. <br /> * If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.<br /> * Would any sort of threading for CEGUI's logic and rendering provide an advantage? In the end, the rendering would always have to wait for the logic to be processed but they could be started at separate times.<br /> <br /> === Points to achieve optimal performance with the CEGUI Vulkan Renderer ===<br /> * Considering that Vulkan as one of its main benefits features threading support, we want to research whether this would be worth it for CEGUI default branch.<br /> * As always, we need to keep batching low. Is there anything provided in Vulkan that allows us to batch things better? We used to make the VBOs as large as possible, which was a notable advantage even though we rendered the quads in separate draw calls. Can this be done better?<br /> <br /> == ToDo ==<br /> <br /> == State of development ==<br /> Nvidia C++ Wrapper for Vulkan will be used. This Wrapper contains of a single header file. For CEGUI this means, that the single header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer. For further building informations, please look into the repository:<br /> <br /> - Repo link: https://github.com/nvpro-pipeline/vkcpp<br /> <br /> - Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5781 Vulkan Renderer Development 2016-06-20T21:47:35Z <p>Ident: </p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the problems/restrictions we need to consider? What should we keep in mind?<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development<br /> <br /> == References ==<br /> ===Links===<br /> <br /> *Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1<br /> <br /> ===Books===<br /> *Vulkan Programming Guide by John M. Kessenich and Graham Sellers: https://www.amazon.co.uk/Vulkan-Programming-Guide-Official-Learning/dp/0134464540<br /> <br /> == CEGUI Vulkan Renderer : Thoughts ==<br /> <br /> === General considerations ===<br /> <br /> * As of now, CEGUI does not support any kind of internal threading. <br /> * If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.<br /> * Would any sort of threading for CEGUI's logic and rendering provide an advantage? In the end, the rendering would always have to wait for the logic to be processed but they could be started at separate times.<br /> <br /> === Points to achieve optimal performance with the CEGUI Vulkan Renderer ===<br /> * Considering that Vulkan as one of its main benefits features threading support, we want to research whether this would be worth it for CEGUI default branch.<br /> * As always, we need to keep batching low. Is there anything provided in Vulkan that allows us to batch things better? We used to make the VBOs as large as possible, which was a notable advantage even though we rendered the quads in separate draw calls. Can this be done better?<br /> <br /> == ToDo ==<br /> <br /> == State of development ==<br /> Nvidia C++ Wrapper for Vulkan will be used. This Wrapper contains of a single header file. For CEGUI this means, that the single header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer. For further building informations, please look into the repository:<br /> <br /> - Repo link: https://github.com/nvpro-pipeline/vkcpp<br /> <br /> - Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5780 Vulkan Renderer Development 2016-06-20T21:10:08Z <p>Ident: /* Improving CEGUI with the Vulkan Renderer */</p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the problems/restrictions we need to consider? What should we keep in mind?<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development<br /> <br /> == References ==<br /> ===Links===<br /> <br /> *Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1<br /> <br /> ===Books===<br /> *Vulkan Programming Guide by John M. Kessenich and Graham Sellers: https://www.amazon.co.uk/Vulkan-Programming-Guide-Official-Learning/dp/0134464540<br /> <br /> == CEGUI Vulkan Renderer : Thoughts ==<br /> <br /> === General considerations ===<br /> <br /> * As of now, CEGUI does not support any kind of internal threading. <br /> * If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.<br /> * Would any sort of threading for CEGUI's logic and rendering provide an advantage? In the end, the rendering would always have to wait for the logic to be processed but they could be started at separate times.<br /> <br /> === Points to achieve optimal performance with the CEGUI Vulkan Renderer ===<br /> * Considering that Vulkan as one of its main benefits features threading support, we want to research whether this would be worth it for CEGUI default branch.<br /> * As always, we need to keep batching low. Is there anything provided in Vulkan that allows us to batch things better? We used to make the VBOs as large as possible, which was a notable advantage even though we rendered the quads in separate draw calls. Can this be done better?<br /> <br /> == ToDo ==<br /> <br /> == State of development ==<br /> Nvidia C++ Wrapper for Vulkan will be used. This Wrapper contains of a single header file. For CEGUI this means, that the single header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer. For further building informations, please look into the repository:<br /> <br /> - Repo link: https://github.com/nvpro-pipeline/vkcpp<br /> <br /> - Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml<br /> <br /> <br /> ----<br /> [[User:Xxarthurxx|Xxarthurxx]] ([[User talk:Xxarthurxx|talk]]) 15:49, 20 June 2016 (UTC)</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5773 Vulkan Renderer Development 2016-06-19T20:19:43Z <p>Ident: </p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the problems/restrictions we need to consider? What should we keep in mind?<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development<br /> <br /> == Vulkan link collection ==<br /> <br /> <br /> == CEGUI Vulkan Renderer : Thoughts ==<br /> <br /> === General considerations ===<br /> <br /> * As of now, CEGUI does not support any kind of internal threading. <br /> * If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.<br /> * Would any sort of threading for CEGUI's logic and rendering provide an advantage? In the end, the rendering would always have to wait for the logic to be processed but they could be started at separate times.<br /> <br /> === Maximising the CEGUI Vulkan Renderer performance ===<br /> * Considering that Vulkan as one of its main benefits features threading support, we might want to consider if this would be worth it for CEGUI default branch or if this even would have any benefits.<br /> * As always, we need to keep batching low. Is there anything provided in Vulkan that allows us to batch things better? We used to make the VBOs as large as possible, which was a notable advantage even though we rendered the quads in separate draw calls. Can this be done better?<br /> <br /> == ToDo ==<br /> <br /> == State of development ==<br /> * We will use the Nvidia C++ Wrapper for Vulkan by creating the header file based on the Vulkan registry. This header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer.<br /> ** Repo: https://github.com/nvpro-pipeline/vkcpp<br /> ** Vulkan registriy: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5772 Vulkan Renderer Development 2016-06-19T07:39:44Z <p>Ident: </p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the problems/restrictions we need to consider? What should we keep in mind?<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development<br /> <br /> == Vulkan link collection ==<br /> <br /> <br /> == CEGUI Vulkan Renderer : Thoughts ==<br /> <br /> === General considerations ===<br /> <br /> * As of now, CEGUI does not support any kind of internal threading. <br /> * If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.<br /> * Would any sort of threading for CEGUI's logic and rendering provide an advantage? In the end, the rendering would always have to wait for the logic to be processed but they could be started at separate times.<br /> <br /> === Maximising the CEGUI Vulkan Renderer performance ===<br /> * Considering that Vulkan as one of its main benefits features threading support, we might want to consider if this would be worth it for CEGUI default branch or if this even would have any benefits.<br /> * As always, we need to keep batching low. Is there anything provided in Vulkan that allows us to batch things better? We used to make the VBOs as large as possible, which was a notable advantage even though we rendered the quads in separate draw calls. Can this be done better?<br /> <br /> == ToDo ==<br /> <br /> == State of development ==</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5771 Vulkan Renderer Development 2016-06-19T07:27:53Z <p>Ident: </p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the problems/restrictions we need to consider? What should we keep in mind?<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development<br /> <br /> == Vulkan link collection ==<br /> <br /> <br /> == CEGUI Vulkan Renderer : Thoughts ==<br /> <br /> === General considerations ===<br /> <br /> * CEGUI does not support any kind of internal threading. <br /> * If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.<br /> <br /> === Maximising the CEGUI Vulkan Renderer performance ===<br /> * Separate threads for logic and rendering processing would be optimal for CEGUI default branch.<br /> * As always, we need to keep batching low.<br /> <br /> == ToDo ==<br /> <br /> == State of development ==</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5770 Vulkan Renderer Development 2016-06-19T07:21:19Z <p>Ident: </p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the caveats? What should we keep in mind<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Keep track of the state of the development</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5769 Vulkan Renderer Development 2016-06-19T07:21:03Z <p>Ident: </p> <hr /> <div>== Purpose of this document ==<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the caveats? What should we keep in mind<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Write about the state of the development</div> Ident http://cegui.org/wiki/index.php?title=Vulkan_Renderer_Development&diff=5768 Vulkan Renderer Development 2016-06-19T07:20:18Z <p>Ident: Created page with &quot;Purpose of this document: * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development * Make a list of specifi...&quot;</p> <hr /> <div>Purpose of this document:<br /> * Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development<br /> * Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:<br /> ** What are the caveats? What should we keep in mind<br /> ** How can we maximize Vulkan performance?<br /> ** What are the restrictions? How could we get around them?<br /> * Write about the state of the development</div> Ident http://cegui.org/wiki/index.php?title=Release_Checklist&diff=5767 Release Checklist 2016-06-08T06:51:37Z <p>Ident: /* CEGUI */</p> <hr /> <div>== CEGUI ==<br /> <br /> This page is mainly for the CEGUI team and serves as a checklist to avoid forgetting steps when making a CEGUI release.<br /> <br /> * First check that the local repo is completely up-to-date and check that no unversioned files or uncommited changes are existing.<br /> * Bump release version in CMakeLists.txt <br /> * Bump ABI version in CMakeLists.txt<br /> * Add change log entries from https://bitbucket.org/cegui/cegui/issues?milestone=0.8.4&amp;status=resolved (change the version in the link) to doc/doxygen/changelog.dox<br /> * Regenerate generated code/other files (i.e regen bindings etc)<br /> * Create mercurial tag for release<br /> * Make source packages.<br /> * Build docs.<br /> * Make docs packages.<br /> * Upload!<br /> * Make sure the new release is listed as the latest release on sourceforge, you can do this by clicking the &quot;i&quot; icon next to the file and selecting all operating systems --&gt; SAVE (takes 3 mins to be updated)<br /> * For 0.8.5 Release announce in the docs and in the Release news that this requires CMAke 2.8.11 minimum &lt;-- what happened to this?<br /> * Create a release on the drupal page - http://cegui.org.uk/node/add/release<br /> * Make sure N+1 version is in bitbucket issue-tracker or add it - also make it the default (bitbucket repo -&gt; Settings -&gt; Issues -&gt; Versions)<br /> * Generate docs and upload to static.cegui.org.uk, see http://bitbucket.org/cegui/docs-builder<br /> * Update the server's htaccess in the static API docs folder to redirect to the latest minor version<br /> * Post to twitter<br /> * Post to google+<br /> <br /> == CEED ==<br /> <br /> * First check that the local repo is completely up-to-date and check that no unversioned files or uncommited changes are existing.<br /> * Bump release version in ceed/version.py<br /> * Make source packages.<br /> * Build docs.<br /> * Upload!<br /> * Create a release on the drupal page - http://cegui.org.uk/node/add/release<br /> * Make sure N+1 version is in bitbucket issue-tracker or add it</div> Ident http://cegui.org/wiki/index.php?title=Release_Checklist&diff=5766 Release Checklist 2016-05-31T16:06:10Z <p>Ident: /* CEGUI */</p> <hr /> <div>== CEGUI ==<br /> <br /> This page is mainly for the CEGUI team and serves as a checklist to avoid forgetting steps when making a CEGUI release.<br /> <br /> * First check that the local repo is completely up-to-date and check that no unversioned files or uncommited changes are existing.<br /> * Bump release version in CMakeLists.txt <br /> * Bump ABI version in CMakeLists.txt<br /> * Add change log entries from https://bitbucket.org/cegui/cegui/issues?milestone=0.8.4&amp;status=resolved (change the version in the link) to doc/doxygen/changelog.dox<br /> * Regenerate generated code/other files (i.e regen bindings etc)<br /> * Create mercurial tag for release<br /> * Make source packages.<br /> * Build docs.<br /> * Make docs packages.<br /> * Upload!<br /> * Make sure the new release is listed as the latest release on sourceforge, you can do this by clicking the &quot;i&quot; icon next to the file and selecting all operating systems --&gt; SAVE (takes 3 mins to be updated)<br /> * For 0.8.5 Release announce in the docs and in the Release news that this requires CMAke 0.8.11 minimum &lt;-- what happened to this?<br /> * Create a release on the drupal page - http://cegui.org.uk/node/add/release<br /> * Make sure N+1 version is in bitbucket issue-tracker or add it - also make it the default (bitbucket repo -&gt; Settings -&gt; Issues -&gt; Versions)<br /> * Generate docs and upload to static.cegui.org.uk, see http://bitbucket.org/cegui/docs-builder<br /> * Update the server's htaccess in the static API docs folder to redirect to the latest minor version<br /> * Post to twitter<br /> * Post to google+<br /> <br /> == CEED ==<br /> <br /> * First check that the local repo is completely up-to-date and check that no unversioned files or uncommited changes are existing.<br /> * Bump release version in ceed/version.py<br /> * Make source packages.<br /> * Build docs.<br /> * Upload!<br /> * Create a release on the drupal page - http://cegui.org.uk/node/add/release<br /> * Make sure N+1 version is in bitbucket issue-tracker or add it</div> Ident http://cegui.org/wiki/index.php?title=Building_CEGUI_for_Ogre_/_OgreRenderer&diff=5765 Building CEGUI for Ogre / OgreRenderer 2016-05-01T10:48:58Z <p>Ident: /* A snapshot of using CMake */</p> <hr /> <div>{{VersionBadge|0.7}}<br /> {{VersionBadge|0.8}}<br /> <br /> = General =<br /> Since Ogre version 1.7 the CEGUI library isn't an Ogre dependency anymore and was replaced by a very simple UI overlay mainly used for the Ogre demos. Users now have to compile the CEGUI library against Ogre on their own, to use CEGUI together with Ogre. This guide has been created to help users building CEGUI against Ogre. We recommend CMake 2.8.X for all version of CEGUI at the moment.<br /> <br /> <br /> == Tested versions ==<br /> * CEGUI 0.8.X and v0-8 branch supports basic configurations of Ogre 1.7 and 1.8 and 1.9. Other versions and specific configurations (such as using boost) are supported but might require additional steps from your side (see below).<br /> * CEGUI 0.8.5 (not yet released at the point of writing) and v0-8 branch support Ogre 2.0 and 2.1 with OGL3+ Renderer only.<br /> * CEGUI v-0 branch and releases starting with 0.8.4 will support Ogre 1.7, 1.8, 1.9. They will also be updated from time to time to support the current version of Ogre default branch (right now it works with the Ogre default branch version of 6th Jan. 2014, including Ogre's OGL3 Renderer)<br /> * CEGUI default branch (unstable) contains an entirely changed but mostly functional OgreRenderer that should work with 1.7-2.0 but might need to be tested further.<br /> <br /> == Environment variables for CMake ==<br /> If you installed Ogre (or OIS or Boost), then certain environment variables might have been set on your computer already, helping CMake find your Ogre version (or OIS or boost). Here are some examplatory paths from my computer:<br /> * OIS_HOME - A:/Libraries<br /> * OGRE_HOME - A:/Libraries/OgreFromSourceCode (alternatively, if you use an SDK and do not compile from source, for example use: A:/Libraries/OgreSDK )<br /> * OGRE_SDK - A:/Libraries/OgreFromSourceCode/build (alternatively, if you use an SDK and do not compile from source, for example use: A:/Libraries/OgreSDK )<br /> * Boost looks for C:/Boost and if nothing is there it looks for BOOST_ROOT env variable: http://stackoverflow.com/a/8770217/3144964<br /> <br /> <br /> == How to acquire the CEGUI source code ==<br /> Here are all the links you will need to build CEGUI and its dependencies - which is the recommended approach:<br /> * Visit the [http://static.cegui.org.uk/docs/current/downloading.html reference manual] for instructions on obtaining the latest CEGUI source code (be sure to be on a '''stable branch''', for example v0-8) - this is the recommended approach as it will include the latest fixes.<br /> '''Note''': If the branch version's source code seems to be unstable or not working, you can try the [http://sourceforge.net/projects/crayzedsgui/files/latest/download?source=files latest stable release] or select a Release version from the [http://cegui.org.uk/download downloads page].<br /> * '''Additionally''' to the CEGUI source code you will need [http://sourceforge.net/projects/crayzedsgui/files/CEGUI%20Mk-2%20Dependencies/0.8.x/cegui-deps-0.8.x-src.zip/download the source code of the CEGUI dependencies]. Download it and build the dependencies on your system (debug &amp; release modes are common and are recommended to be built). You can use this document as guideline for the building process if needed: [http://static.cegui.org.uk/docs/current/building_deps.html Building dependencies]. Move the &quot;dependencies&quot; folder, which should have been created during the build process and should contain the headers, .lib files and .dll files, into your CEGUI main folder, so that it will co-exist next to the folders &quot;bin&quot;, &quot;cegui&quot;, &quot;datafiles&quot; etc.<br /> <br /> <br /> == A snapshot of using CMake ==<br /> CMake has a great GUI that allows to change your project's configuration by specifiying the dependencies, renderers and parsers you want. You need to fill out the paths to all files and folders the dependencies require.<br /> &lt;div class=&quot;toccolours mw-collapsible mw-collapsed&quot; style=&quot;width:80%&quot;&gt;<br /> ''' Expand this to see an example on how to utilise the filters/search in CMake and how to set the Ogre variables'''<br /> &lt;div class=&quot;mw-collapsible-content&quot;&gt;<br /> {{[[File:Ogrescreen.png|How to set CMake variables]]}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> <br /> <br /> <br /> &lt;div class=&quot;toccolours mw-collapsible mw-collapsed&quot; style=&quot;width:80%&quot;&gt;<br /> ''' Expand this for an example of fully set boost variables based on a boost binary release. Reminder: For Ogre you only need thze include folder and the &quot;system&quot; and &quot;thread&quot; libraries.'''<br /> &lt;div class=&quot;mw-collapsible-content&quot;&gt;<br /> {{[[File:Boostconfig.png|How to set CMake Boost variables]]}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> == Optional: If you want to use CMake to set up your own project ==<br /> We offer a FindCEGUI.cmake file in our repository [https://bitbucket.org/cegui/cegui/src/b975a6885624277808189ac3d503dea7ba82b1a7/cmake/FindCEGUI.cmake?at=v0-8&amp;fileviewer=file-view-default *here*] that you may want to use. An example CMake file can be found in this post: http://www.ogre3d.org/addonforums/viewtopic.php?f=34&amp;t=30480&amp;p=103432#p103432<br /> <br /> = Step-by-step guide =<br /> <br /> <br /> '''Important:''' If you make a mistake such as confusing Debug and Release paths and you already clicked &quot;Configure&quot; again, then please trigger &quot;Delete Cache&quot; (File-&gt;Delete Cache) in Cmake and start from 0 again!<br /> Also we recommend you to switch on the &quot;Advanced&quot; and &quot;Grouped&quot; checkboxes.<br /> * 1. Get the appropriate '''CEGUI''' version from the CEGUI download page or get the very latest CEGUI version from the SVN repository (see links and info above).<br /> <br /> * 2. Get the latest '''Ogre''' version. If you are build it yourself (recommended), you will need to compile/link it first in the modes you want to use (Debug/Release) to get Ogre's .lib and .dll files ready for CEGUI.<br /> <br /> <br /> == Steps for Microsoft Visual Studio ==<br /> <br /> <br /> <br /> ===CEGUI 0.8.x ===<br /> * 3. Open the CMake GUI Utility<br /> * 4. Set the '''source path''' to the directory where your CEGUI files are located (e.g. C:/CEGUI - contains folders like 'cegui' 'cmake' 'datafiles', etc. )<br /> * 5. Set the '''build path''' to the directory where you want CMake to generate your build configuration(e.g. C:/CEGUI/build)<br /> * 6. Press the '''Configure''' button. At this stage CMake will ask you for a generator for this project(e.g. Visual Studio 10) and then will try to find the required packages needed by CEGUI. Please note that you should have the CEGUI dependencies built and installed in your CEGUI_ROOT directory. E.g. if your CEGUI directory is C:/CEGUI then the dependencies would be expected to be in C:/CEGUI/dependencies by default<br /> * 7. Search the '''CEGUI_BUILD_RENDERER_OGRE''' boolean variable in the list of CMake GUI Utility and set the value to TRUE by clicking on the checkbox. <br /> * 8. Check if OGRE and OIS (and boost - '''IF''' your Ogre version was built with boost as dependency) were found by cmake. (For more information about how boost can be found by CMake please see the Cmake docu: http://www.cmake.org/cmake/help/git-master/module/FindBoost.html) Look through the CMake GUI Utility output to see if there is a message like 'Could NOT find OGRE'. '''If both Ogre and OIS (and boost) were found (and reference the right version in case you got multiple ones) you can jump to step #9 now'''. &lt;span style=&quot;color:#3333AA&quot;&gt; If this was not the case it means that you either have not set the environment variables for Ogre (OGRE_SDK and OGRE_HOME) and OIS (OIS_HOME) at all, or that you have not set them correctly. You can try to fix this and click configure again to see if it works. If it does you can skip to #9. If it does not work then set the paths yourself.<br /> <br /> &lt;div class=&quot;toccolours mw-collapsible mw-collapsed&quot; style=&quot;width:80%&quot;&gt;<br /> ''' Expand this field to get a very elaborate explanation on the CMake settings for Ogre, OIS and Boost including examplatory paths: '''<br /> &lt;div class=&quot;mw-collapsible-content&quot;&gt;<br /> {{BUILD_OGRE_FOR_CEGUI_0_8_HELP}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> * 9 After you changed all the CMake settings to your liking (deactivating/activating Image codecs, parsers, renderer, etc.) you have to rerun '''Configure'''. You need to do this in order to save your additional variables in the CMake cache and in the build configuration.<br /> * 10 Press the '''Generate''' button. At this stage CMake will read your build configuration and then generate a solution using your selected generator.<br /> * 11 Go to the cegui build directory and open the Visual Studio solution '''cegui.sln'''<br /> * 12 Build the entire cegui solution.<br /> * 13 (Optional) Start the SampleBrowser to see if the samples work correctly (don't forget to copy the created samples.xml from build/datafiles/samples to your datafiles/samples folder so that the SampleBrowser can find the samples you want to use. Also make sure you copied all the dlls that your setup requires to the foldering containing the SampleBrowser.exe and in Visual Studio: for Project-&gt;Properties-&gt;Debugging-&gt;Working Directory set the value to $(OutDir) )<br /> <br /> ===CEGUI 0.7.x ===<br /> * 3. In your CEGUI folder there should be a folder called &quot;'''projects'''&quot; with a subfolder called &quot;'''premake'''&quot;. It is recommended to use the [https://sourceforge.net/projects/crayzedsgui/files/CEGUI%20Mk-2/premake/premake-3.7-custom.zip/download custom premake version of CEGUI]. Otherwise you can get version 3.6 or 3.7 of premake. Once you have premake extract the '''premake.exe''' file into the said folder.<br /> <br /> * 4. Open '''config.lua''' in the premake folder and edit the Ogre and OIS paths accordingly, so that they will point to the dependency files. In my case for example the 2 lines look like this (having the OGRE and CEGUI main folders on the same level):<br /> <br /> &lt;pre&gt;<br /> OGRE_PATHS = { &quot;../OGRE&quot;, &quot;include/OGRE&quot;, &quot;lib&quot; }<br /> OIS_PATHS = { &quot;../OGRE&quot;, &quot;include/OIS&quot;, &quot;lib&quot; }<br /> &lt;/pre&gt;<br /> <br /> '''Note:''' Remember to use forward slashes here! Just copying the paths from the Windows explorer will give you backward slashes. Replace them!<br /> <br /> Next, set all Renderers you do not need to &quot;false&quot;, in this case we will only need ''OGRE_RENDERER''. You can also set all samples to false, except maybe ''SAMPLES_OGRE'' if you want to compile those.<br /> <br /> '''Important:''' Since Ogre 1.7 the &quot;boost&quot; library is a new dependency of OGRE. If you are unsure if your Ogre version needs boost, you might want to check if there is a boost folder in your Ogre main folder. In case your Ogre version makes use of boost, you will additionally add boost to the extra paths of CEGUIOgreRenderer, in my case it looks like this:<br /> &lt;pre&gt;<br /> CEGUI_EXTRA_PATHS = { <br /> { &quot;../OGRE/boost_1_42&quot;, &quot;&quot;, &quot;lib&quot;, &quot;CEGUIOgreRenderer&quot; }<br /> }<br /> &lt;/pre&gt;<br /> <br /> * 5. Next, we create our Visual Studio Projects - Execute '''build_vs2008.bat''' to create a Visual Studio 2008 project or execute any other .bat file for your respective compiler version.<br /> <br /> * 6. This should create '''CEGUI.sln''' in the premake folder. Open it.<br /> <br /> * 7. If you have the Ogre lib files seperated into a Debug and Release folder, you will have to change the path in the '''Linker''' settings of the project so they will point to the '''lib/Debug''' or '''lib/Release''' folder for each configuration respectively.<br /> <br /> * 8. '''Build''' the '''CEGUIOgreRenderer''' in Debug and Release mode.<br /> * 9. Now that you have built the .dll files and .lib files for CEGUI by yourself, you only have to change the linker settings of your project so that the needed .lib files and their folder paths are included there. Also you might want to include the dll's into a folder where your executable application will find them (for example just the folder your executable starts from). Finally remember to set the CEGUI '''include''' directory (for example &quot;..\..\CEGUI\cegui\include\cegui&quot;) inside your C++ project settings.<br /> <br /> <br /> == Steps for GNU and Unix-like environments ==<br /> ===CEGUI 0.8.x ===<br /> <br /> Going to the extracted CEGUI source directory and running the following commands seems to work. It also seems that the configurations are not used anymore. (noobnote: don't include the dollar-signs at the start of the lines. They represent the prompt.):<br /> <br /> &lt;pre&gt;<br /> $ mkdir build &amp;&amp; cd build<br /> <br /> $ export NUMBER_OF_CORES=`cat /proc/cpuinfo | grep &quot;cpu cores&quot; | uniq | awk '{print $4}'`<br /> <br /> $ cmake -D CMAKE_BUILD_TYPE=Release ..<br /> <br /> $ make -j$NUMBER_OF_CORES<br /> <br /> $ sudo make install<br /> <br /> $ sudo ldconfig<br /> &lt;/pre&gt;<br /> <br /> <br /> If everything worked out, you now have CEGUI up and running!<br /> <br /> ===CEGUI 0.7.x ===<br /> Going to the extracted CEGUI source directory and running the following commands seems to work (noobnote: don't include the dollar-signs at the start of the lines. They represent the prompt.):<br /> <br /> &lt;pre&gt;<br /> $ ./bootstrap &amp;&amp; mkdir build &amp;&amp; cd build<br /> <br /> $ export NUMBER_OF_CORES=`cat /proc/cpuinfo | grep &quot;cpu cores&quot; | uniq | awk '{print $4}'`<br /> <br /> $ ../configure &amp;&amp; make -j$NUMBER_OF_CORES<br /> <br /> $ sudo make install<br /> <br /> $ sudo ldconfig<br /> &lt;/pre&gt;<br /> <br /> <br /> If everything worked out, you now have CEGUI up and running!<br /> <br /> <br /> ==Errors==<br /> *CEGUI Exception - bad allocation<br /> This error is rather cryptic in its meaning and can occur when linking debug libraries to release libraries or vice-versa. Simply check all CMAKE paths to see if you accidently mixed up the debug and release paths for libraries (OIS, Ogre). If you did not then this might be due to a now-fixed error in 0.8.3. If this is the case you will have to change the .lib file to the OgreMain_d.lib version in Debug mode. Otherwise delete the cache (see mention above) and restart the CMake configuration.<br /> <br /> <br /> ==Questions==<br /> Feel free to edit this page using your CEGUI forum account login if you want to append something. If you have questions you can ask in the CEGUI forum or join our IRC channel #cegui on irc.freenode.net - <br /> In case you need help building Ogre in general, I'd recommend reading for example [http://blog.tidalware.com/2009/08/building-ogre-with-visual-studio/ this short guide (might be outdated though)].<br /> <br /> <br /> For the Ogre-wiki version of this article you can also check this link: http://www.ogre3d.org/tikiwiki/tiki-index.php?page=Building+CEGUI<br /> <br /> [[Category:HowTo]]</div> Ident http://cegui.org/wiki/index.php?title=Building_CEGUI_for_Ogre_/_OgreRenderer&diff=5764 Building CEGUI for Ogre / OgreRenderer 2016-05-01T10:48:45Z <p>Ident: /* Optional: If you want to use CMake to set up your own project */</p> <hr /> <div>{{VersionBadge|0.7}}<br /> {{VersionBadge|0.8}}<br /> <br /> = General =<br /> Since Ogre version 1.7 the CEGUI library isn't an Ogre dependency anymore and was replaced by a very simple UI overlay mainly used for the Ogre demos. Users now have to compile the CEGUI library against Ogre on their own, to use CEGUI together with Ogre. This guide has been created to help users building CEGUI against Ogre. We recommend CMake 2.8.X for all version of CEGUI at the moment.<br /> <br /> <br /> == Tested versions ==<br /> * CEGUI 0.8.X and v0-8 branch supports basic configurations of Ogre 1.7 and 1.8 and 1.9. Other versions and specific configurations (such as using boost) are supported but might require additional steps from your side (see below).<br /> * CEGUI 0.8.5 (not yet released at the point of writing) and v0-8 branch support Ogre 2.0 and 2.1 with OGL3+ Renderer only.<br /> * CEGUI v-0 branch and releases starting with 0.8.4 will support Ogre 1.7, 1.8, 1.9. They will also be updated from time to time to support the current version of Ogre default branch (right now it works with the Ogre default branch version of 6th Jan. 2014, including Ogre's OGL3 Renderer)<br /> * CEGUI default branch (unstable) contains an entirely changed but mostly functional OgreRenderer that should work with 1.7-2.0 but might need to be tested further.<br /> <br /> == Environment variables for CMake ==<br /> If you installed Ogre (or OIS or Boost), then certain environment variables might have been set on your computer already, helping CMake find your Ogre version (or OIS or boost). Here are some examplatory paths from my computer:<br /> * OIS_HOME - A:/Libraries<br /> * OGRE_HOME - A:/Libraries/OgreFromSourceCode (alternatively, if you use an SDK and do not compile from source, for example use: A:/Libraries/OgreSDK )<br /> * OGRE_SDK - A:/Libraries/OgreFromSourceCode/build (alternatively, if you use an SDK and do not compile from source, for example use: A:/Libraries/OgreSDK )<br /> * Boost looks for C:/Boost and if nothing is there it looks for BOOST_ROOT env variable: http://stackoverflow.com/a/8770217/3144964<br /> <br /> <br /> == How to acquire the CEGUI source code ==<br /> Here are all the links you will need to build CEGUI and its dependencies - which is the recommended approach:<br /> * Visit the [http://static.cegui.org.uk/docs/current/downloading.html reference manual] for instructions on obtaining the latest CEGUI source code (be sure to be on a '''stable branch''', for example v0-8) - this is the recommended approach as it will include the latest fixes.<br /> '''Note''': If the branch version's source code seems to be unstable or not working, you can try the [http://sourceforge.net/projects/crayzedsgui/files/latest/download?source=files latest stable release] or select a Release version from the [http://cegui.org.uk/download downloads page].<br /> * '''Additionally''' to the CEGUI source code you will need [http://sourceforge.net/projects/crayzedsgui/files/CEGUI%20Mk-2%20Dependencies/0.8.x/cegui-deps-0.8.x-src.zip/download the source code of the CEGUI dependencies]. Download it and build the dependencies on your system (debug &amp; release modes are common and are recommended to be built). You can use this document as guideline for the building process if needed: [http://static.cegui.org.uk/docs/current/building_deps.html Building dependencies]. Move the &quot;dependencies&quot; folder, which should have been created during the build process and should contain the headers, .lib files and .dll files, into your CEGUI main folder, so that it will co-exist next to the folders &quot;bin&quot;, &quot;cegui&quot;, &quot;datafiles&quot; etc.<br /> <br /> <br /> == A snapshot of using CMake ==<br /> CMake has a great GUI that allows to change your project's configuration by specifiying the dependencies, renderers and parsers you want. You need to fill out the paths to all files and folders the dependencies require.<br /> &lt;div class=&quot;toccolours mw-collapsible mw-collapsed&quot; style=&quot;width:80%&quot;&gt;<br /> ''' Expand this to see an example on how to utilise the filters/search in CMake and how to set the Ogre variables'''<br /> &lt;div class=&quot;mw-collapsible-content&quot;&gt;<br /> {{[[File:Ogrescreen.png|How to set CMake variables]]}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> == Optional: If you want to use CMake to set up your own project ==<br /> We offer a FindCEGUI.cmake file in our repository [https://bitbucket.org/cegui/cegui/src/b975a6885624277808189ac3d503dea7ba82b1a7/cmake/FindCEGUI.cmake?at=v0-8&amp;fileviewer=file-view-default *here*] that you may want to use. An example CMake file can be found in this post: http://www.ogre3d.org/addonforums/viewtopic.php?f=34&amp;t=30480&amp;p=103432#p103432<br /> <br /> = Step-by-step guide =<br /> <br /> <br /> '''Important:''' If you make a mistake such as confusing Debug and Release paths and you already clicked &quot;Configure&quot; again, then please trigger &quot;Delete Cache&quot; (File-&gt;Delete Cache) in Cmake and start from 0 again!<br /> Also we recommend you to switch on the &quot;Advanced&quot; and &quot;Grouped&quot; checkboxes.<br /> * 1. Get the appropriate '''CEGUI''' version from the CEGUI download page or get the very latest CEGUI version from the SVN repository (see links and info above).<br /> <br /> * 2. Get the latest '''Ogre''' version. If you are build it yourself (recommended), you will need to compile/link it first in the modes you want to use (Debug/Release) to get Ogre's .lib and .dll files ready for CEGUI.<br /> <br /> <br /> == Steps for Microsoft Visual Studio ==<br /> <br /> <br /> <br /> ===CEGUI 0.8.x ===<br /> * 3. Open the CMake GUI Utility<br /> * 4. Set the '''source path''' to the directory where your CEGUI files are located (e.g. C:/CEGUI - contains folders like 'cegui' 'cmake' 'datafiles', etc. )<br /> * 5. Set the '''build path''' to the directory where you want CMake to generate your build configuration(e.g. C:/CEGUI/build)<br /> * 6. Press the '''Configure''' button. At this stage CMake will ask you for a generator for this project(e.g. Visual Studio 10) and then will try to find the required packages needed by CEGUI. Please note that you should have the CEGUI dependencies built and installed in your CEGUI_ROOT directory. E.g. if your CEGUI directory is C:/CEGUI then the dependencies would be expected to be in C:/CEGUI/dependencies by default<br /> * 7. Search the '''CEGUI_BUILD_RENDERER_OGRE''' boolean variable in the list of CMake GUI Utility and set the value to TRUE by clicking on the checkbox. <br /> * 8. Check if OGRE and OIS (and boost - '''IF''' your Ogre version was built with boost as dependency) were found by cmake. (For more information about how boost can be found by CMake please see the Cmake docu: http://www.cmake.org/cmake/help/git-master/module/FindBoost.html) Look through the CMake GUI Utility output to see if there is a message like 'Could NOT find OGRE'. '''If both Ogre and OIS (and boost) were found (and reference the right version in case you got multiple ones) you can jump to step #9 now'''. &lt;span style=&quot;color:#3333AA&quot;&gt; If this was not the case it means that you either have not set the environment variables for Ogre (OGRE_SDK and OGRE_HOME) and OIS (OIS_HOME) at all, or that you have not set them correctly. You can try to fix this and click configure again to see if it works. If it does you can skip to #9. If it does not work then set the paths yourself.<br /> <br /> &lt;div class=&quot;toccolours mw-collapsible mw-collapsed&quot; style=&quot;width:80%&quot;&gt;<br /> ''' Expand this field to get a very elaborate explanation on the CMake settings for Ogre, OIS and Boost including examplatory paths: '''<br /> &lt;div class=&quot;mw-collapsible-content&quot;&gt;<br /> {{BUILD_OGRE_FOR_CEGUI_0_8_HELP}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> * 9 After you changed all the CMake settings to your liking (deactivating/activating Image codecs, parsers, renderer, etc.) you have to rerun '''Configure'''. You need to do this in order to save your additional variables in the CMake cache and in the build configuration.<br /> * 10 Press the '''Generate''' button. At this stage CMake will read your build configuration and then generate a solution using your selected generator.<br /> * 11 Go to the cegui build directory and open the Visual Studio solution '''cegui.sln'''<br /> * 12 Build the entire cegui solution.<br /> * 13 (Optional) Start the SampleBrowser to see if the samples work correctly (don't forget to copy the created samples.xml from build/datafiles/samples to your datafiles/samples folder so that the SampleBrowser can find the samples you want to use. Also make sure you copied all the dlls that your setup requires to the foldering containing the SampleBrowser.exe and in Visual Studio: for Project-&gt;Properties-&gt;Debugging-&gt;Working Directory set the value to $(OutDir) )<br /> <br /> ===CEGUI 0.7.x ===<br /> * 3. In your CEGUI folder there should be a folder called &quot;'''projects'''&quot; with a subfolder called &quot;'''premake'''&quot;. It is recommended to use the [https://sourceforge.net/projects/crayzedsgui/files/CEGUI%20Mk-2/premake/premake-3.7-custom.zip/download custom premake version of CEGUI]. Otherwise you can get version 3.6 or 3.7 of premake. Once you have premake extract the '''premake.exe''' file into the said folder.<br /> <br /> * 4. Open '''config.lua''' in the premake folder and edit the Ogre and OIS paths accordingly, so that they will point to the dependency files. In my case for example the 2 lines look like this (having the OGRE and CEGUI main folders on the same level):<br /> <br /> &lt;pre&gt;<br /> OGRE_PATHS = { &quot;../OGRE&quot;, &quot;include/OGRE&quot;, &quot;lib&quot; }<br /> OIS_PATHS = { &quot;../OGRE&quot;, &quot;include/OIS&quot;, &quot;lib&quot; }<br /> &lt;/pre&gt;<br /> <br /> '''Note:''' Remember to use forward slashes here! Just copying the paths from the Windows explorer will give you backward slashes. Replace them!<br /> <br /> Next, set all Renderers you do not need to &quot;false&quot;, in this case we will only need ''OGRE_RENDERER''. You can also set all samples to false, except maybe ''SAMPLES_OGRE'' if you want to compile those.<br /> <br /> '''Important:''' Since Ogre 1.7 the &quot;boost&quot; library is a new dependency of OGRE. If you are unsure if your Ogre version needs boost, you might want to check if there is a boost folder in your Ogre main folder. In case your Ogre version makes use of boost, you will additionally add boost to the extra paths of CEGUIOgreRenderer, in my case it looks like this:<br /> &lt;pre&gt;<br /> CEGUI_EXTRA_PATHS = { <br /> { &quot;../OGRE/boost_1_42&quot;, &quot;&quot;, &quot;lib&quot;, &quot;CEGUIOgreRenderer&quot; }<br /> }<br /> &lt;/pre&gt;<br /> <br /> * 5. Next, we create our Visual Studio Projects - Execute '''build_vs2008.bat''' to create a Visual Studio 2008 project or execute any other .bat file for your respective compiler version.<br /> <br /> * 6. This should create '''CEGUI.sln''' in the premake folder. Open it.<br /> <br /> * 7. If you have the Ogre lib files seperated into a Debug and Release folder, you will have to change the path in the '''Linker''' settings of the project so they will point to the '''lib/Debug''' or '''lib/Release''' folder for each configuration respectively.<br /> <br /> * 8. '''Build''' the '''CEGUIOgreRenderer''' in Debug and Release mode.<br /> * 9. Now that you have built the .dll files and .lib files for CEGUI by yourself, you only have to change the linker settings of your project so that the needed .lib files and their folder paths are included there. Also you might want to include the dll's into a folder where your executable application will find them (for example just the folder your executable starts from). Finally remember to set the CEGUI '''include''' directory (for example &quot;..\..\CEGUI\cegui\include\cegui&quot;) inside your C++ project settings.<br /> <br /> <br /> == Steps for GNU and Unix-like environments ==<br /> ===CEGUI 0.8.x ===<br /> <br /> Going to the extracted CEGUI source directory and running the following commands seems to work. It also seems that the configurations are not used anymore. (noobnote: don't include the dollar-signs at the start of the lines. They represent the prompt.):<br /> <br /> &lt;pre&gt;<br /> $ mkdir build &amp;&amp; cd build<br /> <br /> $ export NUMBER_OF_CORES=`cat /proc/cpuinfo | grep &quot;cpu cores&quot; | uniq | awk '{print $4}'`<br /> <br /> $ cmake -D CMAKE_BUILD_TYPE=Release ..<br /> <br /> $ make -j$NUMBER_OF_CORES<br /> <br /> $ sudo make install<br /> <br /> $ sudo ldconfig<br /> &lt;/pre&gt;<br /> <br /> <br /> If everything worked out, you now have CEGUI up and running!<br /> <br /> ===CEGUI 0.7.x ===<br /> Going to the extracted CEGUI source directory and running the following commands seems to work (noobnote: don't include the dollar-signs at the start of the lines. They represent the prompt.):<br /> <br /> &lt;pre&gt;<br /> $ ./bootstrap &amp;&amp; mkdir build &amp;&amp; cd build<br /> <br /> $ export NUMBER_OF_CORES=`cat /proc/cpuinfo | grep &quot;cpu cores&quot; | uniq | awk '{print $4}'`<br /> <br /> $ ../configure &amp;&amp; make -j$NUMBER_OF_CORES<br /> <br /> $ sudo make install<br /> <br /> $ sudo ldconfig<br /> &lt;/pre&gt;<br /> <br /> <br /> If everything worked out, you now have CEGUI up and running!<br /> <br /> <br /> ==Errors==<br /> *CEGUI Exception - bad allocation<br /> This error is rather cryptic in its meaning and can occur when linking debug libraries to release libraries or vice-versa. Simply check all CMAKE paths to see if you accidently mixed up the debug and release paths for libraries (OIS, Ogre). If you did not then this might be due to a now-fixed error in 0.8.3. If this is the case you will have to change the .lib file to the OgreMain_d.lib version in Debug mode. Otherwise delete the cache (see mention above) and restart the CMake configuration.<br /> <br /> <br /> ==Questions==<br /> Feel free to edit this page using your CEGUI forum account login if you want to append something. If you have questions you can ask in the CEGUI forum or join our IRC channel #cegui on irc.freenode.net - <br /> In case you need help building Ogre in general, I'd recommend reading for example [http://blog.tidalware.com/2009/08/building-ogre-with-visual-studio/ this short guide (might be outdated though)].<br /> <br /> <br /> For the Ogre-wiki version of this article you can also check this link: http://www.ogre3d.org/tikiwiki/tiki-index.php?page=Building+CEGUI<br /> <br /> [[Category:HowTo]]</div> Ident http://cegui.org/wiki/index.php?title=Building_CEGUI_for_Ogre_/_OgreRenderer&diff=5763 Building CEGUI for Ogre / OgreRenderer 2016-05-01T10:48:05Z <p>Ident: </p> <hr /> <div>{{VersionBadge|0.7}}<br /> {{VersionBadge|0.8}}<br /> <br /> = General =<br /> Since Ogre version 1.7 the CEGUI library isn't an Ogre dependency anymore and was replaced by a very simple UI overlay mainly used for the Ogre demos. Users now have to compile the CEGUI library against Ogre on their own, to use CEGUI together with Ogre. This guide has been created to help users building CEGUI against Ogre. We recommend CMake 2.8.X for all version of CEGUI at the moment.<br /> <br /> <br /> == Tested versions ==<br /> * CEGUI 0.8.X and v0-8 branch supports basic configurations of Ogre 1.7 and 1.8 and 1.9. Other versions and specific configurations (such as using boost) are supported but might require additional steps from your side (see below).<br /> * CEGUI 0.8.5 (not yet released at the point of writing) and v0-8 branch support Ogre 2.0 and 2.1 with OGL3+ Renderer only.<br /> * CEGUI v-0 branch and releases starting with 0.8.4 will support Ogre 1.7, 1.8, 1.9. They will also be updated from time to time to support the current version of Ogre default branch (right now it works with the Ogre default branch version of 6th Jan. 2014, including Ogre's OGL3 Renderer)<br /> * CEGUI default branch (unstable) contains an entirely changed but mostly functional OgreRenderer that should work with 1.7-2.0 but might need to be tested further.<br /> <br /> == Environment variables for CMake ==<br /> If you installed Ogre (or OIS or Boost), then certain environment variables might have been set on your computer already, helping CMake find your Ogre version (or OIS or boost). Here are some examplatory paths from my computer:<br /> * OIS_HOME - A:/Libraries<br /> * OGRE_HOME - A:/Libraries/OgreFromSourceCode (alternatively, if you use an SDK and do not compile from source, for example use: A:/Libraries/OgreSDK )<br /> * OGRE_SDK - A:/Libraries/OgreFromSourceCode/build (alternatively, if you use an SDK and do not compile from source, for example use: A:/Libraries/OgreSDK )<br /> * Boost looks for C:/Boost and if nothing is there it looks for BOOST_ROOT env variable: http://stackoverflow.com/a/8770217/3144964<br /> <br /> <br /> == How to acquire the CEGUI source code ==<br /> Here are all the links you will need to build CEGUI and its dependencies - which is the recommended approach:<br /> * Visit the [http://static.cegui.org.uk/docs/current/downloading.html reference manual] for instructions on obtaining the latest CEGUI source code (be sure to be on a '''stable branch''', for example v0-8) - this is the recommended approach as it will include the latest fixes.<br /> '''Note''': If the branch version's source code seems to be unstable or not working, you can try the [http://sourceforge.net/projects/crayzedsgui/files/latest/download?source=files latest stable release] or select a Release version from the [http://cegui.org.uk/download downloads page].<br /> * '''Additionally''' to the CEGUI source code you will need [http://sourceforge.net/projects/crayzedsgui/files/CEGUI%20Mk-2%20Dependencies/0.8.x/cegui-deps-0.8.x-src.zip/download the source code of the CEGUI dependencies]. Download it and build the dependencies on your system (debug &amp; release modes are common and are recommended to be built). You can use this document as guideline for the building process if needed: [http://static.cegui.org.uk/docs/current/building_deps.html Building dependencies]. Move the &quot;dependencies&quot; folder, which should have been created during the build process and should contain the headers, .lib files and .dll files, into your CEGUI main folder, so that it will co-exist next to the folders &quot;bin&quot;, &quot;cegui&quot;, &quot;datafiles&quot; etc.<br /> <br /> <br /> == A snapshot of using CMake ==<br /> CMake has a great GUI that allows to change your project's configuration by specifiying the dependencies, renderers and parsers you want. You need to fill out the paths to all files and folders the dependencies require.<br /> &lt;div class=&quot;toccolours mw-collapsible mw-collapsed&quot; style=&quot;width:80%&quot;&gt;<br /> ''' Expand this to see an example on how to utilise the filters/search in CMake and how to set the Ogre variables'''<br /> &lt;div class=&quot;mw-collapsible-content&quot;&gt;<br /> {{[[File:Ogrescreen.png|How to set CMake variables]]}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> == Optional: If you want to use CMake to set up your own project ==<br /> We offer a FindCEGUI.cmake file in our repository [https://bitbucket.org/cegui/cegui/src/b975a6885624277808189ac3d503dea7ba82b1a7/cmake/FindCEGUI.cmake?at=v0-8&amp;fileviewer=file-view-default *here*] that you may want to use. An example CMake file can be found in this post: http://www.ogre3d.org/addonforums/viewtopic.php?f=34&amp;t=30480&amp;p=103432#p103432<br /> <br /> <br /> <br /> &lt;div class=&quot;toccolours mw-collapsible mw-collapsed&quot; style=&quot;width:80%&quot;&gt;<br /> ''' Expand this for an example of fully set boost variables based on a boost binary release. Reminder: For Ogre you only need thze include folder and the &quot;system&quot; and &quot;thread&quot; libraries.'''<br /> &lt;div class=&quot;mw-collapsible-content&quot;&gt;<br /> {{[[File:Boostconfig.png|How to set CMake Boost variables]]}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> = Step-by-step guide =<br /> <br /> <br /> '''Important:''' If you make a mistake such as confusing Debug and Release paths and you already clicked &quot;Configure&quot; again, then please trigger &quot;Delete Cache&quot; (File-&gt;Delete Cache) in Cmake and start from 0 again!<br /> Also we recommend you to switch on the &quot;Advanced&quot; and &quot;Grouped&quot; checkboxes.<br /> * 1. Get the appropriate '''CEGUI''' version from the CEGUI download page or get the very latest CEGUI version from the SVN repository (see links and info above).<br /> <br /> * 2. Get the latest '''Ogre''' version. If you are build it yourself (recommended), you will need to compile/link it first in the modes you want to use (Debug/Release) to get Ogre's .lib and .dll files ready for CEGUI.<br /> <br /> <br /> == Steps for Microsoft Visual Studio ==<br /> <br /> <br /> <br /> ===CEGUI 0.8.x ===<br /> * 3. Open the CMake GUI Utility<br /> * 4. Set the '''source path''' to the directory where your CEGUI files are located (e.g. C:/CEGUI - contains folders like 'cegui' 'cmake' 'datafiles', etc. )<br /> * 5. Set the '''build path''' to the directory where you want CMake to generate your build configuration(e.g. C:/CEGUI/build)<br /> * 6. Press the '''Configure''' button. At this stage CMake will ask you for a generator for this project(e.g. Visual Studio 10) and then will try to find the required packages needed by CEGUI. Please note that you should have the CEGUI dependencies built and installed in your CEGUI_ROOT directory. E.g. if your CEGUI directory is C:/CEGUI then the dependencies would be expected to be in C:/CEGUI/dependencies by default<br /> * 7. Search the '''CEGUI_BUILD_RENDERER_OGRE''' boolean variable in the list of CMake GUI Utility and set the value to TRUE by clicking on the checkbox. <br /> * 8. Check if OGRE and OIS (and boost - '''IF''' your Ogre version was built with boost as dependency) were found by cmake. (For more information about how boost can be found by CMake please see the Cmake docu: http://www.cmake.org/cmake/help/git-master/module/FindBoost.html) Look through the CMake GUI Utility output to see if there is a message like 'Could NOT find OGRE'. '''If both Ogre and OIS (and boost) were found (and reference the right version in case you got multiple ones) you can jump to step #9 now'''. &lt;span style=&quot;color:#3333AA&quot;&gt; If this was not the case it means that you either have not set the environment variables for Ogre (OGRE_SDK and OGRE_HOME) and OIS (OIS_HOME) at all, or that you have not set them correctly. You can try to fix this and click configure again to see if it works. If it does you can skip to #9. If it does not work then set the paths yourself.<br /> <br /> &lt;div class=&quot;toccolours mw-collapsible mw-collapsed&quot; style=&quot;width:80%&quot;&gt;<br /> ''' Expand this field to get a very elaborate explanation on the CMake settings for Ogre, OIS and Boost including examplatory paths: '''<br /> &lt;div class=&quot;mw-collapsible-content&quot;&gt;<br /> {{BUILD_OGRE_FOR_CEGUI_0_8_HELP}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> * 9 After you changed all the CMake settings to your liking (deactivating/activating Image codecs, parsers, renderer, etc.) you have to rerun '''Configure'''. You need to do this in order to save your additional variables in the CMake cache and in the build configuration.<br /> * 10 Press the '''Generate''' button. At this stage CMake will read your build configuration and then generate a solution using your selected generator.<br /> * 11 Go to the cegui build directory and open the Visual Studio solution '''cegui.sln'''<br /> * 12 Build the entire cegui solution.<br /> * 13 (Optional) Start the SampleBrowser to see if the samples work correctly (don't forget to copy the created samples.xml from build/datafiles/samples to your datafiles/samples folder so that the SampleBrowser can find the samples you want to use. Also make sure you copied all the dlls that your setup requires to the foldering containing the SampleBrowser.exe and in Visual Studio: for Project-&gt;Properties-&gt;Debugging-&gt;Working Directory set the value to $(OutDir) )<br /> <br /> ===CEGUI 0.7.x ===<br /> * 3. In your CEGUI folder there should be a folder called &quot;'''projects'''&quot; with a subfolder called &quot;'''premake'''&quot;. It is recommended to use the [https://sourceforge.net/projects/crayzedsgui/files/CEGUI%20Mk-2/premake/premake-3.7-custom.zip/download custom premake version of CEGUI]. Otherwise you can get version 3.6 or 3.7 of premake. Once you have premake extract the '''premake.exe''' file into the said folder.<br /> <br /> * 4. Open '''config.lua''' in the premake folder and edit the Ogre and OIS paths accordingly, so that they will point to the dependency files. In my case for example the 2 lines look like this (having the OGRE and CEGUI main folders on the same level):<br /> <br /> &lt;pre&gt;<br /> OGRE_PATHS = { &quot;../OGRE&quot;, &quot;include/OGRE&quot;, &quot;lib&quot; }<br /> OIS_PATHS = { &quot;../OGRE&quot;, &quot;include/OIS&quot;, &quot;lib&quot; }<br /> &lt;/pre&gt;<br /> <br /> '''Note:''' Remember to use forward slashes here! Just copying the paths from the Windows explorer will give you backward slashes. Replace them!<br /> <br /> Next, set all Renderers you do not need to &quot;false&quot;, in this case we will only need ''OGRE_RENDERER''. You can also set all samples to false, except maybe ''SAMPLES_OGRE'' if you want to compile those.<br /> <br /> '''Important:''' Since Ogre 1.7 the &quot;boost&quot; library is a new dependency of OGRE. If you are unsure if your Ogre version needs boost, you might want to check if there is a boost folder in your Ogre main folder. In case your Ogre version makes use of boost, you will additionally add boost to the extra paths of CEGUIOgreRenderer, in my case it looks like this:<br /> &lt;pre&gt;<br /> CEGUI_EXTRA_PATHS = { <br /> { &quot;../OGRE/boost_1_42&quot;, &quot;&quot;, &quot;lib&quot;, &quot;CEGUIOgreRenderer&quot; }<br /> }<br /> &lt;/pre&gt;<br /> <br /> * 5. Next, we create our Visual Studio Projects - Execute '''build_vs2008.bat''' to create a Visual Studio 2008 project or execute any other .bat file for your respective compiler version.<br /> <br /> * 6. This should create '''CEGUI.sln''' in the premake folder. Open it.<br /> <br /> * 7. If you have the Ogre lib files seperated into a Debug and Release folder, you will have to change the path in the '''Linker''' settings of the project so they will point to the '''lib/Debug''' or '''lib/Release''' folder for each configuration respectively.<br /> <br /> * 8. '''Build''' the '''CEGUIOgreRenderer''' in Debug and Release mode.<br /> * 9. Now that you have built the .dll files and .lib files for CEGUI by yourself, you only have to change the linker settings of your project so that the needed .lib files and their folder paths are included there. Also you might want to include the dll's into a folder where your executable application will find them (for example just the folder your executable starts from). Finally remember to set the CEGUI '''include''' directory (for example &quot;..\..\CEGUI\cegui\include\cegui&quot;) inside your C++ project settings.<br /> <br /> <br /> == Steps for GNU and Unix-like environments ==<br /> ===CEGUI 0.8.x ===<br /> <br /> Going to the extracted CEGUI source directory and running the following commands seems to work. It also seems that the configurations are not used anymore. (noobnote: don't include the dollar-signs at the start of the lines. They represent the prompt.):<br /> <br /> &lt;pre&gt;<br /> $ mkdir build &amp;&amp; cd build<br /> <br /> $ export NUMBER_OF_CORES=`cat /proc/cpuinfo | grep &quot;cpu cores&quot; | uniq | awk '{print $4}'`<br /> <br /> $ cmake -D CMAKE_BUILD_TYPE=Release ..<br /> <br /> $ make -j$NUMBER_OF_CORES<br /> <br /> $ sudo make install<br /> <br /> $ sudo ldconfig<br /> &lt;/pre&gt;<br /> <br /> <br /> If everything worked out, you now have CEGUI up and running!<br /> <br /> ===CEGUI 0.7.x ===<br /> Going to the extracted CEGUI source directory and running the following commands seems to work (noobnote: don't include the dollar-signs at the start of the lines. They represent the prompt.):<br /> <br /> &lt;pre&gt;<br /> $ ./bootstrap &amp;&amp; mkdir build &amp;&amp; cd build<br /> <br /> $ export NUMBER_OF_CORES=`cat /proc/cpuinfo | grep &quot;cpu cores&quot; | uniq | awk '{print $4}'`<br /> <br /> $ ../configure &amp;&amp; make -j$NUMBER_OF_CORES<br /> <br /> $ sudo make install<br /> <br /> $ sudo ldconfig<br /> &lt;/pre&gt;<br /> <br /> <br /> If everything worked out, you now have CEGUI up and running!<br /> <br /> <br /> ==Errors==<br /> *CEGUI Exception - bad allocation<br /> This error is rather cryptic in its meaning and can occur when linking debug libraries to release libraries or vice-versa. Simply check all CMAKE paths to see if you accidently mixed up the debug and release paths for libraries (OIS, Ogre). If you did not then this might be due to a now-fixed error in 0.8.3. If this is the case you will have to change the .lib file to the OgreMain_d.lib version in Debug mode. Otherwise delete the cache (see mention above) and restart the CMake configuration.<br /> <br /> <br /> ==Questions==<br /> Feel free to edit this page using your CEGUI forum account login if you want to append something. If you have questions you can ask in the CEGUI forum or join our IRC channel #cegui on irc.freenode.net - <br /> In case you need help building Ogre in general, I'd recommend reading for example [http://blog.tidalware.com/2009/08/building-ogre-with-visual-studio/ this short guide (might be outdated though)].<br /> <br /> <br /> For the Ogre-wiki version of this article you can also check this link: http://www.ogre3d.org/tikiwiki/tiki-index.php?page=Building+CEGUI<br /> <br /> [[Category:HowTo]]</div> Ident http://cegui.org/wiki/index.php?title=Release_Checklist&diff=5761 Release Checklist 2016-04-23T18:35:04Z <p>Ident: /* CEGUI */</p> <hr /> <div>== CEGUI ==<br /> <br /> This page is mainly for the CEGUI team and serves as a checklist to avoid forgetting steps when making a CEGUI release.<br /> <br /> * First check that the local repo is completely up-to-date and check that no unversioned files or uncommited changes are existing.<br /> * Bump release version in CMakeLists.txt <br /> * Bump ABI version in CMakeLists.txt<br /> * Add change log entries from https://bitbucket.org/cegui/cegui/issues?milestone=0.8.4&amp;status=resolved (change the version in the link) to doc/doxygen/changelog.dox<br /> * Regenerate generated code/other files (i.e regen bindings etc)<br /> * Create mercurial tag for release<br /> * Make source packages.<br /> * Build docs.<br /> * Make docs packages.<br /> * Upload!<br /> * Make sure the new release is listed as the latest release on sourceforge, you can do this by clicking the &quot;i&quot; icon next to the file and selecting all operating systems --&gt; SAVE (takes 3 mins to be updated)<br /> * For 0.8.5 Release announce in the docs and in the Release news that this requires CMAke 0.8.11 minimum<br /> * Create a release on the drupal page - http://cegui.org.uk/node/add/release<br /> * Make sure N+1 version is in bitbucket issue-tracker or add it<br /> * Generate docs and upload to static.cegui.org.uk, see http://bitbucket.org/cegui/docs-builder<br /> * Update the server's htaccess in the static API docs folder to redirect to the latest minor version<br /> * Post to twitter<br /> * Post to google+<br /> <br /> == CEED ==<br /> <br /> TODO</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5760 Ident TODO 2016-04-02T22:41:50Z <p>Ident: </p> <hr /> <div>=== CEGUI General ===<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> * CEGUI default: rename isActive() to isInFocus() or similar to be more meaningful? http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=7162<br /> <br /> === Opengl Renderers === <br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> === Renderers === <br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> === SVG === <br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> === SampleBrowser === <br /> * Separate duties (input, Renderer-related stuff, etc) in different facets. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> === CEGUI docu === <br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> === SVG Tessellator tests === <br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> === Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs === <br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> === Adapt CEGUI System/Renderer for multi-window support and write a simple demo app === <br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14<br /> <br /> <br /> = FINISHED =<br /> <br /> === Add tooltips to some demo === <br /> &lt;strike&gt;It is currently not covered anywhere. Or is it( need to check!)?&lt;/strike&gt;<br /> Added to the look n' feel demo (and fixed some bugs with inherited tooltips that I noticed ;) )</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5759 Ident TODO 2016-03-20T18:54:20Z <p>Ident: </p> <hr /> <div>=== CEGUI General ===<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> <br /> === Opengl Renderers === <br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> === Renderers === <br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> === SVG === <br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> === SampleBrowser === <br /> * Separate duties (input, Renderer-related stuff, etc) in different facets. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> === CEGUI docu === <br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> === SVG Tessellator tests === <br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> === Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs === <br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> === Adapt CEGUI System/Renderer for multi-window support and write a simple demo app === <br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14<br /> <br /> <br /> = FINISHED =<br /> <br /> === Add tooltips to some demo === <br /> &lt;strike&gt;It is currently not covered anywhere. Or is it( need to check!)?&lt;/strike&gt;<br /> Added to the look n' feel demo (and fixed some bugs with inherited tooltips that I noticed ;) )</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5758 Ident TODO 2016-03-20T18:52:45Z <p>Ident: </p> <hr /> <div>== CEGUI General ==<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> <br /> == Opengl Renderers ==<br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> == Renderers ==<br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> == SVG ==<br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> == SampleBrowser ==<br /> * Separate duties (input, Renderer-related stuff, etc) in different facets. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> == CEGUI docu ==<br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> == SVG Tessellator tests ==<br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> == Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs ==<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> == Adapt CEGUI System/Renderer for multi-window support and write a simple demo app ==<br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14<br /> <br /> <br /> = FINISHED =<br /> <br /> == Add tooltips to some demo ==<br /> &lt;strike&gt;It is currently not covered anywhere. Or is it( need to check!)?&lt;/strike&gt;<br /> Added to the look n' feel demo (and fixed some bugs with inherited tooltips that I noticed ;) )</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5757 Ident TODO 2016-03-19T10:30:46Z <p>Ident: /* SampleBrowser */</p> <hr /> <div>== CEGUI General ==<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> <br /> == Opengl Renderers ==<br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> == Renderers ==<br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> == SVG ==<br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> == SampleBrowser ==<br /> * Separate duties (input, Renderer-related stuff, etc) in different facets. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> == CEGUI docu ==<br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> == SVG Tessellator tests ==<br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> == Add tooltips to some demo ==<br /> &lt;strike&gt;It is currently not covered anywhere. Or is it( need to check!)?&lt;/strike&gt;<br /> Added to the look n' feel demo<br /> <br /> == Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs ==<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> == Adapt CEGUI System/Renderer for multi-window support and write a simple demo app ==<br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5756 Ident TODO 2016-03-19T10:05:18Z <p>Ident: /* Add tooltips to some demo */</p> <hr /> <div>== CEGUI General ==<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> <br /> == Opengl Renderers ==<br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> == Renderers ==<br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> == SVG ==<br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> == SampleBrowser ==<br /> * Separate duties (input, Renderer-related stuff, etc) in different managers. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> == CEGUI docu ==<br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> == SVG Tessellator tests ==<br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> == Add tooltips to some demo ==<br /> &lt;strike&gt;It is currently not covered anywhere. Or is it( need to check!)?&lt;/strike&gt;<br /> Added to the look n' feel demo<br /> <br /> == Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs ==<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> == Adapt CEGUI System/Renderer for multi-window support and write a simple demo app ==<br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14</div> Ident http://cegui.org/wiki/index.php?title=Main_Page&diff=5754 Main Page 2016-02-27T18:43:06Z <p>Ident: </p> <hr /> <div>&lt;!-- Main Page Header (formerly Template:CEGUIWelcome) --&gt; <br /> {{Section|1=Welcome to the &lt;em&gt;&lt;b&gt;CEGUI Community Wiki&lt;/b&gt;&lt;/em&gt;|2=<br /> <br /> &lt;div style=&quot;text-align:center;font-size:14px;&quot;&gt;<br /> Welcome to the official CEGUI community Wiki. All users are encouraged to contribute! This is a community driven wiki, which serves as an addition to [http://static.cegui.org.uk/docs/ the official API documentation].<br /> &lt;/div&gt;<br /> &lt;div style=&quot;text-align:center;font-size:14px;&quot;&gt;<br /> To contribute to the wiki, please login with your [http://www.cegui.org.uk/phpBB2/index.php forum] account (registration is easy!). To improve the API documentation, create a pull request on [https://bitbucket.org/cegui/cegui/ our bitbucket repository].<br /> &lt;/div&gt;<br /> &lt;div style=&quot;text-align:center;font-size:14px;&quot;&gt;<br /> All news, releases and more can be found on the official [http://www.cegui.org.uk CEGUI website].<br /> &lt;/div&gt;<br /> <br /> }}<br /> <br /> <br /> &lt;!-- Section 2: Downloading and Installing --&gt;<br /> {{Section|1=Getting CEGUI|2=<br /> * [[Downloads|Download a Release]]<br /> * [[Obtaining_the_library_source_from_Mercurial|Build it from source]]<br /> }}<br /> <br /> &lt;!-- Section 3: How to use CEGUI --&gt;<br /> {{Section|1=Working with CEGUI|2= <br /> * [http://static.cegui.org.uk/docs Official API docs for all Releases]<br /> * [https://bitbucket.org/cegui/cegui CEGUI ReadMe]<br /> * [[Helpful_Links|A concise collection of helpful links for CEGUI users]]<br /> * [[:Category:Tutorials|Tutorials]]: All tutorials to help you getting started with CEGUI<br /> * [[:Category:HowTo|How-To series]]: How to deal with a specific feature of CEGUI<br /> * [[:Category:Manuals|Manuals]]: Some more advanced material on using CEGUI <br /> }}<br /> <br /> &lt;!-- Section 4: CEGUI for Content Creators --&gt; <br /> {{Section|1=CEGUI for Content Creators|2=<br /> * [[CEED]] - The official tool for CEGUI<br /> * [[Assembling a Toolset|Tools]]: Gather the tools that can help you with the creation of your GUI <br /> * [http://cegui.org.uk/docs/current/fal_man.html &quot;Falagard&quot; Skinning System Documentation]: All you ever wanted to know on falagard skinning system (and more) <br /> * [[XML File formats]]: Description of all XML file format used in CEGUI <br /> * [http://skins.cegui.org.uk Skins]: (WIP) Find some existing skins. There are more on the forums.<br /> }}<br /> <br /> &lt;!-- Section 1: About CEGUI --&gt; <br /> {{Section|1=About CEGUI|2=<br /> * [http://cegui.org.uk CEGUI website]<br /> * [[FAQ|Everything About CEGUI (FAQ)]] (Old)<br /> * [[Developer Team]]<br /> * [[Projects Using CEGUI]]: Games and other software using CEGUI<br /> }}<br /> <br /> <br /> {{Section|1=Featured Videos from our [http://www.youtube.com/ceguiproject YouTube Channel]|2=<br /> &lt;table width=&quot;795&quot; style=&quot;margin-left: auto; margin-right: auto&quot;&gt;<br /> &lt;tr&gt;<br /> &lt;td rowspan=&quot;2&quot; colspan=&quot;2&quot;&gt;&lt;youtube width=&quot;640&quot; height=&quot;320&quot;&gt;iXsZh1owpBI&lt;/youtube&gt;<br /> &lt;/td&gt;<br /> &lt;td&gt;&lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;AM5_YarbwNg&lt;/youtube&gt;&lt;/td&gt;&lt;td&gt;<br /> &lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;ldSd45xlVU0&lt;/youtube&gt;&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;&lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;eRC5R9aA_Zs&lt;/youtube&gt;&lt;/td&gt;&lt;td&gt;<br /> &lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;Z5Uf9IsWCXY&lt;/youtube&gt;&lt;/td&gt;&lt;/tr&gt;<br /> &lt;/table&gt;<br /> }}<br /> {| width=&quot;100%&quot; background-color=&quot;transparent&quot;<br /> |valign=&quot;top&quot;|</div> Ident http://cegui.org/wiki/index.php?title=Building_CEED_for_Windows&diff=5748 Building CEED for Windows 2015-11-09T21:21:14Z <p>Ident: /* Installing the prerequisites */</p> <hr /> <div>{{VersionBadge|0.8}}<br /> <br /> '''Written by Ident (Lukas Meindl) &amp; Nickenstein79 (Working correctly as of 11th June, 2014)'''<br /> <br /> The following instructions need to be done in the presented order and are created for the currently available version of CEED and could therefore be outdated at some point. Please notify us if you think this is outdated.<br /> <br /> <br /> == Installing the prerequisites ==<br /> <br /> When downloading/installing binaries, be sure to get the version which matches your version of visual studio, for instance choose the 32-bit and VC10 (visual studio 2010) versions of the binaries if that is what you are using to build. (or VC9 / VC11 / VC12 / ... if you are building with those.) If you use VC14 and not for example VC9 then be sure that the paths also match this. Don't get confused about the '''paths''' listed in this article, they are '''exemplatory''' and based on VC9. '''Do not mix VC9 binaries with VC10 or VC11, etc.''' We recommend using VC9 to build CEED because this one is assured to work.<br /> <br /> == Installing Python ==<br /> * Get Python 2.7.7 (32 bit version) for Windows and install it: <br /> https://www.python.org/downloads/<br /> * Add your Python install folder path to the PATH variable in your Windows environment variables, e.g.: C:Projects\Python27<br /> * Now add the Scripts folder to the PATH environment variable, e.g.: C:\Projects\Python27\Scripts &amp; C:\Projects\Python27\Tools\Scripts (depending on which of those folders exists in your install)<br /> * Open up a dos-command-prompt (cmd.exe) with admin rights and type &quot;python&quot; - See if you get something written into the console, such as &quot;Python 2.7.6 (default [...]&quot;, if this is the case then the install worked.<br /> <br /> <br /> == Installing pip ==<br /> * Install the latest pip distribution: First download get-pip.py: <br /> http://pip.readthedocs.org/en/latest/installing.html<br /> * Open up a dos-command-prompt (cmd.exe) with admin rights, change to the folder to which you downloaded &quot;get-pip.py&quot; by using the &quot;cd&quot; command, e.g.: cd &quot;A:/Downloads/Not porn&quot;<br /> * Type &quot;python get-pip.py&quot; and click enter in the dos-command-prompt<br /> * pip should now be installed<br /> * Afterwards enter &quot;pip&quot; and click enter. You should get some sort of information about pip now, if the install succeeded.<br /> <br /> <br /> == Installing pyside ==<br /> * Now you can install pyside easily with the following command: &quot;pip install -U PySide&quot;<br /> * You should get a console output notifying you of a successful install<br /> <br /> <br /> == Installing pyOpenGL ==<br /> * Install pyOpenGL on Windows with this installer: <br /> https://pypi.python.org/packages/any/P/PyOpenGL/PyOpenGL-3.0.2.win32.exe<br /> <br /> <br /> == Installing boost binaries ==<br /> * We also need to install boost. You can use an .exe file for this that will install the necessary binaries from this download page:<br /> http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0-build2/ <br /> (Be sure to get the version which matches the version of msvc you intend to build with. If use MSVC2008, then get the download with 'msvc-9.0' in the name, if you use MSVC2010 get the version with 'msvc-10.0' in the name, etc...)<br /> <br /> * Note : If you have multiple versions of MSVS on your machine, it is safe to install different versions of these boost distributions into the same root folder (e.g C:/boost_1_55_0/), as the *.h and *.hpp files are all identical, and the pre-compiled binary libs all get installed to sub-folders specific to different versions of msvc. (It is these folders and libs that we will be manually pointing cmake to in the next section.)<br /> <br /> <br /> == Configuring a PyCEGUI build with cmake == <br /> <br /> * Clone CEGUI v0-8 from the CEGUI repository to a new local folder from here:<br /> https://bitbucket.org/cegui/cegui/branch/v0-8<br /> e.g. to C:/cegui-v0-8<br /> * Check that the branch of your working directory is really v0-8 after cloning, if not then update to the latest v0-8 commit<br /> * Add the CEGUI dependencies folder into the CEGUI_v0_8 repository folder that you just cloned.<br /> * Open CMake and set the source code folder to your new local folder, e.g.: C:/cegui-v0-8 and the binaries to for example: C:/cegui-v0-8/build<br /> * Set the tick-boxes 'Advanced' and 'Grouped' to true. It makes it much easier to manage variables within cmake.<br /> <br /> ''[The following two steps are optional but will make finding boost libraries a lot more comfortable: If you, for whatever reason, can not or do not want to add or modify environment variables, you can directly specify all of the paths manually in CMake, by setting the variables to path values analogously to those used in the boost path examples below]''<br /> * Set the following windows environment variables:<br /> <br /> * 'BOOST_INCLUDEDIR' (Where the boost *.hpp files are)<br /> * 'BOOST_LIBRARYDIR' (Where the platform/compiler specific libs are)<br /> * 'BOOST_ROOT' (Set this to the root folder which contains the above two folders.)<br /> <br /> * Now click 'configure'. CMake will now auto-detect most of the build requirements. &lt;br /&gt;It 'should' now correctly auto-detect boost, However, if it failed to find any bost components, then you need to set them manually:<br /> <br /> These are directory-paths and file-paths to locations inside the boost and Python distributions that you installed in the previous steps.<br /> <br /> (Here are examples of what they are set to on my machine)<br /> <br /> === cmake Boost path examples ===<br /> ------------------------------------------------------------------------------------------------------------<br /> ** Boost_PYTHON_LIBRARY_DEBUG C:/boost_1_55_0/lib32-msvc-9.0/boost_python-vc90-mt-gd-1_55.lib<br /> ** Boost_PYTHON_LIBRARY_RELEASE C:/boost_1_55_0/lib32-msvc-9.0/boost_python-vc90-mt-1_55.lib<br /> ** Boost_SYSTEM_LIBRARY_DEBUG C:/boost_1_55_0/lib32-msvc-9.0/boost_system-vc90-mt-gd-1_55.lib<br /> ** Boost_SYSTEM_LIBRARY_RELEASE C:/boost_1_55_0/lib32-msvc-9.0/boost_system-vc90-mt-1_55.lib<br /> ** Boost_INCLUDE_DIR C:/boost_1_55_0<br /> ------------------------------------------------------------------------------------------------------------<br /> <br /> <br /> CMake may correctly auto-find the following Python variables, but it may fail. So be sure to inspect them, and if they were not found, you need to set them manually. <br /> <br /> Here are examples of mine:<br /> <br /> === cmake Python path examples ===<br /> ------------------------------------------------------------------------------------------------------------<br /> ** PYTHON_INCLUDE_DIR C:/Python27/include<br /> ** PYTHON_LIBRARY C:/Python27/libs/python27.lib<br /> ** PYTHON_EXECUTABLE C:/Python27/python.exe<br /> ------------------------------------------------------------------------------------------------------------<br /> <br /> <br /> * Unselect Building the CEGUI samples and select only OpenGL3 and OpenGL out of the available renderers to build<br /> * Select CEGUI_BUILD_PYTHON_MODULES so that this option is checked<br /> * Click 'configure' again, and then click 'generate', this should now work without errors and generate a solution-file in the binary folder that you specified as your build location.<br /> <br /> == Building PyCEGUI ==<br /> <br /> * Open the generated solution using MSVC and build the ALL_BUILDS project (You need 'Release' mode only)<br /> * Go for a very long walk along a very long beach. Building PyCEGUI &amp; PyCEGUI_OpenGLRenderer is very slow.<br /> <br /> <br /> == Setting up the PyCEGUI dll dependencies ==<br /> * Put the following dependencies of CEGUI into your build's bin folder, e.g.: C:/cegui-v0-8/build/bin<br /> ** From your CEGUI dependencies folder (e.g.: C:/cegui-v0-8/dependencies) :<br /> *** freetype.dll<br /> *** glew.dll<br /> *** pcre.dll<br /> ** From the boost binaries folder (e.g.: A:\Programs\boost_1_55_0\lib32-msvc-9.0 )<br /> *** boost_python-vc90-mt-1_55.dll (Or higher, depending on your version of MSVS &amp; the boost lib folder you are using.)<br /> <br /> <br /> == Cloning the CEED repository ==<br /> * clone the following CEED repository, and verify that you are on the v0-8 branch.<br /> https://bitbucket.org/cegui/ceed<br /> <br /> <br /> == Running CEED ==<br /> * Go to your CEED\bin folder (the bin folder inside the folder that you just cloned CEED to)<br /> * Edit runwrapper.bat so that the relative path CEGUI_BUILD_PATH matches the folder you just compiled PyCEGUI to<br /> * Run the batch file, and the CEED editor should be launched (if not, start the guide again. If it still fails, ask for help on the CEGUI forums)<br /> <br /> <br /> == Using Python-CEED-Migrate ==<br /> You can also use the ceed-migrate tool for convert your old cegui-datafiles to the newer formats. See this page for some examples of the parameters ceed-migrate takes: [[Using CEED-Migrate]]<br /> <br /> <br /> [[Using CEED-Migrate]] <br /> [[Category:HowTo]]<br /> [[Category:Tutorials]]</div> Ident http://cegui.org/wiki/index.php?title=Building_CEED_for_Windows&diff=5747 Building CEED for Windows 2015-11-09T21:19:46Z <p>Ident: /* Installing the prerequisites */</p> <hr /> <div>{{VersionBadge|0.8}}<br /> <br /> '''Written by Ident (Lukas Meindl) &amp; Nickenstein79 (Working correctly as of 11th June, 2014)'''<br /> <br /> The following instructions need to be done in the presented order and are created for the currently available version of CEED and could therefore be outdated at some point. Please notify us if you think this is outdated.<br /> <br /> <br /> == Installing the prerequisites ==<br /> <br /> When downloading/installing binaries, be sure to get the version which matches your version of visual studio, for instance choose the 32-bit and VC10 (visual studio 2010) versions of the binaries if that is what you are using to build. (or VC9 / VC11 / VC12 / ... if you are building with those.) If you use VC14 and not for example VC9 then be sure that the paths also match this. Don't get confused about the '''paths''' listed in this article, they are '''exemplatory''' and based on VC9. '''Do not mix VC9 binaries with VC10 or VC11, etc.'''<br /> <br /> == Installing Python ==<br /> * Get Python 2.7.7 (32 bit version) for Windows and install it: <br /> https://www.python.org/downloads/<br /> * Add your Python install folder path to the PATH variable in your Windows environment variables, e.g.: C:Projects\Python27<br /> * Now add the Scripts folder to the PATH environment variable, e.g.: C:\Projects\Python27\Scripts &amp; C:\Projects\Python27\Tools\Scripts (depending on which of those folders exists in your install)<br /> * Open up a dos-command-prompt (cmd.exe) with admin rights and type &quot;python&quot; - See if you get something written into the console, such as &quot;Python 2.7.6 (default [...]&quot;, if this is the case then the install worked.<br /> <br /> <br /> == Installing pip ==<br /> * Install the latest pip distribution: First download get-pip.py: <br /> http://pip.readthedocs.org/en/latest/installing.html<br /> * Open up a dos-command-prompt (cmd.exe) with admin rights, change to the folder to which you downloaded &quot;get-pip.py&quot; by using the &quot;cd&quot; command, e.g.: cd &quot;A:/Downloads/Not porn&quot;<br /> * Type &quot;python get-pip.py&quot; and click enter in the dos-command-prompt<br /> * pip should now be installed<br /> * Afterwards enter &quot;pip&quot; and click enter. You should get some sort of information about pip now, if the install succeeded.<br /> <br /> <br /> == Installing pyside ==<br /> * Now you can install pyside easily with the following command: &quot;pip install -U PySide&quot;<br /> * You should get a console output notifying you of a successful install<br /> <br /> <br /> == Installing pyOpenGL ==<br /> * Install pyOpenGL on Windows with this installer: <br /> https://pypi.python.org/packages/any/P/PyOpenGL/PyOpenGL-3.0.2.win32.exe<br /> <br /> <br /> == Installing boost binaries ==<br /> * We also need to install boost. You can use an .exe file for this that will install the necessary binaries from this download page:<br /> http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0-build2/ <br /> (Be sure to get the version which matches the version of msvc you intend to build with. If use MSVC2008, then get the download with 'msvc-9.0' in the name, if you use MSVC2010 get the version with 'msvc-10.0' in the name, etc...)<br /> <br /> * Note : If you have multiple versions of MSVS on your machine, it is safe to install different versions of these boost distributions into the same root folder (e.g C:/boost_1_55_0/), as the *.h and *.hpp files are all identical, and the pre-compiled binary libs all get installed to sub-folders specific to different versions of msvc. (It is these folders and libs that we will be manually pointing cmake to in the next section.)<br /> <br /> <br /> == Configuring a PyCEGUI build with cmake == <br /> <br /> * Clone CEGUI v0-8 from the CEGUI repository to a new local folder from here:<br /> https://bitbucket.org/cegui/cegui/branch/v0-8<br /> e.g. to C:/cegui-v0-8<br /> * Check that the branch of your working directory is really v0-8 after cloning, if not then update to the latest v0-8 commit<br /> * Add the CEGUI dependencies folder into the CEGUI_v0_8 repository folder that you just cloned.<br /> * Open CMake and set the source code folder to your new local folder, e.g.: C:/cegui-v0-8 and the binaries to for example: C:/cegui-v0-8/build<br /> * Set the tick-boxes 'Advanced' and 'Grouped' to true. It makes it much easier to manage variables within cmake.<br /> <br /> ''[The following two steps are optional but will make finding boost libraries a lot more comfortable: If you, for whatever reason, can not or do not want to add or modify environment variables, you can directly specify all of the paths manually in CMake, by setting the variables to path values analogously to those used in the boost path examples below]''<br /> * Set the following windows environment variables:<br /> <br /> * 'BOOST_INCLUDEDIR' (Where the boost *.hpp files are)<br /> * 'BOOST_LIBRARYDIR' (Where the platform/compiler specific libs are)<br /> * 'BOOST_ROOT' (Set this to the root folder which contains the above two folders.)<br /> <br /> * Now click 'configure'. CMake will now auto-detect most of the build requirements. &lt;br /&gt;It 'should' now correctly auto-detect boost, However, if it failed to find any bost components, then you need to set them manually:<br /> <br /> These are directory-paths and file-paths to locations inside the boost and Python distributions that you installed in the previous steps.<br /> <br /> (Here are examples of what they are set to on my machine)<br /> <br /> === cmake Boost path examples ===<br /> ------------------------------------------------------------------------------------------------------------<br /> ** Boost_PYTHON_LIBRARY_DEBUG C:/boost_1_55_0/lib32-msvc-9.0/boost_python-vc90-mt-gd-1_55.lib<br /> ** Boost_PYTHON_LIBRARY_RELEASE C:/boost_1_55_0/lib32-msvc-9.0/boost_python-vc90-mt-1_55.lib<br /> ** Boost_SYSTEM_LIBRARY_DEBUG C:/boost_1_55_0/lib32-msvc-9.0/boost_system-vc90-mt-gd-1_55.lib<br /> ** Boost_SYSTEM_LIBRARY_RELEASE C:/boost_1_55_0/lib32-msvc-9.0/boost_system-vc90-mt-1_55.lib<br /> ** Boost_INCLUDE_DIR C:/boost_1_55_0<br /> ------------------------------------------------------------------------------------------------------------<br /> <br /> <br /> CMake may correctly auto-find the following Python variables, but it may fail. So be sure to inspect them, and if they were not found, you need to set them manually. <br /> <br /> Here are examples of mine:<br /> <br /> === cmake Python path examples ===<br /> ------------------------------------------------------------------------------------------------------------<br /> ** PYTHON_INCLUDE_DIR C:/Python27/include<br /> ** PYTHON_LIBRARY C:/Python27/libs/python27.lib<br /> ** PYTHON_EXECUTABLE C:/Python27/python.exe<br /> ------------------------------------------------------------------------------------------------------------<br /> <br /> <br /> * Unselect Building the CEGUI samples and select only OpenGL3 and OpenGL out of the available renderers to build<br /> * Select CEGUI_BUILD_PYTHON_MODULES so that this option is checked<br /> * Click 'configure' again, and then click 'generate', this should now work without errors and generate a solution-file in the binary folder that you specified as your build location.<br /> <br /> == Building PyCEGUI ==<br /> <br /> * Open the generated solution using MSVC and build the ALL_BUILDS project (You need 'Release' mode only)<br /> * Go for a very long walk along a very long beach. Building PyCEGUI &amp; PyCEGUI_OpenGLRenderer is very slow.<br /> <br /> <br /> == Setting up the PyCEGUI dll dependencies ==<br /> * Put the following dependencies of CEGUI into your build's bin folder, e.g.: C:/cegui-v0-8/build/bin<br /> ** From your CEGUI dependencies folder (e.g.: C:/cegui-v0-8/dependencies) :<br /> *** freetype.dll<br /> *** glew.dll<br /> *** pcre.dll<br /> ** From the boost binaries folder (e.g.: A:\Programs\boost_1_55_0\lib32-msvc-9.0 )<br /> *** boost_python-vc90-mt-1_55.dll (Or higher, depending on your version of MSVS &amp; the boost lib folder you are using.)<br /> <br /> <br /> == Cloning the CEED repository ==<br /> * clone the following CEED repository, and verify that you are on the v0-8 branch.<br /> https://bitbucket.org/cegui/ceed<br /> <br /> <br /> == Running CEED ==<br /> * Go to your CEED\bin folder (the bin folder inside the folder that you just cloned CEED to)<br /> * Edit runwrapper.bat so that the relative path CEGUI_BUILD_PATH matches the folder you just compiled PyCEGUI to<br /> * Run the batch file, and the CEED editor should be launched (if not, start the guide again. If it still fails, ask for help on the CEGUI forums)<br /> <br /> <br /> == Using Python-CEED-Migrate ==<br /> You can also use the ceed-migrate tool for convert your old cegui-datafiles to the newer formats. See this page for some examples of the parameters ceed-migrate takes: [[Using CEED-Migrate]]<br /> <br /> <br /> [[Using CEED-Migrate]] <br /> [[Category:HowTo]]<br /> [[Category:Tutorials]]</div> Ident http://cegui.org/wiki/index.php?title=Ident_TODO&diff=5745 Ident TODO 2015-09-24T19:27:15Z <p>Ident: /* SVG Tessellator tests */</p> <hr /> <div>== CEGUI General ==<br /> * Texture filtering should use trilinear filtering, instead of bilinear for magnification in some (!) cases. Need to figure out which cases need which and implement a switch, etc<br /> * &lt;strike&gt;Replacing ColourRect with Colour would allow us to strip all per-vertex attributes for colours and allows us to use a highly performant uniform instead. People who want fancy fonts etc should just use Bitmap Fonts and Widgets can simply be changed to using different Images instead of applying Gradients with ColourRect there as well. &lt;/strike&gt; http://cegui.org.uk/forum/viewtopic.php?f=6&amp;t=6863<br /> * setAlpha apparently triggers recreation of GeometryBuffer should be replaced by a uniform instead of applying it to the per-vertex attributes (Done by Henri - Todo:Check if this is really 100% bullet-proof)<br /> * Check for the necessity and performance loss of unproject calls : d_owner-&gt;getRenderTarget().unprojectPoint(*d_geometry, in, p_out);<br /> * There are some Colour features that are currently unused and entirely undocumented in the CEGUI Colour class. I suggest replacing them with my own Colour classes, which were added along with the ColourPicker, and keeping onyl reworked and documented existing stuff. ( I think there was HSB or something?)<br /> <br /> == Opengl Renderers ==<br /> * Improve OpenGL Renderer(s) extra states functions (and also rename it):<br /> ** Add and also do the restore for: glUseProgram(0); glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,0); &lt;br /&gt; see https://github.com/kortemik/RBDOOM-3-BFG/blob/cegui/neo/sys/sdl/sdl_glimp.cpp#L553<br /> ** http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6752&amp;sid=6bb9fb4a04417b28278538ed3f89af57&amp;p=31632#p31632<br /> ** What about blending and scissor test?<br /> ** Good source: http://blogs.nvidia.com/blog/2014/03/20/opengl-gdc2014/<br /> <br /> == Renderers ==<br /> * If applying the ColourRect changes is successful and performance-wise alright&lt;strike&gt;, then it should be possible to use instancing for the vbo's, which basically allows to use a single VBO to render all windows. This whole procedure is supported by OpenGL 3.1+ Core (see: https://www.opengl.org/wiki/GLAPI/glDrawArraysInstanced ) and can therefore definitely be supported by the OGL3 Renderer. Probably D3D11 supports it as well (will have to look into it). &lt;/strike&gt; After checking the instancing methods, I encountered that they are not really giving any advantage for low-complexity meshes. Still, there should be ways to reduce the amount of batches.<br /> <br /> == SVG ==<br /> * Need to implement MSAA in all Renderers as alternative for the alpha blending AA<br /> * Need to fix D3D11 Rendering of SVG demo<br /> <br /> == SampleBrowser ==<br /> * Separate duties (input, Renderer-related stuff, etc) in different managers. Reduce the inheritation levels to a maximum of one. Simplify the classes. Make initialisation and deinitialisation more overlookable. Remove namespace &quot;CEGUI&quot; from all Sample-related stuff.<br /> <br /> == CEGUI docu ==<br /> * Improve cegui docu:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [17:07:59] Ident we really need to fix the docu for how to set up an application for CEGUI<br /> [17:08:33] Ident and by &quot;we&quot; i mean someone except me<br /> [17:12:50] timotei Ident: Well, there is already one, isn't it? :P<br /> [17:13:07] Ident it lacks crucial info<br /> [17:13:12] timotei Like?<br /> [17:13:19] Ident how to deinitialise cegui<br /> [17:13:25] Ident how to update cegui exactly (code samples)<br /> [17:13:37] Ident for example the notifydisplaysizechanged<br /> [17:13:49] Ident or how to render in detail<br /> [17:14:11] Ident there were some posts in the forum in that regard too<br /> [17:14:20] Ident when i have time i look through all of them and update the api docu<br /> [17:14:21] timotei CEGUI_SamplesBrowser provides some examples as far as I know<br /> [17:14:24] Ident nah<br /> [17:14:31] Ident thats not a good place to look for this<br /> [17:14:32] timotei Or you mean, simple CEGUI-ed application?<br /> [17:14:35] Ident the rendering is super-specific<br /> [17:14:43] Ident and also some of it is hidden<br /> [17:14:55] Ident it doesnt make sense to look into SamplesBrowser<br /> [17:15:13] Ident thats not what the browser is there for<br /> [17:17:35] Ident how to make an application using cegui should be well documented with examples in the api docu<br /> [17:17:43] Ident this should be the only resource for this<br /> [17:17:57] timotei I see :)<br /> [17:17:59] Ident then- how to initialise resources, load layouts and use cegui - this is where the samples come into play<br /> [17:18:00] Ident because<br /> [17:18:12] Ident there is many different ways to set up a cegui application<br /> [17:18:21] Ident we cant cover all<br /> [17:18:39] Ident of course we can and should provide code snippetsd<br /> <br /> http://cegui.org.uk/forum/viewtopic.php?f=10&amp;t=6772&amp;p=31775#p31775<br /> <br /> &lt;/source&gt;<br /> <br /> == SVG Tessellator tests ==<br /> Should be done for the various tessellator functions by comparing against the expected result in each case (as I did with the PropertyHelper unit tests)<br /> <br /> == Add tooltips to some demo ==<br /> It is currently not covered anywhere. Or is it( need to check!)?<br /> <br /> == Add properties for the classes and maybe the entire output from the properties (such as done in the WidgetDemo) into the doxygen docs ==<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [18:52:13] BoomerBile if you /*** this is the comment for class X<br /> [18:52:44] BoomerBile *** m_SomeVariable description<br /> [18:53:01] BoomerBile *** @property description<br /> [18:53:09] BoomerBile it will dump them into the api docs<br /> &lt;/source&gt;<br /> <br /> == Adapt CEGUI System/Renderer for multi-window support and write a simple demo app ==<br /> See: <br /> https://bitbucket.org/cegui/cegui/pull-request/141/improved-ogre-renderer/diff#comment-5004142<br /> <br /> and:<br /> &lt;source lang=&quot;text&quot;&gt;<br /> [15:20:53] Ident so how do you render to another window?<br /> [15:21:23] Ident if you just need to swap the FBO to render to another platofrm window then it should be easily doable in cegui<br /> [15:22:32] Luben to render to another window i would keep the default(0) fbo bound but switch ogl context if i remember correctly<br /> [15:23:04] Ident in that case the solution is also simple<br /> [15:23:12] Ident do u still have that function i gave u before open?<br /> [15:23:28] Luben SampleData::initialize?<br /> [15:24:52] Ident in the heavily convoluted System::System() constructor<br /> [15:24:54] Ident you will find<br /> [15:25:02] Ident this line: createGUIContext(d_renderer-&gt;getDefaultRenderTarget());<br /> [15:25:14] Ident what does this mean? it creates a guicontext with the default rendertarget<br /> [15:25:36] Ident the defaultrendertarget is basically<br /> [15:25:37] Ident FBO 0<br /> [15:25:44] Ident so what you would wanna do is create 3 of these<br /> [15:25:52] Ident or X of these for X amount of windows<br /> [15:26:11] Ident and when you draw them, you change your OpenGL Context before each draw call<br /> [15:30:20] Ident also do u know how to draw?<br /> [15:31:09] Luben i checked renderAllGUIContexts so i think i should be ok<br /> [15:31:14] Ident good good<br /> [15:31:25] Ident createGUIContext(d_renderer-&gt;getDefaultRenderTarget()); is all you need<br /> [15:31:28] Ident u dont need to specify a size<br /> [15:31:37] Ident oh wait<br /> [15:31:39] Ident yea<br /> [15:31:43] Ident this means that it will only work<br /> [15:31:47] Ident if all your windows are the same size<br /> [15:31:56] Ident the size that is specified for system::notifydisplaysizechanged<br /> [15:32:14] Luben well, that blows..<br /> &lt;/source&gt;<br /> <br /> docs: http://blog.gvnott.com/2013/05/18/tutorial-multiple-windows-with-glfw3-and-glew-mx/<br /> <br /> http://www.glfw.org/docs/latest/group__context.html#ga15a5a1ee5b3c2ca6b15ca209a12efd14</div> Ident http://cegui.org/wiki/index.php?title=Category:Tutorials&diff=5744 Category:Tutorials 2015-09-07T14:12:16Z <p>Ident: </p> <hr /> <div>Tutorials are longer articles focused on how to achieve just the one thing (preferably). How-tos are very similar but are usually much shorter and less in-depth. Remember to look at the official docs (API docu) for version-specific and potentially more up to date information. Also feel free to correct any issues you might find on the wiki.</div> Ident http://cegui.org/wiki/index.php?title=MediaWiki:Sidebar&diff=5743 MediaWiki:Sidebar 2015-09-07T14:10:27Z <p>Ident: </p> <hr /> <div>* Main<br /> ** http://www.cegui.org.uk/wiki | Home<br /> ** http://www.cegui.org.uk/download | Releases<br /> ** http://www.cegui.org.uk/news | News<br /> ** https://bitbucket.org/cegui/ | Repository<br /> ** recentchanges-url | Recent Changes<br /> <br /> * Community<br /> ** http://www.cegui.org.uk/phpBB2/index.php | Forum<br /> ** https://twitter.com/ceguilib | Twitter<br /> ** irc://irc.freenode.net/#cegui | #cegui<br /> <br /> * Documentation<br /> ** http://static.cegui.org.uk/docs/ | Official documentation<br /> ** Category:Tutorials |Tutorials<br /> ** Category:HowTo |HowTo<br /> ** Category:Manuals |Manuals</div> Ident http://cegui.org/wiki/index.php?title=Main_Page&diff=5742 Main Page 2015-09-07T14:07:44Z <p>Ident: </p> <hr /> <div>&lt;!-- Main Page Header (formerly Template:CEGUIWelcome) --&gt; <br /> {{Section|1=Welcome to the &lt;em&gt;&lt;b&gt;CEGUI Community Wiki&lt;/b&gt;&lt;/em&gt;|2=<br /> <br /> &lt;div style=&quot;text-align:center;font-size:14px;&quot;&gt;<br /> Welcome to the official CEGUI community Wiki. All users are encouraged to contribute! To contribute, please login with your [http://www.cegui.org.uk/phpBB2/index.php forum] account.<br /> &lt;/div&gt;<br /> &lt;div style=&quot;text-align:center;font-size:14px;&quot;&gt;<br /> For the official API docs please visit [http://static.cegui.org.uk/docs/ our api docs page]<br /> &lt;/div&gt;<br /> &lt;div style=&quot;text-align:center;font-size:14px;&quot;&gt;<br /> All news, releases and more can be found on the official [http://www.cegui.org.uk CEGUI website].<br /> &lt;/div&gt;<br /> <br /> }}<br /> <br /> <br /> &lt;!-- Section 2: Downloading and Installing --&gt;<br /> {{Section|1=Getting CEGUI|2=<br /> * [[Downloads|Download a Release]]<br /> * [[Obtaining_the_library_source_from_Mercurial|Build it from source]]<br /> }}<br /> <br /> &lt;!-- Section 3: How to use CEGUI --&gt;<br /> {{Section|1=Working with CEGUI|2= <br /> * [http://static.cegui.org.uk/docs Official API docs for all Releases]<br /> * [https://bitbucket.org/cegui/cegui CEGUI ReadMe]<br /> * [[Helpful_Links|A concise collection of helpful links for CEGUI users]]<br /> * [[:Category:Tutorials|Tutorials]]: All tutorials to help you getting started with CEGUI<br /> * [[:Category:HowTo|How-To series]]: How to deal with a specific feature of CEGUI<br /> * [[:Category:Manuals|Manuals]]: Some more advanced material on using CEGUI <br /> }}<br /> <br /> &lt;!-- Section 4: CEGUI for Content Creators --&gt; <br /> {{Section|1=CEGUI for Content Creators|2=<br /> * [[CEED]] - The official tool for CEGUI<br /> * [[Assembling a Toolset|Tools]]: Gather the tools that can help you with the creation of your GUI <br /> * [http://cegui.org.uk/docs/current/fal_man.html &quot;Falagard&quot; Skinning System Documentation]: All you ever wanted to know on falagard skinning system (and more) <br /> * [[XML File formats]]: Description of all XML file format used in CEGUI <br /> * [http://skins.cegui.org.uk Skins]: (WIP) Find some existing skins. There are more on the forums.<br /> }}<br /> <br /> &lt;!-- Section 1: About CEGUI --&gt; <br /> {{Section|1=About CEGUI|2=<br /> * [http://cegui.org.uk CEGUI website]<br /> * [[FAQ|Everything About CEGUI (FAQ)]] (Old)<br /> * [[Developer Team]]<br /> * [[Projects Using CEGUI]]: Games and other software using CEGUI<br /> }}<br /> <br /> <br /> {{Section|1=Featured Videos from our [http://www.youtube.com/ceguiproject YouTube Channel]|2=<br /> &lt;table width=&quot;795&quot; style=&quot;margin-left: auto; margin-right: auto&quot;&gt;<br /> &lt;tr&gt;<br /> &lt;td rowspan=&quot;2&quot; colspan=&quot;2&quot;&gt;&lt;youtube width=&quot;640&quot; height=&quot;320&quot;&gt;iXsZh1owpBI&lt;/youtube&gt;<br /> &lt;/td&gt;<br /> &lt;td&gt;&lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;AM5_YarbwNg&lt;/youtube&gt;&lt;/td&gt;&lt;td&gt;<br /> &lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;ldSd45xlVU0&lt;/youtube&gt;&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;&lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;eRC5R9aA_Zs&lt;/youtube&gt;&lt;/td&gt;&lt;td&gt;<br /> &lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;Z5Uf9IsWCXY&lt;/youtube&gt;&lt;/td&gt;&lt;/tr&gt;<br /> &lt;/table&gt;<br /> }}<br /> {| width=&quot;100%&quot; background-color=&quot;transparent&quot;<br /> |valign=&quot;top&quot;|</div> Ident http://cegui.org/wiki/index.php?title=Main_Page&diff=5741 Main Page 2015-09-07T14:07:20Z <p>Ident: </p> <hr /> <div>&lt;!-- Main Page Header (formerly Template:CEGUIWelcome) --&gt; <br /> {{Section|1=Welcome to the &lt;em&gt;&lt;b&gt;CEGUI Community Wiki&lt;/b&gt;&lt;/em&gt;|2=<br /> <br /> &lt;div style=&quot;text-align:center;font-size:14px;&quot;&gt;<br /> Welcome to the official CEGUI community Wiki. All users are encouraged to contribute! To contribute, please login with your [http://www.cegui.org.uk/phpBB2/index.php forum] account. &lt;br /&gt;&lt;br /&gt;<br /> For the official API docs please visit [http://static.cegui.org.uk/docs/ our api docs page]<br /> &lt;/div&gt;<br /> &lt;div style=&quot;text-align:center;font-size:14px;&quot;&gt;<br /> All news, releases and more can be found on the official [http://www.cegui.org.uk CEGUI website].<br /> &lt;/div&gt;<br /> <br /> }}<br /> <br /> <br /> &lt;!-- Section 2: Downloading and Installing --&gt;<br /> {{Section|1=Getting CEGUI|2=<br /> * [[Downloads|Download a Release]]<br /> * [[Obtaining_the_library_source_from_Mercurial|Build it from source]]<br /> }}<br /> <br /> &lt;!-- Section 3: How to use CEGUI --&gt;<br /> {{Section|1=Working with CEGUI|2= <br /> * [http://static.cegui.org.uk/docs Official API docs for all Releases]<br /> * [https://bitbucket.org/cegui/cegui CEGUI ReadMe]<br /> * [[Helpful_Links|A concise collection of helpful links for CEGUI users]]<br /> * [[:Category:Tutorials|Tutorials]]: All tutorials to help you getting started with CEGUI<br /> * [[:Category:HowTo|How-To series]]: How to deal with a specific feature of CEGUI<br /> * [[:Category:Manuals|Manuals]]: Some more advanced material on using CEGUI <br /> }}<br /> <br /> &lt;!-- Section 4: CEGUI for Content Creators --&gt; <br /> {{Section|1=CEGUI for Content Creators|2=<br /> * [[CEED]] - The official tool for CEGUI<br /> * [[Assembling a Toolset|Tools]]: Gather the tools that can help you with the creation of your GUI <br /> * [http://cegui.org.uk/docs/current/fal_man.html &quot;Falagard&quot; Skinning System Documentation]: All you ever wanted to know on falagard skinning system (and more) <br /> * [[XML File formats]]: Description of all XML file format used in CEGUI <br /> * [http://skins.cegui.org.uk Skins]: (WIP) Find some existing skins. There are more on the forums.<br /> }}<br /> <br /> &lt;!-- Section 1: About CEGUI --&gt; <br /> {{Section|1=About CEGUI|2=<br /> * [http://cegui.org.uk CEGUI website]<br /> * [[FAQ|Everything About CEGUI (FAQ)]] (Old)<br /> * [[Developer Team]]<br /> * [[Projects Using CEGUI]]: Games and other software using CEGUI<br /> }}<br /> <br /> <br /> {{Section|1=Featured Videos from our [http://www.youtube.com/ceguiproject YouTube Channel]|2=<br /> &lt;table width=&quot;795&quot; style=&quot;margin-left: auto; margin-right: auto&quot;&gt;<br /> &lt;tr&gt;<br /> &lt;td rowspan=&quot;2&quot; colspan=&quot;2&quot;&gt;&lt;youtube width=&quot;640&quot; height=&quot;320&quot;&gt;iXsZh1owpBI&lt;/youtube&gt;<br /> &lt;/td&gt;<br /> &lt;td&gt;&lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;AM5_YarbwNg&lt;/youtube&gt;&lt;/td&gt;&lt;td&gt;<br /> &lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;ldSd45xlVU0&lt;/youtube&gt;&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;&lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;eRC5R9aA_Zs&lt;/youtube&gt;&lt;/td&gt;&lt;td&gt;<br /> &lt;youtube width=&quot;320&quot; height=&quot;180&quot;&gt;Z5Uf9IsWCXY&lt;/youtube&gt;&lt;/td&gt;&lt;/tr&gt;<br /> &lt;/table&gt;<br /> }}<br /> {| width=&quot;100%&quot; background-color=&quot;transparent&quot;<br /> |valign=&quot;top&quot;|</div> Ident