On Sun, Dec 21, 2008 at 9:52 AM, Viktor Kojouharov <vkojouha...@gmail.com> wrote: > On Sun, 2008-12-21 at 11:10 +0100, Vincent Torri wrote: >> >> On Sun, 21 Dec 2008, Gustavo Sverzut Barbieri wrote: >> >> > Hello guys, >> > >> > Since INdT guys released EFL-Webkit port some days ago some hacks >> > started to appear to test it. Nicolas (captainigloo) did some tests in >> > order to evaluate using it in enna, Raoul started a cool test >> > application called ewww: >> > >> > svn co http://dev.calaos.fr/calaos-svn/ewww >> > >> > I did a checkout of this code and created my own git so I keep a >> > patchset on top of it easily: >> > >> > git clone git://git.profusion.mobi/users/gustavo/ewww.git >> > >> > I diverged a bit with regard to theme, going a more "black & white" >> > approach and the layout is towards google chrome: >> > http://staff.get-e.org/~barbieri/ewww.png (scrollbars are just >> > indicators and are hidden automatically after 1 second, that's why >> > there are none in the screenshot). >> > >> > My next steps on the interface is to provide proper smart objects for >> > the view+scroll and then the tab chrome (the current ui can be thought >> > as a tab). With that I plan to write some basic tabs and then explore >> > with Google Chrome's idea of multiple process, since I'll not do any >> > fancy shared memory work, I just plan to reparent >> > ecore_evas_software_x11 on top of my other canvas, that might do for >> > now. >> >> As I said on IRCn as Nicolas, Raoul and you are interested in that >> program: >> >> 1) the code should be placed somewhere everyone can commit. Of course, >> PROTO/ is the way to go for now >> >> 2) More important, we should first discuss about the UI design of such >> app. ML and also a page in the wiki should be used, imho >> >> Vincent > > Does ewk use edje to theme everything, including html elements like > un-styled buttons?
so far it's very barebones, ui elements like un-styled buttons are ugly and hardcoded, we really need to use edje there, but I'm not sure how easy it is. I'm not sure of the threads usage, but seems that webkit is using them, and threads don't play well with efl, so rendering edje from threads is a no-go... if we can avoid/workaround that than it should be easy. > 2) I'm personally at odds between firefox's and chrome's UI. While > firefox's interface is familiar to virtually anyone, chrome does offer > some interesting ideas (like the address bar being outside the tab, not > inside). We should also introduce some e-based ideas, like "toolbars" > which are just gadget containers. We can implement fav bookmarks on such > a toolbar using a module, much like the e_fm or e17, or use already > existing modules. we can do that later, as I said I want to have 2 smart objects for now, one will be just about scrollbars + view and the other is the controls like back/forward. For now they're fixed and all in edje, but I guess it's better to have a slot using edje 'box' and append buttons from C code, so user can reorder and even hide some. Some could be loaded from plugins, of course. But remember this is a separate app and cannot rely on e-internals for plugins (maybe I'll use guarana for that). > 3) It would also be interesting to create an e17 module for displaying > things like dashboard widgets (or web pages for that matter). it shouldn't be too difficult, maybe it's even easier than having a full browser working. but we need more information from webkit than what is provided so far: we need a way to query for meta-information so we can choose transparent bg or query required size to draw the page. but e17 runs modules inside the same process and this is not trustworthy yet, so let's wait. > 3.5) The ultimate goal would be to use edje inside web pages / widgets, > like apple allows dashboard users to use cocoa (or whatever their > framework is called). this is a different matter, but doable. maybe it's easier to ask indt to push this themselves, as qedje is compatible with edje, so if qt-webkit gets it, we may get it as well. > lots of interesting ideas for this one :) > > btw, is the code in c, or c++? most of efl-webkit code is in c++, but there is a public api in C that is exposed as Evas_Object *. ewww code was started by raoulh and is all C. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
