Result for 3BB93D6ECD4B98080D1F36136CA31FE774E661CF

Query result

Key Value
FileName./usr/share/doc/liberis-1.2/changelog.Debian.gz
FileSize808
MD570AC547338F6702484328F02C3BDC9FE
SHA-13BB93D6ECD4B98080D1F36136CA31FE774E661CF
SHA-256C89635676B235176E1E19B4C369C929B1792372B257A058CDCD11A58D2E11F75
SSDEEP24:X4/+/DhzN8hnDvGHlKoPAFeo1zFdd1uojQnx8:X4/UannooFeo5TuojCO
TLSHT1090186CBD110160C6867D2E643B3512ECBEE0ED894562C5421270FB0AF86ED6093D26E
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
FileSize60478
MD5118B64A550C199D1DAC5529CBF317BE1
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-18B4600813A4D5CFA86E9AF2748F6DCCE6F04F586
SHA-256A295D89DFD9C287209A0EAA292C52AF87FD4E84E6A1059578DAEC86F773F3BF8
Key Value
FileSize3379108
MD5C29E7F7B47D795F15FED504BA2A54F60
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-130ADD611DF75152A66EBFC0E46F9C5181FD98AF7
SHA-256D3096EF3FAEFB4CCE9918C71E98E42FACA31E67FE63F15BD0A3A5D93F6C3C798
Key Value
FileSize311828
MD5CBC8CA50A1C799FC86C5506030F254B3
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-1EC7B082BD886EB49BB9818EC2D1E9332F1238764
SHA-256D173A03DDF4BDB29043E2FE279498C6CEA458A4EFDB2E70B513AD36581C3E4CB