Share it all!

RESULTS OF SSC-2 (Science group) 2010 karachi board

2010-07-19T12:53:00.004+05:00

SSC-2 results of matric science group 2010 has announced and after the data entry the results will publish on internet. the time for the announcement of results is 12:00 noon. due to the data entry of results will take some time! after that you can check your results!

BEST OF LUCK FOR ALL THE STUDENTS OF MATRIC

you can check the results from the following website:

www.resultspk.com
www.geo.tv/results
www.bsek.edu.pk

COKE STUDIO SEASON 3 PART 4

2010-07-17T19:31:00.008+05:00

coke studio season 3 part 4 has launched and all the previous seasons were great and very famous among those people who love to listen songs! here are some songs of this season

promo

Abida Parveen, Ramooz-e-Ishq - Coke Studio

2010-07-12T02:16:00.001+05:00

Mori Araj Suno, Tina Sani - Coke Studio

2010-07-12T01:10:00.002+05:00

COUNTER STRIKE 1.6 NON-STEAM

2010-07-07T23:10:00.005+05:00

The most popular game played world wide some people play this game with bots while others play using LAN servers or online servers! This game based upon the two teams one is counter terrorist and another is terrorist
Counter terrorist team is that team which were against the terror of terrorist team. Terrorist team which plant the bombs and explosives at different places and the team which were against all of the terror of terrorist try to finish them.
The destination of counter terrorist team is to find out the places where the bomb has been planted and get there and diffuse the bomb and finish the terrorist and their terror.

There are some problem with this game, some of the patches of this game not supported SXe injected while the other patches not supported Amx mod.
here i have the solution of all these problems. I have some patches which are useful for you!
1. CS1.6full_v7
2. CS1.6patch_full_V23B
3. CS1.6patch_full_V24
4. CS1.6patch_full_v27
5. CS1.6patch_full_v28
6. CS1.6_Patch_to_v32.1

These are the patches which are very useful for all of you
All these patches supported SXe injected and Amx mod.
Its 100% works
please try these patches
NOTE:- Install these patches in increasing order.
like v7 then V23B and then so on..

there are some more other useful stuff for u
SXe injected
Amx mod

GREAT PERFORMANCE OF PAKISTAN

2010-07-06T18:47:00.004+05:00

PAKISTANI TEAM WON YESTERDAY T20 MATCH AGAINST AUSTRALIA

Pakistan defeated Australia in T20 match its seems that this time Pakistani team shows some improvement and had done a great job!!
This time Pakistani team prove that there is a success behind every defeat!!!
if this team really work hard and shows some improvement than in future this team will go higher and higher and will overcome and will reach to the top!!!!
Pakistani team must have to improve the fielding as it improved the bowling and batting!!!
Some of the experienced player which are retired from cricket team must have to coach this team !!!! like INZIMAM-UL-HAQ , SAEED ANWAR and WASIM AKRAM these were the cream of the cricket team in past and if they coaches this team than this team will come at the top of cricket world ranking!!!!

2010-07-06T17:25:00.006+05:00

PAKISTANI CRICKET TEAM IS IN BIG CONSEQUENCES AFTER LOOSING THE ASIAN CUP:::::::

Pakistani cricket team is a weakest team among all the teams as we can see the performance of this team before loosing the Asian cup tournament this is the most worst performance in Asia cup tournament as well as in T20 series !!!
Pakistan needs to wakeup and being more powerful to play against all of its opponent teams!!!
Pakistani cricket team are not like that as they were in past when this team is full of experienced players
Now there are only few experienced players left in Pakistani cricket team like SHAHID AFRIDI who is the captain of this team and IMRAN NAZIR , ABDUL RAZZAQ
SOME of the youngest players in this team which perform well!!
but unfortunately they r not playing that's why this team become weaker and weaker !!!
Pakistan cricket team has so many players by the which team become stronger but as you could see they are not in Pakistani cricket team due to the selection comity of Pakistan they don't give them a chance to play along with this team!
If the selection comity of Pakistan give them a chance to play along this team than neither ENGLAND nor AUSTRALIAN or any other team can beat our Pakistani team!!!!!

