D-LAN

h1. Functional definition

This page will describes the scope and utilization of Aybabtu.

Some sections will describe a particular window from the user interface, it may refer to the [[GUI]] page.

h2. Description

Aybabtu come with two executables, the Core and the GUI. It possible to launch one of them alone or both together. The GUI is needed to command a Core, to tell it what you want to download, to share, to search, etc. To do that the user have to tell the GUI to connect to a given Core. The Core can be _local_ or _remote_, by default the GUI will try to connect to a local Core. If the connecting attempt to a local Core failed it will try to launch a local Core.

The simple usage of Aybabtu is to launch the GUI which will automatically launch the Core. The user may not know there is two distinct process. The core will display an icon in the tray icon (if a tray icon exists). If the user close the GUI the core will continue to run, if he want to stop the core he have to invoke a contextual menu from the tray icon and choose _Close the Core_. The user can launch the core by double-clicking under the tray icon.

To connect to a remote Core, the user have to explicitly enter an IP address and a password. The password is mandatory for a remote Core. For one Core it cannot be more than one GUI connected (this limitation may be removed in further version of Aybabtu).

The [[GUI]] shows some default windows, a download windows, an upload window and a chat window. The others windows are the search window, the browse window and the options window. All of them are described in the sections below.

h2. The main window

At the first launch of Aybabtu it will connect to all peers in the LAN and show them in a panel to the left. The information show for a peer are its name and its amount of sharing. To view the peer files you have to double-click in its name or to invoke the action "browse" from the contextual menu.

Above the peer list there is an input box for searching. You can write something and hit 'return', a new search window will be created and displayed. Each known peer will be asked and the list is filled as a respond is received. You can change the pattern into the search window. You can have as many search window as you want.

* Recursive folder downloading.

* The paths of the files are recreated in the downloading peer.

* The files that are currently downloaded have the final size with a name like "movie.mkv.unfinished". The ".unfinished" will be removed when the download is finished. Maybe do the same thing for folder.

h2. The download window

* The list is ordered, first the complete downloads then the incomplete ones with 0 peers then the current downloading files and finally the queued files and folders.

* The list can contains both file or folder, when a folder is downloaded its files and folders are retrieved from the peer and will replace the folder in the list (lazy download).

* There is a limit of the number of complete download. 500 for example.

h2. The upload window

h2. The chat window

h2. The browse window

h2. The search window

h2. The options window