Result for D1C2A0FE8F813B8602EA83844004EF7AC4EC3951

Query result

Key Value
FileName./usr/share/doc/liberis-doc/changelog.Debian.gz
FileSize1989
MD5B2A4FFD058D747CFB7E30FC98DA38DFE
SHA-1D1C2A0FE8F813B8602EA83844004EF7AC4EC3951
SHA-25618FCA6E44B4F403CE3C757D01D7CAB6A476D3D13898DE7A03459CEF49730CBAB
SSDEEP48:XwDnhztJhtu586FneOwKBkQwGgRReo/3puFKRjvhbguQkwLylrb7bkvQv:Q1tJhtI86F2KBkQdgCipKGvhEuQkySbf
TLSHT100412AD9C399428ABFAF052DD62CCA015637D6D47DA4C05BCAB25C7705C7F64C438260
hashlookup:parent-total7
hashlookup:trust85

Network graph view

Parents (Total: 7)

The searched file hash is included in 7 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize244326
MD52C4B16357965EBF814CCBE32F731CBAC
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-15
PackageSectionlibs
PackageVersion1.3.14-3
SHA-1B2C8AA7395D7B5D130E1399B6615678B9F1B72ED
SHA-2569BBA7D38BC1273A21075D3119D210EE3857F606D80870C6C4EB4031114764152
Key Value
FileSize247748
MD5C0E61CED9251AC8DB2F387F6DA6E61D0
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-15
PackageSectionlibs
PackageVersion1.3.14-3
SHA-1DEF0D596EA84E44453A2D19DC1DFEB00063DCC6A
SHA-256D97886AAB4A186FB14DE1743BCBBAE6B0AC088A7EE7E21856896FEF7C923F64E
Key Value
FileSize201250
MD57372D5FBAAD7D698210D1CD2CBC7477C
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-15
PackageSectionlibs
PackageVersion1.3.14-3
SHA-1F25419A97BAF9DA77F3992D4C6BEB72CC967CA28
SHA-25678318B3087376A473BA9A99FCF063E87FD701BED2B0684D5CD7924B7B5DECCC4
Key Value
FileSize247352
MD59829FAAB9D87F583F7C16EB28C105C88
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-15
PackageSectionlibs
PackageVersion1.3.14-3
SHA-1AE83BC2A575C6871252771CE9106709C4593679A
SHA-25601A742465446A830A869BC6610D56B4A954D1531B26973861CF95F00A391A1C2
Key Value
FileSize258794
MD5A8C863F385CBFCD8EC5A560B1C2DF620
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-15
PackageSectionlibs
PackageVersion1.3.14-3
SHA-1B35B695A85C3DF565656199FAE3C4C05F251A3C0
SHA-25616884DDC2811EE163896200188621939C466BFC68D61F11F2D8E92F9DE59A726
Key Value
FileSize341000
MD58970B0C1334A0374AFFE0786E564E1E1
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-15
PackageSectionlibs
PackageVersion1.3.14-3
SHA-1BA7A96CBB8159C91636722FC6DB52D1B2FEFB592
SHA-256E16BEAE4F19462801FC409778A9D37F6C8E7462195BDA7ECE51995E20E6DBEC9
Key Value
FileSize301032
MD57A94D49E6CA5F3DB53E2B06CB09E8CA0
PackageDescriptionThe WorldForge client entity library - API documentation 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 API documentation in HTML format.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-doc
PackageSectiondoc
PackageVersion1.3.14-3
SHA-1F563C4A6853D3F5C9B687026776F5F66E877F416
SHA-25689D8FBD2C7A395DB55EA4B9F3436CCF4369B0D062B6736776E76AF7F417B3435