A RECIPE FOR REAL LOVE

For many of us around the world, Valentine's Day is almost here. Over the years, Valentine's Day has evolved into that one special day for focusing on the love we have in our lives and expressing this love usually in the form of beautiful words, cards and all manner of gifts. It has occurred to me that:

This celebration of love needs to be, not a one day event, (one day is definitely not enough!!!), but a year-round event.

And for "Real Love" to really occur, certain ingredients are required.

First, what is Real Love? Too many of us have no idea. For example, there is the myth of "love at first sight". Let's look at it logically: How can you love someone when you don't even know them? That "stranger across a crowded room" could be someone you should definitely avoid.

I have come to call this kind of love "Enchanted Love". Indeed, enchantment can be defined as "a spell that comes over us." And that's exactly what seems to happen when we experience love at first sight. It is mystical, exciting, passionate and delicious ...BUT... it is not Real Love. Ultimately the spell wears off, our humanness reveals itself, and questions arise as to whether this is really the person we want to have in our lives. It is at this time that many decide to end the relationship. Others decide it is worth the effort to move forward. It is only then that the journey to Real Love truly can begin. And sometimes Real Love surprisingly happens to a couple who had no romantic interest in each other in the beginning. As time passes and the inner beauty of each party is revealed to each other, a romantic interest is spurred and again the journey to Real Love begins.

Here is list of this wonderful recipe:

VALIDATION: Real Love can't exist in an environment of negative judgment and putdowns. Nothing feeds a feeling of love more than making our mate feel good about him or herself.

RESPONSIBILITY: Real Love can't exist when we blame our mate for our unhappiness. My favorite tool for moving into Real Love is to pick up the mirror instead of the magnifying glass. When we pick up the magnifying glass, we are into blame. A sad and powerless choice. When we pick up the mirror, we are filled with self-awareness which gives us the power to change what isn't working. As a result our resentment and anger disappear, and love is allowed to thrive. That's powerful!

APPRECIATION: Real Love can't exist in the absence of "thank you's". First we have to notice the gifts our mate brings into our lives instead of focusing on the negatives. (Why would we want to fill our heads with negativity instead of a feeling of abundance?) Then after noticing, we have to express our thanks. What a warm and wonderful feeling for both parties when thanks are expressed!

A RESPECT BASED ON THE HUMANNESS OF OUR PARTNERS: Real Love can't exist with fairy-tale expectations. As I already explained, it is when the original feeling of "Enchanted Love" (which isn't Real Love) disappears that the journey to Real Love begins. And as we train ourselves to focus on what I call our "Higher Purpose" in a relationship...that of becoming a more loving person...we are able to push through our negative habits and emerge as strong and caring human beings. In this way, step-by-step, our love can grow...and grow...and grow.

COMMITMENT: Real Love can't exist when one foot is out the door. When we are in a relationship, we should be there 100%. This doesn't mean you have to stay there forever if circumstances tell you it is time to leave, but while you are there...give it everything you've got.

AN OPEN HEART: Real Love can't exist when we shut the door to the beauty that lies within our own being...and that of our mates. Fear often causes us to close our hearts. We need to learn how to push through the fear, knowing that we can handle whatever happens. Say to yourself over and over again, "Whatever happens, I'll handle it." When we have this important knowing, we become "safely vulnerable" allowing our hearts to open.

ALONE-TIME TOGETHER: Real Love requires sacred time to focus on and appreciate the beauty of each other. Life too often steps in and interferes with the couple-closeness needed for love to flourish. Two big barriers to couple-closeness are children and work. We have to get very creative and find our way to beautiful moments alone together.

COMMUNICATION: Real Love requires that we connect from a place of sharing, caring and learning. Again, it isn't about blame...it is about learning how to ask for what we need in a loving way and learning how to better understand the needs of our mate. Only from understanding can constructive actions take place.