What Beautiful HTML Code Looks Like?

2009-02-10T12:01:00.006+05:00

Top 10 Things That Annoy Programmers

2009-01-27T19:57:00.003+05:00

Programmers all have their pet peeves. Whether it's scope creep, Hungarian notation, or smelly coworkers, we've come to accept that there are certain nuisances that come with our line of work. The following is a list of the top 10 things that annoy programmers, compiled from the results of my recent question on StackOverflow (you must be a closed beta tester to access the link) along with some of my own experiences as a programmer:

10. Comments that explain the "how" but not the "why"

Introductory-level programming courses teach students to comment early and comment often. The idea is that it's better to have too many comments than to have too few. Unfortunately, many programmers seem to take this as a personal challenge to comment every single line of code. This is why you will often see something like this code snippit taken from Jeff Atwood's post on Coding Without Comments:

r = n / 2; // Set r to n divided by 2

// Loop while r - (n/r) is greater than t
while ( abs( r - (n/r) ) > t ) {
r = 0.5 * ( r + (n/r) ); // Set r to half of r + (n/r)
}

Do you have any idea what this code does? Me neither. The problem is that while there are plenty of comments describing what the code is doing, there are none describing why it's doing it.

Now, consider the same code with a different commenting methodology:

// square root of n with Newton-Raphson approximation

r = n / 2;

while ( abs( r - (n/r) ) > t ) {
r = 0.5 * ( r + (n/r) );
}

Much better! We still might not understand exactly what's going on here, but at least we have a starting point.

Comments are supposed to help the reader understand the code, not the syntax. It's a fair assumption that the reader has a basic understanding of how a for loop works; there's no need to add comments such as "// iterate over a list of customers". What the reader is not going to be familiar with is why your code works and why you chose to write it the way you did.

9. Interruptions

Very few programmers can go from 0 to code at the drop of a hat. In general, we tend to be more akin to locomotives than ferraris; it may take us awhile to get started, but once we hit our stride we can get an impressive amount of work done. Unfortunately, it's very hard to get into a programming zone when your train of thought is constantly being derailed by clients, managers, and fellow programmers.

There is simply too much information we need to keep in mind while we're working on a task to be able to drop the task, handle another issue, then pick up the task without missing a beat. Interruptions kill our train of thought and getting it back is often a time-consuming, frustrating, and worst of all, error-prone process.

8. Scope creep

From Wikipedia:

Scope creep (also called focus creep, requirement creep, feature creep, and sometimes kitchen sink syndrome) in project management refers to uncontrolled changes in a project's scope. This phenomenon can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered a negative occurrence that is to be avoided.

Scope creep turns relatively simple requests into horribly complex and time consuming monsters. It only takes a few innocent keystrokes by the requirements guy for scope creep to happen:

Version 1: Show a map of the location
Version 2: Show a 3D map of the location
Version 3: Show a 3D map of the location that the user can fly through

Argh! What used to be a 30 minute task just turned into a massively complex system that could take hundreds of man hours. Even worse, most of the time scope creep happens during development, which requires rewriting, refactoring, and sometimes throwing out code that was developed just days prior.

7. Management that doesn't understand programming

Ok, so maybe there are some perks.

Management is not an easy job. People suck; we're fickle and fragile and we're all out for #1. Keeping a large group of people content and cohesive is a mountain of a task. However, that doesn't mean that managers should be able to get away without having some basic understanding of what their subordinates are doing, especially in the tech industry. When management cannot grasp the basic concepts of our jobs, we end up with scope creep, unrealistic deadlines, and general frustration on both sides of the table. This is a pretty common complaint amongst programmers and the source of a lot of angst (as well as one hilarious cartoon).

6. Documenting our applications

Let me preface this by saying that yes, I know that there are a lot of documentation-generating applications out there, but in my experience those are usually only good for generating API documentation for other programmers to read. If you are working with an application that normal everyday people are using, you're going to have to write some documentation that the average layman can understand (e.g. how your application works, troubleshooting guides, etc.).

