Inclusion in Google's search results is free and easy; you don't even need to submit your site to Google. Google is a fully automated search engine that uses software known as "spiders" to crawl the web on a regular basis and find sites to add to our index. In fact, the vast majority of sites listed in our results aren't manually submitted for inclusion, but found and added automatically when our spiders crawl the web.

However, if your site offers specialized products, content, or services (for example, video content, local business info, or product listings), you can reach out to the world by distributing it on Google Web Search. For more information, visit Google Content Central.

To determine whether your site is currently included in Google's index, do a site: search for your site's URL. For example, a search for [ site:google.com ] returns the following results: http://www.google.com/search?q=site%3Agoogle.com .

Although Google crawls billions of pages, it's inevitable that some sites will be missed. When our spiders miss a site, it's frequently for one of the following reasons:

* The site isn't well connected through multiple links from other sites on the web.
* The site launched after Google's most recent crawl was completed.
* The design of the site makes it difficult for Google to effectively crawl its content.
* The site was temporarily unavailable when we tried to crawl it or we received an error when we tried to crawl it. You can use Google Webmaster Tools to see if we received errors when trying to crawl your site.

Our intent is to represent the content of the internet fairly and accurately. To help make this goal a reality, we offer guidelines as well as tips for building a crawler-friendly site. While there's no guarantee that our spiders will find a particular site, following these guidelines should increase your site's chances of showing up in our search results.

Consider creating and submitting a detailed Sitemap of your pages. Sitemaps are an easy way for you to submit all your URLs to the Google index and get detailed reports about the visibility of your pages on Google. With Sitemaps, you can automatically keep us informed of all of your current pages and any updates you make to those pages. Please note that submitting a Sitemap doesn't guarantee that all pages of your site will be crawled or included in our search results.

Read more...

Sites' positions in our search results are determined based on a number of factors designed to provide end-users with helpful, accurate search results. These factors are explained in more detail at http://www.google.com/corporate/tech.html.

In general, webmasters can improve the rank of their sites by increasing the number of high-quality sites that link to their pages. For more information about improving your site's visibility in the Google search results, we recommend reviewing our webmaster guidelines. They outline core concepts for maintaining a Google-friendly website.

Read more...

In general, there are two types of sitemaps. The first type of sitemap is a HTML page listing the pages of your site - often by section - and is meant to help users find the information they need. While this type of sitemap can help both visitors and search engines navigate your site, it's different from an XML Sitemap that can be submitted to Google using Webmaster Tools.

XML Sitemaps - usually called Sitemaps, with a capital S - are a way for you to give Google information about your site. This is the type of Sitemap we'll be discussing in this article.

If you've created and verified a site using Google Sites, we've already created a Sitemap for you. All you need do is submit it in the normal way.

If you have a blog with an RSS or Atom feed, you can easily submit that feed as a Sitemap.

Using an RSS / Atom feed as a Sitemap

Google accepts RSS (Real Simple Syndication) 2.0 and Atom 1.0 feeds. If you have a blog with an RSS or Atom feed, you submit the feed's URL as a Sitemap. Most blog software creates your feed for you. If your site doesn't have a feed, you can use Feedburner to create and publish one. Note that the feed may only provide information on recent URLs.

Creating a Sitemap based on a text file
Google accepts RSS (Real Simple Syndication) 2.0 and Atom 1.0 feeds. If you have a blog with an RSS or Atom feed, you submit the feed's URL as a Sitemap. Most blog software creates your feed for you. If your site doesn't have a feed, you can use Feedburner to create and publish one. Note that the feed may only provide information on recent URLs.
Creating a Sitemap based on a text file
back to top

A Sitemap should contain a list of your site's URLs - up to 50,000 of them. If you have a large site with more than 50,000 URLs, you should create multiple Sitemaps and submit a Sitemap index file <>.

You can provide Google with a simple text file that contains one URL per line. For example:

http://www.example.com/file1.html

http://www.example.com/file2.html

For best results, follow these guidelines:

1. You must fully specify URLs as Google attempts to crawl them exactly as provided.
2. Each text file can contain a maximum of 50,000 URLs. If you site includes more than 50,000 URLs, you can separate the list into multiple text files and add each one separately.
3. The text file must use UTF-8 encoding. You can specify this when you save the file (for instance, in Notepad, this is listed in the Encoding menu of the Save As dialog box).
4. The text file should contain no information other than the list of URLs.
5. The text file should contain no header or footer information.
6. You can name the text file anything you wish. Google recommends giving the file a .txt extension to identify it as a text file (for instance, sitemap.txt).

You should upload the text file to your server, generally to the highest-level directory you want search engines to crawl. Once you've created this file, you can submit it as a Sitemap. This process, while manual, is the simplest and is probably best if you're not familiar with scripting or managing your web server.

