FREE Quality downloadable Ebook @ Laku-Abis » Flex

Essential Techniques for Flex 2 and 3 Developers

FREE EBOOK EXPERT @ LAKU-ABIS — Mon, 14 Jun 2010 09:36:47 +0000

Essential Techniques for Flex 2 and 3 Developers

If you want to learn more about Flex, this is the book for you. It is intended for readers who want to take their knowledge further with quick-fire solutions to common problems and best practice techniques to improve their Flex skills for Rich Internet Application development.
Moreover, this book is also aimed at readers who do not know Flex, but want to learn what they can do with Flex by using real-world examples. Whether you are a Windows, Mac, or Linux developer, this book will work for you. Solutions and examples are intended for all platforms. Throughout the chapters you’ll find detailed information that takes into account the differences between these platforms

Essential Techniques for Flex 2 and 3 Developers

Enterprise Development with Flex

FREE EBOOK EXPERT @ LAKU-ABIS — Sun, 16 May 2010 01:45:05 +0000

Enterprise Development with Flex

Whenever the subject of third-party architectural frameworks is raised at a gathering of Flex developers, the developers are quick to start explaining how they use and like a particular framework. But a simple question like, “Why do you use this framework?” often catches them off guard. Many enterprise developers, especially those who came to Flex after spending some time developing Java EE applications, just know that using
these frameworks is the right thing to do. Is it so?

What are the benefits of using architectural frameworks? This chapter offers some answers as to what you should expect of a framework built on top of the Flex framework. The goal of any well-designed framework is to make the process of software development
and maintenance easier. There are different ways of achieving this goal. Some people prefer working with frameworks that are based on the Model-View-Controller pattern; others like dealing with libraries of components. Each approach has its benefits and costs. In this chapter, you will learn how to build the same application using several frameworks or component libraries used by Flex developers.

download link

The Essential Guide to Flex 3

FREE EBOOK EXPERT @ LAKU-ABIS — Sat, 01 May 2010 07:14:14 +0000

The Essential Guide to Flex 3

can’t believe that we have now reached the second generation of Flex. It seemed like I had just finished the first edition and, within a few weeks, we were in a long and ever-changing series of betas for Flex 3. In the course of that period, many of the chapters you read in this book were rewritten three or four times. Let me begin by thanking the many readers who took the time to write kind reviews for Amazon.com and other places. I read nearly every suggestion and incorporated them into this edition. I cut down a bit on the technical ActionScript explanations and focused on the

features of Flex itself. After years of doing technical training, where I have only a couple of days to cover large topics,

I have learned to substitute shorter, and more pointed, explanations that clarify a concept in place of larger, more technical (and often confusing) explanations. In other words, I often like to get right to the heart of the matter, without taking circuitous routes.

Can’t believe that we have now reached the second generation of Flex. It seemed like I hadjust finished the first edition and, within a few weeks, we were in a long and ever-changingseries of betas for Flex 3. In the course of that period, many of the chapters you read in thisbook were rewritten three or four times.Let me begin by thanking the many readers who took the time to write kind reviews forAmazon.com and other places. I read nearly every suggestion and incorporated them intothis edition. I cut down a bit on the technical ActionScript explanations and focused on thefeatures of Flex itself.

After years of doing technical training, where I have only a couple of days to cover large topics,I have learned to substitute shorter, and more pointed, explanations that clarify a conceptin place of larger, more technical (and often confusing) explanations. In other words, Ioften like to get right to the heart of the matter, without taking circuitous routes.

download link

Learning Flex

FREE EBOOK EXPERT @ LAKU-ABIS — Thu, 22 Apr 2010 09:48:40 +0000

Learning Flex

Flex is the next step in the development of RIAs. The phrase rich Internet applications was coined by Macromedia (now Adobe) in 2002 to account for the trend in more expressive applications on the web. In the beginning, HTML documents on the web were just that, documents. They were text and, later, images and multimedia. This client-server paradigm meant a user, by typing a URL in their browser, would request a document. The web being so far-reaching, savvy folks quickly learned to create server-based applications, programs, which a user could access online. Think of all those forms you’ve filled out, where you type your name and address and hit the submit button. After a few moments, you’re greeted with an entirely new page telling you your form was submitted (or that you had some errors you have to fix first). This was a client-server model, where a “thin” client (a browser) requested content and sent it back to a server for processing. To create dynamic HTML pages, a server had to create the HTML and send it to the client, which would read it like any other page. This took time. Then, with the advent of JavaScript came the power to offload some application workload onto the client. For instance, when configuring an item in an online store, it used to be necessary send all calculations like shipping or sales tax back to the server. With scripting, it was possible to calculate that information right on the client machine and update the layout of the page based on user interaction. Dubbed a “thick” client in contrast to the thin client, a user’s computer needed to be a bit more powerful in order to run the scripts and re-render the page.

Flex is the next step in the development of RIAs. The phrase rich Internetapplications was coined by Macromedia (now Adobe) in 2002 to accountfor the trend in more expressive applications on the web. In the beginning,HTML documents on the web were just that, documents. They were text and,later, images and multimedia. This client-server paradigm meant a user, bytyping a URL in their browser, would request a document. The web being sofar-reaching, savvy folks quickly learned to create server-based applications,programs, which a user could access online. Think of all those forms you’vefilled out, where you type your name and address and hit the submit button.After a few moments, you’re greeted with an entirely new page telling youyour form was submitted (or that you had some errors you have to fix first).This was a client-server model, where a “thin” client (a browser) requestedcontent and sent it back to a server for processing. To create dynamic HTMLpages, a server had to create the HTML and send it to the client, which wouldread it like any other page. This took time.Then, with the advent of JavaScript came the power to offload some applicationworkload onto the client. For instance, when configuring an item in anonline store, it used to be necessary send all calculations like shipping or salestax back to the server. With scripting, it was possible to calculate that informationright on the client machine and update the layout of the page basedon user interaction. Dubbed a “thick” client in contrast to the thin client, auser’s computer needed to be a bit more powerful in order to run the scriptsand re-render the page.

download link

Flex on Java

FREE EBOOK EXPERT @ LAKU-ABIS — Tue, 13 Apr 2010 09:57:44 +0000

Flex on Java

In 1995, Sun introduced the first Java platform and with it birthed the “applet.” The applet allowed Java applications to run inside the browser with rich functionality and all the benefits of the Java framework, including connecting to the server side. The applet became hugely popular for a couple of years but then its popularity waned. The applet adoption rate dropped mainly because of problems surrounding the browser plugin. Building features in an applet from scratch or even other rich implementations can be expensive compared to the
simplicity of using the Flex framework.

download link