mirror of
https://github.com/rkd77/elinks.git
synced 2024-12-04 14:46:47 -05:00
This commit is contained in:
commit
2fcf33541c
@ -35,7 +35,7 @@ you will add them) and couple of buttons shriveling at the bottom. So, as a
|
||||
start, move with the right (or left; both will do) arrow to the button *Add
|
||||
bookmark* and fill in the input fields it offers to you. I mean, you can type
|
||||
something like "ELinks homepage" to the first field, then move down by e.g.
|
||||
the down arrow and fill "http://elinks.or.cz/" to the second field. Then,
|
||||
the down arrow and fill "http://elinks.cz/" to the second field. Then,
|
||||
bravely press enter and watch the bookmark popping up at the top of the vast
|
||||
area reserved for bookmarks.
|
||||
|
||||
|
@ -5,7 +5,7 @@ This is an introduction to how some of the internals of ELinks work. It
|
||||
focuses on covering the basic low level subsystems and data structures and
|
||||
give an overview of how things are glued together. Some additional information
|
||||
about ELinks internals are available in ELinks Hacking. Consult the README
|
||||
file\cite{6} in the source directory to get an overview of how the different
|
||||
file in the source directory to get an overview of how the different
|
||||
parts of ELinks depend on each other.
|
||||
|
||||
|
||||
@ -74,7 +74,7 @@ or initialised in an allocated data structure using the following:
|
||||
|
||||
When iterating a list, there are two looping macros:
|
||||
|
||||
foreach (list-item, list-head})::
|
||||
foreach (list-item, list-head)::
|
||||
|
||||
Iterates through all items in the list.
|
||||
|
||||
@ -194,7 +194,7 @@ The `select()` loop regularly causes timer expiration to be checked. The
|
||||
interface is defined in `src/main/timer.h` and can be used to schedule work to
|
||||
be performed some time in the future.
|
||||
|
||||
install_timer(timer-id, time-in-milliseconds, expiration-callback}, data)::
|
||||
install_timer(timer-id, time-in-milliseconds, expiration-callback, data)::
|
||||
|
||||
Starts a one shot timer bound to the given timer ID that will expire
|
||||
after the given time in milliseconds. When the timer expires the
|
||||
@ -213,7 +213,7 @@ using bottom halves. This is especially useful when nested deeply in some call
|
||||
tree and one needs to cleanup some data structure but cannot do so immidately.
|
||||
The interface is defined in `src/main/select.h`
|
||||
|
||||
register_bottom_half(work-function, data})::
|
||||
register_bottom_half(work-function, data)::
|
||||
|
||||
Schedules postponed work to be run and completed in the nearest
|
||||
future. Note that although this helps to improve the response time it
|
||||
@ -225,10 +225,10 @@ Simple Threads
|
||||
^^^^^^^^^^^^^^
|
||||
|
||||
ELinks also supports a simple threading architecture. It is possible to start
|
||||
a thread\footnote{(on UNIX systems this will end up using the `fork()`
|
||||
system call} so that communication between it and the ELinks program is
|
||||
a thread footnote:[on UNIX systems this will end up using the `fork()`
|
||||
system call] so that communication between it and the ELinks program is
|
||||
handled via a pipe. This pipe can then be used to pass to the
|
||||
`set_handlers()` function so that communcation is done asynchronously.
|
||||
`set_handlers()` function so that communication is done asynchronously.
|
||||
|
||||
start_thread(thread-function, thread-data, thread-data-length)::
|
||||
|
||||
@ -261,14 +261,14 @@ make_connection(socket, uri, connect-callback, no-dns-cache)::
|
||||
|
||||
This function handles connecting to the host and port given in the uri
|
||||
argument. If the internal DNS cache is not to be used the
|
||||
no-dns-cache} argument should be non-zero. Upon successful connection
|
||||
no-dns-cache argument should be non-zero. Upon successful connection
|
||||
establishment the connect callback is called.
|
||||
|
||||
read_from_socket(socket, read-buffer, connection-state, read-callback)::
|
||||
|
||||
Reads data from socket into the given read buffer. Each time new data
|
||||
is received the read callback is called. Changes the connection state
|
||||
to connection-state} immediately after it has been called.
|
||||
to connection-state immediately after it has been called.
|
||||
|
||||
write_to_socket(socket, data, datalen, connection-state, write-callback)::
|
||||
|
||||
@ -304,7 +304,7 @@ connection state. How the protocol back-end chooses to handle the connection
|
||||
and load the URI it points to is entirely up to the back-end. The interface
|
||||
is defined in `src/protocol/protocol.h` and `src/network/connection.h`.
|
||||
|
||||
A connection can have multiple downloads attached to it. Each download struct}
|
||||
A connection can have multiple downloads attached to it. Each `download struct'
|
||||
contains information about the connection state and the connection with which
|
||||
it is attached. Additionally, the `download struct` specifies callback data,
|
||||
and a callback which is called each time the download progresses. The
|
||||
@ -319,7 +319,7 @@ load_uri(uri, referrer, download, priority, cache-mode, offset)::
|
||||
|
||||
change_connection(old-download, new-download, new-priority, interrupt)::
|
||||
|
||||
Removes the old download from the connection it is attached to and add
|
||||
Removes the old download from the connection it is attached to and adds
|
||||
the new download instead. If the new download argument is `NULL`, the
|
||||
old download is simply stopped.
|
||||
|
||||
|
@ -138,9 +138,9 @@ BUGS
|
||||
|
||||
Please report any other bugs you find to the either the ELinks mailing list at
|
||||
mailto:elinks-users@linuxfromscratch.org[] or if you prefer enter them into
|
||||
http://bugzilla.elinks.or.cz/[the bug tracking system]. More information about
|
||||
http://bugzilla.elinks.cz/[the bug tracking system]. More information about
|
||||
how to get in contact with developers and getting help can be found on
|
||||
http://elinks.or.cz/community.html[the community page].
|
||||
http://elinks.cz/community.html[the community page].
|
||||
|
||||
LICENSE
|
||||
-------
|
||||
|
@ -59,7 +59,7 @@ key-binding configuration) use Space to open and close the folders.
|
||||
Why are there so many Links flavors?
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Please refer to the link:http://elinks.or.cz/history.html[history page] to read
|
||||
Please refer to the link:http://elinks.cz/history.html[history page] to read
|
||||
about the various flavors and the differences between them.
|
||||
|
||||
|
||||
|
@ -502,7 +502,7 @@ All the .c files MUST start by a short one-line description:
|
||||
|
||||
/* <short one-line description> */
|
||||
|
||||
All the .h files MUST start by a CVS Id tag and then anti-reinclusion ifdef.
|
||||
All the .h files MUST start by an anti-reinclusion ifdef.
|
||||
The macro is
|
||||
|
||||
EL_<path_relative_to_src:s/[\/.]/_/>.
|
||||
@ -682,7 +682,7 @@ which is why everybody concerned with ELinks develepment should use it:
|
||||
In 0.5 versions `--enable-debug` add some fancy things:
|
||||
- many data integrity checking (see `lists.h`)
|
||||
- hotkey debugging: especially cool for translators, it highlights redundant
|
||||
hotkeys in a menu.
|
||||
hotkeys in a menu. (See also po/perl/README.)
|
||||
- more errors messages
|
||||
- low bug tolerance: it will core dump on some errors instead of just writing
|
||||
an error description.
|
||||
|
@ -97,7 +97,7 @@ and buttons at the bottom. Below, a view of the cookie manager is shown.
|
||||
|
||||
+------------------------- Cookie manager -------------------------+
|
||||
| |
|
||||
| [-]- bugzilla.elinks.or.cz |
|
||||
| [-]- bugzilla.elinks.cz |
|
||||
| | |-- BUGLIST |
|
||||
| | `-- LASTORDER |
|
||||
| [+]- kerneltrap.org |
|
||||
|
@ -100,7 +100,7 @@ You need to write some scripts.
|
||||
ELinks Lua additions
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
The Lua support is based on the idea of @dfn{hooks}. A hook is a function that
|
||||
The Lua support is based on the idea of *hooks*. A hook is a function that
|
||||
gets called at a particular point during the execution of ELinks. To make
|
||||
ELinks do what you want, you can add and edit such hooks.
|
||||
|
||||
@ -180,14 +180,13 @@ standard Lua functions.
|
||||
enable_systems_functions ()::
|
||||
Enable some potentially dangerous functions, as well as some other
|
||||
functions which were unfortunate enough to be lumped in the same group.
|
||||
|
||||
+
|
||||
The functions are: `openfile`, `closefile`, `readfrom`, `writeto`, `appendto`,
|
||||
`pipe_read`, `remove`, `rename`, `flush`, `seek`, `tmpname`, `read`, `write`
|
||||
`execute`, `exit`, `clock`, `date`, `getenv`, `setlocale`.
|
||||
|
||||
+
|
||||
Note: `setlocale` is a standard Lua function and will not affect
|
||||
the current ELinks locale.
|
||||
@end deffn
|
||||
|
||||
current_url ()::
|
||||
Returns the URL of the current page being shown (in the ELinks session
|
||||
@ -249,13 +248,13 @@ instead of copying code out of this document. Also, not everything in there is
|
||||
covered here.
|
||||
|
||||
If you would like to contribute scripts, that would be great! Please send
|
||||
them to me at mailto:tjaden@@users.sourceforge.net[]. Cliff and I plan to
|
||||
them to me at mailto:tjaden@users.sourceforge.net[]. Cliff and I plan to
|
||||
start a script repository, provided we get some contributions. As for script
|
||||
ideas, you'll just have to be a little creative :-)
|
||||
|
||||
Also take a look at the `contrib/lua/` directory in the ELinks distribution.
|
||||
Note that Peter and Cliff don't maintain the Lua support intensively anymore,
|
||||
thus it would be probably nice to Cc me (mailto:pasky@@ucw.cz[]) if you want
|
||||
thus it would be probably nice to Cc me (mailto:pasky@ucw.cz[]) if you want
|
||||
to contribute some patch, so that I would be able to add it to the ELinks
|
||||
distribution.
|
||||
|
||||
|
5
po/fi.po
5
po/fi.po
@ -7,7 +7,7 @@ msgstr ""
|
||||
"Project-Id-Version: ELinks 0.5pre0.CVS\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2006-02-24 23:08+0200\n"
|
||||
"PO-Revision-Date: 2006-02-23 23:17+0200\n"
|
||||
"PO-Revision-Date: 2006-04-08 17:33+0300\n"
|
||||
"Last-Translator: Kalle Olavi Niemitalo <kon@iki.fi>\n"
|
||||
"Language-Team: Finnish <translation-team-fi@lists.sourceforge.net>\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -7736,9 +7736,10 @@ msgstr "L
|
||||
msgid "Radio button"
|
||||
msgstr "Radionäppäin"
|
||||
|
||||
# kenttä, jossa on joukko arvoja, joista pitää valita yksi
|
||||
#: src/viewer/text/form.c:1460
|
||||
msgid "Select field"
|
||||
msgstr "Valitse kenttä"
|
||||
msgstr "Valintakenttä"
|
||||
|
||||
#: src/viewer/text/form.c:1464
|
||||
msgid "Text area"
|
||||
|
@ -2,7 +2,7 @@ PURPOSE
|
||||
=======
|
||||
|
||||
The scripts in this directory scan the PO files and search for
|
||||
translations that assign the same accelerator to for multiple buttons
|
||||
translations that assign the same accelerator to multiple buttons
|
||||
in a dialog box or to multiple items in a menu.
|
||||
|
||||
In addition to this static checking, ELinks can also detect
|
||||
|
51
src/bfu/README
Normal file
51
src/bfu/README
Normal file
@ -0,0 +1,51 @@
|
||||
OVERVIEW OF BFU
|
||||
===============
|
||||
|
||||
BFU is the text-mode user interface used by ELinks. It builds dialogs,
|
||||
widgets and menus on top of the window system implemented at src/terminal/.
|
||||
|
||||
=====================
|
||||
| struct widget_ops |
|
||||
| bfu/widget.h |
|
||||
=====================
|
||||
1^
|
||||
|
|
||||
*|
|
||||
==================== ====================== =================
|
||||
| struct menu_item | | struct widget_data | * 1 | struct widget |
|
||||
| bfu/menu.h | | bfu/widget.h | ---> | bfu/widget.h |
|
||||
==================== ====================== =================
|
||||
+^ +^ +^
|
||||
| | |
|
||||
?| 1| 1|
|
||||
=============== ====================== =================
|
||||
| struct menu | | struct dialog_data | * 1 | struct dialog |
|
||||
| bfu/menu.h | | bfu/dialog.h | ----> | bfu/dialog.h |
|
||||
=============== ====================== =================
|
||||
?^ ?^ ?^ ?| 1| 1|
|
||||
| | | | | |
|
||||
| | | 1v | 1v
|
||||
| 1v 1v ====================== | ========================
|
||||
| ===================== | struct memory_list | | | struct dialog_layout |
|
||||
| | struct window | | util/memlist.h | | | bfu/dialog.h |
|
||||
| | terminal/window.h | ====================== | ========================
|
||||
| ===================== ?v
|
||||
| *^ =========================
|
||||
| | | struct dialog_refresh |
|
||||
| 1v | bfu/dialog.h |
|
||||
| ======================= =========================
|
||||
| ? | struct terminal |
|
||||
---------- | terminal/terminal.h |
|
||||
main_menu =======================
|
||||
?| ?|
|
||||
| |
|
||||
1v ?v
|
||||
========================== =============================
|
||||
| struct terminal_screen | | struct terminal_interlink |
|
||||
| terminal/screen.h | | terminal/event.c |
|
||||
========================== =============================
|
||||
|
||||
Legend: ---> can be followed like a pointer
|
||||
? zero or one 1 exactly one
|
||||
* zero or more + one or more
|
||||
There may be errors in the quantifiers.
|
Loading…
Reference in New Issue
Block a user