PHP and Windows Based Application...

The days are not far away when PHP will dominate windows based application development also. Here are some pointers...


http://winbinder.org/

http://www.bambalam.se/bamcompile/

http://www.gnope.org/

http://gtk.php.net/

Hungry for Quality Content?Know about Hidden Content Sources on Internet

As I travel through the Google search engine, there is one element that defines almost all of the top-ranking websites. It's great content. People come online for information and those that offer the best content reap the greatest rewards.

Unfortunately, this type of content is hard to come by. In most cases, you either have to spend hours in front of the keyboard or outsource the job to others. Both of these options are very costly. One requires your valuable time and the other requires an ínvestment of around $10 - $20 per article.

That's why I have scoured the net in search of valuable frëe content sources. I'm still not quite sure why I'm revealing my treasured piles of frëe content, but I certainly hope you enjoy them.

One of my favorite sources of content is public domain. This comprises the body of knowledge without a copyright. Anyone can use this material for commercial or non-commercial purposes. Below are some excellent sources for public domain material.

Project Gutenberg
Project Gutenberg is a library of 18,000 frëe ebooks whose copyright has expired. "The Adventures of Sherlock Holmes", "Pride and Prejudice", "The Time Machine", "The Adventures of Tom Sawyer", and "The Canterbury Tales" have all passed into the public domain.

This means that you can put these on your website or even sell them in electronic or book format.

Explore a wealth of frëe content at Gutenberg.org.

Archive.org
At Archive.org you can find thöusands of works that are currently in the public domain. Want to put some cartoons on your web site? Take a look at the "Film Chest Vintage Cartoons", which is full of classic animated cartoons from the 1930's and 1940's. The collection includes Popeye, Porky Pig, Bugs Bunny, Woody Woodpecker, The Three Stooges and Betty Boop. They also provide tons of other reproducable content including:

Brick Films: Commonly called "LEGO Movies". Brick films are dedicated to the art of stop motion animation.

SabuCat Movie Trailers: The world's largest collection of theatrical trailers.

Feature Films: A large number of classic feature films and shorts.

Universal Newsreels: Newsreels were shown before every feature film in the pre-tv era.

Computer Chronicles: Was the world's most popular television program on personal technology during the height of the computer revolution.

Net Cafe: Television series covering the revolution during the height of the dot com boom.

All of these content sources are available for you to put on your website. You can find them at Archive.org.

Another popular public domain destination is Wikipedia.org. Here you will find over 1 million articles ranging from Greek mythology and Egyptian history to business, health, and technology.

Go to Wikipedia.org for a huge collection of articles you can reprint on your own website.

Creative Commons
Every creative work receives copyright protetion as soon as you put pen to paper, hit save, or press record. Because of this, no one can use that work without express permission from the author.

Creative Commons provides a new content license that allows you to share your work with others. If you want, you can even allow other people to expand upon your existing work. This allows for creative co-authorship.

The Creative Commons license has made piles of content available for use on your web site. Whether you are looking for audio, images, video, or text, you can find an abundance of reusable information within the creative commons.

To search for content to put on your own web site, go to CreativeCommons.org.

Government Web Sites
Works produced by the U.S. Federal government are not copyrighted. If you obtain a government document from the net, you are frëe to copy and distribute the document. I have found plenty of great content about finance, retirement, health, business, and traveling on government websites.

To search for content offered by the United States government, go to http://www.google.com/unclesam.

Article Directories
There are thöusands of writers on the internet and many of them would love for you to reprint their articles on your website. You can find thöusands of frëe web articles at the following article directories.

GoArticles.com
EzineArticles.com
ArticleCity.com

Interviews
I consider interviews to be one of the best sources of quality content for your site. Simply interview industry professionals and post the recording and transcript on your website. This allows you to create original content very quickly.

Don't be afraid to ask for an interview, most experts would be delighted to speak with you. Remember, this is probably one of their greatest passions. If you ask them politely, your chances for landing an interview are good.

You can conduct an interview in person, over the telephone, or even through an e-mailed questionaire.

RSS Feeds
RSS is changing the way we consume information online. In addition, it has also provided thöusands of new content sources for the online publisher. RSS is simply a file format similar to XML that is used by publishers to make their content available to others in a format that can be easily understood by web publishing software and content aggregators.

By using RSS feeds, you can enhance the content on your site without ever writing a single word. And remember, on the Internet, content is King.

Want to put Amazon products on your site, updated news from the New York Times, financial advice from Motley Fool, or press releases from PRWeb?

This is all possible with RSS. No matter what type of information you are looking for, RSS can provide you with a constant stream of updated content for your web site.

