2012-06-16 20:03:08 +00:00
|
|
|
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
2013-10-30 02:06:15 +00:00
|
|
|
package="com.retroarch"
|
2013-09-23 01:54:28 +00:00
|
|
|
android:versionCode="25"
|
|
|
|
|
android:versionName="0.9.9.7" >
|
2013-10-08 23:51:37 +00:00
|
|
|
<uses-feature android:glEsVersion="0x00020000" />
|
2013-02-01 23:47:11 +00:00
|
|
|
<uses-feature android:name="android.hardware.touchscreen" android:required="false"/>
|
2012-12-06 06:47:52 +00:00
|
|
|
<uses-sdk
|
2013-01-27 10:51:51 +00:00
|
|
|
android:minSdkVersion="9"
|
[Android] Initial huge underlying UI update:
- The UI is now mostly Fragment-centric (finally!)
- The Load Core, Load Game, Load Game (History) are now DialogFragments.
- The directory activities are killed off and consolidated into one fragment named DirectoryFragment.
DirectoryFragment is now a self-contained instantiable DirectoryFragment that can be instantiated anywhere by doing roughly the following.
DirectorFragment dFrag = DirectoryFragment.newInstance(/* Resource ID for a string title here*/);
dFrag.show(getFragmentManager(), "tag");
There are also other methods that were modified within the DirectoryFragment, such as addAllowedExt and disAllowedExt being changed to support a variable amount of arguments. This way, multiple calls of the same function aren't necessary in the case of adding multiple extensions, as well as supporting the case where only one extension is added.
DirectoryFragment also has a new interface added to it called OnDirectoryFragmentClosedListener. Say you have a DirectoryFragment instance, but want to use the selected item's path for something *after* the dialog has closed, with this interface, it is now possible. Just implement this interface within an Activity or Fragment, and then set the DirectoryFragment to use the listener through setOnDirectoryFragmentClosedListener() method.
Now what happens if this isn't set, wouldn't it be pointless to even use a DirectoryFragment in this case?
Not necessarily. What if you only wanted to save the selected item into the applications SharedPreferences?
This is a situation where it would be unnecessary to need that interface. So, to make a DirectoryFragment.java for the sole purpose of saving a selected directory/file path to the SharedPreferences, you would do this:
DirectoryFragment dFrag = DirectoryFragment.newInstance(/* Resource ID to a string title here*/);
dFrag.setPathSettingKey("key to store value in SharedPreferences at");
dFrag.show(getFragmentManager(), "tag");
Outside of these major changes, large portions of the code outside of this were simplified.
2013-11-17 07:37:33 +00:00
|
|
|
android:targetSdkVersion="19" />
|
2012-12-02 19:35:13 +00:00
|
|
|
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
|
2012-12-06 06:47:52 +00:00
|
|
|
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
|
2013-11-17 22:02:06 +00:00
|
|
|
<uses-permission android:name="android.permission.CAMERA"/>
|
2013-12-14 18:25:58 +00:00
|
|
|
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION " />
|
2012-12-06 06:47:52 +00:00
|
|
|
|
2012-06-16 20:03:08 +00:00
|
|
|
<application
|
2012-12-31 11:21:33 +00:00
|
|
|
android:allowBackup="true"
|
2012-06-16 20:03:08 +00:00
|
|
|
android:icon="@drawable/ic_launcher"
|
2013-07-18 11:27:30 +00:00
|
|
|
android:label="@string/app_name"
|
|
|
|
|
android:hasCode="true">
|
2013-10-30 02:06:15 +00:00
|
|
|
<activity android:name="com.retroarch.browser.DisplayRefreshRateTest"/>
|
2013-11-24 21:02:57 +00:00
|
|
|
<activity android:name="com.retroarch.browser.mainmenu.MainMenuActivity" android:exported="true" android:launchMode="singleInstance">
|
2012-06-16 20:03:08 +00:00
|
|
|
<intent-filter>
|
|
|
|
|
<action android:name="android.intent.action.MAIN" />
|
|
|
|
|
<category android:name="android.intent.category.LAUNCHER" />
|
2013-10-14 00:48:08 +00:00
|
|
|
<category android:name="tv.ouya.intent.category.GAME" />
|
2012-06-16 20:03:08 +00:00
|
|
|
</intent-filter>
|
2013-10-15 14:28:02 +00:00
|
|
|
</activity>
|
2013-10-30 02:06:15 +00:00
|
|
|
<activity android:name="com.retroarch.browser.FileWrapper"/>
|
|
|
|
|
<activity android:name="com.retroarch.browser.RetroTVMode"/>
|
2013-10-08 23:50:23 +00:00
|
|
|
|
[Android] Initial huge underlying UI update:
- The UI is now mostly Fragment-centric (finally!)
- The Load Core, Load Game, Load Game (History) are now DialogFragments.
- The directory activities are killed off and consolidated into one fragment named DirectoryFragment.
DirectoryFragment is now a self-contained instantiable DirectoryFragment that can be instantiated anywhere by doing roughly the following.
DirectorFragment dFrag = DirectoryFragment.newInstance(/* Resource ID for a string title here*/);
dFrag.show(getFragmentManager(), "tag");
There are also other methods that were modified within the DirectoryFragment, such as addAllowedExt and disAllowedExt being changed to support a variable amount of arguments. This way, multiple calls of the same function aren't necessary in the case of adding multiple extensions, as well as supporting the case where only one extension is added.
DirectoryFragment also has a new interface added to it called OnDirectoryFragmentClosedListener. Say you have a DirectoryFragment instance, but want to use the selected item's path for something *after* the dialog has closed, with this interface, it is now possible. Just implement this interface within an Activity or Fragment, and then set the DirectoryFragment to use the listener through setOnDirectoryFragmentClosedListener() method.
Now what happens if this isn't set, wouldn't it be pointless to even use a DirectoryFragment in this case?
Not necessarily. What if you only wanted to save the selected item into the applications SharedPreferences?
This is a situation where it would be unnecessary to need that interface. So, to make a DirectoryFragment.java for the sole purpose of saving a selected directory/file path to the SharedPreferences, you would do this:
DirectoryFragment dFrag = DirectoryFragment.newInstance(/* Resource ID to a string title here*/);
dFrag.setPathSettingKey("key to store value in SharedPreferences at");
dFrag.show(getFragmentManager(), "tag");
Outside of these major changes, large portions of the code outside of this were simplified.
2013-11-17 07:37:33 +00:00
|
|
|
<activity android:name="com.retroarch.browser.preferences.PreferenceActivity" android:theme="@style/Theme.AppCompat" />
|
2013-10-30 04:55:41 +00:00
|
|
|
<activity android:name="com.retroarch.browser.coremanager.CoreManagerActivity" android:theme="@style/Theme.AppCompat"/>
|
2013-10-08 23:50:23 +00:00
|
|
|
|
2013-12-10 02:33:43 +00:00
|
|
|
<activity android:name="com.retroarch.browser.RetroActivityFuture" android:exported="true" android:configChanges="mcc|mnc|locale|touchscreen|keyboard|keyboardHidden|navigation|orientation|screenLayout|uiMode|screenSize|smallestScreenSize|fontScale" android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:launchMode="singleInstance">
|
2013-11-29 00:35:56 +00:00
|
|
|
<meta-data android:name="android.app.lib_name" android:value="retroarch-activity" />
|
|
|
|
|
<meta-data android:name="android.app.func_name" android:value="ANativeActivity_onCreate" />
|
|
|
|
|
</activity>
|
2013-12-10 02:33:43 +00:00
|
|
|
<activity android:name="com.retroarch.browser.RetroActivityPast" android:exported="true" android:configChanges="mcc|mnc|locale|touchscreen|keyboard|keyboardHidden|navigation|orientation|screenLayout|uiMode|screenSize|smallestScreenSize|fontScale" android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:launchMode="singleInstance">
|
2013-10-08 23:51:37 +00:00
|
|
|
<meta-data android:name="android.app.lib_name" android:value="retroarch-activity" />
|
|
|
|
|
<meta-data android:name="android.app.func_name" android:value="ANativeActivity_onCreate" />
|
2012-10-14 03:18:53 +00:00
|
|
|
</activity>
|
2012-06-16 20:03:08 +00:00
|
|
|
</application>
|
2013-01-26 16:16:23 +00:00
|
|
|
</manifest>
|