As extraordinary as your app might be in features, content, and technical razzle dazzle, it’s only tapworthy if your users find it convenient, necessary, and easy to use in a mobile context. “Mobile” means on the go, of course, but in the iPhone context it’s helpful to think of its meaning more flexibly as “away from my desk.” Whether you’re on the peak of Kilimanjaro or just curled up on your couch, both are mobile contexts—each with their own opportunities and potential distractions. What mobile context are you designing for? Why would you use this app when you’re away from your desk or computer? Why is it especially convenient to have anytime-anywhere access to this app in your pocket?
Sometimes this is a no-brainer; some apps are naturally mobile because their whole purpose is to be used in the field. Take a gander at iBird Explorer Plus, a sprawling field-guide encyclopedia of birds and bird calls. It’s an app for bird watchers (who) to look up info and birdsongs (what) when peeping at their finefeathered friends in the wild (when and where) to identify a bird or attract one with a bird call (why). This is a niche audience, to be sure, but it’s also a natural mobile app whose value is undeniably tapworthy if you happen to be a birdwatcher in the brush. By wrapping your five W’s tightly around a mobile context, you’ve got the makings of a must-have app for your audience.
iBird is an example of an accessory, an app that augments an activity—a birdwatching expedition in this case—but accessories don’t have to be so explicitly mobile. Other iPhone accessories like a calculator, guitar tuner, or recipe collection are just as useful on your couch or in your kitchen. These, too, are mobile contexts—nontraditional computing environments— where you can craft a convincing set of five W’s for an app to extend and enhance another activity. No matter what the specific setting, consider how your app can take advantage of the size and portability of the iPhone to do something that desktop computers cannot.
duminică, 12 iunie 2011
The Mission of Search Engines
Search engines generate revenue primarily through paid advertising. The great majority of this revenue comes from a pay-per-click (or cost-per-click) model, in which the advertisers pay only for users who click on their ads.
Since web searchers are free to use any of the many available search engines on the Web to find what they are seeking, the burden is on the search engines to develop a relevant, fast, and resh search experience. For the most part, search engines accomplish this by being perceived as having the most relevant results and delivering them the fastest, as users will go to the search engine they think will get them the answers they want in the least amount of time.
As a result, search engines invest a tremendous amount of time, energy, and capital in improving their relevance. This includes performing extensive studies of user responses to their search results, comparing their results against those of other search engines, conducting eyetracking studies (discussed later in this chapter), and conducting PR and marketing campaigns.
Because the search engines’ success depends so greatly on the relevance of their search results, manipulations of search engine rankings that result in non-relevant results (generally referred to as spam) are dealt with very seriously. Each major search engine employs a team of people who focus solely on finding and eliminating spam from their search results. This matters to SEO practitioners because they need to be careful that the tactics they employ will not be seen as spam by the search engines and carry the risk of resulting in penalties for the websites they work on.
Since web searchers are free to use any of the many available search engines on the Web to find what they are seeking, the burden is on the search engines to develop a relevant, fast, and resh search experience. For the most part, search engines accomplish this by being perceived as having the most relevant results and delivering them the fastest, as users will go to the search engine they think will get them the answers they want in the least amount of time.
As a result, search engines invest a tremendous amount of time, energy, and capital in improving their relevance. This includes performing extensive studies of user responses to their search results, comparing their results against those of other search engines, conducting eyetracking studies (discussed later in this chapter), and conducting PR and marketing campaigns.
Because the search engines’ success depends so greatly on the relevance of their search results, manipulations of search engine rankings that result in non-relevant results (generally referred to as spam) are dealt with very seriously. Each major search engine employs a team of people who focus solely on finding and eliminating spam from their search results. This matters to SEO practitioners because they need to be careful that the tactics they employ will not be seen as spam by the search engines and carry the risk of resulting in penalties for the websites they work on.
“IVAN the Ripper”
In 1974, a decade after VLADIMIR IONOSYAN sparked a local panic with the “Mosgas” murders, residents of Moscow circulated rumors of another homicidal maniac at large. According to reports, the slayer was a fair-haired, handsome young man, armed with a cobbler’s bodkin or similar instrument, who trailed his female victims from the city’s ornate subway stations, stabbing them to death in nearby streets and alleys.
Manhunting is doubly difficult in a society that admits no crime problem, but Moscow police indirectly confirmed at least some of the reports. By October 19, extra police and militia patrols were at large, their activity officially explained as preparation for the annual celebration of the Bolshevik revolution on November 7. At the same time, posters bearing sketches of a suspect surfaced in the city’s 17 taxi garages, enlisting cab drivers as lookouts in the search.
By October 21, police confirmed that they were searching for the killer of “a woman.” Inside sources put the body count at seven, with the latest murder five days earlier. An eighth intended victim had survived her wounds, providing homicide investigators with the likeness reproduced in suspect sketches. Five days later, on October 26, authorities reported they were holding a suspect in a series of stabbings who had killed at least 11 Moscow women. The unnamed prisoner had been arrested on the evening of October 24, after three victims were slain in a period of 24 hours.
Police maintained their news blackout as the suspect was shuffled off for psychiatric evaluation, and the disposition of the case remains unknown, but this time he official silence backfired. On the streets, a population starved for solid news fell back on rumor, doubting that the slayer had been captured. “They caught one, but there is a second killer,” one woman confided to a Western journalist. “They still have not caught the main one.” “IVAN the Ripper”
Manhunting is doubly difficult in a society that admits no crime problem, but Moscow police indirectly confirmed at least some of the reports. By October 19, extra police and militia patrols were at large, their activity officially explained as preparation for the annual celebration of the Bolshevik revolution on November 7. At the same time, posters bearing sketches of a suspect surfaced in the city’s 17 taxi garages, enlisting cab drivers as lookouts in the search.
By October 21, police confirmed that they were searching for the killer of “a woman.” Inside sources put the body count at seven, with the latest murder five days earlier. An eighth intended victim had survived her wounds, providing homicide investigators with the likeness reproduced in suspect sketches. Five days later, on October 26, authorities reported they were holding a suspect in a series of stabbings who had killed at least 11 Moscow women. The unnamed prisoner had been arrested on the evening of October 24, after three victims were slain in a period of 24 hours.
Police maintained their news blackout as the suspect was shuffled off for psychiatric evaluation, and the disposition of the case remains unknown, but this time he official silence backfired. On the streets, a population starved for solid news fell back on rumor, doubting that the slayer had been captured. “They caught one, but there is a second killer,” one woman confided to a Western journalist. “They still have not caught the main one.” “IVAN the Ripper”
Microsoft SharePoint 2010 : Permissions
SharePoint permissions fundamentally define two things: who can see things and who can do things. Permissions can be applied at many different levels, but for ease of management, they are usually defined at the site level. Generally, groups are then used to control which users have rights to each site. This makes permissions for the most common collaboration scenarios relatively easy to manage.
Furthermore, many SharePoint sites, lists, and items are configured to use permissions inheritance. This means that many assets in SharePoint don’t have their own permissions applied—they inherit permissions from their parent. This is not only convenient, it is also a SharePoint best practice. While there may be plenty of reasons to define security at the site level, adding security at the list level—or even the item level—can make your permissions management so complicated that you don’t really know who has rights to what.
To modify the permissions on a site, go to Site Actions | Site Settings | Site Permissions to open the Permissions page .Although it is possible to assign permissions to SharePoint items, it is generally not considered to be a good idea. Once you start using permissions other than at the site level, it becomes vastly more difficult to manage and track the permissions of each user.
In SharePoint 2010, there is a new feature called Check Permissions that allows you to go to the settings of a list and quickly see what rights a particular user or group has to the library. To use the feature, go to the library ribbon and click Check Permissions .
After you enter the name of a user or group, the results will show the relevant rights and whether those rights have been granted directly or as a result of group membership .
Furthermore, many SharePoint sites, lists, and items are configured to use permissions inheritance. This means that many assets in SharePoint don’t have their own permissions applied—they inherit permissions from their parent. This is not only convenient, it is also a SharePoint best practice. While there may be plenty of reasons to define security at the site level, adding security at the list level—or even the item level—can make your permissions management so complicated that you don’t really know who has rights to what.
To modify the permissions on a site, go to Site Actions | Site Settings | Site Permissions to open the Permissions page .Although it is possible to assign permissions to SharePoint items, it is generally not considered to be a good idea. Once you start using permissions other than at the site level, it becomes vastly more difficult to manage and track the permissions of each user.
In SharePoint 2010, there is a new feature called Check Permissions that allows you to go to the settings of a list and quickly see what rights a particular user or group has to the library. To use the feature, go to the library ribbon and click Check Permissions .
After you enter the name of a user or group, the results will show the relevant rights and whether those rights have been granted directly or as a result of group membership .
Restore Your iPad’s Settings
Your iPad offers a way to revert to previous settings, so if you’ve made changes to the Home screen and want it to look as it did out of the box, you can reset Home screen icons. You may have also input network settings you’re unhappy with now, and you can reset those easily as well. You can also reset other things, like the Keyboard Dictionary, and even erase all content and all settings.
To reset any of the settings you’ve changed so far, and to reconfigure the settings to work like they did out of the box:
1. Tap Settings.
2. Tap General.
3. At the bottom of the screen, tap Reset.
4. Tap the settings to change. Note that opting to erase all content and settings will remove all of the personal data you’ve added so far, and chances are you don’t want to do that.
5. Click Reset to apply the changes.
So when would you want to erase all of your personal data and settings? When you sell your iPad, of course! You can be sure that new models of iPads will be released, and you may want to trade up. That’s why the iPad offers the option of erasing all content and settings. The next model of the iPad may have a camera, a web cam, or a media card slot. Future models may also support Flash, have a paper-thin slide-out keyboard, or even offer a built-in app for Voice over IP (VOIP) for making Internet-based phone calls. Whatever happens, there will likely come a time when you want to sell your current model and purchase something better. Before you do, you’ll need to restore your iPad to its factory settings.
When you restore the iPad to factory settings, you make it appear brand new again, at least on the inside! After it’s restored, there will be no trace of your email accounts, messages, photos, videos, applications, iBooks, or anything else; it’s returned to the state it was in when you purchased it. You must do this before selling it to erase all of your personal data, and to make it easier for the next person to personalize.
To restore your iPad to factory settings:
1. Click Settings.
2. Click General.
3. At the bottom of the right pane, click Reset.
4. To reset your iPad to factory settings, tap Erase All Content and Settings.
5. Click Erase to verify.
To reset any of the settings you’ve changed so far, and to reconfigure the settings to work like they did out of the box:
1. Tap Settings.
2. Tap General.
3. At the bottom of the screen, tap Reset.
4. Tap the settings to change. Note that opting to erase all content and settings will remove all of the personal data you’ve added so far, and chances are you don’t want to do that.
5. Click Reset to apply the changes.
So when would you want to erase all of your personal data and settings? When you sell your iPad, of course! You can be sure that new models of iPads will be released, and you may want to trade up. That’s why the iPad offers the option of erasing all content and settings. The next model of the iPad may have a camera, a web cam, or a media card slot. Future models may also support Flash, have a paper-thin slide-out keyboard, or even offer a built-in app for Voice over IP (VOIP) for making Internet-based phone calls. Whatever happens, there will likely come a time when you want to sell your current model and purchase something better. Before you do, you’ll need to restore your iPad to its factory settings.
When you restore the iPad to factory settings, you make it appear brand new again, at least on the inside! After it’s restored, there will be no trace of your email accounts, messages, photos, videos, applications, iBooks, or anything else; it’s returned to the state it was in when you purchased it. You must do this before selling it to erase all of your personal data, and to make it easier for the next person to personalize.
To restore your iPad to factory settings:
1. Click Settings.
2. Click General.
3. At the bottom of the right pane, click Reset.
4. To reset your iPad to factory settings, tap Erase All Content and Settings.
5. Click Erase to verify.
Using ADSI
"When will Microsoft ship an Active Directory provider (or cmdlets)?" is a frequently asked question. There's no direct support for working with Active Directory in either PowerShell vl or v2.
WINDOWS SERVER 2008 R2 PowerShell cmdlets for Active Directory are available in Windows Server 2008 R2, along with a huge raft of other PowerShell functionality. PowerShell v2 is installed and enabled by default.
Automating Active Directory is one of the major areas of scripting, judging by the number of scripts available and die questions being asked on newsgroups. So we have a declared need to automate Active Directory work and a new shell that doesn't directly support working with Active Directory what are we going to do? NOTE The discussion in this section is focused on Active Directory, but the same technologies and interfaces are used to access local user and group accounts, as well as work with Active Directory Lightweight Directory Services (ADLDS, formerly known as ADAM).
The COM-based interface ADSI has been used extensively in VBScript to work with Active Directory. As it's COM-based, we can work with it in PowerShell as we've seen. But there's also a .NET wrapper, System.DirectoryServices, that gives .NET access to ADSI. This situation is further complicated in that PowerShell has introduced a type accelerator for System. DirectoryServices called [ADSI] that provides yet another layer of wrapping.
There are third-party tools available for working with Active Detailed background information on ADSI can be found in the SDK
WINDOWS SERVER 2008 R2 PowerShell cmdlets for Active Directory are available in Windows Server 2008 R2, along with a huge raft of other PowerShell functionality. PowerShell v2 is installed and enabled by default.
Automating Active Directory is one of the major areas of scripting, judging by the number of scripts available and die questions being asked on newsgroups. So we have a declared need to automate Active Directory work and a new shell that doesn't directly support working with Active Directory what are we going to do? NOTE The discussion in this section is focused on Active Directory, but the same technologies and interfaces are used to access local user and group accounts, as well as work with Active Directory Lightweight Directory Services (ADLDS, formerly known as ADAM).
The COM-based interface ADSI has been used extensively in VBScript to work with Active Directory. As it's COM-based, we can work with it in PowerShell as we've seen. But there's also a .NET wrapper, System.DirectoryServices, that gives .NET access to ADSI. This situation is further complicated in that PowerShell has introduced a type accelerator for System. DirectoryServices called [ADSI] that provides yet another layer of wrapping.
There are third-party tools available for working with Active Detailed background information on ADSI can be found in the SDK
Using .NET
It's necessary to use .NET code to access certain functionality, but most of what you'll be doing is using tire PowerShell language. .NET enters tire picture because you need to load extra bits and create new objects.
The .NET Framework or just .NET (there are differences but we don't need to worry about drem) is tire way to create applications in the modern Microsoft environment. Microsoft made .NET available in 2002, and new versions have appeared on a regular basis since then. Each new version of .NET tends to be a superset of tire previous version, in that new functionality is added but tire old functionality remains more
or less intact.
.NET VERSIONS PowerShell vl needs .NET 2.0. PowerShell v2 needs .NET 2.0 apart from some features that require .NET 3.5 SP1. Unless you need multiple versions of .NET loaded, j u s t load .NET 3.5 SP 1, as it also contains .NET 2.0. PowerShell is based on .NET, and as we've seen, one of tire major features is that
PowerShell cmdlets output .NET objects rather than text we're used to in more traditional shells. These .NET objects are passed along tire pipeline so they can be used by other cmdlets.
As with any piece of technology, there's a set of terminology we need to master. So we'll start by looking at the terms used when talking about .NET and explain them from an administrator's viewpoint. This is definitely .NET for administrators rather than a full explanation of .NET.
It's possible to access some .NET functionality, such as tire Math functions, directly from PowerShell, not everything is immediately available. We'll learn how to load additional .NET functionality, such as SMO or tire IIS interface, into PowerShell and how to work with it. Our old friend Get-Member will be useful when we start to investigate working with .NET. First, we need to know what we're talking about, so we'll look at .NET terminology.
The .NET Framework or just .NET (there are differences but we don't need to worry about drem) is tire way to create applications in the modern Microsoft environment. Microsoft made .NET available in 2002, and new versions have appeared on a regular basis since then. Each new version of .NET tends to be a superset of tire previous version, in that new functionality is added but tire old functionality remains more
or less intact.
.NET VERSIONS PowerShell vl needs .NET 2.0. PowerShell v2 needs .NET 2.0 apart from some features that require .NET 3.5 SP1. Unless you need multiple versions of .NET loaded, j u s t load .NET 3.5 SP 1, as it also contains .NET 2.0. PowerShell is based on .NET, and as we've seen, one of tire major features is that
PowerShell cmdlets output .NET objects rather than text we're used to in more traditional shells. These .NET objects are passed along tire pipeline so they can be used by other cmdlets.
As with any piece of technology, there's a set of terminology we need to master. So we'll start by looking at the terms used when talking about .NET and explain them from an administrator's viewpoint. This is definitely .NET for administrators rather than a full explanation of .NET.
It's possible to access some .NET functionality, such as tire Math functions, directly from PowerShell, not everything is immediately available. We'll learn how to load additional .NET functionality, such as SMO or tire IIS interface, into PowerShell and how to work with it. Our old friend Get-Member will be useful when we start to investigate working with .NET. First, we need to know what we're talking about, so we'll look at .NET terminology.
Abonați-vă la:
Postări (Atom)