Horde3D Wiki - User contributions [en]

GUI Extension

2010-01-25T16:40:56Z

Phoenix64: Small additions/fixes

[[category: Extensions]]
{| border="0"
| {{ContentBlock|width=800|color=white |content=The GUI extensions adds a GUi system to Horde3D which can be used to display both 3D GUIs and 2D menus. This is done by defining a common GUI scene node which renders 2D geometry at the local xy plane of the scene node. All GUI elements are skinnable. The GUI uses wchar_t for all strings.

The extension was presented in the forum here: http://www.horde3d.org/forums/viewtopic.php?f=6&t=1065

= Getting the extension =
The extension is in my mercurial fork of the official horde3d repository at http://bitbucket.org/mgottschlag/horde3dext/. Click on "get source" in the upper right corner to download a snapshot of the sources.

The repository contains always-up-to-date CMake files, but the MSVC files might be outdated. If you cannot compile Horde3D, ask in the forum thread mentioned above.

= Font rendering options =
If compiling with CMake, you can select FreeType font rendering via cmake options as an alternative to the internal font renderer. This provides better looking text, but comes with the disadvantage that you need FreeType development files and the CMake freetype module installed. Only has been tested on Linux so far.

= Implemented widgets =

* Buttons
* Edit boxes
* Check boxes
* Group boxes

= Position system =

For pixel-perfect layouts at all (and even at varying) screen sizes, a combination of relative and absolute addressing is used. A position (or size) is built from 4 values, 2 absolute ones in pixels, and to values relative to the screen size. For example the position (0.5, 10, 0.25, -20) with a screensize of 1280 * 1024 pixels would result in the absolute position with x = 0.5 * 1280 + 10 = 650 and y = 0.25 * 1024 - 20 = 236.

= Rendering =
The GUI resource only provides position and UV coordinate information for the vertices, the normals are assumed to be along the local z axis.

The GUI scene node only can render quads, and the quads are put together in batches. The batches are cached and only updated when necessary (though this can still be optimized, much more is updated than what would be necessary atm).

The font glyphs are rendered in software once when they are used for the first time and then saved to a texture specified in the font resource (for an example resource see the GUI example in the repository).

= Usage example =

The following code creates a GUI with one button and one edit box:

<pre>
H3DRes fontMatRes = h3dAddResource( H3DResTypes::Material, "overlays/font.material.xml", 0 );
// GUI skin
H3DRes skinRes = h3dAddResource( H3DGUI_ResType_Skin, "skins/gui.skin.xml", 0 );
// Load resources
h3dutLoadResourcesFromDisk( _contentDir.c_str() );
// Add gui
H3DNode gui = h3dguiAddGUI( screen, "GUI", skinRes );
h3dSetNodeTransform( gui, 0, 0, 0, 0, 0, 0, 0.8f, 0.6f, 1 );
// Set virtual screen size
h3dSetNodeParamI( gui, H3DGUINode::WidthI, 320 );
h3dSetNodeParamI( gui, H3DGUINode::HeightI, 240 );
H3DGUIElement root = h3dguiGetRoot(_gui);
h3dguiSetElementParamI( _gui, root, H3DElementParam::ShowBackgroundI, 1 );
// Add a frame around the elements
H3DGUIElement frame = h3dguiAddFrame(_gui, root);
h3dguiSetElementParamStr( _gui, frame, FrameParam::LabelStr, L"Example GUI" );
// Add an editbox
H3DGUIElement editbox = h3dguiAddEditBox(_gui, frame);
h3dguiSetPosition( gui, editbox, 0.1f, 0, 0.1f, 0 );
h3dguiSetSize( gui, editbox, 0.8f, 0, 0.3f, 0 );
h3dguiSetElementParamStr( gui, editbox, EditBoxParam::TextStr, L"EditBox" );
// Add a button
H3DGUIElement button = h3dguiAddButton(gui, frame);
h3dguiSetPosition( gui, button, 0.f, 0, 0.5f, 0 );
h3dguiSetSize( gui, button, 0.8f, 0, 0.3f, 0 );
h3dguiSetElementParamStr( gui, button, ButtonParam::LabelStr, L"Button" );
// Set an action ID for the button
h3dguiSetElementParamI( gui, button, H3DElementParam::ActionIdI, 1 );
</pre>

Mouse and keyboard input are injected like this:

<pre>
// Insert printable char
h3dguiInsertChar( gui, 'A' );
// Insert special key (1 = pressed)
h3dguiInsertKey( gui, H3DGUIKey::Return, 1 );
// Insert new mouse position
h3dguiSetMousePosition( gui, 100, 100 );
// Insert left mouse button event (0 = left mouse button, 1 = pressed)
h3dguiSetMouseButton( gui, 0, 1 );
</pre>

Events from the GUI are handled like this:
<pre>
while( h3dguiHasEvent( gui ) )
{
int type = h3dguiGetEventType( gui );
unsigned int actionid = h3dguiGetEventActionID( gui );
if( type == H3DGUIEvent::Action && actionid == 1 )
{
std::cout << "Button has been pressed!" << std::endl;
}
}
</pre>

There also is an example showing how to use a 3D GUI in the repository at Extensions/GUI/Sample.

= Screenshot =

http://img63.imageshack.us/img63/3766/guir.png

= Things still missing =

Feel free to participate here:

* Windows, dialogs, modal events
* List boxes
* Radio buttons
* Copy/Paste
* Image elements

}} 
| valign="top" |{{Extension_Summary|
name = GUI Extension|
screenshot = H3DGUI.jpg|
description = The GUI extension adds a tightly integrated GUI system to Horde3D.|
horde3dversion = svn head|
author = Mathias Gottschlag|
}}
|}

