Parents (Total: 22)

The searched file hash is included in 22 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
FileSize	104680
MD5	8A92C4892FFD9B6897FA18A0E6D09F87
PackageDescription	WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainer	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-1.3-dev
PackageSection	libdevel
PackageVersion	1.3.23-8
SHA-1	05DD00D40D0DEF31C6F23D4EC992F38B373FE5EF
SHA-256	0B3C796F047CF271C9832DF936B0B4A408B289379613A5F73174659C007667AF

Key	Value
FileSize	226356
MD5	81D0DA8BC1A5628C292250AC27FAC689
PackageDescription	WorldForge client entity library Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction.
PackageMaintainer	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-1.3-21
PackageSection	libs
PackageVersion	1.3.23-8
SHA-1	05F454429211F9CC61E8B4900EEB9312C1385C42
SHA-256	00042998D9CFAF3776A71BA5E060B7A307EB40F0BCA74494AFB3110B9F93A168

Key	Value
FileSize	242396
MD5	017FBB92D00BF3900B33BA22EB39B428
PackageDescription	WorldForge client entity library Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction.
PackageMaintainer	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-1.3-21
PackageSection	libs
PackageVersion	1.3.23-8
SHA-1	0D6151886294087799EAD8D22F2A06A8F0B56D5D
SHA-256	54AA1011C3CCAA61C77C58175C376D3AD27BEC99C5EBABE969BFE9721DE2A46F

Key	Value
FileSize	271572
MD5	BC7AE9ACB87CA16045FBEA0441DDBA41
PackageDescription	WorldForge client entity library - API documentation Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the API documentation in HTML format.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	liberis-doc
PackageSection	doc
PackageVersion	1.3.23-8
SHA-1	1279CC5B3BD45C2FD80F3A2B1E9FDBF71D782385
SHA-256	E2B2473136CDFA01759316B6CD53B809512C92CDEA63DCA679E39392380A0609

Key	Value
FileSize	104680
MD5	9AFA05F48767018DA8DC74863B5FB8E7
PackageDescription	WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainer	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-1.3-dev
PackageSection	libdevel
PackageVersion	1.3.23-8
SHA-1	2BA45C1E266FB74067C6767A128FC565C41766C8
SHA-256	8F9D71FF1569883D94723A47F40152EFF22CB240A91674701DA16ADB20D70CD6

Key	Value
FileSize	104676
MD5	8CDDF70DB8456FB745CCF9E10A8FE2E7
PackageDescription	WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainer	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-1.3-dev
PackageSection	libdevel
PackageVersion	1.3.23-8
SHA-1	3431CBEBA27314B570C83625CF93458A6E724F5B
SHA-256	C9B50B778CBA4C55466B3D9A187DA7EF8841EF81F4B19F872A4F28A00C71505D

Key	Value
FileSize	104676
MD5	F997140FEB3F9AF6DC1F9D96284A1A4C
PackageDescription	WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainer	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-1.3-dev
PackageSection	libdevel
PackageVersion	1.3.23-8
SHA-1	4BE391E5C5ACCD732C688E7E6F9A8E4F42FB0FB3
SHA-256	335BB5582A4A9F2EFD16DBF51875FA3D272FB6AF60393A47D45B4E8BCDA795B4

Key	Value
FileSize	42648
MD5	0075B01054A48BD9DE4792422F7C2423
PackageDescription	WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	liberis-1.3-dev
PackageSection	libdevel
PackageVersion	1.3.23-8
SHA-1	63AFDFD29ED950202B2B9D8C1AD9EA9D84C0C284
SHA-256	14B1AE99C98983A215E9F5D1AA81BB4131E8C5D0F381E337A31F841F1527762E

Key	Value
FileSize	232260
MD5	6C0EF9B38A87EF337F862DA6D86550EF
PackageDescription	WorldForge client entity library Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction.
PackageMaintainer	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-1.3-21
PackageSection	libs
PackageVersion	1.3.23-8
SHA-1	661FEA4ABC8A628640BD3E43472390A061C4EA31
SHA-256	1CC921A6C82BC1E70A979AE3107C5AD8FDA076888503EE5D8C75B6D4944493AF

Key	Value
FileSize	241336
MD5	B6780414E82ED508D3E210B7642EF990
PackageDescription	WorldForge client entity library Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction.
PackageMaintainer	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-1.3-21
PackageSection	libs
PackageVersion	1.3.23-8
SHA-1	6D1B2B19DEE52B13B7A6B56FF32760C16886EE46
SHA-256	8F1FC3050B514E1DB43D05FB12B64AE4A7DC8B851AC78A64DF58866BFF445856