السعر | البرنامج مجانى |
النظام | Windows 10/8/7/Vista/XP |
الموقع الرسمى | Game Maker |
حجم البرنامج | m12.12 |
If you’re an indie game developer, you know that games are a powerful medium of
expression of art, whimsy, and delight. Being on Google Play can help you reach
over a billion users and build a successful, global business. That’s why we
recently introduced programs, like the href="https://play.google.com/store/info/topic?id=topic_b000054_games_indie_corner_tp&e=-EnableAppDetailsPageRedesign">Indie
Corner, to help more gamers discover your works of art.
To further celebrate and showcase the passion and innovation of indie game
developers, we’re hosting the Google Play Indie Games Festival at the href="https://www.google.com/maps/place/Terra+Gallery+%26+Event+Venue/@37.785531,-122.3929643,15z/data=!4m5!3m4!1s0x0:0xf5fb5bcb9c7795ab!8m2!3d37.785531!4d-122.3929643">Terra
Gallery in San Francisco, on September 24.
This is a great opportunity for you to showcase your indie title to the public,
increase your network, and compete to win great prizes, such as Tango devices,
free tickets for Google I/O 2017, and Google ad campaign support. Admission will
be free and players will get the chance to play and vote on their favorites.
If you’re interested in showcasing your game, we’re href="https://docs.google.com/a/google.com/forms/d/e/1FAIpQLSduaM998L0WXm_4znsZjHX5-unZLBChNXHuCHbTlWuAcmMNmQ/viewform">accepting
submissions now through August 14. We’ll then select high-quality games that
are both innovative and fun for the festival. Submissions are open to US and
Canadian developers with 15 or less full time staff. Only games published on or
after January 1, 2016 or those to be published by December 31, 2016 are
eligible. See href="https://docs.google.com/a/google.com/forms/d/e/1FAIpQLSduaM998L0WXm_4znsZjHX5-unZLBChNXHuCHbTlWuAcmMNmQ/viewform">complete
rules.
We encourage virtual reality and augmented reality game submissions that use the
Google VR SDK and the href="https://store.google.com/product/tango_tablet_development_kit?srp=/product/project_tango_tablet_development_kit">Tango
Tablet Development Kit.
At the end of August, we’ll announce the group of indies to be featured at the
festival.
You can learn more about the event href="https://events.withgoogle.com/google-play-indie-game-festival/">here.
We can’t wait to see what innovative and fun experiences you share with us!
السعر | البرنامج مجانى |
النظام | Windows 10/8/7/Vista/XP |
الموقع الرسمى | eMule Plus |
حجم البرنامج | يتغير باختلاف النظام |
Posted by Hoi Lam, Android Wear
Developer Advocate
At Google I/O 2016, we launched the Android
Wear 2.0 Developer Preview, which gives developers early access to the next
major release of Android Wear. Since I/O, feedback from the developer community
has helped us identify bugs and shape our product direction. Thank you!
Today, we are releasing the second developer preview with new functionalities
and bug fixes. Prior to the consumer release, we plan to release additional
updates, so please send us your
feedback early and often. Please keep in mind that this preview is a work in
progress, and is not yet intended for daily use.
compileSdkVersion
to API 24, and we recommendtargetSdkVersion
to API 24.WearableActionDrawer
’s peek view. For developers that want to makepeek_view
anddrawer_content
attributes to WearableDrawerView
. Andhref="https://developer.android.com/reference/android/widget/ArrayAdapter.html?utm_campaign=android wear_launch_preview2_071216&utm_source=anddev&utm_medium=blog#notifyDataSetChanged()">notifyDataSetChanged
. public class MainActivity extends Activity {
...
@Override /* KeyEvent.Callback */
public boolean onKeyDown(int keyCode, KeyEvent event) {
switch (keyCode) {
case KeyEvent.KEYCODE_NAVIGATE_NEXT:
Log.d(TAG, "Next");
break;
case KeyEvent.KEYCODE_NAVIGATE_PREVIOUS:
Log.d(TAG, "Previous");
break;
}
// If you did not handle, then let it be handled by the next possible element as deemed by
// Activity.
return super.onKeyDown(keyCode, event);
}
}
The Android Wear 2.0 Developer Preview includes an updated SDK with tools and
system images for testing on the official Android emulator, the href="https://store.google.com/product/lg_watch_urbane_2nd_edition_lte">LG Watch
Urbane 2nd Edition LTE, and the href="https://store.google.com/product/huawei_watch">Huawei Watch.
To get started, follow these steps:
We will update this developer preview over the next few months based on your
feedback. The sooner we hear from you, the more we can include in the final
release, so don't be shy!
Posted by Chad Brubaker, Android Security team
In Android Nougat, we’ve changed how Android handles trusted certificate
authorities (CAs) to provide safer defaults for secure app traffic. Most apps
and users should not be affected by these changes or need to take any action.
The changes include:
For more details on these changes and what to do if you’re affected by them,
read on.
Apps have always been able customize which certificate authorities they trust.
However, we saw apps making mistakes due to the complexities of the Java TLS
APIs. To address this we href="https://developer.android.com/preview/features/security-config.html">improved
the APIs for customizing trust.
Protection of all application data is a key goal of the Android application
sandbox. Android Nougat changes how applications interact with user- and
admin-supplied CAs. By default, apps that target API level 24 will—by design—not
honor such CAs unless the app explicitly opts in. This safe-by-default setting
reduces application attack surface and encourages consistent handling of network
and file-based application data.
Customizing the CAs your app trusts on Android Nougat is easy using the Network
Security Config. Trust can be specified across the whole app or only for
connections to certain domains, as needed. Below are some examples for trusting
a custom or user-added CA, in addition to the system CAs. For more examples and
details, see href="https://developer.android.com/preview/features/security-config.html">the
full documentation.
To allow your app to trust custom CAs only for local debugging, include
something like this in your Network Security Config. The CAs will only be
trusted while your app is marked as debuggable.
To allow your app to trust custom CAs for a specific domain, include something
like this in your Network Security Config.
internal.example.com
To allow your app to trust user-added CAs for multiple domains, include
something like this in your Network Security Config.
userCaDomain.com
otherUserCaDomain.com
To allow your app to trust user-added CAs for all domains, except for those
specified, include something like this in your Network Security Config.
sensitive.example.com
To allow your app to trust user-added CAs for all secure connections, add this
in your Network Security Config.
To provide a more consistent and more secure experience across the Android
ecosystem, beginning with Android Nougat, compatible devices trust only the
standardized system CAs maintained in href="https://android.googlesource.com/platform/system/ca-certificates/">AOSP.
Previously, the set of preinstalled CAs bundled with the system could vary from
device to device. This could lead to compatibility issues when some devices did
not include CAs that apps needed for connections as well as potential security
issues if CAs that did not meet our security requirements were included on some
devices.
First, be sure that your CA needs to be included in the system. The preinstalled
CAs are only for CAs that meet our security requirements
because they affect the secure connections of most apps on the device. If you
need to add a CA for connecting to hosts that use that CA, you should instead
customize your apps and services that connect to those hosts. For more
information, see the Customizing trusted CAs section above.
If you operate a CA that you believe should be included in Android, first
complete the Mozilla CA
Inclusion Process and then file a href="https://code.google.com/p/android/issues/entry">feature request
against Android to have the CA added to the standardized set of system CAs.