MoboRobo Lets You Manage Your Android Smartphone & iPhone Never Like Before

Have you ever wished if you had a bigger screen for your Smartphone? Or, have you ever thought of integrating your Smartphone/Tablet PC to your computer so that you can simultaneously keep track of both these devices? If answer for both of these questions is ‘YES’, we hope it is your time to check out MoboRobo, which is an all-in-one solution to manage your Android Smartphones & iPhones! According to our experience, MoboRobo, the most useful tool for any Smartphone vendors, seemed to be a superb way to manage information in Android Smartphones [We used an Android Smartphone to understand MoboRobo], and it seems that each power-user of Android/iOS should check this completely free software for Windows PCs.

Read more »

Read More

Getting Started with Redis, Chatting Application

Most of my readers are expecting a better chatting system from 9lessons, I have been working with different technologies like Node, Socket.io and etc. Finally I found Redis, it is an open source advanced key-value database storage system, works like NoSQL database. Redis operations can be executed on the server side and reduce the client's workload. It is used for caches to speed up web applications

Read more »

Read More

AngularJS 1.3: a new release approaches

Heads up! A new Angular release is on its way. Since we plan to discontinues support for old browsers, we wanted to give you plenty of notice. As a secondary goal, this release will cover features to improve performance, and small API fixes that require small breaking changes and removal of apis that were previously deprecated. We're also making a change to how we number stable/unstable releases.

AngularJS 1.3 discontinues support for Internet Explorer 8

Why we're doing this:

• Modern browsers have evolved. Although our stats tell us that only a small percentage of users are on Internet Explorer 8, maintaining compatibility requires code that slows the rest of AngularJS down.
• In April 2014, Microsoft will be ending support for Windows XP, which means the end of support for the operating system most of Internet Explorer 8 users use.

Dropping support for Internet Explorer 8  will enable us to add more exciting features to Angular faster, decrease Angular's support burden, and cut our build time in half, while affecting only a very small proportion of users.

But what if your users still rely heavily on Internet Explorer 8? If your app needs to keep supporting older browsers, you have a few options:

