|
May 01, 2004
Tripping the Light Fantastic
So now that Menu Master 1.1.1 is ready for release (it is a download link, that it is) and will be released sometime next week As promised, work on the massively massive FontCard update will now commence. What do y'all want? The sky is the limit. Screenshots or mockups of what you would like are much appreciated. Email those to my name at unsanity.com (my name is rosyna, the at is an @ and there are no spaces). Of course, those that are first to ask for a feature that does get implemented will get a free license so it is recommended you give a valid email address so you can get what's coming to you. Now, here is another question. First, the set up: some features can only be implemented on Panther and later. Now, the punch line: should the next FC be 10.3 only or should it work on 10.2 as well? There are no major problems with supporting 10.2 still but testing FC under 10.2 is very difficult so we'd need a lot of people still running 10.2.8 to play with it. Trackback Pings: TrackBack URL for this entry: Related:
Comments
i think there were enough programs that had broken functionality without panther that most people would have switched, and that someone who puts high esteem on fonts would be sure to have already switched to panther. path finder, by cocoatech had a period where it worked with both, but with more features if you are using panther. at this point i think that most people will have already switched. Posted by: tbuddy on May 1, 2004 7:30 AM2 things: 1) The first link in your entry has a typo - it has a comma instead of a period. 2) I've never used FontCard so I just looked at the screenshots and those images next to the font names are really jarring. I highly suggest creating new, nice-looking images for that. Posted by: kevin on May 1, 2004 2:21 PMDon't sacrifice features for the sake of 10.2. The main thing I'd actually like to see in FontCard is for it to be faster creating that menu the first time you open it. However, since there doesn't exist a good font management program for OS X, one that can manage a large library and activate/deactivate fonts, that's what I'd sure love to see! Cocoa support, of course, would be most wonderful. Re Fontcard I'd like it to incorporate all of TypeReunion's old tricks. I'd like it to work across Macromedia/Adobe/MS apps without hitches. I'd like to be able to set the font size for individual fonts in the menu as well as the way the name displays, WYSIWYG (on or off) for each font, antialiasing (on or off) for each font. I'd like it to play nice with font managers (I tried everything and have settled on Font Agent Pro as the most robust, but others here use Suitcase & Font Reserve). Most of all I'd like it to work in Photoshop. Speediness with huge font sets and robust fault tolerance would also be appreciated. Posted by: hal on May 4, 2004 12:00 AMHey, ability to shut off WYSIWYG on a per-font basis would be great -- some fonts aren't actually readable, so having their name in the font itself isn't really useful. But I can't think of any way for the program to know this, other than to be told manually. Posted by: Jeremy on May 4, 2004 12:30 PM
Well, I'm sure everyone has their favorites. I couldn't care less about Fruit Menu, but I love FontCard. How about we just let Unsanity update their products as appropriate? :) Posted by: Jeremy on May 6, 2004 8:51 PMActually, I'm all in favor of bugging Unsanity to work on my faves, and not as much, on my non-faves. If fact, as Brian said about a month ago when I'd emailed him and Slava again about Labels X 1.6, "Keep on us though - it motivates us to get it done quicker! :)" So, here's another nudge: Please finish the work on Labels X 1.6 to finally get it working in 10.3. You gave us a teaser screenshot back in December ( http://www.unsanity.org/archives/000296.php ) but have left us hanging ever since; 4+ months and counting... Personally, I can live with the way OS X handles fonts. And if not, there are several other utilities out there already, that can improve the situation (i.e. FontReserve, etc.). And the current version of FontCard is "done" and functional. However, nobody else that I'm aware of, has made any effort to fix OS X's ugly implementation of labels... except Unsanity, with Labels X. But it doesn't... quite... work yet in 10.3, the way it was planned - and previewed for us (bet you're regretting ever posting that screenshot, eh Slava? ;)) So, Unsanity programmers - I'll appeal to your sense of skillz, ego, badassness - whatever: really, how hard could it be to just... finish Labels X? You're up to the challenge, right? Ain't no big thing at all..... right? Please, prove me right. Please finish the job on this poor not-quite-functional orphan of a project (but which will be dearly loved when done) before launching into a major overhaul of another project, which, in its current form, at least works with 10.3 (which is more than we can say about Labels X). All the old Labels X 10.2 stuff w/ the command line tool, and the 'extra, faux' column can just be thrown out, or code-forked into the past - all I care about now, now that Apple has actually finally 'revealed' the hidden actual Labels column in 10.3, is fixing its hideous look and feel. Just take away the color from the item name text, and put it on the item's icon, like in the teaser screenshot (and in OS 9), and I'll be happy. Thanks for reading. This post has also cross-posted in the old, ancient, Labels X thread from last year, so if anyone wants to reply about Labels X, please do so there: http://www.unsanity.org/archives/000296.php Posted by: Ed Mechem on May 7, 2004 11:12 PMLove unsanity and would love an improved font card. I really like the suggestion of being able to set the size/aliasing/etc... Basically the way I imagine it is like an advanced version of the old type reunion (or if anyone remembers the old OS 9 Now Menus that let you control the apple menu) in which you have a window with all the fonts and then you can move things around, group things, set specific attributes at will... If you launched the program after installing new fonts they would simply be listed below organized fonts. Deleted/unavailable fonts simply wouldn't show up (or would show up as greyed out). I also like the idea of being able to have a persistent menu item as an option...even if it didn't do anything but showed you what the fonts looked like. This would be great for photoshop where the font menu isn't wysiwyg. I think this company is going to do something like that: http://www.yousoftware.com/products/fonts.php#screenshots ---------- Suitcase & FontAgentPro support would be the main programs most designers around here use. FontReserve is also popular. ---------- As far as other unsanity programs, a windowshade update would be on the top of my wishlist. I'd like minimized in place winodws to work in expose, and I'd like several longstanding bugs fixed (min in place windows in the background screw up, auto sorting of min in place windows screws up, "dead" corner on the screen for other apps when windowshade is running). Also cool would be if we could have a one window mode where you click on a window and all others minimize... Posted by: raul on May 8, 2004 3:56 AMMy FontCard Wishlist 1. Cocoa support (before FontSight gets Carbon Support :-) ) For me FontCard is more important than WindowShade Posted by: MaX on May 10, 2004 11:39 AM1. FontSight will NEVER work with Carbon. Keep comments on topic. If a comment is unrelated to this post, it may be removed or moderated. |