It's not hard to see that this is something programmers dread doing. Take a quick look at all the open-source projects out there. What's the one thing that all of them are constantly asking for help with? Documentation.

I think I can safely speak on behalf of all programmers everywhere when I say, "can't someone else do it?".

5. Applications without documentation

I never said that we weren't hypocrites. :-) Programmers are constantly asked to incorporate 3rd party libraries and applications into their work. In order to do that, we need documentation. Unfortunately, as mentioned in item 6, programmers hate writing documentation. No, the irony is not lost on us.

There's nothing more frustrating than trying to utilize a 3rd party library while having absolutely no fricken idea what half the functions in the API do. What's the difference between poorlyNamedFunctionA() and poorlyButSimilarlyNamedFunctionB()? Do I need to perform a null check before accessing PropertyX? I guess I'll just have to find out through trial and error! Ugh.

4. Hardware

Any programmer who has ever been called upon to debug a strange crash on the database server or why the RAID drives aren't working properly knows that hardware problems are a pain. There seems to be a common misconception that since programmers work with computers, we must know how to fix them. Granted, this may be true for some programmers, but I reckon the vast majority of us don't know or really care about what's going on after the code gets translated into assembly. We just want the stuff to work like it's supposed to so we can focus on higher level tasks.

3. Vagueness

"The website is broken". "Feature X isn't working properly". Vague requests are a pain to deal with. It's always surprising to me how exasperated non-programmers tend to get when they are asked to reproduce a problem for a programmer. They don't seem to understand that "it's broken, fix it!" is not enough information for us to work off of.

Software is (for the most part) deterministic. We like it that way. Humor us by letting us figure out which step of the process is broken instead of asking us to simply "fix it".

2. Other programmers

Programmers don't always get along with other programmers. Shocking, but true. This could easily be its own top 10 list, so I'm just going to list some of the common traits programmers have that annoy their fellow programmers and save going into detail for a separate post:

Being grumpy to the point of being hostile.
Failing to understand that there is a time to debate system architecture and a time to get things done.
Inability to communicate effectively and confusing terminology.
Failure to pull ones own weight.
Being apathetic towards the code base and project

And last, but not least, the number 1 thing that annoys programmers...

1. Their own code, 6 months later

Don't sneeze, I think I see a bug.

Ever look back at some of your old code and grimace in pain? How stupid you were! How could you, who know so much now, have written that? Burn it! Burn it with fire!

Well, good news. You're not alone.

The truth is, the programming world is one that is constantly changing. What we regard as a best practice today can be obsolete tomorrow. It's simply not possible to write perfect code because the standards upon which our code is judged is evolving every day. It's tough to cope with the fact that your work, as beautiful as it may be now, is probably going to be ridiculed later. It's frustrating because no matter how much research we do into the latest and greatest tools, designs, frameworks, and best practices, there's always the sense that what we're truly after is slightly out of reach. For me, this is the most annoying thing about being a programmer. The fragility of what we do is necessary to facilitate improvement, but I can't help feeling like I'm one of those sand-painting monks.

Well, there you have it. The top 10 things that annoy programmers. Again, if you feel that I missed anything please be sure to let me know in the comments!

Source: http://www.kevinwilliampang.com/post/Top-10-Things-That-Annoy-Programmers.aspx

Top Ten Mistakes in Web Design

2009-01-26T11:02:00.003+05:00

1. Bad Search

Overly literal search engines reduce usability in that they're unable to handle typos, plurals, hyphens, and other variants of the query terms. Such search engines are particularly difficult for elderly users, but they hurt everybody.

A related problem is when search engines prioritize results purely on the basis of how many query terms they contain, rather than on each document's importance. Much better if your search engine calls out "best bets" at the top of the list -- especially for important queries, such as the names of your products.

Search is the user's lifeline when navigation fails. Even though advanced search can sometimes help, simple search usually works best, and search should be presented as a simple box, since that's what users are looking for.

2. PDF Files for Online Reading

