#info.plist

[taman777]

info.plist が コンフリクトで PhpStorm のアップデートができない

info.plist が コンフリクトで PhpStorm のアップデートができなかった

PhpStormの更新を確認したら…新しいバージョンがあった。

更新…　ん、なんか出てきた

（画像なし） info.plist が なんかで…　ん！？なに！？

some conflicts were found in the installation area

えっと、それで info.plist っていうのがコンフリクト起こしているらしい。

で、解決方法…

一度、PhpStorm をアンインストール して 再インストール

これが一番はやい…ってことで。

アンインストールはこちら

https://pleiades.io/help/phpstorm/uninstall.html?keymap=primary_default_for_macos

インストールはこちら

https://pleiades.io/help/phpst…

View On WordPress

[psinke1974]

Running XCode simulator results in "LaunchServicesError error 0."

Running XCode simulator results in “LaunchServicesError error 0.”

So, one moment you’re app was running fine in the simulator and the next moment you get an error saying  “The operation could not be completed. (LaunchServicesError error 0.)”

Bummer! When you check your logs (see ~/Library/Logs/CoreSimulator/CoreSimulator.log or ~/Library/Logs/CoreSimulator/[Device UDID]/system.log) you’ll find errors like “/.app did not have a CFBundleIdentifier in its…

View On WordPress

[dchakarov]

The file “Info.plist” couldn’t be opened because there is no such file.

After spending insane amount of time trying to debug this dreaded error and trying every suggestion out there - from deleting the Info.plist file and replacing it with an old copy, through copying over some other project's Info.plist file, to the boring deleting and reinstalling Xcode and my Storyboard file - I stumbled on the solution by accident.

Look closely and tell me if you can spot the difference between these two screenshots.

Why on Earth would you allow the user to edit this field by hand and not validate it after? And how is this error message supposed to guide you to solve the issue?

Anyway, now I can finally move on with my life and begin experimenting with iOS9. Staring happily at this:

[nsfail]

Expand Build Settings in Info.plist File Does Not Work for Command Line Tool Targets

Replacing variables with those defined in build settings in a target’s info.plist is supported for most targets, but doesn’t work for command line targets which have an optional info.plist

https://openradar.appspot.com/21961400

[codejong-blog-blog]

Titanium에서 Custom Font 사용하기 (+FontAwesome)

Titanium에서 Custom Font를 사용하는 법은 상당히 간단하다. 특히 FontAwesome 같은 아이콘 폰트 사용하면 이미지 작업 없이도 이쁜 아이콘을 편하고 빠르게 사용가능하다.

1. 폰트파일 설치

font file은 Resource/fonts 파일에 복사한다. Alloy 프로젝트의 경우 app/asset/fonts/ 나 app/lib/fonts에 저장한다. FontAwesome의 경우에는 다운받아서 압축 풀면 나오는 폰트 파일중에 fontawesome-webfont.ttf 파일을 이용하면 된다. 위치가 fonts다 font가 아니다. (이 실수로 삽질을 ㅠㅠ)

2. tiapp.xml 수정 (iOS 인경우만)

iOS 일경우 tiapp.xml 파일에 아래 코드를 수정하면 된다. Titanium Doc Guide 나와있는 info.plist 파일을 복사해서 수정하는 방법 보다 훨씬 간단하다. 참고로 이렇게 추가한경우 프로젝트를 클린하고 다시 빌드해만 확인 할 수 있었다.

<ios> <plist> <dict> <key>UIAppFonts</key> <array> <string>fonts/fontawesome-webfont.ttf</string> </array> </dict> </plist> </ios>

3. 끝. 이제부터 사용가능하다.

바로 사용이 가능하다. 한가지 주의할 점은 아래에 나와있듯이 fontFamily에 들어가는 값이 iOS와 Android의 경우 다르다. iOS는 friendly-name으로 폰트 파일을 열면 상단에 나오는 이름이고, android의 경우는 확장자를 제외한 파일명이다.

