ECORE-CON-SOCKS! SOCKS ON!!!!
now ecore_con supports socks (v4 and v4a only, so no ipv6) connections natively for making remote connections
for those of you who want their apps to start proxying immediately, just update and export this handy environment variable:
ECORE_CON_SOCKS_V4=[user@]PROXY_IP_ADDRESS:PROXY_PORT[:1] <--use :1 here to enable dns lookups on the proxy
SVN revision: 65934
Subject: [E-devel] eina 1.1.0beta patches for/from pkgsrc
Several patches to fix warnings and potential on netbsd/solaris. minor
so i think i'll skip changelog for this.
SVN revision: 65898
addition to evas gl backend.
Working on different mobile devices, we've noticed that the cost of context
switch (MakeCurrent) in GL can be very expensive depending on the driver
implementation. To minimize the poorly written driver's context switch
overhead, I've implemented a state tracking layer on top of the driver
implemented GL.
Essentially, this layer wraps all the GL/Glue(GLX/EGL) APIs and manages its own
state changes. Internally, only one real GL context is created and logical
contexts are created every time a user requests context creation. The logical
contexts keep track of its states and sets only the necessary states
(the ones that are different than the current ones)
when there is a MakeCurrent request. The real MakeCurrent gets called when
there is a Surface/Window change request.
The GL library is dlopened and all the APIs are dlsym'ed and wrapped
accordingly. All the GL functions are in evas_gl_core.{h,c}.
Here's a very simply flow of the code.
- all the APIs are exported as function pointers (*glsym_glBegin),
(*glsm_eglCreatContext), and etc.
- all the native GL/Glue(GLX/EGL) APIs are dlsym'ed as _sym_glBegin,
_sym_eglCreateContext, and etc.
- all the fastpath APIs are implmemnted as fpgl_glBegin,
fpgl_eglCreateContext, and etc.
- if faspath is seletected, the exported APIs are set accordingly
ie. glsym_glBegin = fpgl_glBegin;
- default mode is the regular gl symbols are directly set.
ie. glsym_glBegin = _sym_glBegin;
I have an Environment variable where you can set it to three different Modes
EVAS_GL_FASTPATH = 0 // Default mode. Regular GL symbols are directly loaded
EVAS_GL_FASTPATH = 1 // Fastpath mode. Takes the path described above.
EVAS_GL_FASTPATH = 2 // Wrapped mode. All the regular GL functions are
wrapped once. This can be used for various
purposes
Since all the GL symbols are now loaded in this library, I took out all
the gl symbol loading parts in the evas gl backend as you'll see in the patch.
The changes to the engine and the backend itself is pretty minor.
There are still some known issues to hammer out but I thought we're at a good
place for an initial version so that my source doesn't diverge too much.
Known Issues and To Do's
* Current GL Fastpath version doesn't support multiple threads. Instead of
having one global real context, I would need to do it for each thread. I'll
get on this soon.
* Issues running Evas GL on certain conditions. When running the elementary
test (with gl engine), if you run ELMGLview test that runs in ON_DEMAND mode,
everything works fine. BUT, when you run the ELMGLView test in ALWAYS
mode, the subsequent elm tests shows blank screen. When you destroy the
GLView window, everything else comes on fine.
* Resource protection code. This actually applies to Evas GL code in general
as well. Since all the resources are shared among all the contexts that get
created, I would like to eventually have a resource protecting mechanism that
prevents access to resources outside of its context unless specifically
specified.
I'm attaching three files
- evas_gl_core.h, evas_gl_core.c, fastpath.patch
To get the code running...
- copy evas_gl_core.{c,h} to src/modules/engine/gl_common/
- apply the fastpath.patch
- compile/install evas
- to run with fastpath GL (ie. % EVAS_GL_FASTPATH=1 ./evasgl_sample1)
SVN revision: 65891
in later 2011, we began using formatting tools to fix problematic formatting caused by previous runs of formatting tools used to fix problematic formatting
SVN revision: 65852
NOTE: need some help to finish splitting this API in a more meaningfull sense.
TODO: Fix a few FIXME and update monitoring backend to work on most system.
SVN revision: 65840
Subject: Fix Neon build with Thumb-2
In assembly part of function evas_common_convert_rgba_to_32bpp_rgb_8888_rot_90:
Don't use 3-operand add instructions (e.g. add r2, r5, #2) as this is
not supported in unified syntax.
SVN revision: 65768
elementary_config does this, and the glib based main loop didn't support it.
Signed-off-by: Mike McCormack <mj.mccormack@samsung.com>
SVN revision: 65683
NOTE: This was necessary for solving issue with the new CURRENT feature. I
don't like this massive change, but there is no way around. This patch is
only the first step, I will wait the full night before completly fixing
the issue with CURRENT.
WARNING: If this patch doesn't break svn, you must feel lucky and go play
money games. In all other case, please report any issue to the developper
mailing-list.
SVN revision: 65619
* fix some event values
* Add the "Windows" key support
* manage modifiers for shift, ctrl, alt and windows keys
that support is not finished, there still several bugs.
SVN revision: 65613
A previous patch had changed its signature, but since this is an EAPI,
we can't break it. Now ecore_fb_input_device_window_set() was added to
provide the same functionality.
SVN revision: 65589
Subject: [E-devel] [Patch][ecore_file] Fix buffer flush bug
fclose() should be called before callback is called to notify user of
download completion because it cannot be flushed sometimes.
SVN revision: 65572
and.... u get the idea. this made an n^m list of messages... where n
was 3 of messages sent and m was # of child parts (42 of them)... this
caused a silly 3 of timers to be allocated... don't ask how many. in a
simple snapshot i saw 101mb of timers allocated... and i was just
starting... anyway - this makes the propagatiopn not propagate down
and then back up again... and it only needs 1 timer allocated to
handle a re-schedule of processing messages. not N. "leak" that was
just a massive memory spike) is now fixed.
SVN revision: 65571
ecore_evas_fb.c: In function ‘_ecore_evas_fb_init’:
ecore_evas_fb.c:248:14: warning: implicit declaration of function ‘ecore_fb_ts_event_window_set’
Signed-off-by: Mike McCormack <mj.mccormack@samsung.com>
SVN revision: 65546
AFAIU, this should be the correct, although this parameter isn't used
anywhere. But let's keep some consistency with the other backends, and
try to avoid future bugs.
Patch for SiT.
SVN revision: 65540
mouse is in on init (as events wont always give this) and focus
is set on show if appropriate if no focus in/out events come
from the back-end later
Fix setting override state to only hide if it should be
visible at that point in x back end support
SVN revision: 65508
tweet: hey, SeoZ here, I really like Microsoft. I mean REALLY like them. I think they're a fantastic company and I hope everyone uses winmo!
SVN revision: 65469