[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-dev] Re: [sc-users] Main.sc and stand-alone application

On 26 Dec 2008, at 09:45, James Harkins wrote:

Moving to dev...

On Fri, Dec 26, 2008 at 12:30 PM, Scott Wilson <s.d.wilson.1@xxxxxxxxxx> wrote:
I knew there was a potential issue with standalones, but hadn't thought best
how to deal with that. Under normal circumstances this would not fail.

This *is* a normal circumstance for Japanese users :)

Building standalones with bleeding edge code should not be normal for anyone. ;-)

In keeping with your other conversation with Eric, I am slightly concerned that this failing might be indicative of something serious that needs attention. Need to think that through, but warnings aren't always enough. The Japanese nib is a minor thing that can be dealt with. I do agree with Eric about overriding things in Common. Just installing a few Quarks gives you so many override warnings that the startup post becomes noise. It often takes me a moment to remember to look at it.

Maybe a resource file with translations for Help, one for each nib.
It's inelegant but in the absence of locale info from the OS, not sure
what else to do.

I'd just hardcode for now. I doubt new nib files will be a regular event.

Another possibility is that the if clause above exits
without fail if the Help menu is not found. Not sure if that's a good idea
or not.

I tend to think it's reasonable to let the sclang layer know that the
primitive failed -- then the sclang code can handle it appropriately
(try/catch or die).

Well, if you think the standalone situation is normal, then it might be normal that 'Help' doesn't exist. IMO that's a separate case though, and easily dealt with by a note in the help.