Ecere: Difference between revisions

24 bytes added ,  15 years ago
no edit summary
No edit summary
No edit summary
Line 11:
The runtime component has a very small footprint. It can either take the form of a shared or static library. In its simplest form it can be bundled into a single application executable smaller than 1 megabyte on Windows.
 
== Cross Platform [[GUI|Graphical User Interface]] ==
One of the most important feature of the runtime component is the custom cross platform GUI engine.
It is an alternative and is analogous to other GUI toolkits such as wxWindows, GTK or Qt.
It also offers a rich 2D text, graphics and image manipulation system supporting a variety of graphics file formats.
 
== System Functionality ==
The runtime component covers many powerful general functionality covering advanced file access, multi-threading, time. It also greatly simplifies socket programming (either through UDP or TCP/IP).
 
== 3D Graphics Engine ==
The runtime component contains a powerful and easy to use 3D graphics engine, introducing concepts of cameras, meshes, materials, lights and objects.
It currently supports loading models from the 3DS file format. Meshes can also be built dynamically through the [[API]]. The engine supports both Direct3D and [[OpenGL]].
 
== Component Object Model ==
The runtime component also enables the entire Ecere Component Object Model and its advanced features such as distributed objects, dynamic class hierarchy amalgamation, dynamic injection and ejection of modules and their components as well as automatic data type management.