Providing Resources You should always externalize application resources such as images and strings from your code, so that you can maintain them independently. You should also provide alternative resources for specific device configurations, by grouping them in specially-named resource directories. At runtime, Android uses the appropriate resource based on the current configuration. For example, you might want to provide a different UI layout depending on the screen size or different strings depending on the language setting. Once you externalize your application resources, you can access them using resource IDs that are generated in your project's R class. Grouping Resource Types You should place each type of resource in a specific subdirectory of your project's res/ directory. MyProject/ src/ MyActivity.java res/ drawable/ icon.png layout/ main.xml info.xml values/ strings.xml Table 1. Caution: Never save resource files directly inside the res/ directory—it will cause a compiler error. Figure 1. Table 2. <?
Authoring HTML & CSS This page lists links to resources on the W3C Internationalization Activity site and elsewhere that help you author HTML and CSS for internationalization. It is one of several techniques pages. You can see a list of updates to this document. You can also raise an issue about this page. You can link to this page and open specific items by using the open parameter in the URL. Hello, L10N It’s always a good practice to extract UI strings from your app code and keep them in an external file. Android makes this easy with a resources directory in each Android project. If you created your project using the Android SDK Tools (read Creating an Android Project), the tools create a res/ directory in the top level of the project. Create Locale Directories and String Files To add support for more languages, create additional values directories inside res/ that include a hyphen and the ISO country code at the end of the directory name. Once you’ve decided on the languages you will support, create the resource subdirectories and string resource files. MyProject/ res/ values/ strings.xml values-es/ strings.xml values-fr/ strings.xml Add the string values for each locale into the appropriate file. At runtime, the Android system uses the appropriate set of string resources based on the locale currently set for the user's device. English (default locale), /values/strings.xml: <? <? <?
GUI Architectures There have been many different ways to organize the code for a rich client system. Here I discuss a selection of those that I feel have been the most influential and introduce how they relate to the patterns. Graphical user interfaces have become a familiar part of our software landscape, both as users and as developers. Looking at it from a design perspective they represent a particular set of problems in system design - problems that have led to a number of different but similar solutions. My interest is identifying common and useful patterns for application developers to use in rich-client development. I've seen various designs in project reviews and also various designs that have been written in a more permanent way. In this essay I want to explore a number of interesting architectures and describe my interpretation of their most interesting features. (There is something of an exception here, in that I did have access to a running Smalltalk-80 to examine MVC. Forms and Controls
Localization Android will run on many devices in many regions. To reach the most users, your application should handle text, audio files, numbers, currency, and graphics in ways appropriate to the locales where your application will be used. This document describes best practices for localizing Android applications. The principles apply whether you are developing your application using ADT with Eclipse, Ant-based tools, or any other IDE. You should already have a working knowledge of Java and be familiar with Android resource loading, the declaration of user interface elements in XML, development considerations such as Activity lifecycle, and general principles of internationalization and localization. It is good practice to use the Android resource framework to separate the localized aspects of your application as much as possible from the core Java functionality: For a short guide to localizing strings in your app, see the training lesson, Supporting Different Languages. Example: Localization Checklist
W3Techs - extensive and reliable web technology surveys How to write in Hindi & other Indian languages on Android Phone | B4Tea.com Advertisement This can be considered as one of the serious flaws of Android makers, that they did not consider most of the Indian languages for the local language support of the Android platform, though Android is selling as much as possible in India. So, I guess, it must feel empty on this part of the Android platform. So, in this article, I shall discuss the ways as to how you can write in any Indian language on your Android handset. Read on for a detailed stepwise discussion. To write in any Indian language, you need to root your handset. Steps to read/write in Indian languages on your Android platform To have the regional keyboards for writing in Indian languages, you may install the corresponding language keyboards directly from the Android market. So, if you haven’t tried reading/writing in Indian languages on your Android handset, then go ahead and explore this wide option available. Source: AndroidAdvices.com Recent Posts in: Tips & Trick
Client-Side vs. Server-Side Rendering Yesterday Twitter announced that it was moving away from client-side rendering back to server-side rendering in order to improve page load time. Today I found myself having to defend my position that server-side rendering will almost always be faster. I figured I'd blog about it. I want to point out a couple things. First, I'm talking specifically about render performance and page speed. How It Works With client-side rendering, your initial request loads the page layout, CSS and JavaScript. With server-side rendering, your initial request loads the page, layout, CSS, JavaScript and content. For subsequent updates to the page, the client-side rendering approach repeats the steps it used to get the initial content. Updates using server-side rendering is where a lot of developers start going off the deep end. In other words, we are still only doing a partial update, but letting the server do the rendering and inserting that finalized output into our DOM. So those are the two workflows.
3.0 Platform API Level: 11 For developers, the Android 3.0 platform (HONEYCOMB) is available as a downloadable component for the Android SDK. The downloadable platform includes an Android library and system image, as well as a set of emulator skins and more. The downloadable platform includes no external libraries. For developers, the Android 3.0 platform is available as a downloadable component for the Android SDK. API Overview The sections below provide a technical overview of what's new for developers in Android 3.0, including new features and changes in the framework API since the previous version. Fragments A fragment is a new framework component that allows you to separate distinct elements of an activity into self-contained modules that define their own UI and lifecycle. You can also use a fragment without providing a UI and instead use the fragment as a worker for the activity, such as to manage the progress of a download that occurs only while the activity is running. Additionally: Action Bar
Bien débuter en référencement naturel (SEO) - Aide Search Console À qui s'adresse ce guide ? Si vous possédez du contenu en ligne, si vous le gérez, le monétisez ou en faites la publicité via la recherche Google, ce guide vous est destiné. Il s'adresse aussi à vous si vous êtes propriétaire d'une entreprise en pleine expansion, propriétaire d'une dizaine de sites, spécialiste du référencement naturel dans une agence Web ou simple amateur qui s'intéresse au SEO et se passionne pour les mécanismes de la recherche. Si vous souhaitez avoir un aperçu complet des rudiments du SEO et de nos bonnes pratiques en la matière, vous êtes au bon endroit. Le référencement naturel (SEO) consiste souvent à apporter de petites modifications à certaines parties de votre site. L'objectif d'un site Web est de répondre aux besoins des utilisateurs, et toute optimisation doit viser à améliorer leur expérience. Premiers pas Êtes-vous présent sur Google ? Déterminer si votre site figure dans l'index Google Si votre site ne figure pas sur Google À éviter : Exemple : ou :
FAQ and Knowledge Base - How do I edit my "hosts" file? Domain Names How do I edit my "hosts" file? Applies to: Grid System Windows Right click the Notepad application and select "Run as Administrator" to edit this system file. Next time you try to go to "www.example.com", your browser will try to find your domain at the corresponding IP instead of looking up the IP through DNS. Mac Open Finder.In the Go menu, select "Go to Folder"Type /etc for the folder name.In the list of files that appears, you should find "hosts. You will need to clear your dns cache or wait for these changes to go into effect. lookupd -flushcache Linux, BSD, and *NIX On unix-based systems, as well as OS X's terminal, you can find the hosts file at /etc/hosts. sudo gedit /etc/hosts Once you have modified your hosts file, you can flush your DNS so that you can see your new changes more quickly. sudo /etc/init.d/nscd restart 333911/10%Last update: 2011-11-01 12:23Author: FAQ AdminRevision: 1.5 The OS 9 TCP/IP Control Panel has a "Select Hosts file" button.