Result for 48D0CFE0366FC6DF4FE448834BADDA8EC230F1B9

Query result

Key Value
FileName./usr/share/doc/liberis-1.3-dev/changelog.Debian.gz
FileSize1508
MD530E923D41F338714E947CCD5FC8668AA
SHA-148D0CFE0366FC6DF4FE448834BADDA8EC230F1B9
SHA-256103C756837B201F54523918C60FE8022A2CA8207052F5C1B6014B3A4B33E9CFE
SSDEEP24:XdxcIfhJja8yBYOpgOxniiYtJe7azYlWujZNSEhLEjeXb1VAV3oLuXr6w:XdWch1axC8nH4IrZEEBqeXpc3oLud
TLSHT1953129C1A492D8169A38CF950E711C306E8D0C59E40774CF7C861FE07BC9D0573394E0
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
FileSize82222
MD5B720FD70D5730BC40EEF156592BC247B
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.3-dev
PackageSectionlibdevel
PackageVersion1.3.10-2
SHA-18D5DD3892F29B9FA5FAE85694204D320267E9B69
SHA-25660C46A10C801D9A36BF4C68856FD3796FC16227D24653E612FC005F9509B8561
Key Value
FileSize296168
MD53156ABD1F11EF81E32526B793A020558
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.3-11
PackageSectionlibs
PackageVersion1.3.10-2
SHA-1CBE42D70B359A2C68997DAFCEC988B7F3CCDEEE4
SHA-25628995003BB5457356CB475A8D97DF722851C403DE4C97374E47AADDC119C0DAF
Key Value
FileSize1868982
MD5BE958468082CB7A3F91CBE909083DAA9
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.3-11-dbg
PackageSectionlibdevel
PackageVersion1.3.10-2
SHA-1046288566EADD81A6304F6097B64AD7AFD584CEC
SHA-256513149CFA5EEF6B17699FAB56B6BF736862AD54DA1EC4E0A925ABB191E68DFCC