Result for 27E0373C5BBE317FE0DC4319958BF8ED146CB850

Query result

Key Value
FileName./usr/share/doc/liberis-doc/TODO
FileSize1104
MD5741CEA48191656438E1FCFB558B0C396
SHA-127E0373C5BBE317FE0DC4319958BF8ED146CB850
SHA-25652193E6DD0EB1FEC840F5DD701F322EA293141EA15194DA693B06DE648733CF4
SSDEEP24:USyrsERCPxjnZznQ/aNkP8k1iV9vbf3Es0T2/QE3o2zr:h9EkPxjWlP8kIVlb0s0TAbzr
TLSHT18D11637B766403A42E7246F7D0CB49F1D7A1D499321611C6ACDEC418B3A621C66BF8CC
hashlookup:parent-total82
hashlookup:trust100

Network graph view

Parents (Total: 82)

The searched file hash is included in 82 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
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
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
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
Key Value
FileSize179864
MD55EC7F097B856EEFA30165A940F4D89BA
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.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-doc
PackageSectiondoc
PackageVersion1.3.10-2
SHA-11D849328297E96EB195C5B5B428C85B57AF54428
SHA-256CC81EFA51906D9238462EE77CCF6057B13E0AF3583AFFC9BE6301C9137A83425
Key Value
MD56BE57EB7A6BFB4BC49B1E07BBC2A1395
PackageArchsparcv9
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
PackageRelease1.fc15
PackageVersion1.3.16
SHA-11E4F86D388F08F7BE2F865364E523C067CC7FE90
SHA-256058946B8DF8A19466C96B71328A3861A5CBEDF1857336864A1BA52D2BF2C5401
Key Value
MD544F95288D8A49B0F6E7368380A867FB7
PackageArchs390x
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.fc15
PackageVersion1.3.16
SHA-123E27F05950FA8E56BCC3BAA023D39AC4BB36693
SHA-2564E0E19883618A7C2EADDF667E4A084811E4C67750B8BDAB2BDD732AFA8F356BF