Tryangled Solutions web designing tips tricks

Hi all,

We are sharing the knowledge about the programming and designing  in this community(http://forum.tryangled.com). I am clearing the lot of doubts in this community((http://forum.tryangled.com)).In few months back,I have a lack of knowledge html , css, and php,but I have a knowledge about the this type programming code and style  of programming.Apart from technical skills I learned more here. Nowadays i have written the poem and self motivated activites.If you join this (http://forum.tryangled.com)community, you will get the great friendship and knowledge and i will get the great friends and master. you are great member , friend , and Master of this community.

Welcome to our(http://forum.tryangled.com)community .

To use Flex Automated Testing, you must install Flex Builder 3. You cannot use Flex Automated Testing with only the Flex 3 SDK.

Flex Automated Testing SWC files are installed by default with Flex Builder 3. They are located in the /frameworks/libs directory with the other SWC files. You can begin using Flex Automated Testing and build your own custom agents without any further installation.

To use run-time automated testing (recommended):

Open a command prompt.
Navigate to the flex_builder_root/sdks/3.0.0/templates/automation-runtimeloading-files directory.
Execute the build.bat file. This compiles the runtimeloading.mxml file into a SWF file.
Copy the runtimeloading. swf and RunTimeLoading.html file to your web server. Copy the Flex application that you want to test to this server as well (the application need not be compiled with automation libraries).
Request the RunTimeLoading.html file and pass your Flex application as the automationswfurl query string parameter; for example:
http://localhost/RunTimeLoading.html?automationswfurl=MyApp.swf
To compile your applications with static automation support:

Start Flex Builder.
Create a new Flex Project.
Select your new Flex project in the Navigator.
Select Project > Properties > Flex Compiler.
In the “Additional compiler arguments” field, enter the following:
-include-libraries “flex_builder_dir\sdks\3.0.0\frameworks\libs\automation.swc”
“flex_builder_dir\sdks\3.0.0\frameworks\libs\automation_agent.swc” “flex_builder_dir\sdks\3.0.0\frameworks\libs\qtp.swc”
“flex_builder_dir\sdks\3.0.0\frameworks\libs\automation_dmv.swc”
The -include-libraries compiler option is relative to the Flex Builder installation directory; the default on Windows is “C:\Program Files\Adobe\Flex Builder 3\”.

6. Click the OK button to save your changes and OK to close the project Properties dialog box.
7. Compile your Flex application.
Examples and documentation for using custom agents can be found at Custom Agents.

To use Flex Automated Testing with the Flex 3 Plug-in for Mercury QuickTest Pro, you must perform additional steps. The rest of this section describes how to install and use the Flex 3 Plug-in for Mercury QuickTest Pro.

[edit]Requirements for Using the QTP Plug-in
To test applications with Flex Automated Testing and the QTP agent, you must install the following:

Mercury QuickTest Professional 9.1 or later (no support for Smart Identification)
Mercury QuickTest Professional 9.2 and patch 1701 if you want Smart Identification support
Adobe Flex 3 Plug-in for Mercury QuickTest Pro
Microsoft Internet Explorer, version 6 or later
Flash Player ActiveX control, version 9.0.28.0 or higher
[edit]Installing the Plug-in
This section describes the steps necessary for a QC testing professional to configure QTP to work with Flex applications. You must install QTP and the plug-in.

To install QTP:

Install Flash Player 9 ActiveX control (9.0.28.0 or higher) for Microsoft Internet Explorer. This is currently the only supported browser/player.
Install QTP 9.1 or later if you do not require support for Smart Identification. If you want to use Smart Identification, install QTP 9.2 and patch 1701. You must get QTP 9.1 from Mercury.
If you are using Mercury QTP on Microsoft Windows Vista you need to turn off the User Account Control (UAC) feature. Instructions to turn off UAC are available here
Restart your computer.
To install the Flex 3 Plug-in for Mercury QuickTest Pro:

Run the flex_builder_root/Installers/QTP_Plugin_Installer.exe.
Start QTP.
Close QTP.
In addition to the plug-in’s DLLs and XML files, the plug-in installer includes the following in the installation directory:

/demo — Contains a Flash movie that describes the basics of using the plug-in. Be sure to enable audio on your computer.
/Uninstall Adobe Flex 3 Plug-in for Mercury QuickTest Pro — Contains the uninstaller.
[edit]Using the Plug-in
Start QTP again after installing the plug-in. The Add-in Manager lists the Flex plug-in.
Select the Flex plug-in in the Add-in Manager.
Select New > Test and click the Record button.
NOTE: Flex application testing with QTP currently supports only Microsoft Internet Explorer with the ActiveX Flash Player.

For more information on these tasks and using QTP to test Flex applications, see Testing with QTP.

For information on the operations and properties of Flex objects in QTP, see QTP Object Type Information.

[edit]Samples for Automated Testing
Sample custom agents are available at Custom Automation Agents.

An application ready for testing with QTP can be found at Flexstore AT. This sample can be used to test if the QTP plugin installation was successful.

An example for automating custom components can be found at Automating Custom Component.

[edit]Using automation with the Adobe Flex Component Kit for Flash CS3
You can create Flex controls, containers, skins, and other assets in Flash CS3 Professional, and then import those assets into your Flex application. When you want to automate an application that uses such assets, you must include the automation_flashflexkit.swc library.

If you are using run-time loading, re-compile the runtimeloading.swf file by using the build.bat file in flex_builder_root\sdks\3.0.0\templates\automation-runtimeloading-files\. The batch file includes the necessary libraries.

If you are compiling automation support into your application, add the automation_flashflexkit.swc to your include-libraries compiler option. This is in addition to the other automation SWC files. The SWC files are located in the flex_builder_root\sdks\3.0.0\frameworks\libs directory.

ADVANCED FLEX DATA SERVICES

Adobe Live Cycle Data Services ES provides a comprehensive set of data-enabling features for using data in RIAs. It enables RIAs to talk to back-end data and business logic in a faster, more efficient operating model. Live Cycle Data Services ES also enables seamless integration with Live Cycle ES business processes and document services.

Blaze DS is a free, open source project providing Flex Remoting and Messaging to all developers. Flex Remoting provides a binary, serialized data transport format called Action Message Format (AMF) to provide a fast, efficient means of transporting data to your RIA, which accelerates application performance. Flex Remoting also makes it fast and easy for developers to connect to back-end business logic and data. Flex Messaging adds real-time data push and publish/subscribe, both powerful capabilities now made easy. Using BlazeDS, you can start using these powerful Java server integration features for free, and then subscribe to LiveCycle Data Services, Community Edition for certified builds and support, or upgrade to the full LiveCycle Data Services ES edition for a complete server solution.

* Learn more about LiveCycle Data Services
* Learn more about open source BlazeDS

ADVANCED DATA VISUALIZATION

ILOG Elixir provides graphical data-display components to further enhance Adobe Flex 3 and Adobe AIR rich Internet applications. ILOG Elixir helps turn raw data into clear, actionable information through a highly graphical and interactive user experience. Components include 3D charts, gauges and dials, maps of the world, radar charts, Gantt charts, treemaps, and org charts.

Why is the internet very similar to real-life communities?

The internet surely has some very big similarities with how real life communities function. A website online is very similar to a home. You can furnish your home, put lots of content (decoration) on it, make sure the foundation is coded properly, and that all the pages (rooms) are properly linked together with the rest of the pages (living room and kitchen) on your website.

Another similarity of the online environment with real-life society is the presence of links or neighbors. Your home-website is composed of your own family – a programmer, a writer, a web designer, and all those involved in making that website work. There are plenty of websites online, and some of them are closely related to each other.

These websites often initiate bonds or links with each other in order to grow better in their online community. These websites help promote each other’s content and products; they help share traffic or visitors with one another, and they function to help supplement each other and those people with the same interests with the information they need about a certain subject or category.

These online communities also hold contests and awards for the best websites, much similar to how real-life society creates challenges and gives award to different people or families that have excelled in their particular field. However, the closest similarity to online community competitions is the real-life challenge dubbed the ‘American Idol’.

Online communities also have what is called ‘Online Idols’, which is judged or spearheaded also by three famous judges – Google, Yahoo and MSN. Every once in awhile they give out awards to those websites which have performed well in terms of content quality, number of visits from online audience, and their relationships with other websites online. These websites that perform well are placed on the top ranks of the search results. Google however likes giving an added sweetener to the awards and provide a PR value to range the well-performing websites in an event called the Google Dance.

Those are just some of the most common similarities among online websites and real-life communities. Online websites that have quality links or relationships with other websites of the same category are praised online, and their PR and rank are often very high on the search engines. However, those websites that don’t have quality links or are related with what is commonly referred to as PPC pages or Porn, Pills and Casino related websites, may not fare very well on the search engine results.

It is very important to have quality reciprocal links, especially with an already high PR or quality webpage. If you have an inbound link coming from a PR 7 or 8 or high traffic website, there is a good chance you will get some of the good traffic shared to you by that website. If you build a network of websites ranging from mid to high traffic classifications, you will surely get good exposure online. Authority links coming from high quality websites are very much preferred. If you reciprocate them with your own outgoing link, to help them with traffic, it would still be greatly beneficial for the both of you.

One thing you may have noticed if you have started writing Javascript to use cookies is that there is no actual delete command that can be used to delete a cookie after you have created it. This doesn’t mean that you can’t delete cookies, it just means that you need to understand how cookies work in order to be able to control when the system will delete them for you.

When you create a session cookie it will continue to exist for as long as the browser remains open and will be deleted as soon as the browser is closed. This is because session cookies are actually retained in memory by the browser and are never actually stored anywhere. You do not specify an expiry date when creating a session cookie.

If you want a cookie to last for a longer (or shorter) time than you get wioth a session cookie you need to create a first party cookie instead. With a first party cookie the cookie is actually stored in a file on your visitor’s hard drive. You specify an expiry date/time when creating a first party cookie that defines how long the cookie is to be retained on the hard drive. The cookie isn’t necessarily deleted when that date/time is reached but cookies that have passed their expiry date/’time are ignored and so as far as the browser is concerned they don’t exist.

So how does this help us if we decide that we need to delete a cookie befre the date/time that it is set to expire? Well the solution is quite simple, we change the expiry date of the cookie so that it will be considered to have already expired. Rather than having to remember what to do each time, let’s just create a small function for deleting whichever cookie that we want.

function del_cookie(name) {
document.cookie = name +
‘=; expires=Thu, 01-Jan-70 00:00:01 GMT;’;
}

Now all we need to do is to call this del_cookie() function passing it the name of whatever cookie it is that we wish to delete. The function will update the expiry date on the cookie to one long in the past so that the cookie will be considered to be expired and will be ignored by the browser exactly the same as if it didn’t exist.

Why choose that particular date for setting the expiry date to delete the cookie? Well it just happens that all of the date processing within Javascript sees the 1st January 1970 as its starting date and actually records all date/times internally as the number of milliseconds from midnight on that day. Using that date therefore is effectively equivalent to setting the expiry to zero which means that the cookie will be deleted even if your visitor has the date on their computer set incorrectly. Were we to choose a more recent date it would be possible (although very unlikely) that one of our visitors might have their computer date set incorrectly to one earlier than the exipry that we chose and so our attempt to delete the cookie wouldn’t then work for them.

The most common meaning of “Cookie” on the Internet refers to a piece of information sent by a Web Server to a Web Browser that the Browser software is expected to save and to send back to the Server whenever the browser makes additional requests from the Server. Depending on the type of Cookie used, and the Browsers’ settings, the Browser may accept or not accept the Cookie, and may save the Cookie for either a short time or a long time. Cookies might contain information such as login or registration information, online “shopping cart” information, user preferences, etc. When a Server receives a request from a Browser that includes a Cookie, the Server is able to use the information stored in the Cookie. For example, the Server might customize what is sent back to the user, or keep a log of particular users’ requests. Cookies are usually set to expire after a predetermined amount of time and are usually saved in memory until the Browser software is closed down, at which time they may be saved to disk if their “expire time” has not been reached. Cookies do not read your hard drive and send your life story to the CIA, but they can be used to gather more information about a user than would be possible without them. From Matisse

The main difference between cookies and sessions is that cookies are stored in the user’s browser, and sessions are not. This difference determines what each is best used for.

A cookie can keep information in the user’s browser until deleted. If a person has a login and password, this can be set as a cookie in their browser so they do not have to re-login to your website every time they visit. You can store almost anything in a browser cookie. The trouble is that a user can block cookies or delete them at any time. If, for example, your website’s shopping cart utilized cookies, and a person had their browser set to block them, then they could not shop at your trouble .

Sessions are not reliant on the user allowing a cookie. They work instead like a token allowing access and passing information while the user has their browser open. The problem with sessions is that when you close your browser you also lose the session. So, if you had a site requiring a login, this couldn’t be saved as a session like it could as a cookie, and the user would be forced to re-login every time they visit.

You can of course get the best of both worlds! Once you know what each does, you can use a combination of cookies and sessions to make your site work exactly the way you want it to.

JavaScript is not a programming language in strict sense. Instead, it is a scripting language because it uses the browser to do the dirty work. If you command an image to be replaced by another one, JavaScript tells the browser to go do it. Because the browser actually does the work, you only need to pull some strings by writing some relatively easy lines of code. That’s what makes JavaScript an easy language to start with.

But don’t be fooled by some beginner’s luck: JavaScript can be pretty difficult, too. First of all, despite its simple appearance it is a full fledged programming language: it is possible to write quite complex programs in JavaScript. This is rarely necessary when dealing with web pages, but it is possible. This means that there are some complex programming structures that you’ll only understand after protracted studies.

Secondly, and more importantly, there are the browser differences. Though modern web browsers all support JavaScript, there is no sacred law that says they should support exactly the same JavaScript. A large part of this site is devoted to exploring and explaining these browser differences and finding ways to cope with them.

So basic JavaScript is easy to learn, but when you start writing advanced scripts browser differences (and occasionally syntactic problems) will creep up.

Although the names are much alike, JavaScript is primarily a scripting language for use within HTML pages, while Java is a real programming language that does quite different things from JavaScript. In addition Java is much harder to learn. It was developed by Sun for use in pretty much anything that needs some computing power.

JavaScript was developed by Brendan Eich, then working at Netscape, as a client side scripting language (even though there’s no fundamental reason why it can’t be used in a server side environment).

Originally the language was called Live Script, but when it was about to be released Java had become immensely popular (and slightly hypey). At the last possible moment Netscape changed the name of its scripting language to “JavaScript”. This was done purely for marketing reasons. Worse, Eich was ordered to “make it look like Java”. This has given rise to the idea that JavaScript is a “dumbed-down” version of Java. Unfortunately there’s not the slightest shred of truth in this story.

Java and JavaScript both descend from C and C++, but the languages (or rather, their ancestors) have gone in quite different directions. You can see them as distantly related cousins. Both are object oriented (though this is less important in JavaScript than in many other languages) and they share some syntax, but the differences are more important than the similarities.

If you are a C++ or Java programmer you will be surprised by some of JavaScript’s features. Since I don’t have any previous programming experience, the differences are not described on this site. The best you can do is buy David Flanagan, “JavaScript, the Definitive Guide”, 5th edition, O’Reilly, 2006. In this book the differences between C++/Java and JavaScript are clearly explained. I co–edited a few chapters of this book.

You can use the regular search box to make certain calculations and conversions. Examples: 2+99= will get you 101; 2*2= will get you 4. To run conversions, use the following format: 100 miles = ? km or 100 pounds = ? kilos. Need to convert US dollars into Indian rupees? 1 USD = ? INR.