From: Donal K. F. <don...@ma...> - 2008-04-18 13:56:11
|
Daniel A. Steffen wrote: > can you please hold off on voting on this until my alternate proposal > for an API has been considered? Now that I'm using Leopard, I find your proposals without merit. :-P I've not seen anything that works that way (I discount things like Pages, since WPs have non-standard demands for font control). > The current 213 API is missing several crucial features without which > an Aqua implementation of the chooser will be less than fully > functional. Most importantly there is currently no API for hiding the > font chooser once it has been shown, and no way to tell wether the > font chooser is visible. I know. But there's no way to make those features work with Windows. Luckily, when I try out font choosers in Apple's own applications (e.g. Safari, iTunes, Terminal, Finder) on Leopard, I find that font choosers just stay open until the user closes them anyway. Ergo, they're not needed. > The TIP does not mention those drawbacks or my alternate proposal, in > the past references to such discussion has been added to TIPs so that > TCT members can make an informed vote... What's to say? It makes life much more awkward elsewhere and it doesn't seem to be necessary to work like a MacOS 10.5.2 application. > In fact I have not had any comments on the alternative at all since I > posted it two weeks ago (below), admittedly I have been busy and have > not been pushing back on this since, but it would be a shame to get > stuck with an API that will make the font chooser awkward to use on > OSX just because of a few weeks delay... > > If necessary (with the vote having been called) I can write up my > alternative as a separate TIP... You can write up anything you want as a TIP (provided it's relevant to Tcl/Tk at all, of course). Donal. |