To search for an RSS feed to enhance your own website, go to Syndic8.com. You can even mix and match a variety of rss feeds at RSSMix.com.

Facts & Statistics
Looking for facts or figures to put on your website? Take a look at some of the sources below. You'll likely be surprised how many facts, figures, and definitions are available in the public domain.

The CIA World Factbook provides a number of statistics on countries, territories, and dependencies. Each profile tracks such demographics as population, ethnicity, and literacy rates, as well as political, geographical and economic data.

http://www.census.gov/: One of the largest repositories for data and statistics related to the U.S.

http://www.1911encyclopedia.org/Main_Page: One of the best encyclopedia's ever written was published over 90 years ago. Search over 40,000 articles, all of which are available for publication on your own site.

http://www.bibliomania.com/2/3/257/frameset.html: A searchable interface of the 1913 public domain Webster's dictionary.

Private Label Articles
Private label articles can be bought for pennies per article. This is possible because they are sold in bülk.

Many people criticize these articles and have declared them as worthless. However, I am here to tell you that private label articles can be very powerful when used appropriately.

Unless you have hours of frëe time every day, it is unlikely that you are going to be able to create the amount of quality content that your web site deserves. This is where private label content enters the picture.

You can use private label articles to:

• Add content to your web site.
• Acquire hundreds of inbound links by syndicating the articles to article directories.
• Create a frëe report for your visitors and other website publishers.
• Create an information-packed RSS feed.

However, the key to using private label articles effectively is to optimize them. Straight out of the box, these articles are near worthless. To give them value, you must add your own touch.

Inject your personality into the article. Combine multiple articles and do some additional touch-ups to ensure that the article is in top shape for your readers.

Once you are finished you can add your resource box and send it off to article directories and website publishers.

If you are looking for one of the top private label article providers, go to InfoGoRound.com.

Images
Quality images can make your content much more inviting and keep people at your site for longer periods of time. Fortunately, there is a site that offers thöusands of pictures completely frëe of charge. Find it at Stock.XCHNG.

Quotes
Quotes can give your website a special touch. Quotes provide interesting content in addition to an element of credibility. I often like to add related quotes to my web site simply to engage the reader's attention.

To find some quotes for your website, go to QuoteLand.com.

In the end, you always want your content to be unique. Not for the search engines, but for your visitors. With quality content comes quality links. Once you have built up a reputation for delivering unique content, you will nevër have to worry about having an audience eager to visit your website.

The Myths of Open Source

It isn't all about cheap: Companies keep finding good reasons to take advantage of open-source software.
BY MALCOLM WHEATLEY

AT FIRST GLANCE, the company Employease seems unremarkable. But look a little closer. Employease, which provides employee benefits administration services to more than 1,000 organizations across America, has an IT architecture chiefly built around open-source software, which makes it a rare bird—not that it was planned that way when the company was founded in 1996.

Advertisers
"It's been quite a surprise to me. The open-source model just seems intuitively wrong," says John Alberg, the company's cofounder, CIO, CTO and vice president of engineering. But the facts speak for themselves.

The company's 25 production application servers run on Red Hat Linux, having been switched from Windows NT in July 2000. Webpages once delivered by Netscape are now served by Apache, supplemented by Tomcat, an open-source Java servlet engine. Send an e-mail to Employease and it's processed by Sendmail, an open-source mail server, while the company's software developers use XEmacs, an open-source development tool.

But that's not all. Although the company's main applications use Informix for database management, Alberg happily confesses that he can see a time when the proprietary software will be displaced by MySQL, an open-source relational database system already used by the company for less critical applications. Snort, an open-source intrusion detection tool, is also under active consideration, says Alberg.

Once seen as flaky, cheap and the work of amateur developers, open source has emerged blinking into the daylight.
Companies such as Employease herald a sea change in corporate attitudes toward open-source software. Once seen as flaky, cheap and the work of amateur developers, open source has emerged blinking into the daylight. With unrestricted access to the source code to run or modify at will, and support coming from an ad hoc collection of software developers and fellow users, the open-source model is very different from proprietary software. But it is nevertheless proving attractive enough for a host of CIOs to make the switch. So who's using open source? Why are they using it? And are the benefits worth the risks? The answers are surprising—and dispel some of the myths surrounding open source.


MYTH 1
THE ATTRACTION IS THE PRICE TAG
One of open source's most touted benefits is its price. Download the software, install it—and don't pay a penny. That's the theory. But to a surprising number of open-source user companies, the price tag—or lack of one—is irrelevant. "It's not about being cheap," insists Employease's Alberg. "It's about doing our jobs effectively—and we're willing to pay quite a bit for that. We want stable software that does what it says it will do."

