Parents (Total: 37)

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

Key	Value
FileSize	188532
MD5	CADB629AD5FA5306CFD2371757FD643C
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	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	liberis-1.3-21
PackageSection	libs
PackageVersion	1.3.23-7ubuntu1
SHA-1	0BA2ADBE58F0D89C55B40BA4470339F9F53D5B4D
SHA-256	91B56BA8E15570FC9AE4834C69F5E11DADBA4974A2D264AEF8AF1B105662D051

Key	Value
FileSize	260188
MD5	DD4F5238E3CA28D828BAA3F4F4CECA19
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-7+b1
SHA-1	209CD6F5B6382D9294E65A6890DFE29D06115C2F
SHA-256	CD52001BAF7283253C80C4EB4AD129E9AFCA803BD2357324EBB311754C7B77BC

Key	Value
FileSize	246184
MD5	082ABE272E591EAFEEDC0F1AE375DF3C
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	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	liberis-1.3-21
PackageSection	libs
PackageVersion	1.3.23-7ubuntu1
SHA-1	3442CFD83B71E7C577ACE65D69FF69C04BEB0E36
SHA-256	1AD8E1579BC5A6574F4D62A232F1A6C678DA26641EA52493E5789BB51E634043

Key	Value
FileSize	281104
MD5	FF21BC80CE58903343DEFFECF06984E5
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-7+b1
SHA-1	3741510C39D82E20B3A14573FAA212AFFD9A2608
SHA-256	FBD4FD233E31FB34DB5041D6A99220F3478CB48B43DD37C722C13980554AD0E5

Key	Value
FileSize	267032
MD5	09E5CA8CA4D8690134DCF39D6EB59D38
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-7ubuntu1
SHA-1	3F5E5C62C0B919D31F69C8CD868C2B79084E6974
SHA-256	CDEFA62ED4E6815C5B1B28EE861CD2A65D8C3D1CC559C79877CE8EDD7E4036E4

Key	Value
FileSize	104872
MD5	7B03BFA8B27C390C5F1CF0C4647EDA6F
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-7+b1
SHA-1	54B3019E35A04F2D48D54EA4891E5ADE7A259F0F
SHA-256	C6143C865FEAC38ED066F72C66A5DE40A2E9D18CAADF17F8F007B5D63BBD6C2C

Key	Value
FileSize	42636
MD5	365BD02C90BDA8CEEBF154CCEB11853B
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-7ubuntu1
SHA-1	5FD85BEA767732BAAD964643A8F1F56EF4796A10
SHA-256	23CECE348E3683D623F3103ED5F078EF2FFB1A519F6B4CEFCFD4588D51C1B8A5

Key	Value
FileSize	104868
MD5	A53014E7D9F864D945774655B71C380F
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-7+b1
SHA-1	632C3FAFFB6CB197E26B770EDDEF5AB53F11D2BE
SHA-256	E400744FE07D980C3C0A20B572DB2577A54CC8CDADEA7D8EF3C464F63A3512E1

Key	Value
FileSize	327372
MD5	C6F2E8C36C61316135DF7EC1742858EC
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	Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageName	liberis-doc
PackageSection	doc
PackageVersion	1.3.23-7
SHA-1	63B39601FA3010A1799A66AC6AA52D9456017C38
SHA-256	7C3BED9CA6B961932D5CFDE00D459A1A89011F7E5878B7D921C0540C0A929F3B

Key	Value
FileSize	104860
MD5	464029F7B98054F3814FFF7D883E048F
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-7+b1
SHA-1	668AB0D1477A2C0FCEA36A9923397BAE817AC8B0
SHA-256	8703BB7DC3A874DA4BD5E309E490F46F99859F871D8CD96E5BEE23C8BF014514