KINDNESS: Real Love can't exist when we are oblivious to the pain we are causing our mate. Too often we say we love our mate, but we don't treat him or her very lovingly. We need to treat our mate as our best friend, and ultimately that's what he or she can become.

CELEBRATION: Real Love can't exist when we take the blessings of our union for granted. Celebrate daily the beauty our mate brings into our life. A simple toast at dinner that says, "Thank you and I love you" reminds us of the sublime gift that our partner brings into our lives.

There you have it...just a taste of what I consider to be the main ingredients of Real Love. I might add that while these components may seem an obvious requirement for a healthy and fulfilling love,it is amazing how many of us don't see or act on what is obvious. Many of these components are absent from the lives of many couples who claim to love one another. Little do they know that, without these ingredients being integrated into their relationship, their love will suffer greatly.

I have at times heard the erroneous concept that you shouldn't have to work on love. "If you have to work on it, it isn't Real Love." I disagree. The reality is that we are all human beings who are very often run by the weakest and most insecure part of who we are - our Lower Self. Our goal in a relationship is to learn how to rise to the most powerful and loving part of who we are - our Higher Self. This takes time; it takes focus; it takes an open mind; and, most importantly, it takes an understanding of what loving another person really means. If this understanding isn't there, very often the relationship breaks down.

You can see that a diet of Real Love is a nourishing gift we give to ourselves and to our mate. And because we are all human, we won't always get it right. As situations change in our lives, we have to keep fine-tuning. But as we focus on our Higher Purpose, that of becoming a more loving person, we begin to understand the joy, satisfaction, peace and caring that Real Love can bring. Heaven!

Happy Valentine's Day!

Adapted from The Feel the Fear Guide to Lasting Love (Susan Jeffers)

AJAX: a new approach to web development

If anything about current interaction design can be called “glamorous,” it’s creating Web applications. After all, when was the last time you heard someone rave about the interaction design of a product that wasn’t on the Web? (Okay, besides the iPod.) All the cool, innovative new projects are online.

Despite this, Web interaction designers can’t help but feel a little envious of our colleagues who create desktop software. Desktop applications have a richness and responsiveness that has seemed out of reach on the Web. The same simplicity that enabled the Web’s rapid proliferation also creates a gap between the experiences we can provide and the experiences users can get from a desktop application.

That gap is closing. Take a look at Google Suggest. Watch the way the suggested terms update as you type, almost instantly. Now look at Google Maps. Zoom in. Use your cursor to grab the map and scroll around a bit. Again, everything happens almost instantly, with no waiting for pages to reload.

Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web.

DEFINING AJAX

Ajax isn’t a technology. It’s really several technologies, each flourishing in its own right, coming together in powerful new ways. Ajax incorporates:

• standards-based presentation using XHTML and CSS;
• dynamic display and interaction using the Document Object Model;
• data interchange and manipulation using XML and XSLT;
• asynchronous data retrieval using XMLHttpRequest;
• and JavaScript binding everything together.

The classic web application model works like this: Most user actions in the interface trigger an HTTP request back to a web server. The server does some processing — retrieving data, crunching numbers, talking to various legacy systems — and then returns an HTML page to the client. It’s a model adapted from the Web’s original use as a hypertext medium, but as fans of The Elements of User Experienceknow, what makes the Web good for hypertext doesn’t necessarily make it good for software applications.

Figure 1: The traditional model for web applications (left) compared to the Ajax model (right).

This approach makes a lot of technical sense, but it doesn’t make for a great user experience. While the server is doing its thing, what’s the user doing? That’s right, waiting. And at every step in a task, the user waits some more.

Obviously, if we were designing the Web from scratch for applications, we wouldn’t make users wait around. Once an interface is loaded, why should the user interaction come to a halt every time the application needs something from the server? In fact, why should the user see the application go to the server at all?

HOW AJAX IS DIFFERENT

An Ajax application eliminates the start-stop-start-stop nature of interaction on the Web by introducing an intermediary — an Ajax engine — between the user and the server. It seems like adding a layer to the application would make it less responsive, but the opposite is true.