What Alberg finds fascinating about moving to open source is the performance improvement that resulted. The move to Linux, for example, dramatically cut the rate of server failure experienced by the company. Typically, under NT, one of the company's servers would fail each working day. Now, he says, "we get at most two failures a month—and often don't get any in a month."

Linux also runs Alberg's applications faster than NT, a fact that has meant that despite more than doubling its business since 2000, the company hasn't needed to buy more servers. "Linux increased our capacity by between 50 percent and 75 percent," says Alberg.

Even so, Alberg is careful to make clear that his commitment to open source isn't the blind buying behavior of a zealot. He wouldn't, for example, go open source if it were more expensive than proprietary code. "Solaris is a strong commercial operating system. We'd choose it over open source if we found it to be less expensive," he says. "[While] cost is a huge driver for our decision-making process, we cannot risk choosing an inferior solution to save money. We couldn't even consider open source if it weren't at par with—or in some cases better than—commercial alternatives."

Ask many users of open source and a similar story emerges. "Cost savings weren't really a factor in our decision to go open source," says John Novak, CIO of 330-plus hotel chain La Quinta, which is moving its online booking system—previously on BEA's WebLogic—to a combination of Apache, JBoss and Tomcat. "What got us into it was that it was simply the best technology open to us."


MYTH 2
THE SAVINGS AREN'T REAL
Open-source software has been described as "free, as in a free puppy." And yes, the absence of software licensing fees needs to be offset along with the costs of training, support and maintenance. On the other hand, proponents of open source also cite reduced costs of "vendor churn," where vendors require users to migrate to a new version or pay for extra support. Most users we spoke to for this story reported a net savings with open source—often a substantial one.

At Sabre Holdings—the company behind Travelocity, the Sabre Travel Network and the Sabre travel reservation system—a major migration to open source is under way, prompted by Sabre's prediction that the move will yield savings of tens of millions of dollars during the next five years.

The company runs two distinct groups of computers, explains CTO Craig Murphy. Where reliability is paramount, Sabre Holdings uses pricing—or "data of record"—applications, which run on high-spec, fault-tolerant Hewlett-Packard NonStop systems. But shopping applications—where customers and travel agents hunt for the best deals—run on a server farm of lower-cost machines. Each shopping computer has its own open-source MySQL database, explains Murphy, synchronized by an application from GoldenGate with the rules, fares and availability information held on the fault-tolerant "data of record" system. The shopping systems were on HP-UX, but by the beginning of this month, all of those servers will have switched over to an open-source operating system—Red Hat Enterprise Linux AS.

The big attraction of open source is that there's a zero marginal cost of scale because open source doesn't require additional licenses as an installation grows, he says. As a result, the cost per transaction plummets as you add more systems. Exact comparisons are tricky, says Murphy, "but where we can make like-for-like comparisons, we're expecting at least an 80 percent reduction in running cost."


MYTH 3
THERE'S NO SUPPORT
According to Gary Hein, an analyst with technology consultancy Burton Group, technical support is a potential open-source user's primary concern. "Who do you call when things go wrong? You can't wring a vendor's neck when there's no vendor," he says.

In practice, the situation is complex. As Hein points out, most open-source projects have a large corps of developers, Internet mailing lists, archives and support databases—all available at no cost. That's the good news. The not-so-good news is that there's no single source of information. "A simple question may result in multiple, conflicting answers with no authoritative source," he says.

Even so, says Klaus Weidner, a senior consultant with technology consultancy Atsec, multiple sources of support can be better than being tied to one vendor—especially when that vendor provides bad support or refuses to continue supporting software of a certain vintage.

In practice, existing users of open-source software appear perfectly happy with open-source support arrangements. "The breadth of resources available for open-source applications is so great worldwide that we can get support, communicate with a developer or download a patch no matter the time of day," says Thomas Jinneman, IT director of RightNow Technologies, an ASP that hosts customer service products for more than 1,000 companies worldwide, including British Airways, Cisco Systems and Nikon.

The company's hosting environment runs on Linux, Apache and Tomcat, and 97 percent of its customers use MySQL, says Jinneman. Indeed, he adds, "we've had more trouble getting support for some of our purchased commercial applications than we've had with open-source applications."

Some open-source applications also have support offered by the original developers. JBoss, for example, is backed by JBoss Group, which includes the 10 core developers who wrote the application. Depending on the contract, explains JBoss Group President Marc Fleury, users can obtain 24/7 professional support with as little as a two-hour response time. The group also offers training.

A similar model also underpins Sourcefire, whose founders created Snort, the popular open-source intrusion detection tool. Downloaded off the Internet, Snort is command-line-driven, explains Sourcefire CTO Martin Roesch. Enterprise users can set it up themselves—but more and more are contracting Sourcefire to do it instead so that the company can handle security management details.

