Nuance launches Dragon Go! for Android, available today for free

My Projects


To secure websites, we usually create user database and develop a login page to authenticate the user. If you have several websites, creating separate user login for each site is time consuming and not favorable to your users because they have to login to each site separately. OpenID was developed to solved such authentication hassles. It is an open standard for developers that enables them to authenticate their users in a decentralized manner. For end-users, OpenID allows them to consolidate their digital identities. Major web services that supports OpenID are Google, Yahoo and Facebook. If you use OpenID with your website, you allow users to login to your site using their Google, Yahoo or Facebook accounts. The authentication will be hosted by the OpenID provider, so no need to maintain the user details on your side except the Identifier returned by the provider.On this article, I will show you a ASP.NET sample code I made that use OpenID Authentication to verify Google Account. To accomplish the authentication, I used the C# library called DotNetOpenAuth. Here is the step-by-step procedure to implement it on your ASP.NET application.
| <form id=”form1″ runat=”server”>
Log in with
</div> |
Take note of the URL: https://www.google.com/accounts/o8/id – this is the unique OpenID URL of Google Account. 5. Include the following namespaces on your “Using” directive.
6. On the Page_Load & OpenLogin_Click, use the following codes
| using DotNetOpenAuth.OpenId; using DotNetOpenAuth.OpenId.RelyingParty; |
| protected void Page_Load(object sender, EventArgs e) { OpenIdRelyingParty rp = new OpenIdRelyingParty(); var r = rp.GetResponse(); if (r != null) { switch (r.Status) { case AuthenticationStatus.Authenticated: NotLoggedIn.Visible = false; Session[“GoogleIdentifier”] = r.ClaimedIdentifier.ToString(); Response.Redirect(“Main.aspx”); //redirect to main page of your website break; case AuthenticationStatus.Canceled: lblAlertMsg.Text = “Cancelled.”; break; case AuthenticationStatus.Failed: lblAlertMsg.Text = “Login Failed.”; break; } } }protected void OpenLogin_Click(object src, CommandEventArgs e) { string discoveryUri = e.CommandArgument.ToString(); OpenIdRelyingParty openid = new OpenIdRelyingParty(); var b = new UriBuilder(Request.Url) { Query = “” }; var req = openid.CreateRequest(discoveryUri, b.Uri, b.Uri); req.RedirectToProvider(); } |
7. Run the project. It should look like the following screens.
Log in with Now the Login page look like ….

Here’s an article for beginners in the practice of CSS Layouts, my reason for writing this one came from remembering the difficulty I once had position elements in CSS. After many frustrating attempts with relative and absolute position techniques I finally found the holy grail of CSS the “Float” attribute!
Ok so I’ve started to design my web site and have learnt how to position things using the position: relative and position: absolute; heres some examples of these below:

This works well, for basic positioning, but when your layouts become a little more complex as they always tend to do, tyring to position div’s within div’s using this method can become a real struggle.
Troubles can start when elements positioned as absolute can often position themselves to the entire page as apposed to the containing div, which can sometimes become a real nightmare.
Other simple tasks such as creating multiple divs in-line with each other for navigations etc can also involve many un-nessisary left right positioning values. So save yourself the trouble and crack open a can red bull and give yourself some wings!
The float attribute allows you to position objects to either the left or right of your page
tag, for example using the following section of code creates a page with two boxes one on the left hand side the other on the right.

Now this is the cool thing about Float, unlike the other positioning attributes it makes it so easy to position elements right next to each other. For example if your wanted to create a navigation menu that spanned left to right with say 5 different boxes, the Float attribute makes this so simple.
When you create a floated div tag using the following code: float: left;providing it fits into the length of the page it will position this flush with the side of a previous floated element, see below.

If you then wanted to start your next element below this new set of navigation boxes, simply add the “clear” setting to the next tag followed by the side setting of the previous float tag, the example above also shows how this set of elements was started on a newline using the clear: left; setting.
float: left; clear: left;
Also using the following setting on your element will drop it onto the next line underneith any left or right floated elements:
float: left; clear: both;
Float: center; does not exist
Don’t ask me why this has never been added to the CSS library but it is easily fixed, if you want to center a div within a float tag simply create a div without the use of the float attribute and use the following margin settings:
</div>
Margin auto does not work in IE?: Yes another IE related bug but heres the fix, for Internet Explorer you will also need to add the following to your CSS for this centering to work.
html, body {
text-align: center;
}
Float inside a Float
When adding a div tag with the float attribute within another div try to remember that the preceeding tag must also have the float attribute applied to it. Think of this tip as a fix for when you float something and it dosent seem to take effect on your layout.
</div>
compatible with Wii Menu version 4.2 only, for older versions see index
:
Wii’s softmodding process has been updated to include an application called multi mod manager. This one app now does the whole job for you, apart from a few button presses the whole thing is pretty much automated. It’s now more difficult to get it wrong than it is to get it right!!
I’ve also included cios249 version 19 into the packs for all Wii softmods as well as a mod of Wadmanager, called yet another wad manager mod which enables you to batch install a number of wad files. Especially useful for those doing safe upgrades of the system menu.
uLoader has also been updated to version 4.9c. Another reason for doing a new post about this is because a bug in how 4.9A handled the uloader config file was causing a number of hard drives that worked before to fail. This most notably affected the buffalo drives. This problem should now be fixed and those users may now want to upgrade to 4.9″.
Grab the files you need from here,
http://www.mediafire.com/?zogjimgyyqm
Install THE HOMEBREW CHANNEL FIRST…………….Then….
Any black screens or DSI stack errors that may occur during any of the steps below are 99% harmless. Simply power off your Wii and turn it back on, then continue from the step you were on.
1. Copy the contents of the pack you downloaded above onto the root of your SD card keeping the folder structure. Overwrite any existing files.
2. Power on your Wii and go into the Homebrew Channel.
3. Load Multi Mod Manager.
4. Press down then press A to select ‘Install and patch IOS36.’
5. Press A to select Express mode.
6. Loads of text will splash across the screen, when the process has finished press any button on the wiimote.
**If you were only able to install Bootmii to IOS, you may want to install Priiloader now and make a NAND backup of your Wii and familarise yourself with how to access
Priiloader before the system menu should you ever need to recover your Wii. Press Home to exit GP DOP-IOS if you choose to do this in order to return to the homebrew channel. When finished installing Priiloader you can continue from step A5.***
7. Press down so Remove stubbed IOS is selected then press A. When asked to check for stub IOSs press A. A number of stub IOSs will be discovered. Press B for ‘NO’ for all IOS files except 222, 223, 249 and 250. Which you should press A to confirm deletion of. Press B for all other IOSs. When the discovery of stub IOS is complete you will be sent to the MMM menu. If you were not asked to remove 222,223,249 or 250 move to step 7.1. Otherwise to continue to step 8.
If you accidentally delete any other stub IOS, it is not the end of the world. However when inserting an original game disc it may ask you to update your system. Should this happen to you visit the ‘safe upgrade to 4.2 page‘, and follow the instructions in that guide to recover your IOS files to the latest versions.
7.1 Run Any Title Deleter MOD from the Homebrew Channel. Choose IOS36 and press A. Go to System Titles and press A. Select the following IOS files one by one and select A to delete them one after the other: IOS222 IOS223 IOS249 IOS250 If any of the above are not listed, check ‘other system files.’ If they are still not to be found, do not worry, just ignore and move onto the next step below, the guide may still work. Press home to exit when finished.
8. Still in MMM, press up to select Run WAD Manager, then press A.
9. Press 1 to select all the wad files in the folder, then press A to continue.
If you get any install errors with the above wads, try step 7.1 above and then try again.
10. When finished press home on your wiimote twice to exit back to the homebrew channel.
You are now set for playing backups on your Wii.
Tutorial above with pictures, thanks to the poster Rob Mulally !!!
http://www.robmulally.net/my-wii-gui…ames-from-hdd/
Blaze tablet coming to developers this August
Back in February when Texas Instruments announced its ARM-based OMAP 4 system-on-chip ‘Blaze’ dev platform, we sort of figured it might be tablet-bound. And, here it is — Blaze is going to be a tablet! Not a shocker, but we’re glad to hear it, of course, since the tablet wars are hotter than ever and we love a good fight. So, what do we know about TI’s entry in the game? Hardware wise it’s going to be a 10.4-inch XVGA touchscreen LCD with two USB ports. Internally, we hear it’ll boast a 1GHz OMAP4430 cpu, 1GB of DDR2 RAM, WLAN, Bluetooth, GPS, and FM, plus external camera and pico projector modules. The tablet is not set for retail release, but for developers, but we’re still pretty excited to see this one come out to play.
UK-based ibtimes got their hands on the specs to one of Google’s new ChromeOS Netbooks that they’ll reportedly sell direct rather than through resellers (though it isn’t had to see mobile carriers subsidizing the product, especially Tmobile and Verizon in the US). They say Google may subsidize it as well, and they’d have to if they want to put the reported $300 price tag on the device.
The specs reveal some interesting directions that Google is going with their product. This particular model is based on an Nvidia Tegra-based ARM processor which has a lot of graphics horsepower. This is the same line of chips that Microsoft’s Zune uses and it will at the very least be able to play 720P video, but very likely will be able to display 1080P, at least on an external display. It will also be good for gaming – as much as can be expected for the ChromeOS which is mostly based on Web technologies.
Also interesting to note that Google is choosing an ARM platform over Intel (at least on this particular spec). As I’ve noted before, ARM has a efficient power-usage footprint compared to Intel’s Atom while providing similar performance.
Ibtimes also states:
It is also rumoured that the netbook will sport a 10.1-inch TFT HD-ready multi-touch display, and would come with 64GB SSD (mind you, not HDD), 2GB RAM and other bells and whistles such as WiFi, 3G, Bluetooth, Ethernet port, USB ports, webcam, 3.5mm audio jack, multi-card reader, etc.
“10-inch multi-touch display?” Maybe. If Apple’s tablet hasn’t used all of those by then. That spec is incredibly similar to what people have been saying about Apple’s tablet and if Google’s netbook has a Multi-Touch display, it isn’t a netbook at all. It is a tablet.
“HD Ready” means 720P to me. We’re looking at 1366×768 or thereabouts. As I said before the hardware will have no problem of playing HD content.
The 64GB SSD is a very interesting spec as well. Google’s ChromeOS is supposed to house everything in the Cloud, so the product should only need a few GB for the OS. Why the very expensive and expansive 64GB SSD?
Likely it will be used to store media offline – which means not everything will be streamed from the net. Also, your huge offline GMail databases will need to live somewhere as well. That being said, I’d think 32GB would be a good size for starters, especially when a 64GB SSD would likely be over half the cost of the product.
This is interesting not only because Google is effectively building a tablet and using ARM as opposed to Intel. It also means that Apple’s rumored tablet will also be competing with a Google product. These two once friendly companies are now looking to be the biggest competitors in the tech world.
With Internet Explorer you have only two options in applying CSS styles to your Static FBML application tab:
Although inlining the styles has appeared to always work with Static FBML application-tab pages, using calls to an external stylesheet seems to be only recently supported. I tested our HyperArts Static FBML Page, calling an external stylesheet, and it’s working fine. (If anyone does notice an issue, please let me know!)
The option that <em>doesn’t</em> work with Internet Explorer is using the style tag to embed your CSS rules:
<style type=”text/css”>
.some-class { margin:0; font-size:14px; }
#some-id { margin:0; font-size:14px; }
</style>
Although the above works in most other browsers, Internet Explorer ignores the contents of that tag.
If at all possible, you should choose the option to call an external stylesheet. You have much greater flexibility in applying — and making changes to — your CSS using a stand-alone stylesheet.
Read more: http://www.hyperarts.com/blog/category/web-coding-html-css-javascript/#ixzz0dYqppB5E
See how to use .htaccess and mod_rewrite to easily transform ugly PHP URLs into search engine friendly ones.
The coming together of PHP and MySQL to create dynamic pages is a wonderful thing. Instead of having hundreds of separate webpages, your entire site can be stored inside a MySQL database, and then retrieved and displayed using a handful of “template” PHP pages. This makes updating the site extremely easy, though the draw back is often that the resulting URLs for the pages aren’t very search engine friendly. For example:
http://www.mysite.com/articles.php?id=3&page=0
The “?” and “&” characters within the URL will stump many search engines, even Google, from crawling the page. What we want instead is something like:
http://www.mysite.com/articles/3/0
which makes the URL appear just like any normal directory structure, with which all search engines have no qualms about. So how do we go about transforming the parameters portion of a dynamic URL into such a setup instead? Here are the simple steps:
Step 1: Rename your template PHP page, such as “articles.php”, as “articles” instead, without any extension. We want to use this page instead to act as our new templates page.
Step 2: Herein lies the key to creating search engine friendly URLs- configuring Apache to interpret a particular file without extension as a normal PHP page instead. In this case, we want Apache to treat “articles” as if it were a PHP page. In your .htaccess file, add the below code inside it:
ForceType application/x-httpd-php
Notice how the word “articles” appear within the tag. By adding the above code to your site’s .htaccess file, it informs Apache to interpret “articles” as a PHP page. You can add additional files for Apache to treat as PHP pages by duplicating the above multiple times.
Step 3: With “articles” now being synomonous to “articles.php”, all that’s left is writing code within “articles” to identify the parameters portion of our new URL format, and store them as variables for further processing. As a reminder, our new working URL looks like:
http://www.mysite.com/articles/3/0
What we want is to create code that detects the “3” and “0” portion of the URL, as they are the parameters. Within “articles”, you could do the following:
//split the URL into parts using "/" as the delimiter:
$urlarray=explode("/", $REQUEST_URI);
//Contains "3", or the ID of the article to display:
$articleID=$urlarray[2];
//Contains "0", or the page number of the article in question:
$pageNum=$urlarray[3];
We now have two variables that contain the two parameters embedded inside our search engine friendly URL, which we can then pass into a MySQL query to display the corresponding article and page number. For example:
$getarticle=mysql_query("SELECT thearticle FROM articletable
WHERE id=$articleID AND page=$pageNum");
echo mysql_result($getarticle, 0); //displays article
And there you have it. As mentioned, the key to creating search engine friendly URLs in PHP and MySQL is in fact via Apache’s .htaccess file.
You will be trading a bit of convenience for your increase in privacy. How many steps you take, and on which occasion you take them will depend on your degree of trust 🙂
1. cookies – by disabling persistent cookies, you can prevent a website (or network of websites) to track your browsing pattern across multiple sessions. Each time you close your browser, any cookies you have received will be deleted. The main drawback is that this will disable any website auto-logins or specific settings you may have enabled.
2. toolbars – assistants, helpers and other gimmicks that you might want to install as a browser toolbar will periodically phone home while you are surfing the web. Some of this may be legit, some of it may not.
3. websites that you register for – Social networking sites or webmail services may be interested in following your activities while you browse their site. Which topics interest you, what opinions did you express, did you make any purchases?
4. geolocation of your ip address – great for targeted advertising, or to display varied content (e.g. languages) depending on a user’s location. You could consider using a proxy that does not relay your original ip address.
5. data harvesting at the ISP level – search for Phorm, Nebuad, Carnivore 😉
The list could go on for a while, many others can comment on the other breeches of security like… Flash cookies, user agents, hopcounts, private browsing, browser anti-phishing features, omnibox, anonymizers, hosts file anyone?