Result for 72F3812B68A33F92635ADFC1AC7C0FE7E81F4F19

Query result

Key Value
FileName./usr/share/doc/liberis-doc/copyright
FileSize1098
MD5B9FDC966B9986EA39F0173DAB32973B7
SHA-172F3812B68A33F92635ADFC1AC7C0FE7E81F4F19
SHA-2566AE503130718736E751E2FD2B1472F3076BF09E0619CA52A02DEBD6AFAC6242F
SSDEEP24:0R3dmJ84SrejNE5byfOkHhylUHTbVu3zQH3qAyAzbsi:E3dmkYN2byJHcp3/xq4i
TLSHT10A11601D5408C3FB184006A13D4A65DF932B96A7369CC080350D832FEF0BA3942F68E4
hashlookup:parent-total57
hashlookup:trust100

Network graph view

Parents (Total: 57)

The searched file hash is included in 57 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
FileSize1712002
MD50302E3FB38E561A541F87F54AA5E2DB9
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.
PackageMaintainerUbuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>
PackageNameliberis-1.3-14-dbg
PackageSectionlibdevel
PackageVersion1.3.13-1
SHA-106BAFD051A302562DE7F89BDBFE39628543DEB8E
SHA-2561BF76F38618748F8F6022856FF72E17CACCA1A99C0CE38641F0757544F6EB069
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
FileSize36410
MD5CD410846FEAF3ED68573C128E1733C46
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.
PackageMaintainerUbuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>
PackageNameliberis-1.3-dev
PackageSectionlibdevel
PackageVersion1.3.13-1
SHA-114198767222DF65796CB438469E1C2579E60F323
SHA-256EBEBC253CAB87BB1BEAFC266724BA6DB3204B90FCA5AB1DCA01C1F96E350027D
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
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
FileSize278694
MD529370854EB3278DF91A3B26F1BECA25D
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-126D1D53312677E55E2E7494FFF4285F39F823ED6
SHA-256B75AAC0744305E66AF0007A60FF765782B2A66719AF550CDF8F0DA29169155A2