After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 710418 - MeeGo extension not ported to GTK3
MeeGo extension not ported to GTK3
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Other Extensions
2.9.0
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-10-17 19:47 UTC by Michał Sawicz
Modified: 2013-10-19 20:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michał Sawicz 2013-10-17 19:47:42 UTC
When building with --enable-meego, the build fails with the following errors:

./Banshee.MeeGo/MediaPanelContents.cs(217,33): error CS0115: `Banshee.MeeGo.MediaPanelContents.OnExposeEvent(Gdk.EventExpose)' is marked as an override but no suitable method found to override
./Banshee.MeeGo/MediaPanelContents.cs(231,63): error CS0234: The type or namespace name `Region' does not exist in the namespace `Gdk'. Are you missing an assembly reference?
./Banshee.MeeGo/MeeGoHeaderBox.cs(100,33): error CS0115: `Banshee.MeeGo.MeeGoHeaderBox.OnExposeEvent(Gdk.EventExpose)' is marked as an override but no suitable method found to override
./Banshee.MeeGo/MeeGoHeaderBox.cs(114,63): error CS0234: The type or namespace name `Region' does not exist in the namespace `Gdk'. Are you missing an assembly reference?
Comment 1 Bertrand Lorentz 2013-10-19 14:07:10 UTC
I've started working on this.

After getting the extension to build, my plan is to rename it to something that doesn't refer to a dead project...
Comment 2 Andrés G. Aragoneses (IRC: knocte) 2013-10-19 16:14:23 UTC
(In reply to comment #1)
> my plan is to rename it to something that
> doesn't refer to a dead project...

How about the name of a Meego successor? Some say it's Tizen, but I believe this one is actually based on new technologies, like HTML5... So maybe the best way to call it is Sailfish? ( http://hexus.net/mobile/news/general/48433-jolla-sailfish-mobile-os-meego-successor-launched/ )
Comment 3 Andrés G. Aragoneses (IRC: knocte) 2013-10-19 16:16:33 UTC
Or "Mer": http://en.wikipedia.org/wiki/Mer_%28operating_system%29
Comment 4 Bertrand Lorentz 2013-10-19 16:36:49 UTC
None of the MeeGo successor use Banshee, as it was only used for the NetBook UI. As we know, netbooks have now gone the way of the dodo.

The name I've chosen for now is "MediaPanel". The idea is that it's a simple panel that allows you to quickly browse and play your media.

In any case, this will be an internal, technical identifier for the extension (folder name, extension id, namespace, etc.).

If a better name emerges, changing the name shown to the user will only be a few string modifications.
Comment 5 Andrés G. Aragoneses (IRC: knocte) 2013-10-19 16:52:23 UTC
(In reply to comment #4)
> None of the MeeGo successor use Banshee

True. Plus I think that Meego actually used QT by default, and there was some way to run "legacy GTK apps" (from the "Maemo" era), but I guess this was also possible with GTK2 (which we're moving from).

> as it was only used for the NetBook
> UI. As we know, netbooks have now gone the way of the dodo.
> The name I've chosen for now is "MediaPanel". The idea is that it's a simple
> panel that allows you to quickly browse and play your media.

Mmm, to be honest, not sure I like the name. Why not use "Netbook" as a name, now that you mentioned it?


> In any case, this will be an internal, technical identifier for the extension
> (folder name, extension id, namespace, etc.).

True, but I guess we should enable it by default in the build (instead of requiring a special flag like it is currently) so we don't forget about it again in a release (and we could still mark it as not enabled by default, even if it's built by default). No?
Comment 6 Andrés G. Aragoneses (IRC: knocte) 2013-10-19 16:53:40 UTC
(In reply to comment #5)
> but I guess this was also possible with GTK2 (which we're moving from).

Typo: s/also/only/
Comment 7 Bertrand Lorentz 2013-10-19 20:28:14 UTC
I've now ported the extension to GTK3, and renamed it MediaPanel.
I stuck with that name because it is generic enough, and it made the whole renaming easier: MeeGoPanel -> MediaPanel.
In addition, the extension was also sometimes referred to as "MeeGo Media Panel".

It is now built by default, but the extension is not enabled by default.

There are still some issues left to fix:
- Solve UI drawing glitches
- Adhere to the current theme, while still retaining the nice UI personality
- Don't show the main window when started with --client=MediaPanel

We'll address those later, and any help on that is welcome, of course.

Everything is available in git master.