Users hate coming across a PDF file while browsing, because it breaks their flow. Even simple things like printing or saving documents are difficult because standard browser commands don't work. Layouts are often optimized for a sheet of paper, which rarely matches the size of the user's browser window. Bye-bye smooth scrolling. Hello tiny fonts.

Worst of all, PDF is an undifferentiated blob of content that's hard to navigate.

PDF is great for printing and for distributing manuals and other big documents that need to be printed. Reserve it for this purpose and convert any information that needs to be browsed or read on the screen into real web pages.

> Detailed discussion of why PDF is bad for online reading

3. Not Changing the Color of Visited Links

A good grasp of past navigation helps you understand your current location, since it's the culmination of your journey. Knowing your past and present locations in turn makes it easier to decide where to go next. Links are a key factor in this navigation process. Users can exclude links that proved fruitless in their earlier visits. Conversely, they might revisit links they found helpful in the past.

Most important, knowing which pages they've already visited frees users from unintentionally revisiting the same pages over and over again.

These benefits only accrue under one important assumption: that users can tell the difference between visited and unvisited links because the site shows them in different colors. When visited links don't change color, users exhibit more navigational disorientation in usability testing and unintentionally revisit the same pages repeatedly.

> Usability implications of changing link colors
> Guidelines for showing links

4. Non-Scannable Text

A wall of text is deadly for an interactive experience. Intimidating. Boring. Painful to read.

Write for online, not print. To draw users into the text and support scannability, use well-documented tricks:

subheads
bulleted lists
highlighted keywords
short paragraphs
the inverted pyramid
a simple writing style, and
de-fluffed language devoid of marketese.

> Eyetracking of reading patterns

5. Fixed Font Size

CSS style sheets unfortunately give websites the power to disable a Web browser's "change font size" button and specify a fixed font size. About 95% of the time, this fixed size is tiny, reducing readability significantly for most people over the age of 40.

Respect the user's preferences and let them resize text as needed. Also, specify font sizes in relative terms -- not as an absolute number of pixels.

6. Page Titles With Low Search Engine Visibility

Search is the most important way users discover websites. Search is also one of the most important ways users find their way around individual websites. The humble page title is your main tool to attract new visitors from search listings and to help your existing users to locate the specific pages that they need.

The page title is contained within the HTML <title> tag and is almost always used as the clickable headline for listings on search engine result pages (SERP). Search engines typically show the first 66 characters or so of the title, so it's truly microcontent.

Page titles are also used as the default entry in the Favorites when users bookmark a site. For your homepage, begin the with the company name, followed by a brief description of the site. Don't start with words like "The" or "Welcome to" unless you want to be alphabetized under "T" or "W."

For other pages than the homepage, start the title with a few of the most salient information-carrying words that describe the specifics of what users will find on that page. Since the page title is used as the window title in the browser, it's also used as the label for that window in the taskbar under Windows, meaning that advanced users will move between multiple windows under the guidance of the first one or two words of each page title. If all your page titles start with the same words, you have severely reduced usability for your multi-windowing users.

Taglines on homepages are a related subject: they also need to be short and quickly communicate the purpose of the site.

7. Anything That Looks Like an Advertisement

Selective attention is very powerful, and Web users have learned to stop paying attention to any ads that get in the way of their goal-driven navigation. (The main exception being text-only search-engine ads.)

Unfortunately, users also ignore legitimate design elements that look like prevalent forms of advertising. After all, when you ignore something, you don't study it in detail to find out what it is.

Therefore, it is best to avoid any designs that look like advertisements. The exact implications of this guideline will vary with new forms of ads; currently follow these rules:

banner blindness means that users never fixate their eyes on anything that looks like a banner ad due to shape or position on the page
animation avoidance makes users ignore areas with blinking or flashing text or other aggressive animations
pop-up purges mean that users close pop-up windoids before they have even fully rendered; sometimes with great viciousness (a sort of getting-back-at-GeoCities triumph).

8. Violating Design Conventions

Consistency is one of the most powerful usability principles: when things always behave the same, users don't have to worry about what will happen. Instead, they know what will happen based on earlier experience. Every time you release an apple over Sir Isaac Newton, it will drop on his head. That's good.