/* * Let's say you downloaded the "Spicy Rice" font from Google WebFonts. * You'd have a file named SpicyRice-Regular.ttf in your fonts directory */ var customFont = 'Spicy Rice'; // use the friendly-name on iOS if(Ti.Platform.osname=='android') { // on Android, use the "base name" of the file (name without extension) customFont = 'SpicyRice-Regular'; } var label1 = Titanium.UI.createLabel({ color:'#000', text:'I am Window 1', font:{ fontSize:40, fontFamily: customFont }, textAlign:'center', width:'auto' });

또한 FontAwesome 같은 경우는 "icon-glass": 0xf000와 같이 각 아이콘에 해당하는 string 값을 매번 찾아서 넣기 귀찮은데 k0sukey / TiIconicFont 를 이용하면 아래와 같이 간단히 사용 가능하다.

var fontawesome = require('lib/IconicFont').IconicFont({ font: 'lib/FontAwesome', ligature: false // optional }); var baloonLabel = Ti.UI.createLabel({ top: 20, right: 25, width: Ti.UI.SIZE, height: Ti.UI.SIZE, color: '#000', font: { fontSize: 100, fontFamily: fontawesome.fontfamily() }, text: fontawesome.icon('icon-comment-alt') });

[myti-blog]

Creating a osx app bundle in Java registered to a protocol url

Recently we extended our enterprise search engine bleen adding a desktop utility automatically launched clicking on a result link.

To achieve this we created a native applciation ( for windows and osx ) registered to the protocol url bleen://

In this tutorial we will see how to build this utility in Java for Mac OS X.

The base code is a simple java class displaying a Dialog

Application bundle

Creating a OSX application bundle is as easy as creating a directory structure following some simple rules.

Out directory tree will contain :

a jar with out classes

the dependency jars

the info.plist file

a native executable  

The following is a ant tast that creates the dir tree.

<target name="application-bundle" depends="jar" description="create mac Os X Application bundle"> <mkdir dir="${dist.appbundle}/Contents/MacOS" /> <mkdir dir="${dist.appbundle}/Contents/Resources/Java" /> <copy file="${auxes.dir}/JavaApplicationStub" todir="${dist.appbundle}/Contents/MacOS" /> <exec executable="chmod"> <arg value="755" /> <arg value="${dist.appbundle}/Contents/MacOS/JavaApplicationStub" /> </exec> <copy file="${auxes.dir}/Info.plist" todir="${dist.appbundle}/Contents" /> <copy file="${auxes.dir}/icon.icns" todir="${dist.appbundle}/Contents/Resources" /> <copy file="${dist.dir}/application.jar" todir="${dist.appbundle}/Contents/Resources/Java" /> <copy file="lib/libreria1.jar" todir="${dist.appbundle}/Contents/Resources/Java"/> </target>

The result is a directory tree viewed ad a application document by OSX.

URL protocol

The application runtime information are stored in info.plist file.

We edited this file inserting a couple of new keys. These keys link out app to the protocol demo://

URL Types

URL Identifier

URL Schemes

Now, the system will launch our utility every time the user clicks on a link starting with demo://

To allow osx to know out utility exist we must :

copy the app to /Application directory

or manually launch it at least once 

OpenURL

Now we reached our target but we don’t use the clicked url in our code, yet. 

To use it, we must relay on a system event osx raises to ask applications to manage urls. We use an extension library provided by Apple, registering a handler to the OpenURI event. 

public static void main(final String[] args) { Application.getApplication().setOpenURIHandler( new OpenURIHandler() { @Override public void openURI(final OpenURIEvent pEvent) { JOptionPane.showMessageDialog ( null, pEvent.getURI().toString(), “demo”, JOptionPane.ERROR_MESSAGE); } }); }

Dependencies

Note that our dependencies jar must be located in Contents/Resources/Java and every jar must be declared in Info.plist under the keys Java/Classpath

Download

You can find a demo project download on our public space in Assembla - link

References

Handling URL shemes in Cocoa

JavaApplicationStub

AppleJavaExtensions

MRJAdapter - java library to enhance osx integration

Apple doc - References to the java info.plist keys

Apple doc - References to application bundles creations

Apple javadoc - Javadoc for Apple Java extensions