Extensions

2010-01-25T16:31:49Z

Phoenix64:

Horde3D provides an easy to use extension mechanism which allows additional functionality to be added to Horde3D.

==Available Extensions==

[[Image:H3Dterrain.jpg]] [[Terrain Extension]] - Heightmap based terrain with automatic LOD

[[Image:H3Dsound.jpg]] [[Sound Extension]] - 3D positional audio based on OpenAL

[[Image:H3DGUI.png]] [[GUI Extension]] - A fully integrated GUI system for Horde3D

GUI Extension

2010-01-25T16:31:13Z

Phoenix64: GUI extension page

[[category: Extensions]]
{| border="0"
| {{ContentBlock|width=800|color=white |content=The GUI extensions adds a GUi system to Horde3D which can be used to display both 3D GUIs and 2D menus. This is done by defining a common GUI scene node which renders 2D geometry at the local xy plane of the scene node. All GUI elements are skinnable. The GUI uses wchar_t for all strings.

The extension was presented in the forum here: http://www.horde3d.org/forums/viewtopic.php?f=6&t=1065

= Getting the extension =
The extension is in my mercurial fork of the official horde3d repository at http://bitbucket.org/mgottschlag/horde3dext/. Click on "get source" in the upper right corner to download a snapshot of the sources.

The repository contains always-up-to-date CMake files, but the MSVC files might be outdated. If you cannot compile Horde3D, ask in the forum thread mentioned above.

= Font rendering options =
If compiling with CMake, you can select FreeType font rendering via cmake options as an alternative to the internal font renderer. This provides better looking text, but comes with the disadvantage that you need FreeType development files and the CMake freetype module installed. Only has been tested on Linux so far.

= Implemented widgets =

* Buttons
* Edit boxes
* Check boxes
* Group boxes

= Usage example =

The following code creates a GUI with one button and one edit box:

<pre>
H3DRes fontMatRes = h3dAddResource( H3DResTypes::Material, "overlays/font.material.xml", 0 );
// GUI skin
H3DRes skinRes = h3dAddResource( H3DGUI_ResType_Skin, "skins/gui.skin.xml", 0 );
// Load resources
h3dutLoadResourcesFromDisk( _contentDir.c_str() );
// Add gui
H3DNode gui = h3dguiAddGUI( screen, "GUI", skinRes );
h3dSetNodeTransform( gui, 0, 0, 0, 0, 0, 0, 0.8f, 0.6f, 1 );
// Set virtual screen size
h3dSetNodeParamI( gui, H3DGUINode::WidthI, 320 );
h3dSetNodeParamI( gui, H3DGUINode::HeightI, 240 );
H3DGUIElement root = h3dguiGetRoot(_gui);
h3dguiSetElementParamI( _gui, root, H3DElementParam::ShowBackgroundI, 1 );
// Add a frame around the elements
H3DGUIElement frame = h3dguiAddFrame(_gui, root);
h3dguiSetElementParamStr( _gui, frame, FrameParam::LabelStr, L"Example GUI" );
// Add an editbox
H3DGUIElement editbox = h3dguiAddEditBox(_gui, frame);
h3dguiSetPosition( gui, editbox, 0.1f, 0, 0.1f, 0 );
h3dguiSetSize( gui, editbox, 0.8f, 0, 0.3f, 0 );
h3dguiSetElementParamStr( gui, editbox, EditBoxParam::TextStr, L"EditBox" );
// Add a button
H3DGUIElement button = h3dguiAddButton(gui, frame);
h3dguiSetPosition( gui, button, 0.f, 0, 0.5f, 0 );
h3dguiSetSize( gui, button, 0.8f, 0, 0.3f, 0 );
h3dguiSetElementParamStr( gui, button, ButtonParam::LabelStr, L"Button" );
// Set an action ID for the button
h3dguiSetElementParamI( gui, button, H3DElementParam::ActionIdI, 1 );
</pre>

Mouse and keyboard input are injected like this:

<pre>
// Insert printable char
h3dguiInsertChar( gui, 'A' );
// Insert special key (1 = pressed)
h3dguiInsertKey( gui, H3DGUIKey::Return, 1 );
// Insert new mouse position
h3dguiSetMousePosition( gui, 100, 100 );
// Insert left mouse button event (0 = left mouse button, 1 = pressed)
h3dguiSetMouseButton( gui, 0, 1 );
</pre>

Events from the GUI are handled like this:
<pre>
while( h3dguiHasEvent( gui ) )
{
int type = h3dguiGetEventType( gui );
unsigned int actionid = h3dguiGetEventActionID( gui );
if( type == H3DGUIEvent::Action && actionid == 1 )
{
std::cout << "Button has been pressed!" << std::endl;
}
}
</pre>

There also is an example showing how to use a 3D GUI in the repository at Extensions/GUI/Sample.

= Screenshot =

http://img63.imageshack.us/img63/3766/guir.png

= Things still missing =

Feel free to participate here:

* Windows, dialogs, modal events
* List boxes
* Radio buttons
* Copy/Paste
* Image elements

}} 
| valign="top" |{{Extension_Summary|
ame = GUI Extension|
screenshot = H3DGUI.jpg|
description = The GUI extension adds a tightly integrated GUI system to Horde3D.|
horde3dversion = svn head|
author = Mathias Gottschlag|
}}
|}

