[EFL] Add getter for Ewk_JS_Object::view.
Created attachment 121687 [details] Patch
Comment on attachment 121687 [details] Patch LGTM.
> Source/WebKit/efl/ewk/ewk_js.cpp:615 > +Evas_Object* ewk_js_object_view_get(const Ewk_JS_Object *jsObject) As far as I know, renewed coding style doesn't like '*' in front of parameter, Would you check the position of '*' in front of jsObject ? > Source/WebKit/efl/ewk/ewk_js.cpp:718 > +Evas_Object* ewk_js_object_view_get(const Ewk_JS_Object *jsObject) Ditto.
Wouldn't it be better to move checking NETSCAPE_PLUGIN_API macro to functions definition instead of duplicate them in source depending on macro value? It is known practice in WebKit and EFL port. Reviewing patches like this may confuse reviewer if he sees the same API in the same file whose return value and implementation are different (especially if macro isn't included in patch). What do you think about it?
Created attachment 121830 [details] Coding style fixes
(In reply to comment #4) > Wouldn't it be better to move checking NETSCAPE_PLUGIN_API macro to functions definition instead of duplicate them in source depending on macro value? Yeah, but it makes more sense to do that in a separate patch IMO. Doing so here would make the patch bigger and the function inconsistent with the rest of the file (the other option, fixing everything here, would be even worse).
(In reply to comment #5) > Created an attachment (id=121830) [details] > Coding style fixes LGTM. :)
(In reply to comment #6) > (In reply to comment #4) > > Wouldn't it be better to move checking NETSCAPE_PLUGIN_API macro to functions definition instead of duplicate them in source depending on macro value? > > Yeah, but it makes more sense to do that in a separate patch IMO. Doing so here would make the patch bigger and the function inconsistent with the rest of the file (the other option, fixing everything here, would be even worse). LGTM.
Committed r104562: <http://trac.webkit.org/changeset/104562>