The Following User Says Thank You to marmistrz For This Useful Post: | ||
|
2014-02-13
, 23:12
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#152
|
The Following User Says Thank You to Android_808 For This Useful Post: | ||
|
2014-02-14
, 01:05
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#153
|
|
2014-02-17
, 19:14
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#154
|
Index: gecko-dev/content/media/gstreamer/GStreamerFormatHelper.cpp =================================================================== --- gecko-dev.orig/content/media/gstreamer/GStreamerFormatHelper.cpp 2014-02-17 14:47:44.019372890 +0000 +++ gecko-dev/content/media/gstreamer/GStreamerFormatHelper.cpp 2014-02-17 18:34:57.438879473 +0000 @@ -294,26 +294,10 @@ GList* GStreamerFormatHelper::GetFactories() { NS_ASSERTION(sLoadOK, "GStreamer library not linked"); -#if GST_VERSION_MAJOR >= 1 - uint32_t cookie = gst_registry_get_feature_list_cookie(gst_registry_get()); -#else - uint32_t cookie = gst_default_registry_get_feature_list_cookie(); -#endif - if (cookie != mCookie) { - g_list_free(mFactories); -#if GST_VERSION_MAJOR >= 1 - mFactories = - gst_registry_feature_filter(gst_registry_get(), - (GstPluginFeatureFilter)FactoryFilter, - false, nullptr); -#else - mFactories = - gst_default_registry_feature_filter((GstPluginFeatureFilter)FactoryFilter, - false, nullptr); -#endif - mCookie = cookie; - } - + g_list_free(mFactories); + mFactories = + gst_default_registry_feature_filter((GstPluginFeatureFilter)FactoryFilter, + false, nullptr); return mFactories; } Index: gecko-dev/content/media/gstreamer/GStreamerFunctionList.h =================================================================== --- gecko-dev/content/media/gstreamer/GStreamerFunctionList.h 2014-02-17 14:47:44.019372890 +0000 +++ gecko-dev/content/media/gstreamer/GStreamerFunctionList.h 2014-02-17 18:34:57.438879473 +0000 @@ -50,6 +50,7 @@ GST_FUNC(LIBGSTREAMER, gst_init_check) GST_FUNC(LIBGSTREAMER, gst_iterator_next) GST_FUNC(LIBGSTREAMER, gst_message_parse_error) +GST_FUNC(LIBGSTREAMER, gst_message_get_type) GST_FUNC(LIBGSTREAMER, gst_message_type_get_name) GST_FUNC(LIBGSTREAMER, gst_mini_object_ref) GST_FUNC(LIBGSTREAMER, gst_mini_object_unref) @@ -63,7 +64,6 @@ GST_FUNC(LIBGSTREAMER, gst_pipeline_get_type) GST_FUNC(LIBGSTREAMER, gst_plugin_feature_get_rank) GST_FUNC(LIBGSTREAMER, gst_registry_feature_filter) -GST_FUNC(LIBGSTREAMER, gst_registry_get_feature_list_cookie) GST_FUNC(LIBGSTREAMER, gst_segment_init) GST_FUNC(LIBGSTREAMER, gst_segment_to_stream_time) GST_FUNC(LIBGSTREAMER, gst_static_caps_get)
|
2014-02-17
, 19:32
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#155
|
size(Qt5libs)
size(Qt4libs) - size(Qt5libs)
|
2014-02-17
, 20:00
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#156
|
|
2014-02-17
, 20:12
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#157
|
What happens if you multitask, say have OMP and browser opened? You'd then need to have Qt4 for OMP loaded and Qt5 for browser.
My real concern with qt5 was how well supported it is on Maemo. I don't see a great deal of apps using it, if any. If you compare the amount of code ripped out in the recent qt5 commit in embedlite, the new port seems to be much easier to work with for some interactions. However that simplification must at times come at a cost of increasing qt library size.
|
2014-02-17
, 23:46
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#158
|
The Following 5 Users Say Thank You to Android_808 For This Useful Post: | ||
|
2014-02-21
, 17:44
|
Posts: 80 |
Thanked: 71 times |
Joined on Jan 2014
@ Albania
|
#159
|
|
2014-02-22
, 17:33
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#160
|
The Following User Says Thank You to marmistrz For This Useful Post: | ||
Tags |
gecko browser, maemo 5 |
|
1. Migrate to Qt5
Pros: maybe better performance of the library, being always up-to-date, no problem "they'll drop our support"
Cons: More RAM usage, possible problems with the port being buggy
2. Stick with Qt4
Pros: no additional work required (apart from the UI creation)
Cons: Being more and more out-of-date, not receiving updates, need to find a stable commit.
3. Go for Gtk
Pros: Gtk support is still there, performance
Cons: Manpower that knows Gtk, how long will they support gtk2, Gtk and Mozembed issues. No examples (correct me if I'm wrong)
4. Switch to WebKit
Pros: We have QtWebkit in Qt4, good documentation
Cons: WebKit is unmaintained AFAIK, WebKit in Qt5 is probably newer.
5. Port Fremantle to Qt5
Pros: compat, possible performance
Cons: Whole lotta work! Really whole lotta... Impossible for two-men team
Please add your opinions and suggestions.
If you want to support my work, you can donate by PayPal or Flattr
Projects no longer actively developed: here