If you have multiple websites, you can simplify the process of creating and submitting Sitemaps by creating one or more Sitemaps that includes URLs for all your verified sites, and saving the Sitemap(s) to a single location. All sites must be verified in Webmaster Tools

Creating a Sitemap based on the Sitemap protocol
Google can accept Sitemaps in a number of formats, but we recommend creating a Sitemap based on the Sitemap protocol because the same file can be submitted to the other search engines, such as MSN and Yahoo!, that are members of sitemaps.org.

You can create a Sitemap in a number of different ways:

1. Manually create a Sitemap based on the Sitemap protocol
2. Use the Sitemap Generator. If you have access to your webserver and it has Python installed, you can use our script to create a Sitemap that uses the Sitemap protocol. The Google Sitemap Generator is a Python script that creates a Sitemap for your site using the Sitemap Protocol. This script can create Sitemaps from URL lists, web server directories, or from access logs.
3. Use a third-party tool. A number of third parties offer tools you can use to create a valid Sitemap.


Other available formats
In addition to regular Sitemaps, you can also create Sitemaps designed to give Google information about specialized URLs. These include:

* Video Sitemaps
* Mobile Sitemaps
* News Sitemaps
* Code Search Sitemaps

Read more...

in general, there are two types of sitemaps. The first type of sitemap is a HTML page listing the pages of your site - often by section - and is meant to help users find the information they need.

XML Sitemaps - usually called Sitemaps, with a capital S - are a way for you to give Google information about your site. This is the type of Sitemap we'll be discussing in this article.

In its simplest terms, a Sitemap is a list of the pages on your website. Creating and submitting a Sitemap helps make sure that Google knows about all the pages on your site, including URLs that may not be discoverable by Google's normal crawling process.

Sitemaps are particularly helpful if:

