Result for 2DD7030014D09103228A75B650C525FCD57EFCEF

Query result

Key Value
FileName./usr/share/doc/liberis-1.2c2/changelog.Debian.gz
FileSize1065
MD53BFAFDEBC5C7E0C64DEE4E44A3D61F5E
SHA-12DD7030014D09103228A75B650C525FCD57EFCEF
SHA-256B87F669FBFB1BAEBBCC3A5AB8D8BABE9C68992B19083B57805CB973B6016C5E9
SSDEEP24:XDb0XJxeseDtVRsAIzlBb/aV4Rvx7sCwKs2iBmwMJIpVf:XEBeDnKdXbyV4T9iBHSIPf
TLSHT16411E9328CB8466F24A5232B09444CA23F4C03C5FF4AB98CDA19B04E44E51F69362924
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
FileSize60726
MD57DCF8333CEF0783645B51A03A639951B
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-1ubuntu4
SHA-11C612240278AEC51A56DB41677B0BEDCC9A568BD
SHA-2560B10F90B4FA85160187038B2497226C887E8A614059D4C94BB1E7340ADA1C948
Key Value
FileSize1662942
MD5218947E71BAB27BD30FE912668F9CD1B
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-1ubuntu4
SHA-11C04913A250426C9D5F656AF7DC0AFD67F07B2C1
SHA-2561B4310338ADE015F6D2A43164ADD1FE1B3278182212ED9E5D1DD00AE7B6E46A1
Key Value
FileSize317660
MD55D563C8CC9BB84EB9997129605D99B33
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.2c2
PackageSectionlibs
PackageVersion1.2.1-1ubuntu4
SHA-133C5C84374BE9E0B192E86D0EE044BB3C86CE5D0
SHA-256B2D6A7E6C59F84712C75B6DCE36C2F12BB656EBC5C8E9B84E9D7179C0292DD2A