Result for 2CC1B993AF0A95AB0FBB530D86E51813B5A16D4A

Query result

Key Value
FileName./usr/share/doc/liberis-1.2/changelog.Debian.gz
FileSize808
MD594A11A4E54AE1606298FE946976BBA11
SHA-12CC1B993AF0A95AB0FBB530D86E51813B5A16D4A
SHA-2568C5A8A1F1F66398B16E564407C31083108400900F2B76D1550D63381F6EA2046
SSDEEP24:XQmQ+/DhzN8hnDvGHlKoPAFeo1zFdd1uojQnx8:XkUannooFeo5TuojCO
TLSHT1F40186CBD111160C6863D2E643B3512ECBEE0EC894562C5421270BB0AF86ED6083D16F
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

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

Key Value
FileSize60472
MD5864523737F1F290BB986358DAAA28364
PackageDescriptionThe 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.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2-dev
PackageSectionlibdevel
PackageVersion1.2.1-1
SHA-1E0AA0ED68F96BDEBB9DC94FD49947ED265B33DB6
SHA-25658BBC127F0D4BBF249FBF383A761F2A14668F0315C1931FC8CAA45B3982B382B
Key Value
FileSize2347532
MD51A786FD51773B47F357B8294BC04688C
PackageDescriptionThe 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.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2-dbg
PackageSectionlibdevel
PackageVersion1.2.1-1
SHA-183B3C90665C1417594C110288BB94BCF4E87C05E
SHA-256F6803B51DD7EE0BF681AAA04A5750DC60577E66861E16423B75C1EEB5F54D23C
Key Value
FileSize402994
MD5738DFB5B00D5F40328DE8267A5A01106
PackageDescriptionThe 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.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2
PackageSectionlibs
PackageVersion1.2.1-1
SHA-1CC3DDDCC7F6DF0A2D21E6C33290E27091357F085
SHA-256273A68881B9478B957065083281AACD671B0C7331453CCCA6AB01571BF3B96A0