Community Roadmap

2008-09-07T10:14:33Z

Phoenix64:

As a way to keep the Horde3D community on the same page in regards to the development of future features, this Community Roadmap will keep an up to date log of the undergoing activities.

{| cellpadding="2" cellspacing="0" style="width: 100%"
|- bgcolor="#6699FF" style="font-size: medium; font-weight: bold"
| Feature
| Description
| Assigned to
| Completion
| Released in
|-
| D3D Backend
| Write a D3D9/D3D10 backend, in addition to the current OpenGL backend
|  
|  
|  
|- bgcolor="#FFFF66"
| [[Community_Roadmap_-_Compressed_Texture_Support|Compressed Texture Support]]
| Support for DDS, PowerVR, and other Texture formats.
| swiftcoder
|  
|  
|-
| OpenGL ES2.x Backend
| Write a OpenGL ES2.x backend, Horde3D port for mobile platforms
| DDd
| 10%
| (EST.) December 2008
|-
| Ambient Occlusion
| Add ambient occlusion support for Horde3D
|  
|  
|  
|}

<h3>Wishlist:</h3>
{| cellpadding="2" cellspacing="0" style="width: 100%"
|- bgcolor="#6699FF" style="font-size: medium; font-weight: bold"
| Feature
| Description
|-
| Texture Improvements
| Support for simple downloading of texture data, mipmaps for RTT render targets (for e.g. impostors)
|}
----

