I rebased patch including elm_need_web and _elm_unneed_web.
Could you let me know what should I do to land this patch?
Best Regards,
Ryuan Choi
2012/10/24 ryuan Choi
>
>
> 2012/10/24 Gustavo Sverzut Barbieri
>
>> On Mon, Oct 22, 2012 at 10:15 PM, ryuan Choi
>> wrote:
>> > In the view point o
2012/10/24 Gustavo Sverzut Barbieri
> On Mon, Oct 22, 2012 at 10:15 PM, ryuan Choi wrote:
> > In the view point of basic behavior, right, they should be almost same.
> >
> > Now, There are three reasons not to keep the same structure
> >
> > 1. WebKit2/efl ignores or choose different(better?) AP
yeah we need colaboration. i think this is a good start.
Daniel Juyung Seo (SeoZ)
On Oct 24, 2012 6:38 AM, "Gustavo Sverzut Barbieri"
wrote:
> On Mon, Oct 22, 2012 at 10:15 PM, ryuan Choi wrote:
> > In the view point of basic behavior, right, they should be almost same.
> >
> > Now, There are t
On Mon, Oct 22, 2012 at 10:15 PM, ryuan Choi wrote:
> In the view point of basic behavior, right, they should be almost same.
>
> Now, There are three reasons not to keep the same structure
>
> 1. WebKit2/efl ignores or choose different(better?) API names from
> WebKit1/Efl.
> It's sad but true.
>
In the view point of basic behavior, right, they should be almost same.
Now, There are three reasons not to keep the same structure
1. WebKit2/efl ignores or choose different(better?) API names from
WebKit1/Efl.
It's sad but true.
For example,
- reload_bypass_cache instead of reload_full (
https
On Mon, Oct 22, 2012 at 2:30 PM, ryuan Choi wrote:
> Hi,
>
> As a second patch of elm-web for WK2,
> I moved some elm-web APIs, which calls same APIs of ewebkt and ewbkit2, to
> common area.
> In addition, I extracted theme related code from elm_web to share.
>
> In order to share, I added elm_web