The more users' expectations prove right, the more they will feel in control of the system and the more they will like it. And the more the system breaks users' expectations, the more they will feel insecure. Oops, maybe if I let go of this apple, it will turn into a tomato and jump a mile into the sky.

Jakob's Law of the Web User Experience states that "users spend most of their time on other websites."

This means that they form their expectations for your site based on what's commonly done on most other sites. If you deviate, your site will be harder to use and users will leave.

9. Opening New Browser Windows

Opening up new browser windows is like a vacuum cleaner sales person who starts a visit by emptying an ash tray on the customer's carpet. Don't pollute my screen with any more windows, thanks (particularly since current operating systems have miserable window management).

Designers open new browser windows on the theory that it keeps users on their site. But even disregarding the user-hostile message implied in taking over the user's machine, the strategy is self-defeating since it disables the Back button which is the normal way users return to previous sites. Users often don't notice that a new window has opened, especially if they are using a small monitor where the windows are maximized to fill up the screen. So a user who tries to return to the origin will be confused by a grayed out Back button.

Links that don't behave as expected undermine users' understanding of their own system. A link should be a simple hypertext reference that replaces the current page with new content. Users hate unwarranted pop-up windows. When they want the destination to appear in a new page, they can use their browser's "open in new window" command -- assuming, of course, that the link is not a piece of code that interferes with the browser’s standard behavior.

10. Not Answering Users' Questions

Users are highly goal-driven on the Web. They visit sites because there's something they want to accomplish -- maybe even buy your product. The ultimate failure of a website is to fail to provide the information users are looking for.

Sometimes the answer is simply not there and you lose the sale because users have to assume that your product or service doesn't meet their needs if you don't tell them the specifics. Other times the specifics are buried under a thick layer of marketese and bland slogans. Since users don't have time to read everything, such hidden info might almost as well not be there.

The worst example of not answering users' questions is to avoid listing the price of products and services. No B2C ecommerce site would make this mistake, but it's rife in B2B, where most "enterprise solutions" are presented so that you can't tell whether they are suited for 100 people or 100,000 people. Price is the most specific piece of info customers use to understand the nature of an offering, and not providing it makes people feel lost and reduces their understanding of a product line. We have miles of videotape of users asking "Where's the price?" while tearing their hair out.

Even B2C sites often make the associated mistake of forgetting prices in product lists, such as category pages or search results. Knowing the price is key in both situations; it lets users differentiate among products and click through to the most relevant ones.

Source: http://www.useit.com/alertbox/9605.html

2009-01-15T22:11:00.004+05:00

The Golden Ratio in Web Design

By Jarel Remick

Math is beautiful. Does that sound a little strange? I sure thought so when I first started designing. Math is so rigid and often times boring, or so I thought. You would be surprised to find out that most aesthetically pleasing designs, works of art, objects and even people have math in common. Specifically the Golden Ratio, also known as the divine proportion, which is designated by the Greek letter Φ (phi). This tutorial will cover the anatomy and layout of a website and how the Golden Ratio relates.

Anatomy of a Web Page

The elements of a web page are like organs; they are vital to a properly functioning and aesthetically pleasing web page.

These are the main elements of a web page. There are many different ways to organize them but this is perhaps the most common basic layout used online.

Container

All web pages use a container and for the same purpose; to contain page elements, however the way it is accomplished varies. For example, the body tag or a div is most commonly used. In the past, even a table has been used (do not use a table as your page container, it is a depreciated method). Think of the container as the external walls of your house in which your bedrooms, kitchen, living room, etc. are then placed.

Types of container:

Liquid: Expands to fill the width of the browser window.
Fixed: A specific width you choose which does not change regardless of browser window size.

Header

The header isn't really a specific element although some may consider it to be. It is more generally used in referring to the top section of your web page where your logo, navigation, tag line, etc. are located. Many people prefer to keep these elements contained within a div for easier page styling, element separation and/or element containment. The header would be considered a container so it would have two types to choose from: liquid or fixed as mentioned above.

