Functional definition » History » Version 8
Greg Burri, 01/01/2009 11:19 PM
1 | 1 | Greg Burri | h1. Functional definition |
---|---|---|---|
2 | |||
3 | This page will describes the scope and utilization of Aybabtu. |
||
4 | 4 | Greg Burri | Some sections will describe a particular window from the user interface, it may refer to the [[GUI]] page. |
5 | 1 | Greg Burri | |
6 | |||
7 | h2. Description |
||
8 | |||
9 | 7 | Greg Burri | 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 and connect to it. |
10 | 1 | Greg Burri | |
11 | 7 | Greg Burri | 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 GUI by double-clicking under the tray icon. |
12 | 1 | Greg Burri | |
13 | 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). |
||
14 | |||
15 | 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. |
||
16 | 5 | Greg Burri | |
17 | 7 | Greg Burri | h3. Downloading |
18 | 1 | Greg Burri | |
19 | 7 | Greg Burri | You can download file or entire folder from the searching windows or from the browsing windows. The item will be enqueued to the download list and displayed in the download window. |
20 | |||
21 | When downloading a folder all theirs containing folders and files will be downloaded recursively. The path will be preserved and recreated in the machine of the downloading peer. |
||
22 | |||
23 | When a file or a directory is being downloaded its name will finished by the tag ".unfinished". For example "my movie.mkv.unfinished". |
||
24 | |||
25 | 8 | Greg Burri | The list of queued items 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. It calls lazy download. |
26 | 7 | Greg Burri | |
27 | 8 | Greg Burri | |
28 | 1 | Greg Burri | h2. The main window |
29 | |||
30 | 7 | Greg Burri | 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 files of a peer you have to double-click in its name or to invoke the action "browse" from the contextual menu. |
31 | 1 | Greg Burri | |
32 | 7 | Greg Burri | Above the peer list there is an input box for file 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 and relaunch the search. You can have as many search window as you want. |
33 | 1 | Greg Burri | |
34 | |||
35 | h2. The download window |
||
36 | 7 | Greg Burri | |
37 | The download windows shows the downloading files and also the queued files and the completed files. |
||
38 | 1 | Greg Burri | |
39 | 8 | Greg Burri | Here is an ordered list of the different states of files and folders that this window shows. |
40 | 1 | Greg Burri | # The complete files. |
41 | 8 | Greg Burri | # The paused incomplete files with no peers. |
42 | # The unfunded find from the peer. |
||
43 | # File or folder from unknown peer. |
||
44 | # Downloading file. |
||
45 | # Enqueued File or folder. |
||
46 | 1 | Greg Burri | |
47 | 8 | Greg Burri | For the third point this can occurs when a file or folder has been moving or delete in the remote peer. |
48 | 5 | Greg Burri | |
49 | 8 | Greg Burri | There is a limit of the number of complete download. 500 for example. |
50 | |||
51 | 5 | Greg Burri | |
52 | 1 | Greg Burri | h2. The upload window |
53 | 5 | Greg Burri | |
54 | h2. The chat window |
||
55 | |||
56 | h2. The browse window |
||
57 | |||
58 | h2. The search window |
||
59 | |||
60 | 1 | Greg Burri | h2. The options window |