INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Mac => Topic started by: Matt on February 08, 2013, 05:46:59 pm
-
We got the JPEG engine, cover art, and thumbnails working today.
We also made the first release build.
Here's a screenshot:
(http://files.jriver.com/images/2013/apple_progress_01.png)
-
(http://www.pix01.com/gallery/8D12431D-7EA0-495D-9EA2-775091458CB9/Touchdown/3511765570.jpg)
-
Is it my imagination or icons (albums, artists etc) are more separated?
What is the font used?
Congratulations for the work done.
-
This looks great!
-
Is the show gonna start soon?
(http://denverpost.slideshowpro.com/albums/001/496/album-125171/cache/color016.sJPG_950_2000_0_75_0_50_50.sJPG?1281011079)
-
Hurray!!!!
Why is there still VIDEO in the menu if the first release will be without the video features?
-
Sorry i'll stop trying to be funny ... :(
-
Thanks. It was close. It would have been funny on another board, at another time.
-
Why is there still VIDEO in the menu if the first release will be without the video features?
It's our dev copy. It doesn't mean anything.
In the Windows version, you can control what appears there. Tools/Options/General/Features.
-
"Macish" discussion split here:
http://yabb.jriver.com/interact/index.php?topic=78154.0
-
What concerns me about this screenshot is that it so much looks like the Windows version.
As far as I can tell, the font is Tahoma — the default on Windows, while the Mac default is Lucida Grande. A curious choice in that this would make the application fit in worse with the rest of the Mac UX. Though, if this were a WINE port, Lucida Grande wouldn't be accessible, so you couldn't use that. Tahoma, on the other hand, is probably the font in WINE that renders the best, if you also use the (illegal) freetype patch enabling ClearType-like subpixel hinting.
The screenshot has been sized down, which makes it impossible to see if the font rendering engine is indeed native Quartz, or say, that of an X11 used by WINE. Which would mean worse antialiasing that what we're used to. We also can't see the system menu bar to pick out what it says about the running application.
The menus are situated inside the main window, a feat that would have you jump through hoops to implement if you are indeed porting this as a native Mac Cocoa app, where you'd normally just use the menu system provided by the OS/Cocoa — saving boatloads of developer time and making an application that would integrate properly with rest of the OS (e.g. hooking into services and allowing one to control keyboard shortcut to menu mappings). Of course, if it were ported using WINE as a wrapper, the opposite would be true: it would be very hard to get the menus out of the main window and integrate with Mac OS X properly.
The window control buttons are at the right, as in Windows, and sport the same appearance as in Windows. Again, this would be something that would require extra work for the developer to not use the regular ones offered by Cocoa. Yet again, if it were a WINE-based port, getting native Mac window control buttons would probably be close to impossible.
Overall, the GUI widgets look exactly like the skinned Windows ones that we know from the native Windows version. Again a feat that would require much work by a developer to make happen in a native Cocoa app. In WINE, on the other hand, the opposite would again be true.
This looks so much like the early Picasa builds for Mac and Linux, which used WINE as a wrapper for the native Windows application. Doing so has some drawbacks with regards to font rendering, performance, resources usage, multiple display servers, UI responsiveness and general system integration, but it's not necessarily a deal-breaker.
It's just that in the interest of full disclosure, I have to ask this question:
Is this port a native Cocoa one or is it based on WINE or any derivative of WINE? If not Cocoa-based, is it scheduled to become so? And if yes to that question, when?
Thank you,
Daniel
-
It's all original code.
There is a "Macish" thread here on the issues you bring up. You could copy your post there.
We haven't yet given it any cosmetic touches.
-
As far as I can tell, the font is Tahoma — the default on Windows, while the Mac default is Lucida Grande. A curious choice in that this would make the application fit in worse with the rest of the Mac UX. Though, if this were a WINE port, Lucida Grande wouldn't be accessible, so you couldn't use that. Tahoma, on the other hand, is probably the font in WINE that renders the best, if you also use the (illegal) freetype patch enabling ClearType-like subpixel hinting.
Whoa, there's another font/rendering nerd here. I thought I was the only defective one. ;)
Are you speaking of OS X WINE or Linux WINE? I dunno about Linux, but, at least by way of CodeWeavers' Crossover WINE setup, any fonts in OS X, even those managed by font management software, are accessible to WINE.
Micah
-
On my OSX system, Media Center is using the "Lucida Grande" font. This is the default font returned by a call to CTFontCreateWithFontDescriptor with the requested type face left empty.
-
I bet you $10 they switch to Helvetica Nue in 10.9
-
Helvetica Neue ;)
-
Helvetica Neue ;)
I know... Typed it on my phone and didn't have time to fix it.
-
I bet you $10 they switch to Helvetica Nue in 10.9
They probably will, and it will probably suck. ::)
Micah
-
Whoa, there's another font/rendering nerd here. I thought I was the only defective one. ;)
LOL :D Guilty as charged. Looking forward to the day that a version of CSS will properly handle typography, including custom typefaces :)
Are you speaking of OS X WINE or Linux WINE? I dunno about Linux, but, at least by way of CodeWeavers' Crossover WINE setup, any fonts in OS X, even those managed by font management software, are accessible to WINE.
OS X WINE, I guess. At least I haven't been successful here in getting any OS fonts made available to WINE. But it's pretty likely that CodeWeavers have done some magic there. They also included the freetype patch in their CrossOver thing last I checked, I assume by paying royalties to MS :)
-
It's all original code.
By the way, does this mean "yes" or "no" to the question if the Mac port is using WINE or a WINE derivative? I mean, with "original" either meaning "new" or "fresh", or "belonging or pertaining to its origin", your answer could really be either one.
So, yes or no, is the Mac port in any way using WINE or WINE-based or WINE-derived software?
Thank you.
-
It does not use Wine anything or anything else like it.
-
It does not use Wine anything or anything else like it.
Great to hear, thank you.