2013-06-11 12:44:31 -07:00
|
|
|
/ecore_animator_example
|
|
|
|
|
/ecore_audio_custom
|
|
|
|
|
/ecore_audio_playback
|
|
|
|
|
/ecore_audio_to_ogg
|
|
|
|
|
/ecore_client_bench
|
2015-03-25 11:26:41 -07:00
|
|
|
/ecore_compose_get_example
|
|
|
|
|
/ecore_con_client_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_con_client_simple_example
|
2015-04-22 05:55:33 -07:00
|
|
|
/ecore_con_eet_client_example
|
|
|
|
|
/ecore_con_eet_server_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_con_lookup_example
|
2015-03-25 11:26:41 -07:00
|
|
|
/ecore_con_server_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_con_server_http_example
|
|
|
|
|
/ecore_con_server_simple_example
|
|
|
|
|
/ecore_con_url_cookies_example
|
|
|
|
|
/ecore_con_url_download_example
|
2015-03-25 11:26:41 -07:00
|
|
|
/ecore_con_url_ftp_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_con_url_headers_example
|
|
|
|
|
/ecore_evas_basics_example
|
|
|
|
|
/ecore_evas_buffer_example_01
|
|
|
|
|
/ecore_evas_buffer_example_02
|
|
|
|
|
/ecore_evas_callbacks
|
2016-12-02 11:17:53 -08:00
|
|
|
/ecore_evas_cursor_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_evas_ews_example
|
|
|
|
|
/ecore_evas_extn_plug_example
|
|
|
|
|
/ecore_evas_extn_socket_example
|
2015-03-25 11:26:41 -07:00
|
|
|
/ecore_evas_object_example
|
2016-10-07 11:57:04 -07:00
|
|
|
/ecore_evas_wayland_multiseat_example
|
2015-03-25 11:26:41 -07:00
|
|
|
/ecore_evas_window_sizes_example
|
2016-09-27 15:17:12 -07:00
|
|
|
/ecore_evas_vnc_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_event_example_01
|
|
|
|
|
/ecore_event_example_02
|
|
|
|
|
/ecore_exe_example
|
|
|
|
|
/ecore_exe_example_child
|
|
|
|
|
/ecore_fd_handler_example
|
2015-03-25 11:26:41 -07:00
|
|
|
/ecore_file_download_example
|
|
|
|
|
/ecore_getopt_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_idler_example
|
2018-12-04 01:09:33 -08:00
|
|
|
/ecore_input_joystick_example
|
2015-03-25 11:26:41 -07:00
|
|
|
/ecore_imf_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_job_example
|
2015-03-25 11:26:41 -07:00
|
|
|
/ecore_pipe_gstreamer_example
|
2013-06-11 12:44:31 -07:00
|
|
|
/ecore_pipe_simple_example
|
|
|
|
|
/ecore_poller_example
|
|
|
|
|
/ecore_server_bench
|
|
|
|
|
/ecore_thread_example
|
|
|
|
|
/ecore_time_functions_example
|
|
|
|
|
/ecore_timer_example
|
ecore-buffer: Add ecore_buffer library to EFL.
Summary:
Ecore_Buffer is abstraction of graphic buffer.
it supports backend of shm, x11_dri2 and x11_dri3 for now,
and this library also provides method to share buffers between processes.
Ecore_Buffer_Provider and Ecore_Buffer_Consumer is for this, sharing buffer.
provider draws something in to Ecore_Buffer, and consumer receives and displays it.
the binary, bq_mgr is a connection maker for buffer provider and consumer.
it can be included Enlightenment as a deamon later.
@feature
Test Plan:
1. Configure with --enable-ecore-buffer and --enable-always-build-examples to build examples.
2. Run bq_mgr, it connects consumer and provider.
3. Run ecore_buffer_provider_example and ecore_buffer_consumer_example
Reviewers: lsj119, gwanglim, cedric, zmike, jpeg, raster, devilhorns
Subscribers: cedric
Differential Revision: https://phab.enlightenment.org/D2197
2015-06-22 07:23:54 -07:00
|
|
|
/ecore_buffer_example
|
|
|
|
|
/ecore_buffer_consumer_example
|
|
|
|
|
/ecore_buffer_provider_example
|
2016-08-13 00:50:29 -07:00
|
|
|
/efl_io_copier_example
|
2016-08-23 07:58:19 -07:00
|
|
|
/efl_io_copier_simple_example
|
2016-08-23 16:03:10 -07:00
|
|
|
/efl_io_queue_example
|
2016-11-24 19:27:33 -08:00
|
|
|
/efl_io_buffered_stream_example
|
efl.net: socket, server and dialer for TCP.
Efl.Net.Server defines how to accept new connections, doing the
bind(), listen() and accept() for protocols such as TCP.
Efl.Net.Dialer defines to to reach a server.
Both are based on Efl.Net.Socket as communication interface that is
based on Efl.Io.Reader, Efl.Io.Writer and Efl.Io.Closer, thus being
usable with code such as Efl.Io.Copier.
The Server will emit an event "client,add" with the established
Socket, which is a child and can be closed by both the server or the
user.
The Dialer extends the Socket and allows for creating one given an
address, that will be resolved and connected.
TCP is the initial implementation so we an validate the
interfaces. UDP, Unix-Local and SSL will come later as derivate
classes.
The examples are documented and should cover the basic principles:
- efl_io_copier_example can accept "tcp://IP:PORT" and will work as a
"netcat", can send data from socket, file or stdin to a socket,
file, stdout or stderr.
- efl_net_server_example listens for connections and can either reply
"Hello World!" and take some data or work as an echo-server,
looping back all received data to the user.
More complex interactions that require a "chat" between client and
server will be covered with new classes later, such as a queue that
empties itself once data is read.
2016-08-17 21:53:16 -07:00
|
|
|
/efl_net_server_example
|
efl_net_{socket,dialer,server}_simple: easy to use, buffered network sockets.
The low level I/O primitives are powerful but adds some complexity to
use, for bi-directional streaming communication one ends creating two
Efl.Io.Queue and two Efl.Io.Copier to pipe data to socket when it can
operate.
Then encapsulate the socket using the new Efl.Io.Buffered_Stream, this
will allow the socket, be a dialer or a server client, to be operated
as a single handle that internally carries about the buffering for
you.
As one can see in the examples, compared to their "manual"
alternatives they are very easy to use, ressembling
Ecore_Con_Server/Ecore_Con_Client, but also offers line-based
delimiters and the possibility to let the socket to handle queueing
for you in case you received partial messages (just do not
read/clear/discard the received data).
2016-11-25 11:18:34 -08:00
|
|
|
/efl_net_server_simple_example
|
2016-08-19 20:55:26 -07:00
|
|
|
/efl_net_dialer_http_example
|
2016-08-29 20:28:00 -07:00
|
|
|
/efl_net_dialer_websocket_example
|
|
|
|
|
/efl_net_dialer_websocket_autobahntestee
|
2016-10-18 13:51:59 -07:00
|
|
|
/efl_net_dialer_udp_example
|
efl_net_{socket,dialer,server}_simple: easy to use, buffered network sockets.
The low level I/O primitives are powerful but adds some complexity to
use, for bi-directional streaming communication one ends creating two
Efl.Io.Queue and two Efl.Io.Copier to pipe data to socket when it can
operate.
Then encapsulate the socket using the new Efl.Io.Buffered_Stream, this
will allow the socket, be a dialer or a server client, to be operated
as a single handle that internally carries about the buffering for
you.
As one can see in the examples, compared to their "manual"
alternatives they are very easy to use, ressembling
Ecore_Con_Server/Ecore_Con_Client, but also offers line-based
delimiters and the possibility to let the socket to handle queueing
for you in case you received partial messages (just do not
read/clear/discard the received data).
2016-11-25 11:18:34 -08:00
|
|
|
/efl_net_dialer_simple_example
|
2016-10-26 13:57:37 -07:00
|
|
|
/efl_net_dialer_unix_example
|
2016-10-27 07:53:17 -07:00
|
|
|
/ecore_evas_vnc
|
2016-10-28 17:48:19 -07:00
|
|
|
/efl_net_socket_ssl_dialer_example
|
|
|
|
|
/efl_net_socket_ssl_server_example
|
2016-11-01 06:52:21 -07:00
|
|
|
/*.pem
|
efl_net_session and efl_net_control for ConnMan
These are objects to allow control of networking devices
(efl_net_control) as well as an application to request for
connectivity (efl_net_session).
They are loosely based on ConnMan.org, which we already use in
Enlightenment Window Manager via DBus access with Eldbus. However they
do not map 1:1 as the goal was to expose a viable subset of controls
but in a simple and general way, thus nome strings were converted to
enums, some arrays of strings were converted to bitwise flags, some
names were made more general, such as "service" was turned into
"access point" so it doesn't generate confusion with other "network
services" (ie: http server), or "favorite" that was renamed to
"remembered". Some behavior are slightly different (yet able to be
implemented on top), such as "Service.MoveBefore" and "MoveAfter" were
converted to a numeric "priority", calculated from service's list
index, changing the priority will reoder the list and thus generate
the MoveBefore and MoveAfter DBus commands.
ConnMan was chosen not only because we already use it, but because its
DBus API is sane and simple, with the server doing almost all that we
need. This is visible in the efl_net_session, which is completely done
in the server and do not require any extra work on our side -- aside
from talking DBus and converting to Eo, which is a major work :-D
NOTE: ConnMan doesn't use FreeDesktop.Org DBus interfaces such as
Properties and ObjectManager, thus we cannot use
eldbus_model_object.
There are two examples added:
- efl_net_session_example: monitors the connection available for an
application and try to connect. You need a connman compiled with
session_policy_local and a configuration file explained in
https://github.com/aldebaran/connman/blob/master/doc/session-policy-format.txt
to get a connection if nothing is connected. Otherwise it will just
monitor the connectivity state.
- efl_net_control_example: monitors, plays the agent and configure
the network details. It can enable/disable technologies, connect to
access points (services) and configure them. It's quite extensive
as allows testing all of ConnMan's DBus API except P2P (Peers).
2016-09-15 17:43:19 -07:00
|
|
|
/efl_net_session_example
|
|
|
|
|
/efl_net_control_example
|
2016-12-11 20:23:29 -08:00
|
|
|
/efl_net_ip_address_example
|
2016-11-22 11:27:16 -08:00
|
|
|
/ecore_ipc_server_example
|
|
|
|
|
/ecore_ipc_client_example
|
2017-09-13 02:16:39 -07:00
|
|
|
/ecore_promise2_example
|
