Bordeaux for OpenIndiana part 2: Safari and VLC media player

Continuing on in my multi-part review of Bordeaux for OpenIndiana, I’m trying out a few of the supported applications to see how well they run.

I must say there are some odd inclusions to the supported applications list, amongst them VLC media player, and Apple’s Safari web browser. Practically every current desktop-ish operating system out there is guaranteed to have a media player of some sort available for it: on OpenIndiana, I use MPlayer (which runs great), and generally if you’re running desktop Linux then you’re going to have access to a whole bunch of media players capable of handling practically any codec or format imaginable – so I’m not entirely sure why VLC under Wine would be desirable, nor even something Wine development resources should be focused on. Running VLC under Bordeaux for Linux, for example, just feels a bit pointless.

Safari is a similarly baffling inclusion. The rationale is so that web designers have access to Safari to check the rendering of web pages on – but I really think any web designer remotely serious about their job (at least, serious enough to use the title “web designer”) would have access to a Mac OS X box of some sort. Furthermore, Safari itself in my opinion is just a pointless browser to support – it runs on a single platform, is controlled by a single vendor, and frankly – in this day and age of cross compatibility – is just increasingly irrelevant to me.

At any rate, the performance of both of these applications under Bordeaux on OpenIndiana leaves plenty to be desired. VLC wouldn’t install at all using the standard Bordeaux GUI: I believe Bordeaux references download locations on the actual source vendors’ sites, and if the vendor changes these at all then the installer ceases to work: unfortunately, the Bordeaux installer GUI does not give sufficient feedback that this is the case. After manually downloading and installing VLC 1.1.0 for Windows under Bordeaux, I immediately noticed graphical artifacts in the VLC GUI:

VLC user interface problems

Interestingly, actual movie quality seemed to be degraded compared to the same file being played back under a native media player. In the below grab, a native media player is on the left, with the same movie being played back under VLC on Bordeaux on the right – click to zoom:

VLC on Bordeaux

 

Regarding Safari, the application appeared to install, but when attempting to view bookmarks, or perform other certain commands, the application would crash:

Safari crashing - part 1

Even worse, it would then screw up the windowing system, requiring manual killing of the wine processes:

Safari crashing - part 2

Finally, I could never actually get to any sites, internal or external, even though internet connectivity on the host was fine.

 

My suggestion to the Bordeaux developers would be to simply remove these redundant applications from the supported applications list, and focus on getting core business applications such as Microsoft Office working seamlessly under Bordeaux. Even if someone out there really does have a use for VLC or Safari under Wine, then it’s imperative to have these applications running smoothly in a shipping product: my initial impressions are that there are several areas where things aren’t quite ready for prime time.

See also: https://davekoelmeyer.wordpress.com/2011/03/17/bordeux-for-openindiana-a-commercial-wine-implementation/

Advertisements

4 thoughts on “Bordeaux for OpenIndiana part 2: Safari and VLC media player

  1. Dr. Μήτσος

    I just wonder why are you using VLC for Windows on a OpenIndiana box? You can use either Mplayer or Xine with libxine. I am using these applications for years with no problem at all. BTW, http://www.sunfreepacks.com/ includes an MPlayer package.

    Reply
    1. davekoelmeyer Post author

      I agree, and that’s the point I was making in the second paragraph of the post. I use MPlayer as built and supplied by Murray Blakeman at: http://solaris.homeunix.com/.

      I personally see commercial Wine products as best serving the running of applications that are proprietary and *not* cross-platform: indeed, applications like Microsoft Office and Photoshop CS for example are on the list of supported applications for Bordeaux. IMO, if there’s money to be made in commercial Wine products, it’s in paid support for running these proprietary applications on free software OSs, without the additional cost for the end-user of having to pay for an OS license if using a desktop virtualisation application otherwise – not in supporting applications which are already open-source and readily available across multiple platforms.

      On that note, Firefox 3.6.8 is another application on the Bordeaux supported apps list which I’m not seeing a use case for.

      Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s