* Your site has dynamic content.
* Your site has pages that aren't easily discovered by Googlebot during the crawl process - for example, pages featuring rich AJAX or Flash.
* Your site is new and has few links to it. (Googlebot crawls the web by following links from one page to another, so if your site isn't well linked, it may be hard for us to discover it.)
* Your site has a large archive of content pages that are not well linked to each other, or are not linked at all.

You can also use a Sitemap to provide Google with additional information about your pages, including:

* How often the pages on your site change. For example, you might update your product page daily, but update your About Me page only once every few months.
* The date each page was last modified.
* The relative importance of pages on your site. For example, your home page might have a relative importance of 1.0, category pages have an importance of 0.8, and individual blog entries or product pages have an importance of 0.5. This priority only indicates the importance of a particular URL relative to other URLs on your site, and doesn't impact the ranking of your pages in search results.

Sitemaps provide additional information about your site to Google, complementing our normal methods of crawling the web. We expect they will help us crawl more of your site and in a more timely fashion, but we can't guarantee that URLs from your Sitemap will be added to the Google index. Sites are never penalized for submitting Sitemaps.

Google adheres to Sitemap Protocol 0.9 as defined by sitemaps.org. The Sitemap Protocol is a dialect of XML for summarizing Sitemap information that is relevant to web crawlers. Sitemaps created for Google using Sitemap Protocol 0.9 are therefore compatible with other search engines that adopt the standards of sitemaps.org.

While a standard Sitemap works for most sites, you can also create and submit specialized Sitemaps for certain types of content. These Sitemap formats are specific to Google and are not used by other search engines. Sitemap formats include:

* Video Sitemaps
* Mobile Sitemaps
* News Sitemaps
* Code Search Sitemaps
* Geo Sitemaps

Read more...

This time I will try to create a famous application “hello world”, using prado framework. For the first time you must create the prado project skeleton below your webserver root . If you don’t know how to create it, you can read my article before.

This is my HelloWorld Project skeleton :


I’ve added framework’s folder inside my HelloWorld project. You can find it from original Prado source.
Open the index.php file and change the value of $frameworkPath variable. And direct it to prado.php file inside the framework folder.


This main purpose for this index.php file is load the prado.php file to our project. And this is the first gate for running our application.
Next, go to protected folder and open the application.xml

This application.xml file used for setting your web application, you can add module, setting path, service configuration or add parameter to your application here. But for this example, you can leave for changing the code for this file. The service tag with id=”page” and DefaultPage=”Home”, it show that your application will be open the Home.page file inside the pages folder for the first time.
Now go inside the pages folder and create Home.page file. And create one button by using the TButton class component. Important in every prado .page , there must be have one TForm class component before using other component. This is the code for Home.page :



We have created the view part represented by Home.page file, then for control part we must create the class named Home.php. Because in the Home.page file we are using the TButton component and already have OnClick event named btHelloClicked, in this file we must handle that event by create a function btHelloClicked with $sender and $param as parameter.
*remember prado is a event driven framework, like ASP.Net

Now try to acces your HelloWorld application using your browser :

Read more...

The optional prado-cli.php PHP script file in the framework directory provides command line tools to perform various tedious takes in Prado. The prado-cli.php can be used to create Prado project skeletons, create initial test fixtures, and access to an interactive PHP shell.

Requirements
To use the command line tool, you need to use your command prompt, command console or terminal. In addition, PHP must be able to execute PHP scripts from the command line.
We will use the “php.exe”, be sure you have already installed PHP5 and WebServer (Xampp, Apache2Triad, etc). just for information I’m using Xampp webserver v1.6.
If your OS is Windows, for make it simple when using “php.exe”, go to control panel-system-advanced-environment variables and create new “User Variable = Path” with “value=C:\xampp\php”.


Usage
Open your command prompt, and type php path/to/framework/prado-cli.php, you should see the following information. Alternatively, if you are not on Windows, you may try to change the prado-cli.php into an executable and execute it as a script.


Create the prado project skeletons
Now for example, I want to create the prado project named “HelloWorld” on my computer at this path “E:/Prado1.4/HelloWorld”. And I will do the following :

1. Change to the directory where I want to create the project skeleton “E:/ Prado1.4/”.


2. Copy my prado folder to E:/ Prado1.4/[Prado folder]


3. And I will type :“php E:Prado1.4\prado\framework\prado-cli.php –c HelloWorld”


4. if success I will get this following result
   

Now I will find my HelloWorld prado project folder at below E:Prado1.4/HelloWorld.

Read more...

The minimum requirement by PRADO is that the Web server support PHP 5. PRADO has been tested with Apache Web server on Windows and Linux. Highly possibly it may also run on other platforms with other Web servers, as long as PHP 5 is supported.
Installation of PRADO mainly involves downloading and unpacking.
1. Go to pradosoft.com to grab the latest version of PRADO.
2. Unpack the PRADO release file to a Web-accessible directory.

Your installation of PRADO is done and you can start to play with the demo applications included in the PRADO release via URL http://[web-server-address]/prado/demos/. Here we assume PRADO is unpacked to the prado subdirectory under the DocumentRoot of the Web server.
If you encounter any problems with the demo applications, please use the PRADO requirement checker script, accessible via http://web-server-address/prado/requirements/index.php, to check first if your server configuration fulfills the conditions required by PRADO.

Read more...

this link will show you the comparison between all phpframework.
phpwiki

Read more...

link source : www.pradoframework.com
Strictly speaking, these two are different concepts in PRADO and are inappropriate for comparison. Controls, i.e., components capable of presentation and user interaction, can have templates to help organize their presentation layout. A page is a special kind of control that may be requested directly by end-users, while other controls are managed by a page.

Pages

* must have templates (.page files)
* do not require page classes and default to TPage if none is specified
* allow page classes, but they must extend TPage
o TPage is a subclass of TTemplateControl

Non-page controls

* must have control classes
* may have associated templates (.tpl files) if the control classes extends TTemplateControl

Read more...

link source : www.pradoframework.com
Briefly, when a request comes in, the request passes through a service (usually TPageService), which handles request fulfillment via mmodules (usually THttp* and TPage).

Modules implement the IModule interface. Modules are "behind the scenes" libraries for the application. Among other roles, modules provide the "model" component of the MVC pattern (if MVC is the design pattern in use).

Services implement the IService interface. Services are bridges between the application and the user. Whenever a user sends a request to the PRADO application, it first goes through a service. Most applications rely exclusively on TPageService and don't implement others.

Read more...

link source : www.pradoframework.com
Expression tags run at the PreRender stage, which is before controls like TRepeater run.

Databind tags load their value at every databinding instance (e.g. each time TRepeater loads a data item). Indiscriminate use of Databind tags will work properly but potentially lower application performance

Read more...

link source : www.pradoframework.com

This is really a question of "What properties (including value) should controls have?" relative to a page's lifecycle. PRADO loads control properties in five stages, each overriding the last:

1. Template data.
2. Data set in onInit: This is where you should initialize components. Part of initialization is databinding. For example, on a page containing a listbox of countries, you would want fill it with countries at this stage. TListControl (and all its descendants TDropDownList, TCheckBoxList, etc), TDataGrid, TDataList, and TRepeater should be initialized here.
3. ViewState data.
4. POST data. If your controls haven't been initialized by this point, strange behavior may result.
5. Data set in onLoad: If you want to override the POST values, you must do this here.

If no data affecting controls load in the ViewState and POST stages, onInit and onLoad are functionally equivalent.

Read more...