"What I like is that you get all the advantages of open source in terms of people working on it, as well as the advantages of a commercial enterprise behind it in terms of longevity and liability," says Kirk Drake, vice president of technology for the National Institutes of Health Federal Credit Union.


MYTH 4
IT'S A LEGAL MINEFIELD
A variety of open-source licenses exist, and helping CIOs understand their implications is good business for lawyers—very good business. "[CIOs'] concerns chiefly revolve around the implications of using code to which they can't verify their right to use," says Jeff Norman, a partner in the intellectual property practice of law firm Kirkland & Ellis. "Just because you've got a piece of paper saying that you own the Brooklyn Bridge, it doesn't mean that you actually own it."

For some users, third-party indemnification is an option. On Nov. 17, 2003, for example, JBoss Group announced it will indemnify and defend JBoss customers from legal action alleging JBoss copyright or patent infringement. Other vendors of open-source software—including HP, Red Hat and Novell—also offer indemnifications of varying types.

And while conceding that the situation isn't perfect, Sabre's Murphy says that he's heard all the legal arguments he needs. "It's a concern, sure, but we've basically got to do this. There may be friction and challenges—but I don't see any showstoppers." (See "Open Source Under Attack," this page.)


MYTH 5
OPEN SOURCE ISN'T FOR MISSION-CRITICAL APPLICATIONS
Mission-critical apps don't come any more crucial than those in banking, where transaction systems simply have to work, period. Experimenting with open source, with its attendant risks in terms of potential infringement, security and maintenance, might be regarded as anathema. "Banks tend to be conservative institutions—first followers, if you like, rather than leaders," says Clive Whincup, CIO of Italian bank Banca Popolare di Milano, who freely admits that the bank's venture into open source was the result of "some fairly lateral thinking."

But walk into Banca Popolare's smart new branch on the Via Savona in Milan's Zona Solari district, and the service these days is much faster than customers have previously experienced. The reason? Unwilling to throw out the bank's legacy banking applications, totaling some 90 million lines of Cobol, but unable to keep them running under IBM's vintage OS/2 Presentation Manager operating system, Whincup has used a proprietary legacy integration tool from Jacada to connect the Cobol to IBM's WebSphere—running in a Linux partition on the bank's mainframe.

The result: Formerly disjointed applications now run slickly in a Web browser, yielding faster transaction times, less time spent training tellers—and many more opportunities for cross-selling the bank's services.

Billed by insiders as one of Europe's largest Linux projects, the Zona Solari branch is piloting the new system, says Whincup. Once testing is complete, full rollout will begin in May. One decision to be made before then: whether to leave the branch desktops running Windows XP, as in the Zona Solari pilot, or move them to Linux as well. "Both of the next two branches to pilot the system will be using Linux [on the desktop]," Whincup says.


MYTH 6
OPEN SOURCE ISN'T READY FOR THE DESKTOP
At Baylis Distribution, a transport and distribution company, IT Director Chris Helps came across the MySQL database four years ago when the company was looking to create a data warehouse. Around the same time, the company began experimenting with Linux, he says, for small-scale, noncritical applications. The move to mission criticality came last year after the vendor of the company's propriety logistics management system, Chess Logistics, brought out a new version that ran on Linux—a version that promised to improve performance by a factor of between 10 and 15 times. Helps happily signed up, and he hasn't regretted the decision.

But his experience of running Red Hat Linux in a true production environment, with users logging on to the main Linux server from what he describes as "thin clients with a cut down Linux operating system," prompted him to reevaluate the company's desktop policy. In the end, the company opted to replace Microsoft on desktops with Linux and open-source personal productivity tools for activities such as word-processing and spreadsheets.

The arguments for and against open-source software get trivialized. It's not a technology issue; it's a business issue.

—CTO ANDY MULHOLLAND, CAP GEMINI ERNST & YOUNG
"We've not done a formal evaluation of the savings, but a broad-brush calculation is that it costs $1,820 per seat to install a PC with all the Microsoft tools a user needs. With Linux, and open-source tools, it's only around half that," Helps says. What's more, usability improved. "People can log in from any PC in the group and have all the same services and facilities available to them as if they were sitting at their own desks." Better still, IT support is simplified. "We haven't got the complications of users establishing a unique personalized environment on their desktops: We've got better control, better upgradability and better traceability."

Nor is Helps alone. Other IT shops—as big and diverse as Siemens Business Services and the Chinese government—are also convinced that Linux is ready for the desktop. Siemens, for example, says it has performed extensive testing with "real-world, nontechnical workers," finally declaring that Linux has now matured as a desktop system. The tests confounded the company's expectations. "We [at first] didn't see Linux on the desktop as a major market, but we were wrong," says a spokesman for the 35,000- employee organization that serves more than 40 countries.