Instead of loading a webpage, at the start of the session, the browser loads an Ajax engine — written in JavaScript and usually tucked away in a hidden frame. This engine is responsible for both rendering the interface the user sees and communicating with the server on the user’s behalf. The Ajax engine allows the user’s interaction with the application to happen asynchronously — independent of communication with the server. So the user is never staring at a blank browser window and an hourglass icon, waiting around for the server to do something.

Figure 2: The synchronous interaction pattern of a traditional web application (top) compared with the asynchronous pattern of an Ajax application (bottom).

Every user action that normally would generate an HTTP request takes the form of a JavaScript call to the Ajax engine instead. Any response to a user action that doesn’t require a trip back to the server — such as simple data validation, editing data in memory, and even some navigation — the engine handles on its own. If the engine needs something from the server in order to respond — if it’s submitting data for processing, loading additional interface code, or retrieving new data — the engine makes those requests asynchronously, usually using XML, without stalling a user’s interaction with the application.

WHO’S USING AJAX

Google is making a huge investment in developing the Ajax approach. All of the major products Google has introduced over the last year — Orkut, Gmail, the latest beta version of Google Groups,Google Suggest, and Google Maps — are Ajax applications. (For more on the technical nuts and bolts of these Ajax implementations, check out these excellent analyses of Gmail, Google Suggest, and Google Maps.) Others are following suit: many of the features that people love in Flickr depend on Ajax, and Amazon’s A9.com search engine applies similar techniques.

These projects demonstrate that Ajax is not only technically sound, but also practical for real-world applications. This isn’t another technology that only works in a laboratory. And Ajax applications can be any size, from the very simple, single-function Google Suggest to the very complex and sophisticated Google Maps.

At Adaptive Path, we’ve been doing our own work with Ajax over the last several months, and we’re realizing we’ve only scratched the surface of the rich interaction and responsiveness that Ajax applications can provide. Ajax is an important development for Web applications, and its importance is only going to grow. And because there are so many developers out there who already know how to use these technologies, we expect to see many more organizations following Google’s lead in reaping the competitive advantage Ajax provides.

MOVING FORWARD

The biggest challenges in creating Ajax applications are not technical. The core Ajax technologies are mature, stable, and well understood. Instead, the challenges are for the designers of these applications: to forget what we think we know about the limitations of the Web, and begin to imagine a wider, richer range of possibilities.

It’s going to be fun.

---

AJAX Q&A

Q. Did Adaptive Path invent Ajax? Did Google? Did Adaptive Path help build Google’s Ajax applications?

A. Neither Adaptive Path nor Google invented Ajax. Google’s recent products are simply the highest-profile examples of Ajax applications. Adaptive Path was not involved in the development of Google’s Ajax applications, but we have been doing Ajax work for some of our other clients.

Q. Is Adaptive Path selling Ajax components or trademarking the name? Where can I download it?

A. Ajax isn’t something you can download. It’s an approach — a way of thinking about the architecture of web applications using certain technologies. Neither the Ajax name nor the approach are proprietary to Adaptive Path.

Q. Is Ajax just another name for XMLHttpRequest?

A. No. XMLHttpRequest is only part of the Ajax equation. XMLHttpRequest is the technical component that makes the asynchronous server communication possible; Ajax is our name for the overall approach described in the article, which relies not only on XMLHttpRequest, but on CSS, DOM, and other technologies.

Q. Why did you feel the need to give this a name?

A. I needed something shorter than “Asynchronous JavaScript+CSS+DOM+XMLHttpRequest” to use when discussing this approach with clients.

Q. Techniques for asynchronous server communication have been around for years. What makes Ajax a “new” approach?

A. What’s new is the prominent use of these techniques in real-world applications to change the fundamental interaction model of the Web. Ajax is taking hold now because these technologies and the industry’s understanding of how to deploy them most effectively have taken time to develop.

