Parents (Total: 19)

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

Key	Value
FileSize	1868982
MD5	BE958468082CB7A3F91CBE909083DAA9
PackageDescription	The WorldForge client entity library - debugging 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. . This package contains the debugging library.
PackageMaintainer	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-11-dbg
PackageSection	libdevel
PackageVersion	1.3.10-2
SHA-1	046288566EADD81A6304F6097B64AD7AFD584CEC
SHA-256	513149CFA5EEF6B17699FAB56B6BF736862AD54DA1EC4E0A925ABB191E68DFCC

Key	Value
FileSize	1903942
MD5	55628EBB79D15594412C84C7F11A3EB5
PackageDescription	The WorldForge client entity library - debugging 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. . This package contains the debugging library.
PackageMaintainer	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-11-dbg
PackageSection	libdevel
PackageVersion	1.3.10-2
SHA-1	05013FF044B3183FD4CBEB8F9F4251DFE40DFC48
SHA-256	D93C93EEC80577F6B4E0DFF9852957974A9599BA5D5F1023001DC8F785B21C15

Key	Value
FileSize	1846356
MD5	EB3BD4013CA2FB93F6BD9C91E12E5968
PackageDescription	The WorldForge client entity library - debugging 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. . This package contains the debugging library.
PackageMaintainer	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-11-dbg
PackageSection	libdevel
PackageVersion	1.3.10-2
SHA-1	177745D4A6D51BF58CE5B73F214B5F7A3B448393
SHA-256	7B4EFFE36AEF78BA1CDD6C4B3F5E3DD7C5B6359347899D6E68792CCE95E556CD

Key	Value
FileSize	82254
MD5	7E93439BC3A4A89B336CB6C1B5143728
PackageDescription	The 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	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-dev
PackageSection	libdevel
PackageVersion	1.3.10-2
SHA-1	1C3E041EE97753DFB1231068756A282A2533E9F1
SHA-256	B7EA04794B9D555E515FED540C52CE96ECF07A0895212852A4D121C5EC6CDE73

Key	Value
FileSize	179864
MD5	5EC7F097B856EEFA30165A940F4D89BA
PackageDescription	The 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	Michael Koch <konqueror@gmx.de>
PackageName	liberis-doc
PackageSection	doc
PackageVersion	1.3.10-2
SHA-1	1D849328297E96EB195C5B5B428C85B57AF54428
SHA-256	CC81EFA51906D9238462EE77CCF6057B13E0AF3583AFFC9BE6301C9137A83425

Key	Value
FileSize	278694
MD5	29370854EB3278DF91A3B26F1BECA25D
PackageDescription	The 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	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-11
PackageSection	libs
PackageVersion	1.3.10-2
SHA-1	26D1D53312677E55E2E7494FFF4285F39F823ED6
SHA-256	B75AAC0744305E66AF0007A60FF765782B2A66719AF550CDF8F0DA29169155A2

Key	Value
FileSize	82204
MD5	38044307D9389E48907A426A9970771D
PackageDescription	The 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	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-dev
PackageSection	libdevel
PackageVersion	1.3.10-2
SHA-1	2BCEA70E1B8202EE6B783D38CBF7A38EC610BEAA
SHA-256	431D9973DE0EAC23AA8B4D68F497F515F52B6260EBDBC9F2C1A7A35EDC4392A9

Key	Value
FileSize	82208
MD5	8708C31FBC5BE232B2AB3D053BBC7599
PackageDescription	The 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	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-dev
PackageSection	libdevel
PackageVersion	1.3.10-2
SHA-1	5957B4BC3F0F479CE56AF441D14B1E09937D2C79
SHA-256	8030F4A13F52C48AC9E71C46B6ADF95CEADA1A3EBA158AA0085B5115A28F6CF2

Key	Value
FileSize	1892008
MD5	3AEEE9462A44EB272B79E56E3B404568
PackageDescription	The WorldForge client entity library - debugging 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. . This package contains the debugging library.
PackageMaintainer	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-11-dbg
PackageSection	libdevel
PackageVersion	1.3.10-2
SHA-1	5B3182474E85E36C1770E97B62170162E27DFD1A
SHA-256	6CC69B3336F7B0842BB0472334FB2BA5B093AF328F12BD5F9296F188950089B3

Key	Value
FileSize	339788
MD5	F1517DC08BC1D74139D12BFC85BC4A76
PackageDescription	The 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	Michael Koch <konqueror@gmx.de>
PackageName	liberis-1.3-11
PackageSection	libs
PackageVersion	1.3.10-2
SHA-1	849C9C29457A70811B51A885492326D6A589563A
SHA-256	5D497B28B6C8B706AC2A77EA84AACA676634C37F1F8C26E797256B8E1ECA8B1E