Archive for June, 2011

Latest News module for the opencart


Click to download the Latest News Module of opencart
Unzip the files andCopy and paste the files in their respective folders.
====================================================
FOR BACK END
====================================================
Paste the following

in the admin\view\template\common\header.tpl

======================================================

For more info : http://nepalrupak.blogspot.com/p/opencart.html

The Beauty of jQuery


I’ll admit, I resisted the use of frameworks. I believe in understanding the core structure and building from it. But after 2 years of working with heavy Javascript, I decided it was time to test out some frameworks to speed up my work.
There’s about 100+ Javascript frameworks out there. Picking one was no easy task. I took about 2 weeks to test out a handful of frameworks and ended up choosing jquery.

It’s tiny. no overhead. It also has a well supported community. Which means plugins galore. And it based off of CSS syntax. So there’s very little learning curve.

And the best feature of all… it’s cross browser compliant!!

No more MSIE hacks or special code for Opera. Your complex Javascript will work on all browsers. That’s a saving of 2 weeks worth of programming already!

With MooTools and Prototype, you have to be careful not to use the same variable name as their API. But not with jQuery. It is completely isolated in it’s scope and won’t affect any global namespace.

Yahoo UI and Dojo, well those are big boys. And i mean HUGE files. I prefer small footprint over bulky features. In fact, I’ll stab my eye out before I use Dojo… but I’ll digress.

For more info : http://htmltree.com/the-beauty-of-jquery/

Firefox Only Print One Page Bug


As a web developer, you will come across various problems related to your web site. A few weeks ago, I was told that my web page only printed one page. Strange, the screen displays a large table set that expands ~4 pages.

And the kicker, it does this on Firefox. Wow. After a few minutes of googling, I have discovered the culprit to be within CSS. Here was my simple solution.

Print.css

Create a new style sheet made for print. It’s best to include this right below all your other style sheets, so it can overwrite any elements right before the user prints.

1.<link rel="stylesheet" type="text/css" media="all" href="style.css" />
2.<link rel="stylesheet" type="text/css" media="print" href="print.css" />

Ok Batman, let’s override some code.

for more information click here : http://htmltree.com/firefox-only-print-one-page-bug/#more-6

The Internet Explorer 6 Countdown


IE610 years ago a browser was born.
Its name was Internet Explorer 6. Now that we’re in 2011, in an era of modern web standards, it’s time to say goodbye.

This website is dedicated to watching Internet Explorer 6 usage drop to less than 1% worldwide, so more websites can choose to drop support for Internet Explorer 6, saving hours of work for web developers.

 Check the Internet Explorer 6 usage around the world

fontsquirrel.com converting typefaces for @font-face


There are a number of formats for typefaces available which are used within @font-face. Typically, you may only have a typeface in one format, such as TrueType or OpenType. To provide as much support for your choice of typeface as possible in your Magento store, you will want to convert to a range of formats.

There are a number of online @font-face conversion tools that generate the necessary CSS and typeface files for you, including Font Squirrel’s FontFace Generator (http://www.fontsquirrel.com/fontface/generator).

@font-face support across browsers
There is surprisingly good support for @font-face across even older browsers.

EOT: Internet Explorer
The EOT (Embedded Open Type) format typefaces are supported in all versions of Internet Explorer.

TTF: Safari, Opera, Chrome, and Firefox
Safari version 3.2 onwards, Opera version 10 onwards, Firefox version 3.5 onwards, and all versions of Chrome support the TTF (TrueType Format) for typefaces in @font-face.

OTF: Safari, Opera, Chrome, and Firefox
Similarly to the TrueType Format, OTF (OpenType Format) is supported by Safari version 3.2 onwards, Opera version 10 onwards, Firefox version 3.5 onwards, and all versions of Chrome support the TTF (TrueType Format) for typefaces in @font-face.

SVG: iPhone and Chrome
The SVG (Scalable Vector Graphics format) is supported by the iPhone and Chrome browsers. SVG font files are specially formatted .svg files that contain vector graphics for each glyph and character of the typeface it represents, allowing for easy scalability.

WOFF: Firefox
The WOFF (Web Open Font Format) is currently supported by Firefox, but is in the process of becoming a standard for font formats across all major browsers, including those by Opera, Microsoft, and Mozilla.

CSS for @font-face
The CSS for using the @font-face attribute is relatively simple. In your new theme’s local.css file (in the /skin/frontend/default/m2/css directory), add the @ font-face  CSS at the top of the file:

@font-face {
font-family: ‘FranchiseRegular’;
src: url(‘../types/franchise-webfont.eot’);
src: local(‘?’), url(‘../types/franchise-webfont. woff’) format(‘woff’), url(‘../types/franchise-webfont. ttf’) format(‘truetype’), url(‘../types/franchise-webfont. svg#webfontgvcdROVT’) format(‘svg’);
font-weight: normal;
font-style: normal;
}

h1, h2, h3, h4, h5, h6 {
font-family: FranchiseRegular, sans-serif;
}

Useful handles in Magento


Some useful layout handles in Magento—the identifiers which allow you to single out a particular page or section of your Magento store are as follows:

XML handle  Page it identifies in Magento  XML layout file the XML handle is referenced in 
catalog_category_default  The default view for a category of products.  catalog.xml 
customer_account  The customer account page, shown when a customer is logged in to their account on your store.  customer.xml 
catalog_product_view  The product page view (that is, a page which displays an individual product).  catalog.xml 
cms_page  Pages created with Magento’s content management system.  cms.xml 
checkout_cart_index  The checkout’s ‘index’ (that is, default) view  checkout.xml 
cms_index_defaultnoroute  The default error page for the 404 ‘not found’ error  cms.xml 
cms_index_defaultindex  The homepage of your Magento store  cms.xml