Q. Is Ajax a technology platform or is it an architectural style?

A. It’s both. Ajax is a set of technologies being used together in a particular way.

Q. What kinds of applications is Ajax best suited for?

A. We don’t know yet. Because this is a relatively new approach, our understanding of where Ajax can best be applied is still in its infancy. Sometimes the traditional web application model is the most appropriate solution to a problem.

Q. Does this mean Adaptive Path is anti-Flash?

A. Not at all. Macromedia is an Adaptive Path client, and we’ve long been supporters of Flash technology. As Ajax matures, we expect that sometimes Ajax will be the better solution to a particular problem, and sometimes Flash will be the better solution. We’re also interested in exploring ways the technologies can be mixed (as in the case of Flickr, which uses both).

Q. Does Ajax have significant accessibility or browser compatibility limitations? Do Ajax applications break the back button? Is Ajax compatible with REST? Are there security considerations with Ajax development? Can Ajax applications be made to work for users who have JavaScript turned off?

A. The answer to all of these questions is “maybe”. Many developers are already working on ways to address these concerns. We think there’s more work to be done to determine all the limitations of Ajax, and we expect the Ajax development community to uncover more issues like these along the way.

Q. Some of the Google examples you cite don’t use XML at all. Do I have to use XML and/or XSLT in an Ajax application?

A. No. XML is the most fully-developed means of getting data in and out of an Ajax client, but there’s no reason you couldn’t accomplish the same effects using a technology like JavaScript Object Notationor any similar means of structuring data for interchange.

Q. Are Ajax applications easier to develop than traditional web applications?

A. Not necessarily. Ajax applications inevitably involve running complex JavaScript code on the client. Making that complex code efficient and bug-free is not a task to be taken lightly, and better development tools and frameworks will be needed to help us meet that challenge.

Q. Do Ajax applications always deliver a better experience than traditional web applications?

A. Not necessarily. Ajax gives interaction designers more flexibility. However, the more power we have, the more caution we must use in exercising it. We must be careful to use Ajax to enhance the user experience of our applications, not degrade it.

Jesse James Garrett is the Director of User Experience Strategy and a founder of Adaptive Path. He is the author of the widely-referenced book The Elements of User Experience. Jesse’s other essays includeThe Nine Pillars of Successful Web Teams and Six Design Lessons From the Apple Store.

Form:http://www.adaptivepath.com/publications/essays/archives/000385.php

How to post to twitter using Command line in windows

Well i found this post interesting :-)

By now, just about everyone knows about the Twitter Command Line Client for Linux. Ever since I started using it, I fell in love and I’ve been looking for something similar for Windows. Well, I’ve finally found it: The Twitter CLI is a simple tool that lets you post updates toTwitter from the Windows Command Line or, my favorite, the Run dialog.

Download

The small file is located at Phalacee.com (local mirror).

Installation

1. Extract the contents of the Twitter CLI.zip file into your Windows folder, which is located at:
   C:\Windows
2. Open the Twitter.bat file in Notepad (right-click, then choose Edit) and enter your Twitter user name and password in the appropriate fields:
   set username=YourTwitterUserName
set password=YourTwitterPassword
3. Save the file and close Notepad.

Update Twitter Via Command Line

Now you are able to Tweet via your Windows Command Line:

1. Hit the Windows Key+R
2. Type in the following:
   twitter ""
   Enter your status between the quotes.
3. Hit OK or the Enter on your keyboard.

That’s all there is to it! If you want your update to read: I’m eating over my keyboard and making a mess! You would enter:
twitter "I'm eating over my keyboard and making a mess!"

Notes

• The message must be less than 140 characters, which is Twitter’s limit.
• It’s not necessary to use quotation marks in your update but will be needed if you’re inputting a URL in your message:
  twitter "I just added a great picture to Flickr http://tinyurl.com/6r95ur"

Get Started with the GWT SDK

This is about the getting started with GWT SDK and setting up the working environment for eclipse and command line tool.(It is for windows)

