NeL Engine Samples

NeL Misc Samples

Theses samples illustrates the usage of the miscellaneous library. This is the based library used by all other Nevrax libraries.
It contains all useful class and features that are not specific for one or another library.

command

This samples describes how to create commands and execute them using ICommand class. It's a generic system to create and execute command at run time (it is used in all services, snowballs client and so on).

configfile

This samples describes how to use NeL configuration file. (This system is used in all services, snowballs client... ).

debug

This program shows you how to use basic debug stuffs that are used everywhere in NeL.

i18n

This sample describes how to use internationalization texts.

log

This sample uses the log and displayer system that is a generic way to generate output (on screen, file... ).

strings

types_check

Basic program to check if NeL types are valid.

NeL Network Samples

Theses samples illustrate the usage of network library.

chat

A basic client/server chat system that use NeL. More information here.

class_transport

This project demonstrates the usage of the CTransportClass class. This class allows services to send easily some class to another service. It manages different class versions. For example, the sender class can have different variables than the receiver class. You can find more information here.

login_system

This examples shows you how to use the login system provided by NeL to connects/check/identify clients.

multi_shards

net_layer3

This project demonstrates the usage of layer 3 (NLNET::CCallbackClient, NLNET::CCallbackServer) and the
service framework (NLNET::IService). It contains three programs: a client, a front-end service and a ping service.

• The client connects to a front-end server at localhost:37000. It sends pings and expects pongs (ping replies).
• The front-end server expects pings, and forward them to the real ping server (known as "PS" in the naming service). When the ping server sends a pong back, the front-end server forwards it to the client.
• The ping service (PS) expects pings and sends pongs back.

To run the front-end service and the ping service, ensure their config files, frontend_service.cfg and ping_service.cfg,
are located in the directory where they are run. These files state the address of the naming service.

net_layer4

This project demonstrates the usage of layer 4 (NLNET::CNetManager), the service framework (NLNET::IService), and the connection and disconnection callbacks. It contains three programs: a client, a front-end service and a ping service.
The functionalities are close to the ones of the previous sample.

• The client connects to a front-end server at localhost:37000. It sends pings and expects pongs (ping replies).
• This front-end server expects pings, and forward them to the real ping server. When the ping server sends a pong back, the front-end server forwards it to the client. Even if the connection to the ping server is broken, our front-end server will keep storing the ping messages and will forward them when the connection is restored, thanks to layer 4.
• The ping service (PS) expects pings and sends pongs back.

To run the front-end service and the ping service, ensure their config files, frontend_service.cfg and ping_service.cfg, are located in the directory where they are run. These files state the address of the naming service.

net_layer5

This project demonstrates the usage of layer 5 (NLNET::CUnifiedNetwork), the service framework (NLNET::IService), and the connection and disconnection callbacks. It contains a set of services that communicate between them. The functionalities are close to the ones of the previous sample but they add some features like unified callback array, and so on.

service

This is a very simple service example to describes the architecture to create services.

udp

This project demonstrates the usage of a client/server architecture for benching an UDP connection. The server listen on TCP port and UDP port for new incoming client. When a client is connected, it communicates on the TCP port to set the bench and after it uses the UDP port to bench the connection. The server log information on text file and send some info on the client using the TCP connection.

udp_ping

NeL Memory Samples

mem_alloc

NeL 3D Samples

FontSample

This sample demonstrates how to use the font system.

ClusterViewer

NeL PACS Samples

PacsSample

This sample demonstrates creating and moving move primitives, colliding them with other primitives, collecting the triggers and managing world images.

NeL Sound Samples

sound_sources

This sample demonstrates initializing the sound system and loading sound backs, creating listeners and sources and moving them around.