Logo

Your logo is your identity and branding. The most common placement for the logo is within the header, aligned left. We read from left to right, top to bottom, so your logo will most likely be the first element your visitors look at.

Navigation

Page navigation is one of the most important elements; your visitors need it to use your website. It should be easy to find and use, which is why it is almost always located within the header or at least near the top of the page. Sometimes both types of navigation are used for high content websites.

Types of navigation:

Horizontal: A series of links displayed inline, usually referred to as "navigation".
Vertical: A series of links displayed as a vertical stack, usually referred to as "menu".

Main Content

As everyone knows (or should), content is king! When people visit your site, this is the element they will be looking for primarily. It should be the main focal point of a web page so visitors find what they are looking for quickly.

Sidebar

The sidebar is the element with your secondary content such as advertising, site search, subscription links (RSS, Twitter, Email, etc), contact methods, etc. This element isn't necessary although many websites use it. It is most often right aligned but can be left aligned or both (two sidebars) so long as it doesn't disrupt main content viewing. For websites that use horizontal AND vertical navigation, the sidebar is often replaced with the vertical navigation element.

Footer

The end of a web page should always use a footer to let your visitors know they have reached the completion of your web page. Like the header, the footer isn't really a specific element but more of a containing section. Within your footer will be copyright, legal and contact information primarily. It's a good idea to include a few links to the most important sections of your site such as the top of the page, home page, contact page, etc. Some websites use this area as an opportunity to mention related material or other important information.

"Whitespace"

This is any area of the web page that is not covered by typography or other content. You may feel the strong urge to fill as much empty space as possible but don't do it! Empty space is just as important to a good web page design as the content to be used. You can see how the NetTuts site uses empty space very effectively to help guide visitors through content, create page balance and give a good sense of content separation.

So that covers the anatomy of a web page. Now lets take a look at how the Golden Ratio relates to these elements.

The Golden Ratio and Using Grids

Remember earlier when I said math was beautiful? We perceive visual appeal based on ratio (i.e. The Golden Ratio). For thousands of years artists, designers, architects, etc. have either intentionally or unintentionally used a common ratio in their work that is aesthetically pleasing. What is the magic number? 1.62 (actually 1.618...) I won't get into the origins of this number but I will tell you how to use it.

Using the golden ratio is very simple. Lets say you want to find the width of your Main Content and Sidebar columns. You would take the total width of your content area (we'll use 900px for this example) and divide that by 1.62. As shown in the example above we divide 900px by 1.62 and get 555.55px. We don't need to be exact so we will round it off to 555px. Now you know your main content element will be 555px wide and your sidebar will be 345px! How easy is that?!

But wait! The fun doesn't stop there. You can also apply the Golden Ratio to other element's width in relation to its height or vice-versa. This produces aesthetically pleasing elements with the Golden Ratio proportions.

Using Grids

If you're like most people though, you won't want to pull out a calculator every time you want to use this ratio. To simplify the process, we can use a simple grid. All you do is divide your width and/or height by thirds.

Each division can be even further reduced by thirds, producing a more detailed grid. If you read the previous article "A Close Look At the Blueprint CSS Framework" you will see that the Blueprint CSS framework uses a detailed grid system. Not only does the grid make designing easier and faster but also it creates an aesthetically pleasing layout! If you aren't already using a grid when designing, now may be a good time to give it a try. You can download a grid template for fireworks, photoshop and more from http://960.gs, which is another fantastic CSS framework that uses grids.

As you can see, NetTuts abides by the Golden Ratio quite well. The top one third of the page is divided again into thirds to show how even the header section breaks down into smaller increments of thirds, very close to the Golden Ratio. No wonder why the NetTuts design is so appealing!

If you're new to design I highly encourage you to find some popular sites, evaluate their element layout and how it abides by the Golden Ratio and grids. Then take some time to practice using the Golden Ratio with your elements and placing them in your layout using a grid.

Source: http://nettuts.com/tutorials/other/the-golden-ratio-in-web-design/