What are the things you need to get started with GWT.

1. You will need the Java SDK version 1.5 or later. If necessary, download and install the Java SE Development Kit (JDK) for your platform.

2. Apache Ant is also necessary to run command line arguments. If you don't already have it, install Apache Ant.

From here after i am assuming that you have downloaded and installed JDK and also you have downloaded Apache ant.

Steps

1. Extract Apache ant to C drive.

2. Rename it as "ant".

3. Set ANT_HOME environment variable

To set it follow the steps

My Computer -> Advanced System Properties -> Environment Variable.

Now on the system variable click on New to add a new Environment Variable.

variable_name="ANT_HOME"

value="C:\ant"

4. Update Path environment variable. e.g.(oldpath;%ANT_HOME%/bin;)

To update it in the environment variable window click on path and put ";" at the end of all the path and then put "%ANT_HOME%/bin" at the end.

Now test ant is installed.

How to set install GWT SDK?

Download and unzip the Google Web Toolkit SDK. This contains the core libraries, compiler, and development server that you need to write web applications.

On Windows, extract the files from the compressed folder gwt-2.0.3.zip

The GWT SDK doesn't have an installer application. All the files you need to run and use the SDK are located in the extracted directory.

How to set up Eclipse IDE?

If you do not already have Eclipse, you may download it from the Eclipse Website.I suggest downloading Eclipse 3.5 (Galileo).

The Google Plugin for Eclipse 3.5 is installed using the following update site. If you are using an earlier version of Eclipse, replace the 3.5 version number with your version (3.3 or 3.4). For detailed instructions on installing plugins in Eclipse, see instructions for Eclipse 3.5, Eclipse 3.4, or Eclipse 3.3.

http://dl.google.com/eclipse/plugin/3.5

In the Install dialog, you will see an option to install the Plugin as well as the GWT and App Engine SDKs. Choosing the SDK options will install a GWT and/or App Engine SDK within your Eclipse plugin directory as a convinience.

Now GWT SDK is installed in your eclipse.

Now you can Write GWT applications.

Google Web Toolkit(GWT)

What is Google web toolkit? Why it is use full to web-developer? What can be done with it?

How it helps the web-developer?

Well this were some question which were there in my mind in last few hours.

Google web toolkit is set of toolkit that is used for building and optimizing complex browsers based applications.

One may ask what is complex browser application?

For me complex applications are writing ajax request like XMLHttpRequest and JavaScript.

It is an open source set of tools that allows web-developer to create and maintain front-end web application in Java.It is licensed under apache license v2.

So how does it works?

Using GWT developer can rapidly develop ajax application in Java using any Java development tool. When the application is developed the GWT cross compiler translate the Java application to stand alone JavaScript file. So whatever is our ajax or JavaScript requirement in our web application we write that application in Java and then we change that to JavaScript file and include that file in our web document. This way it saves a lot of time of developers to write complex JavaScript.

Some other interesting stuff about GWT

1. The GWT SDK provides a core set of Java API's and library that allows developers to build user interface and logic for the browser client . Than it is cross compiled to JavaScript and at the end we have plain JavaScript.

2. GWT can handle all the client -server communication. so we don't need to worry about XMLHttpRequest it is handled by GWT.

3. The handwritten JavaScript can be mixed with Java Source code to interface with existing JavaScript API's .

Some of the projects which uses GWT are Google Wave and AdWords.

I hope this will help to those who are just browsing the net to find out basic idea about GWT.

Making a dynamic web page

I was just wondering from last few days how to make my webpage more user friendly

user friendly i mean if a user wants to register to my web site why i will redirect him to a new page rather i will make the form appear there it self.

this i can do using jquery and ajax.

i will be coming with the ways how to do it in few days keep checking. :-)

Electronics work bench

for using multisim install eletronic work bench software it is very nice for installing read the instruction carefully and then install. if u have any prb contact me at my gmail id