Result for 9C7B7770AF36402A03C96DD0E1F7BAFF55AECD34

Query result

Key Value
FileNamecopyright
FileSize2823
MD5B494800F97786A634CD1704EA2BB893B
RDS:package_id182052
SHA-19C7B7770AF36402A03C96DD0E1F7BAFF55AECD34
SHA-25642E0C05F9390E701A0DFAD16969E294ACA3F2C173688653FBB1771F80A28F563
SSDEEP48:yRUuaLpsHkWcDhD+lxEVW4KweyvHkL7n72qCGEyvHkL7n72q9:y+M4iSVRK+gaqL3gaq9
TLSHT11151444D18D0C3FF698027C1394998EFE32B679B75AC9191714D829EAB0AE7512F70E4
insert-timestamp1679427784.323547
sourceRDS.db
hashlookup:parent-total49
hashlookup:trust100

Network graph view

Parents (Total: 49)

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

Key Value
FileSize251730
MD5C99C56831BE962774CB4A87CCD50BE8D
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-10C965657ED8785906E5A80F1A0F392C4EC23E35E
SHA-25675DDD9732A7DB8CD07BD396F3CE8C6C382759CA78277944AD695C14CA9D2E284
Key Value
FileSize200456
MD5CCA78DFF79E2ED2251B7169F9177A789
PackageDescriptionWorldForge 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-21
PackageSectionlibs
PackageVersion1.3.23-4
SHA-10E1CE38C7F7FD5A833976B5AE3F80D45F367AC4A
SHA-256EFEEB283217BCB7CACD8B4AEADAA1BEADF3478A835476287BAD43A82D10384D1
Key Value
FileSize42650
MD56FBB06F650E07D6E9A435FF025DF2E01
PackageDescriptionWorldForge 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.23-5
SHA-1164FA83873415D4A76B1A38ED92F3C32C2E7C6DE
SHA-256AECD44CB75933DB5F5DAB4417F96755A1EF1C27FA3BC6857FF47B377D81CF821
Key Value
FileSize42650
MD5B23648528B5AED75E4A7B8DFD0AD7599
PackageDescriptionWorldForge 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.23-4
SHA-1190C936980ECECCD545D703C77B2441EB0B07C48
SHA-2563909ED2BF3BDF2369AB3C5E6176C2D3211F94E54E28370168DA9E1867D006D32
Key Value
FileSize42648
MD523CDEBDAC59D1BAD4C2657325EBA5C40
PackageDescriptionWorldForge 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.23-4
SHA-11940A4168BC2E889EF9FFEB80CE979426CD635AD
SHA-2562DE6CB04707546C9306CA5F8B2688C74FD8C86F575BCECAEA5309D452C5FF8BE
Key Value
FileName16276
FileSize42650
MD5B556B119F08702D1E3CD9F03ED0EEEBA
PackageDescriptionWorldForge 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.23-5
RDS:package_id182052
SHA-11E4FCDD4D5F867943BFAB08E63EEB9170DEB035B
SHA-256AB734AF98A3DC7FD616C4860DB8658CAAD4FF7CDCFB63F4D230DA79A452A0EA1
insert-timestamp1679408376.0644429
sourceRDS.db
Key Value
FileSize104272
MD5212A8685CEF825BA8C1B9C6C35E403CB
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.23-5
SHA-11F0A9F21D6816FCA15F3780F71C0031EAA08191C
SHA-256DC07C888CF686D36A2FEE797B9B5F72D56752B5541CA8C2D59141032EED66F08
Key Value
FileSize239232
MD557C46ACD1860D3F7EAB9A9EFC301396B
PackageDescriptionWorldForge 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-21
PackageSectionlibs
PackageVersion1.3.23-5
SHA-1275F871E28F57FC61ADD4A7DCB3BFB4042AF7987
SHA-256F82973A9AB31A7945D4F6109CA98EE90A0489FA5325B5A29B9FB121B10F4BE9E
Key Value
FileSize328106
MD5D0D9A7E89331294202D51E1C0F81F9C4
PackageDescriptionWorldForge 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.
PackageMaintainerDebian Games Team <pkg-games-devel@lists.alioth.debian.org>
PackageNameliberis-doc
PackageSectiondoc
PackageVersion1.3.23-5
SHA-1295028AA16F1DE11E1F7E0D1511CEA787A67843E
SHA-2561E44B0656BC54BD2E375B5F1BA343C7B2987B6DE4F2020DF955B0C8608E633F6
Key Value
FileSize42652
MD5C813BF1087202424EAB8F81EFE042B1E
PackageDescriptionWorldForge 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.23-4
SHA-12F1BE3F8B1516D26EABF47B90F8C5F40124E8DDF
SHA-256ADA1FA86F469B6C02F2253762D6990818CB4189F99AF83DC6C775B94F621B54C