“translate scheme”

Hi, Valery. The idea behind the XLIFF export/import feature is that you would create the app in your native language, then export it out so you can send the file to a translation company. They will take what you've written (the development language) and translate it into whatever language you're requesting, then give you back another XLIFF file for that language, and you can import that into your project. You wouldn't need to import anything for a language you already have in your project.

I think Interface Builder works fairly well for the most part, mainly when you are not using Autolayout. Autolayout/Size Classes have this goal that you should only do the UI once, and it should work on all devices. That is a good goal, but in practice you have to handle edge cases. For certain layouts, it is required that a 3.5 inch screen has a slightly different layout than larger screens. Interface Builder and size classes do not give you enough control to easily handle this, although it could because you can wire up size class specific constraints. We are encouraged to use size class specific constraints as little as possible (only when you need them). They could have just allowed us to switch and quickly make device specific constraints. I'm hesitant to adopt Autolayout in my apps though. Mainly for the following reasons:1) It isn't obvious when/where you should change constraints for things like orientation changes. You have to be careful that invalidating one constraint doesn't break other constraints

To follow up, I fixed one problem - in the build settings for one of the tests (not the app itself), I had to include a 3 in the targetted device family. But, now it's telling me The run destination Apple TV is not valid for Running the scheme... (followed by the name of my app). Again, this was running just fine the past few days. Anyone know what this could be?

Hi Taxxodium & Nightmare_82,Thanks for this feedback and suggestions. I would highly encourage you to file enhancement requests for these via the bug reporter. This will allow us to better track your requests and stay in contact with you. The more details you elaborate on the better we can provide you the experience you are looking for.Currently there is support for snapping to nodes by holding shift while translating a node, but don’t hesitate to file requests to extend this feature.As for the font panel, what aspects do you find slow? Do you find yourself using the same fonts often? Would a ‘recently used’ list help?Thank you.

Hello Tcatella,Currently there is support for snapping to nodes by holding shift while translating a node, but don’t hesitate to file requests to extend this feature.I didn't know this. Is there any manual for this editor? I never could find one.

I've spent the best part of a day trying to figure this one out too - I finally found the answer buried in the Apple docs: https://developer.apple.com/library/tvos/documentation/MacOSX/Conceptual/BPInternational/TestingYourInternationalApp/TestingYourInternationalApp.html#//apple_ref/doc/uid/10000171i-CH7-SW1TL;DR - edit the Watch App's scheme: Run->Options->Application Language - choose the language you want to test and re-run the watch app.Update: it seems only to work with Xcode 7.2 by the way - when I try the exact same project on Xcode 7.1 it doesn't work for me. Sigh.

The SDK does not provide for arbitrary file selection/picker without iCloud involvement, so you'll need to create your own scheme.

Old school autoresizing masks are translated into auto layout constraints behind the scenes, so there's not much difference really. Autoresizing masks are nowhere near as flexible. But if the layout you need can be accomplished with autoresizing masks there should be no difference to the end user.

I can't see the Radar(s), but I do want to up-vote this as an issue.For many situations, it's critical to know that:The queue is ensuring the seriality of the command buffers that have been submitted to it.Once the last command buffer has invoked its callback, all previously submitted command buffers on the same queue have completed as well, which is important for things like coordinating resource sychronization dispatching, and presentation of the drawable.Because of the uncertainty, we have ended up creating a semi-elaborate scheme of tracking multiple command buffer completion callbacks to determine ordering and finalization activities.Thanks......Bill

Adding '-destination' as a workaround seems to work for me.This worked for me after I added the destination:xcodebuild clean build -workspace ${WORKSPACE} -scheme ${TARGET_NAME} -sdk iphonesimulator ONLY_ACTIVE_ARCH=NO -configuration ${CONFIGURATION} BUILD_DIR=${BUILD_DIR} BUILD_ROOT=${BUILD_ROOT} -destination 'platform=iOS Simulator,name=iPhone 6'

It might be easier to simply avoid basing that app on a SVC and just create a custom orientation layout scheme of your own.