• Keep using Angular 1.2.x.
• Use 1.3 and test (or if you're feeling lucky, hope for the best). The changes in version 1.3 won't be actively removing the hacks in Angular that make Internet Explorer 8 work. Most things that work now will probably keep working. But we're going to stop testing against Internet Explorer 8 in our CI server configuration. And we won't be fixing issues that are solely related to support for Internet Explorer 8 users.
• Look for commercial support outside the core project - the Angular ecosystem is now big enough that it wouldn't be shocking to us if a company started offering commercial support for Angular apps on IE8. (entrepreneurs: hint hint!)

Removal of deprecated apis

We are aiming at the promise unwrapping in Angular templates that we deprecated before v1.2.

New naming conventions for release versions

Since our long term goal is to move to semantic versioning (semver) for Angular 2.0, starting with AngularJS 1.3 we are replacing odd/even versioning we used previously with semver's pre-release notation.

What does that mean?

• The first stable release under the 1.3.x release train will be 1.3.0.
• Unstable releases toward 1.3.0 will use semver's pre-release notation (#.#.#-text.#) So, for example, 1.3.0-beta.1 and 1.3.0-beta.2 would be unstable releases.

New features for 1.3? Tell us what you care about.

We have a handful of things that we want to add, but we also want to hear from you! Since there is no good way to create a poll on GitHub, we are going to abuse GitHub a bit — if you care about a particular Issue or PR please post a comment with text "+1" on it. When the poll closes Mary Poppins will count the votes casted during the duration of the poll, *de-dupe* them and count them. (She'll then delete the vote comments and replace them with a summary comment.) The poll will close on January 2 and we'll use the results when deciding what to add to the 1.3 release.

OK. But when is Angular 1.3 actually coming?

We still have a few things lined up for the 1.2.x release train, and we want time to consider your votes. In spite of that you should see the first beta builds of 1.3.0 starting to roll out in January with the usual 1-2 week frequency.

Read More

On launching AngularJS 1.2: what we learned, what we're changing

You might have noticed something new since we launched 1.2... Now that we're caught up, we've begun pushing a new release every week or two to stay on top of things and keep the PR queue responsive. Unless there's something big or noteworthy, we're also no longer blogging about every release.

We learned a lot from launching 1.2. Here are our own notes on the 1.2 launch process, and what we'll be improving, in case you're curious too.

1.2 took way too long!

• The community uptake and increase in github activity alongside 1.2 caught us by surprise. We got swamped, and it took some time to get on top of the new volume of contributions. We're back in the flow now, with a few new folks on the core team, and we're taking steps to keep from getting overwhelmed.
• To handle this new volume, we needed better infrastructure in place. We were depending too much on manual processes; managing them took time that couldn't be spent on development. We've since improved the CI server, and added more automation to our launch processes and tests. We're also looking for more ways of automating and streamlining the release process.
• Some of our 1.2 goals turned out to be much more challenging than we anticipated. Animations, for example -- we realized that we needed to do something different, to make it really easy to use by thoroughly anticipating use cases, instead of putting the burden on the developer to implement. Getting it right took longer.
• Our release schedule wasn't all that well organized. Because the core team was overwhelmed, we often sat on fixes and features for too long, delaying the feedback loop with contributors. We're generating pre-release builds from the CI server and working on providing them via bower (either nightly or even after each commit) so that we can get feedback faster.

Underscore issues and the revert in 1.2.1

Shortly after 1.2, we issued 1.2.1, reverting a late change around hiding "private" properties prefixed with an underscore. We tested the change on hundreds of apps at Google, and with a few minor exceptions, nobody was affected, so we assumed it was safe to proceed. But we missed the real impact on apps elsewhere.  We reverted the change within a week, but we'd like to avoid making the same mistake again.

What steps are we taking?

• We're committing to release more frequently, reducing the feature pressure on any one release.  With a consistent release schedule, we'll have more time to fully consider the implications of the features that we add and the changes we make.  
• New pre-release builds from the CI server provide greater visibility into what we're working on. No surprises.
• Even if the impact seems small, no more breaking changes in the last release before a final major version. We learned this lesson and we really mean it.

Read More

Farewell, Disqus

tl;dr: We are removing Disqus comments from the AngularJS docs.

Problems with Disqus

Besides making it difficult to moderate off-topic or inflammatory comments, many comments are specific to past versions of Angular. We think the documentation should be versioned alongside the code so there's never a question of whether information is out of date.

Disqus has been great for allowing us to get feedback and allow developers to share tips about AngularJS, but we think there are better ways to do this now. You'll always be able to see the Disqus comments in past versions of Angular (<=1.2.2), but going forward, here's where we think the things previously posted in comments should belong:

Questions

Post questions to StackOverflow or the mailing list. They tend to get answered more quickly and stay up-to-date because of the active community there.

Bug Reports (Issues)

Bug reports should go on Github. It's useful to be able to see everyone's issues, workarounds, and the progress towards fixing them all in the same place. See the relevant section of the contributing guide for more.

Improvements to the Documentation

We think the best way to improve the docs is by directly improving the text. You can do this via the "improve this doc" button at the top of each page.

Read More

Htaccess File Tutorial and Tips.

After posting Understanding of Regular Expression article most of my readers are expecting .htaccess basics, and I did not find any useful article on Google first page results. Specially I love to write .htaccess file, using this you can easily configure and redirect Apache Web Server file system. This post will explain you how to create friendly URLs, sub domain directory re-directions and many more.

Read more »

Read More

AngularJS 1.2.1 - underscore-empathy available now

Our first stable release in the brave new post-1.2 world is available now.

AngularJS 1.2.1 underscore-empathy reverts hiding "private" properties, improves $compile for transcluded directives by making it possible for the child elements of a transcluded directive to access the transcluded directive's controller, and fixes a few minor bugs.

We introduced "private" properties (for properties prefaced with an underscore) in 1.2 thinking that this would be a fairly uncontroversial change. Oops! Apologies (and thank you) to the folks who filed bugs alerting us to the larger consequences in your code of making this breaking change. We've reverted this feature.

For full details in this release, see the changelog.

Thanks to the 33 superheroic individuals who contributed PRs!

Aaditya Talwai, andre, Andrei Korzhevskii, Ari, Ben Wiklund, Brian Ford, Caitlin Potter, Chirayu Krishnappa, Derek Peterson, Eddie Monge Jr, gdi2290, Igor Minar, James deBoer, Jeff Cross, Julien Sanchez, Martin Field, Mathis Hofer, Mauro Carrero, Miško Hevery, mkolodny, PatrickJS, Pete Bacon Darwin, Peter Kosa, Phillip Alexander, rsnapp, Sebastien Roul, smarigowda, Stéphane Reynaud, Tatham Oddie, Tobias Bosch, victorbjelkholm, Vojta Jina, xdhmoore.

Read More