Result for 2A2444999E43D538E01ABCD1B953E8E048023474

Query result

Key Value
FileName./usr/share/doc/liberis-1.3-dev/changelog.Debian.gz
FileSize1508
MD5BD07B0A50D942690B3EEA7AB6C35D6EE
SHA-12A2444999E43D538E01ABCD1B953E8E048023474
SHA-2567D76E55683C67461891DE62C1ECA7C51A794C851B1E1A920026D7BFFF86ED4B6
SSDEEP24:XlxcIfhJja8yBYOpgOxniiYtJe7azYlWujZNSEhLEjeXb1VAV3oLuXr6w:XlWch1axC8nH4IrZEEBqeXpc3oLud
TLSHT1583129C1A492D41A9A38CF950E701C305E8D0C99E40774CF7C861BE07BC9D0573394E0
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
FileSize339788
MD5F1517DC08BC1D74139D12BFC85BC4A76
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-1849C9C29457A70811B51A885492326D6A589563A
SHA-2565D497B28B6C8B706AC2A77EA84AACA676634C37F1F8C26E797256B8E1ECA8B1E
Key Value
FileSize1903942
MD555628EBB79D15594412C84C7F11A3EB5
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-105013FF044B3183FD4CBEB8F9F4251DFE40DFC48
SHA-256D93C93EEC80577F6B4E0DFF9852957974A9599BA5D5F1023001DC8F785B21C15
Key Value
FileSize82254
MD57E93439BC3A4A89B336CB6C1B5143728
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-11C3E041EE97753DFB1231068756A282A2533E9F1
SHA-256B7EA04794B9D555E515FED540C52CE96ECF07A0895212852A4D121C5EC6CDE73