{| style="width: 100%"
|-
| <h3><span class="mw-headline">Upcoming Horde3D Version: 1.0</span></h3>
| <h3><span class="mw-headline">Upcoming Horde3D Editor version: 1.0</span></h3>
|-
| <b>The current version is: v1.0.0 Beta1</b>
| <b>The current version is: v0.7.0</b>
|-
|For version 1.0.0 Beta1 of Horde3D the following features have been
integrated:</p>
<ul>
<li><b>Occlusion Culling</b></li>
<li><b>Render-to-Texture</b></li>
<li><b>Stereo Rendering</b></li>
<li><b>Software Skinning</b></li>
<li><b>Node Sorting</b></li>
</ul>
The first will give polygonally dense worlds a boost in speed and the second can be used to do all sorts of effects. See also the
[http://www.horde3d.org/docs/_changeLog.html changelog] for more details.
In the following weeks no new features will be implemented. Instead the development will be focused on bug fixes and further documentation.
| The next version 0.7.0 will be based on Horde3D v.1.0.0 Beta1 and will focus on a better extensibility using plugins (e.g. the terrain node extension will be a plugin and not a fixed part of the editor anymore). Further on there will be support for front, top, and right view of the scene with orthographic projection.
|}

Community Roadmap

2008-09-06T22:27:16Z

Phoenix64:

As a way to keep the Horde3D community on the same page in regards to the development of future features, this Community Roadmap will keep an up to date log of the undergoing activities.

{| cellpadding="2" cellspacing="0" style="width: 100%"
|- bgcolor="#6699FF" style="font-size: medium; font-weight: bold"
| Feature
| Description
| Assigned to
| Completion
| Released in
|-
| D3D Backend
| Write a D3D9/D3D10 backend, in addition to the current OpenGL backend
|  
|  
|  
|- bgcolor="#FFFF66"
| [http://horde3d.org/wiki/index.php5?title=Community_Roadmap_-_Compressed_Texture_Support Compressed Texture Support]
| Support for DDS, PowerVR, and other Texture formats.
| swiftcoder
|  
|  
|-
| OpenGL ES2.x Backend
| Write a OpenGL ES2.x backend, Horde3D port for mobile platforms
| DDd
| 10%
| (EST.) December 2008
|-
| Ambient Occlusion
| Add ambient occlusion support for Horde3D
|  
|  
|  
|}

<h3>Wishlist:</h3>
{| cellpadding="2" cellspacing="0" style="width: 100%"
|- bgcolor="#6699FF" style="font-size: medium; font-weight: bold"
| Feature
| Description
|-
| Texture Improvements
| Support for simple downloading of texture data, mipmaps for RTT render targets (for e.g. impostors)
|}
----

{| style="width: 100%"
|-
| <h3><span class="mw-headline">Upcoming Horde3D Version: 1.0</span></h3>
| <h3><span class="mw-headline">Upcoming Horde3D Editor version: 1.0</span></h3>
|-
| <b>The current version is: v1.0.0 Beta1</b>
| <b>The current version is: v0.7.0</b>
|-
|For version 1.0.0 Beta1 of Horde3D the following features have been
integrated:</p>
<ul>
<li><b>Occlusion Culling</b></li>
<li><b>Render-to-Texture</b></li>
<li><b>Stereo Rendering</b></li>
<li><b>Software Skinning</b></li>
<li><b>Node Sorting</b></li>
</ul>
The first will give polygonally dense worlds a boost in speed and the second can be used to do all sorts of effects. See also the
[http://www.horde3d.org/docs/_changeLog.html changelog] for more details.
In the following weeks no new features will be implemented. Instead the development will be focused on bug fixes and further documentation.
| The next version 0.7.0 will be based on Horde3D v.1.0.0 Beta1 and will focus on a better extensibility using plugins (e.g. the terrain node extension will be a plugin and not a fixed part of the editor anymore). Further on there will be support for front, top, and right view of the scene with orthographic projection.
|}