Saturday, December 14, 2013

RWD is short introduction to designing responsive web pages. It includes start code, some best practices and lots of pointers to information that will help you learn more about responsive web. It is written in a simple and clear manner keeping it short and to the point. The author focuses on the main point and you can read this book and try out lots of code in a day.

Some examples of what is covered in the book:
1. media queries like max-width, braille, handheld
2. screen, print interface
3. Different strategies to make responsive websites
Goldilocks Approach
The Fluid Approach
4. Design aspects
Desktop first v Mobile first
5. Media
Images and Movie responsive

Table of Contents
Instant Responsive Web Design
Instant Responsive Web Design
So, what is Responsive web design (RWD)?
Getting started
Quick start – making your first responsive web page
Step 1 – creating an HTML page
Step 2 – adding a stylesheet
Step 3 – making it responsive
Top 5 features you need to know about
The power of CSS Media Queries
Media types
Logical operators
Different strategies to make responsive websites
The Goldilocks approach
The Fluid approach
Desktop-first versus Mobile-first
Desktop-first
Mobile-first
Gotchas and best practices
Putting it all together
People and places you should get to know

Wednesday, December 04, 2013

Tuesday, November 05, 2013

Server Error in '/Forms' Application.

A potentially dangerous Request.Form value was detected from the client (Comment="...10:27 PM, <CustomerService@amc...").

Description: ASP.NET has detected data in the request that is potentially dangerous because it might include HTML markup or script. The data might represent an attempt to compromise the security of your application, such as a cross-site scripting attack. If this type of input is appropriate in your application, you can include code in a web page to explicitly allow it. For more information, see http://go.microsoft.com/fwlink/?LinkID=212874. Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (Comment="...10:27 PM, <CustomerService@amc..."). Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL: 1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" %> or: 2) Add the following section to the configuration file of your application: <configuration> <system.web> <compilation debug="true"/> </system.web> </configuration> Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode. Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Sunday, November 03, 2013

Sessions. Unless you use 'sticky' load balancing, you will have to have some way of sharing session state between servers. This probably means storing session data on either shared storage, or in a DB.

File uploads and replication. If you allow users to upload files, or you have a CMS that allows you to upload images/documents, it needs to cater for the fact that these files will also need to find their way onto other nodes in your cluster. However, if you've gone down the shared storage route mentioned above, this should cover it.

DB scalability. If you're using traditional DB servers, you might want to think about how you'll implement scalability at that level. This may mean coding your app so you use one connection string for reads, and another for writes. Then, you are free to implement replication with one master node handling the inserts/updates cascading the changes to read only nodes that handle the bulk of the work.

Middleware. You might even want to go down the route of implementing some kind of message oriented middleware solution to completely hand off business logic functions - this will give you a great level of flexibility in how you wish to scale this business logic layer in the future. Although initially this will be a lot of complication and work for not a great deal of payoff.

Saturday, October 12, 2013

DisadvantagesWrong invoice Support in Germany Support and Customer Service does not understand English Servers are old and frequently go down Customer Service do not acknowledge their server issues Not easy to transfer between servers

Saturday, October 05, 2013

The HTC Inspire 4G with its 4.3 inch touchscreen and 1.0 GHz processor is a fantastic device for daily use. On paper, the Inspire 4G is overshadowed by many dual-core devices, but once you have root access on this device, the possibilities are endless. My prime for rooting include sluggishness of the device, more than 10 apps installed by service provider AT&T, speakerphone not working (needs patch), inability of HTC to release ICS update.
Thanks to a rooting kit known as the Advanced Ace Hack Kit, HTC Inspire 4G owners will never have problems in rooting their phone again. Using this method will not only root your device but also SIM-Unlocks your phone as well as letting you gain S-OFF on your phone.
Features:

Much smaller firmware flash to obtain the exploit – comparatively very fast processing.

Warnings

Do not attempt this procedure on any other device other than the HTC Inspire 4G. Using this procedure on a non-compatible phone can result in damage.
Certain builds of HTC Sense 3.0 will necessitate downgrading to earlier versions in order for the Advanced Ace Hack Kit to work. Check the manual included in the package for the versions. The Advanced Ace Hack Kit performs the downgrade automatically but, in the process, your phone data will be completely wiped; so, make sure you create backups of your important phone data including : messages, app data, phone book (sync with google contacts)

Requirements

HTC Inspire 4G running stock ROM (not a custom ROM)

A PC running Windows 7, Vista, XP, or XP Home

If you have Droid Explorer, remove it.

Remove HTC Sync.

Remove your phone’s drivers from your computer if the drivers are installed.

Disable all system utilities such as antivirus and firewall programs before extracting the Advanced Ace Hack Kit.

If you have any Apple program running in the background or as a service, stop it.

Do not run any other program while the Hack Kit is running.

My idea : use Linux machine (I used my Ubuntu)

Instructions

Download the Advanced Ace Hack Kit from here or here (aahk-13012012.zip, md5sum: d04975c6d085419c7c15f6d1934f7852) and save it to your PC.

Extract the downloaded ZIP file and place the contents inside a single folder.

The package includes the HTC USB drivers for your phone. Use the installer file inside the “toolswindrivers” subfolder located within the extraction folder to install the drivers. You may need to reboot your computer after installing the drivers.

Enable USB Debugging on your phone. You can do this by heading to Settings > Applications > USB Debugging. Make sure that there is a check mark beside that option.

On your phone, go to Menu > Settings > Connect to PC and set the default mode to “Charge only.”

Connect your phone to your PC via USB cable in charge-only mode. Use the USB port that is directly connected to the motherboard. Do not use the USB port on the front panel. Do not use a USB hub. Do not use a USB extension cable.

Open the folder where you extracted the Hack Kit files to. Depending on your Windows version, right-click on the script file and run it as Administrator (from the popup menu):

Sunday, February 17, 2013

Wednesday, January 02, 2013

Found out that Java 64-bit only works in Internet Explorer (IE). Mozilla and Chorme do not detect Java if 64-bit is installed. I had to uninstall all 64-bit versions and install 32-bit Java for all of the above browsers to detect.