Result for 7A4F0B5CD5A4D80FC835B2E95B56E22D7F936EF7

Query result

Key Value
FileName./usr/share/doc/liberis-doc/AUTHORS
FileSize629
MD51AEFBB9CD9810114D40B3A627ED7A0D6
SHA-17A4F0B5CD5A4D80FC835B2E95B56E22D7F936EF7
SHA-25661A508A44003CCA573504C770E8DBE7D908B93EAC6C2E87ED0E6F507A5315507
SSDEEP12:lAW1zZkulQ66FeyoSRVQz4j8k2eEzdSnmpDVqTkeM1qpQVg5:lzlZkYQ66kW9j8k6pDVHe95
TLSHT112F0DD63592C13BC4E920A9A9403C5BAC23D81B9B10D8732046EF386261A581CDBBA5D
hashlookup:parent-total101
hashlookup:trust100

Network graph view

Parents (Total: 101)

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

Key Value
FileSize309938
MD5C87FCDEE235D2E62D3746B0C9F2C23E0
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 MOTU Developers <ubuntu-motu@lists.ubuntu.com>
PackageNameliberis-1.3-13
PackageSectionlibs
PackageVersion1.3.12-1
SHA-101B1613AB3FADCE90E74638086E3C4B52AEECE44
SHA-256F3F688E37DA7E1BC2C11AD780A6393A8466B97216381C89F0A7D24163F34088E
Key Value
MD591FFFDD5CC8DB16AC7A9A827E1F82D45
PackageArchppc
PackageDescriptionA client side session layer for WorldForge; Eris manages much of the generic work required to communicate with an Atlas server. Client developers can extend Eris in a number of ways to rapidly add game and client specific functions, and quickly tie game objects to whatever output representation they are using.
PackageMaintainerKoji
PackageNameeris
PackageRelease3.fc16
PackageVersion1.3.19
SHA-101C954D2D3428CA2068B87D78DFE531E9EE6824A
SHA-256DCE37665B335CDCC722FBEBECE331C7C2EBAB814049099275B3E4BB108EF1202
Key Value
FileSize1868982
MD5BE958468082CB7A3F91CBE909083DAA9
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-1046288566EADD81A6304F6097B64AD7AFD584CEC
SHA-256513149CFA5EEF6B17699FAB56B6BF736862AD54DA1EC4E0A925ABB191E68DFCC
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
MD5F16F34208127FB4EA33F5A32FFA6A5D3
PackageArchs390
PackageDescriptionA client side session layer for WorldForge; Eris manages much of the generic work required to communicate with an Atlas server. Client developers can extend Eris in a number of ways to rapidly add game and client specific functions, and quickly tie game objects to whatever output representation they are using.
PackageMaintainerFedora Project
PackageNameeris
PackageRelease2.fc19
PackageVersion1.3.21
SHA-106A8572AFD0D71259AD00BF9C5A330B216449C43
SHA-25648D7E5E511A5C7B2A0FA7F9E173C5E53DBD1A0C3BD07D302CC0170BB4D08FAFA
Key Value
FileSize195566
MD5E656874E846F67DD6F7B225D4D787EB8
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 MOTU Developers <ubuntu-motu@lists.ubuntu.com>
PackageNameliberis-doc
PackageSectiondoc
PackageVersion1.3.12-1
SHA-111B8A4C18FC202BAEA88438020F82F8936C0004F
SHA-256C04095D742A8A1F4B9A52A3F8E26C136280829A85CF7F5BE8D5B8FBA3E2DCBC5
Key Value
FileSize1846356
MD5EB3BD4013CA2FB93F6BD9C91E12E5968
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-1177745D4A6D51BF58CE5B73F214B5F7A3B448393
SHA-2567B4EFFE36AEF78BA1CDD6C4B3F5E3DD7C5B6359347899D6E68792CCE95E556CD
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
Key Value
MD571E09E5B36EF4737BC304E1D3660C13D
PackageArchppc64
PackageDescriptionA client side session layer for WorldForge; Eris manages much of the generic work required to communicate with an Atlas server. Client developers can extend Eris in a number of ways to rapidly add game and client specific functions, and quickly tie game objects to whatever output representation they are using.
PackageMaintainerKoji
PackageNameeris
PackageRelease3.fc16
PackageVersion1.3.19
SHA-11CC00A3936439B6A89E7187ECD9C6B1596CE2457
SHA-256550B1C06F82E8A84544DCAC6DA253A75B14CCF91EC10CBDC4607471136C34EB1
Key Value
FileSize239594
MD5B4F420D67BF68F0252920EC9AF482EED
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.13-2ubuntu1
SHA-11CF88C43331A3E58772D78B811D106768C53D86E
SHA-25632C6FAEF646A4EA6BECAEDBC01320D3C1229D9BACC272C5C26AB0705D4632A24