THE BOTTOM LINE
Is open source right for every organization? In the end, argues Andy Mulholland, chief technology officer for Cap Gemini Ernst & Young, it's a question of attitude. "The arguments for and against open-source software often get very trivialized," he says. "It's not a technology issue; it's a business issue to do with externalization."

Companies with an external focus, he says, which are used to working collaboratively with other organizations, and perhaps are already using collaborative technologies, stand to gain much more from open source than companies with an internal focus, which see the technology in terms of cost savings.

"The lesson of the Web is that standardization is better than differentiation," Mulholland claims. "Is there a virtue in doing things differently? Is there a virtue in doing things the same way as everybody else?" As the past decade has shown, standardization with a proprietary flavor—think Microsoft—has its drawbacks: bloatware, security loopholes, eye-popping license fees and an unsettling reliance upon a single vendor. In offices around the globe, an era of open-source standardization, determined to condemn such drawbacks to history, may be dawning. end

Formatting Tips To Speed up Your Website

While more and more people are getting access to high speed internet, there are many left on dial up. Be kind to those visitors and do a few, simple things to speed up your webpages. Not only will these tips give you a faster load time, most will also help keep your bandwidth fees low as well!

Use CSS For Faster Pages

Even if you decide to use tables, CSS can greatly improve your web sites load time! With your styles in an external .css file, the browser can cache all the formatting and stylizing for your pages instead of having to read each and every single tag all over again. Also it cuts down on long drawn out tags and replaces them with smaller class styles instead.

Use External Scripts

Use the same script on multiple pages? Switch to an external script. I'm not talking about remotely hosted, I mean loading javascript files from one source instead of adding all that code to each of your pages like this:

<script type="text/javascript" src="yourscript.js"></script>

That way the browser already has it in it's cache and won't have to read it each time another page loads. This one saves a ton of load time, specially for larger scripts!

Remove Anything You Don't Really Need

OK, while this might sound obvious sometimes the hardest thing about creating a website is not using every fancy trick that you know. Images, flash and sometimes even sound files are very impressive.. but do you really need to showcase all your talents one one page?

Embedded sound files are something many people just find annoying anyway. You'd be surprised how many are surfing at work ;-). The last thing anyone wants is a loud music or sounds announcing to their boss that they're surfing. Also many people have their own music playing... hearing a song over top of what we're listening to is less than pleasant. As for Java applets, try to ditch them or if you want those effects, JavaScript unusually loads faster and can do just as much or more. Stand back and take a critical look at your website, you may see a few special effects that can be let go of for the sake of faster load time.

Avoid Nested Tables

OK, I'm not a big fan of using tables for layout anyway (I'm one of those people that believes content and presentation should be separate.. but thats another tip page). With that said, if in your templates tables seem neccessary (or the easier way to do it), try to avoid nesting. Why? When you place a table inside another table, it takes a lot longer for the browser to work out the spacing since it has to wait to read the entire html and then work out the layout. If at all possible, try using CSS to create the columns on your page.

Avoid Full Page Tables for Faster Rendering

If you use tables, try avoiding the whole page being one big table. The browser won't show anything until it's read the whole thing that way. For a faster loading webpage, either try multiple tables (not nested) or having stuff above the main table to make your content in the first table show up faster. That way your visitors will have something to read while the rest of your page loads. It may not really make you page faster, but it will feel like it to your visitors.

Split Up Long Pages - Multiple Short Pages Load Faster

By splitting up long pages into multiple pages you not only make the content show up faster but many people that see a very long scroll bar give up. Remember, people's attention spans are often shorter than a grasshoppers (OK, not literally, but you get my point) since so much information is available at our fingertips. Try breaking it up into more readable lengths.

Remove Excess "Whitespace"

Whitespace is the spaces between your coding, removing the unneeded tabs and spaces can help a lot! That can be done by hand or by using the HTML Page Squisher. Doing this will take a lot of extra bytes off the total size of your page and will speed up load time quite a bit. (Careful using the squisher, I find it squishes too much and makes it rather hard to edit later.)

Keep Your Code Clean

If you do use a wysiwyg editor, most times the will add useless code to your pages for example, many will leave empty tags (ie. <font> </font>). Removing any of those excess tags will not only speed up your load time, but make you pages validate a lot cleaner.

Speed up Images Load Time

Don't Go Overboard On Images

While images can greatly enhance the look of a site they can really slow it down if there are too many. Try to decide if all your images are really needed (quite a few nice effects can be done with css, so sometimes images are unneeded.)

