Result for C8EA9FFBAEFDC463AB140072F67EB2920063494D

Query result

Key Value
FileName./usr/share/doc/liberis-1.3-dev/changelog.Debian.gz
FileSize1508
MD5E603422FCE6D6FFF4BE65E2619A547D4
SHA-1C8EA9FFBAEFDC463AB140072F67EB2920063494D
SHA-256811FF234761C2AC52D1A662AEDDC49543454D5C71976608A4FC98D0A3314646C
SSDEEP24:XOxcIfhJja8yBYOpgOxniiYtJe7azYlWujZNSEhLEjeXb1VAV3oLuXr6w:XOWch1axC8nH4IrZEEBqeXpc3oLud
TLSHT1973129C2A492D4169A38CF950E701C315E8D0C59E40774CF7C861BE07BC9D0573394E0
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
FileSize82216
MD57120FC3813B618521C0CC609C0232F22
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-1C721B6D3F0F33341FC1874ADDF70453F7043E821
SHA-256AE95AA958C1114816515843D674DF57E2301FC7BA629075518191F1AE05A6288
Key Value
FileSize377314
MD5C7A9323D6C29F000ECB0298020D79CE0
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-1E6E53C487F7280E85C97E9176EBE9B030DA1C9B8
SHA-2562DEFF3E54CDB7CBAB93E953FF5CDDB80473719E93C072E91C679FCAFF08F3B1F
Key Value
FileSize1892008
MD53AEEE9462A44EB272B79E56E3B404568
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-15B3182474E85E36C1770E97B62170162E27DFD1A
SHA-2566CC69B3336F7B0842BB0472334FB2BA5B093AF328F12BD5F9296F188950089B3