On Jun 21, 2014 2:26 AM, "Carsten Haitzler" <ras...@rasterman.com> wrote: > > On Fri, 20 Jun 2014 21:25:54 -0300 Felipe Magno de Almeida > <felipe.m.alme...@gmail.com> said: > > > On Fri, Jun 20, 2014 at 9:07 PM, Carsten Haitzler <ras...@rasterman.com> > > wrote: > > > On Fri, 20 Jun 2014 15:02:37 -0300 Felipe Magno de Almeida > > > <felipe.m.alme...@gmail.com> said: > > > > > >> Em 19/06/2014 23:59, "Carsten Haitzler" <ras...@rasterman.com> escreveu: > > >> > > > >> > just webkit2 will do. if we can migrate to it for elm_web completely then > > >> > that'd be awesome. > > >> > > >> And maybe use EFL++ too? :-) > > > > > > no - as that would mean making elementary core pull in all the efl++ > > > bindings, forcing everyone to link to the efl++ binding libs regardless. > > > > There's no linking involved. Everything is header-only, even the > > generated files. > > > > > also i see no value here. we are using webkit2. with webkit1, the api we > > > used was a C api exposed by webkit (the webkit efl api). i don't know what > > > the webkit2 api looks like, but all we need to do is drive the api exposed > > > to control it and use the efl glue already in webkit2 to get it to display > > > and work in a widget. we don't need efl++ for that. it's a bit of a > > > contortion. :) > > > > I think it would make the port easier to mantain. It would give RAII, > > STL-compatibility, easier callback support with lambda-support and a > > value-based API. But that's just my opinion. > > elm web has a c api. will always have one. thus we then would have to write a c+ > + elm web by hand AND a c+eo one. no. use eo to write one and efl++ exposes elm > web. webkit api is internal then and thats how it should be.
I think Felipe was referring to the internal of WebKit talking to efl which is already in c++ and would likely benefit from using the c++ with no penalty. > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > ------------------------------------------------------------------------------ > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