Height And Width Tags

When the page loads and the image size is already defined (ie. you've used the height and width tags), the browser knows where everything will be before the images are loaded. Otherwise the page has to wait and load the images before the text. Same goes for tables, so try to use width tags when possible on those as well for a speedier page.

Faster Images? Reduce Their File Size

There are many totally free, online image optimizers so you don't even have to install anything and it's extremely easy! Online Image Optimizer will greatly reduce the file size of your gif, jpg, or pngs and neither you or your visitors will be able to see the difference other than a page that loads a heck of a lot faster. They also keep the transparency and animations in gifs! For another JPEG reduction, try JPEG Wizard, also free, this one will only work with pictures in your hard drive not ones from the net. You can also choose some simple effects to be done (flip, mirror and rotate).

GIF vs JPG vs PNG

Personally on new sites I design I tend to go for optimized pngs. They have lossless compression (unlike jpgs and can be used without worry (gifs have the potential to have copyright issues) and load fast! With all that said, if you still want to use gifs and jpgs, here's a bit of fast info... If you don't need sharp resolution, choose GIFs over JPEGs, as GIFs generally load quicker. JPGs are generally best for photos, GIFs for anything else.

(I'd add a rant here about how Microsoft has held up the web's development with not making IE6 support png transparency... but *sigh* I've ranted about this already to anyone who will listen. Firefox, Opera and other modern browsers however have been able to show alpha transparency in png for years... oops, sorry, that was a mini rant after all!)

Want to Control over HTML Elements?Disable HTML Elements JavaScript

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Dev-PHP 1.9.4">
<title>Document Title</title>

<script language="javascript">
function enableField()
{
if(document.form1.terms.checked){
document.form1.ORDER.disabled=false ;
}

else{
document.form1.ORDER.disabled=true;
}
}

function enableField1()
{

//alert(document.form2.terms1.value);

if(document.form2.terms1.value == "1"){
document.form2.ORDER1.disabled=false ;
document.form2.ORDER2.disabled=false;
}

else{
document.form2.ORDER1.disabled=true;
document.form2.ORDER2.disabled=true;
}

}


</script>

</head>
<body>

<FORM name="form1" ACTION="" METHOD="POST">
<B><INPUT TYPE="SUBMIT" VALUE="Add to Cart" NAME="ORDER" disabled="true"><BR><br><br>
<input type="checkbox" name="terms" value="" onClick="enableField()">Here, I agree with <a href="terms.php ">Terms & Conditions</a>
 </form>

 <br><br><br><br><br><br>
<FORM name="form2" ACTION="" METHOD="POST">

<select name="terms1" onChange="enableField1()">
<option value="1">1 </option>
<option value="2">2 </option>
<option value="3">3 </option>
</select>

<select name="ORDER1">
<option value="1">1 </option>
<option value="2">2 </option>
<option value="3">3 </option>
</select>

<select name="ORDER2">
<option value="1">1 </option>
<option value="2">2 </option>
<option value="3">3 </option>
</select>
 </form>

</body>
</html>

Really Good Blog for Programmers..

I am sure its really a very helpful to all programmers to enhance their skills one way or other way...

http://engtech.wordpress.com/

Enjoy...

How to Hack Online Database? Lesson 1...

Below article just give you overview of hacking into database..Lesson 1

Follow the instructions below and use your brain also:

1. Go to: http://www.forsalebyowner.com/ . You will see "BUYING A HOME?" on very top part.
Below of it, you will find a search facility with "Go" button.

2.We need to use only "State" for searching. Select "AL" first, and click "Go".

3.Now you should see  - "Search Results" - "451 homes found." and below you will see the headings like:
Listing ID       City, State      Property Type      Sq.Ft.      Beds/Baths      Price      Fav etc.

4. Our main objective is to get only "Listing ID" from this page.

5. Now, the problem is - there are 19 pages of results, and you need to copy and paste the "Listing ID" from each page. DO NOT DO THIS.

6. Now, see the browser's URL bar. You should see:
http://www.forsalebyowner.com/searchResults.php?iPerPage=25&iRadius=25&iPropTypeCode=0&szCity=&szStateCode=AL&submit.x=11&submit.y=5&submit=Find

7. Change iPerPage=25 to iPerPage=451 We are doing this because we get all the results on a single page only. iPerPage=<number>, and this <number> = Total search results found. Getting all results on a single page is very IMPORTANT.

8. Now, copy all the data - next to this line:
Listing ID       City, State      Property Type      Sq.Ft.      Beds/Baths      Price      Fav

and paste it in the "data.txt" file.

9. Now, in the browser, run " codes.php" file, and you should get only "Listing IDs" in the browser.

10. Just copy those "Listing IDs", and store it in seperate file - like "al.txt".

11. Remove any unnecessary characters. All data must be numeric "Listing IDs" only.

------------------------------------------------------------------------------------------------------------------------------------
Repeat the whole process for each State, and make seperate text files with Listing IDs in it.

If you want to have codes.php file, then contact Ankur PateL - who is master in hacking online databases.

Thanks.

Getting to Deadline - Programmer Productivity Tips At Work (Getting to Done)

Getting to Deadline - Programmer Productivity Tips At
Work (Getting to Done)

Posted in Programming, Best Practices, Verification,
!Original Commentary, Career Skills, Workplaces at by
engtech

I am my own worst enemy when it comes to achieving my
deadline goals. These are tips / reminders I?ve found
useful through work experience.

Most of the tips are general, but some are
specifically suited to programmers/engineers in
situations with long compile/simulation phases
(compiling is the act of building an executable,
simulation is the act of running it to completion).
General Office Productivity Tips:Procrastination.It
comes down to inertia and momentum.

* Understand the problem. It is very easy to avoid
work you do not understand well enough to solve.
* Break it down. Break the larger problem into
smaller problems that conceptually you understand and
can tackle.
* Review milestones. They are closer than you
might think, and it can be a good kick in the pants to
think ?I have to get this feature done by Thursday?
instead of ?I have to get this all done in three
months?.
* Prioritization. Do not starve a high priority
feature for lack of understanding to feed a low
priority feature you know like the back of your hand.
* Just do it. Attack the problem, no matter how
feeble the attempt. Even if you throw out the work, it
increases your understanding. It is better try fail
than to waste time on something unrelated. Like
writing a blog post or checking the InterWeb. LIKE YOU
ARE DOING RIGHT NOW.
* Go for a walk. Can?t focus? Get away from your
desk and stimulate the blood flow to your brain. A
change of scenery can unplug a mental block.

Interruptions.

What is of concern isn?t the time lost servicing the
interrupt, it is the time spent context switching back
to the original problem. Interrupting someone in flow
can take 15 minutes for them to get back to the point
they were at before the interruption occurred.

* Net connectivity. Close email, web browser and
any messenger programs.
* Answering machine. Forward phone to voice mail.
* Office hours. If you are in a partial support
role, set up ?office hours? during the day where you
will answer questions.
* Meetings. Reduce the number of weekly meetings
wherever possible.
* Maximize use of time. Know what time of day you
are most effective and schedule the
interruptions/meetings to the time when you are not.

Environment.

The key is to create a work environment that is free
of distractions so that when you?ve achieved flow you
can maintain your focus on the problem at hand.

* Noise. Noise cancellation headsets or headphones
with music can cut down on the distracting nature of
open concept cube farm hell. Be kind to your
co-workers and never use a portable radio or your
computer speakers unless you are working late alone.
If you?re going to have an extended discussion with
someone move to a break room or an empty conference
room.
* Temperature. Have a portable fan to cool down
and a portable heater/sweaters to warm up if your cube
doesn?t have ideal temperature conditions.
* Snacks. Have food around so that hunger can be
satisfied without leaving the building. Don?t let your
belly be a source of distraction. Nothing that will
rot should be left out of sight. Some good low-fat
choices: apples, cans of tuna, microwave popcorn,
turkey sandwiches (if you have access to a fridge).
* Hydration. Have a bottle/cup of water on your
desk that you can sip from throughout the day. The
short term gains made from drinking coffee isn?t worth
the long term loses on memory, dehydration, and the
productivity lose from caffeine crashes.
Non-caffeinated herbal teas such as peppermint can be
useful for weaning yourself from coffee.
* Clutter. I am not hypocritically recommending
clean desks, but file away any papers that aren?t
germane to the problem at hand. When it comes time to
search the mountain of looseleaf, at least you will be
looking at stuff related to what you are working on.

Manage Expectations.

The biggest secret to getting more work done is having
less work to do.

* Give feedback. Do not tell management what they
want to hear, tell them what you think will happen.
* Accurate Estimations. Develop your estimation
skills so that when you say ?task X will take Y to do?
they believe you.
* Under commit and over deliver. Realistic
schedules give room to do a better job instead of
fighting to keep your head above water.

Avoid Burnout.

This is the most important tip. Meet the deadline in a
sane manner. Ever waste half an hour because you were
looking at the wrong results? Ever make a minor two
character typo that drastically changed results and
was very insidious to find because it ?looked right'??
If you were more alert that would not have happened.

* Relax. Find the balance between enough stress to
motivate but not so much stress that you lose the
ability to see the simplest solutions and recognize
time sinks before you fall into them.
* Minimum overtime. An hour of overtime is less
than a regular hour of work because you?re reducing
your overall ability to produce when you don?t get
proper rest. Find a balance between working hard and
working smart.
* Sleep. Don?t let thinking about work impact your
sleeping. Sleep debt has to be paid off eventually.
You don?t want to be useless during the eight hours a
day you have to be in front of the keyboard.
* Balance. Find a balance between work, health,
activity, friends, family and hobbies. It will
increase your overall work performance. You lose the
ability to bounce back with age.
* Don?t force alertness. Much like a sleep debt,
forcing alertness with caffeine or other stimulates
will eventually develop a dependency on them to
achieve a baseline state.

Programming Specific Tips: Complexity.
Don?t create more work for yourself than is needed.

* Only code what is needed. If a feature ?might be
useful? then code it later when it is necessary.
* Simplest solution is the best solution. K.I.S.S.
Every line coded is a line that potentially has to be
debugged. Focus your debugging effort on solving the
problem, not on debugging bells and whistles that
don?t contribute to the deadline. More time is lost in
debugging an unnecessarily complex feature then in
designing it.
* Notes to yourself. Put comments in your code
with standard identifiers such as ?TODO? and ?FIXME?
that you can come back to later to add the
improvements you didn?t add the first time. Putting
the date you added that comment is optional, but can
help during a code cleanup (sorry, I mean
?refactoring?) five years later.

Multiple build / project directories.

?Hey, can you check out the latest version of this
file to see if my changes work?'? Except it?s never
just one file, and the changes never work the first
time. Checking code out into your working copy is not
just an interruption, but can lose an entire afternoon
trying to re-achieve the state you were at before
updating that ?one file?. Having multiple directory
trees (hard drive space is cheap) can remove this
problem.

* Working. What you currently have checked out any
are working on. Only checkout code when you?ve already
verified it works using the Stable/Branch directories.
* Stable. The latest valid snapshot/tag of code
that is known to work.
* Branch/Current. The absolute latest checked in
version of all code.

Decompose.

Problems seem more daunting when you can?t see the
trees for the forest. Breaking it up into smaller
tasks not only reduces procrastination, but it also
can increase performance time.

* Design assumptions. Create small unit proofs of
any design assumption upfront so that you know the
design will work before investing time and energy.
* Strawman Integration. When rapidly prototyping a
smaller subset of the design you are pushing the
integration issues until the end. It is best to do an
upfront integration of a strawman of your design to
make sure there aren?t any major gotchas and then
continue with the prototyping.
* Reduce dependencies. Debugging a rapid prototype
can be much faster because you don?t have as many
sources of errors to look at.
* Smallest solution space. Reduce the unit
testbench to only what is necessary to run your
prototype. The goal is to reduce the time between
starting a simulation run and getting results during
development. Keep the inherent downtime in your job
from interrupting your flow. You shouldn?t have time
to think about something other than the problem at
hand (ie: Checking Slashdot. Checking this blog is
ok).
* Symbolic links. Set up the file structure such
that you can run your small unit testbench in parallel
with the main design, ie: symbolically link to where
any files will exist in the real design. It may still
be useful down the road when you want to isolate a
problem.
* Metrics. It is much easier to grab
profiling/coverage metrics from a smaller testbench
that you can iterate many, many times more often then
the main design. The statistics might not be ?real
world?, but they can still be helpful.
* Design for debug. Litter your code with error
assertions when they receive unexpected values or hit
unexpected states. If necessary add a debugging define
so that these assertions can be turned off in the
production code but turned on again when you encounter
a problem. Assertions to test inputs and outputs for
illegal values and raise a big red flag will save you
a lot of time when integrating.

Parallelism.
If you have access to multiple CPUs or a server farm
then use them!

* Pipeline. If the compile/simulate/debug flow has
dead cycles where you are ?waiting for results?, then
you can make use of those cycles by breaking the work
down into distinct units that can be pipelined in
parallel. This keeps you actively solving the problem
instead of getting caught up in procrastination and
servicing interrupts.
* Tracking. Keep a piece of paper (or use your
engineering lab book) beside your desk to write down
reminders of where you left off in the parallel
problems.
* Don?t fire and forget. When you switch to
working on the next task in the pipeline, periodically
check the status on the first task to make sure that
it is running properly.
* Always run something. The goal is to always have
something running in the background while you develop
during the cycles where you would instead be waiting
for results. It could be as simple as seeing if what
you are working on compiles properly while you?re
working on something else.
* Organize. Use tools to keep the multiple tasks
organized such as different workspaces for different
tasks, tabbed terminal windows with different title
bars, saved session views, etc.