New “ShareThis” Feature!

I’ve added a new feature to all posts on my site called “ShareThis”. You can now choose to share posts with friends on tons of different social networks and blogs, including Facebook, Twitter, Digg, Reddit, StumbleUpon, Blogger, and Google Buzz. You’ve probably seen these buttons on, like, every single blog ever written already, and I’m proud to announce that they’re now on my site as well. To try it now, simply click one of the share icons at the bottom of this post. I’m hoping that these share buttons will bring even more visitors to my site. Not only that, but these buttons are also a really fun feature that lets you share posts that you find interesting with your friends. Check it out! The default selection of networks listed under the posts is subject to change, as I may add or remove preset networks based on recommendations from visitors, as well as my own intuition.

How To Get Skype on a Non-Verizon Wireless Android Device

Skype Technologies S.A. logo

Image via Wikipedia

I don’t usually write how-to guides and tutorials on my blog, but this is a really cool (and useful) trick, and I just tried this recently on a friend’s AT&T HTC Aria phone, and it works. The reason that this is so important is because Skype Mobile  for Android/Blackberry devices  is currently exclusive to Verizon Wireless, and no devices (with the exception of the iPhone) on other carriers are supposed to have access to it. The software doesn’t work very well, but it’s better than nothing. Keep in mind that this is the “Lite” version of Skype, and it’s still in Beta. It’s really simple to do this, actually. You just need to go to the market URL for the unpublished Skype Lite Beta package, and download it to your phone. That being said, the application has a lot of issues, such as crashing, and it feels incomplete, so it may be better to just hold off on Skype mobile for the moment. For your convenience, here is a QR code to make downloading the Skype Lite Beta application easier for those of you who have a barcode scanning application on your Android powered device:

Clippy Public Beta 0.1.5 Released

I just released version 0.1.5 of the Clippy Public Beta. In this version, I made a ton of major interface improvements, in fact, I think you might not even be able to recognize it any more. There is a new settings menu, but for the moment, I am not allowing users to enable the settings, as some of them may cause serious problems, as they are not fully developed yet. I am speaking from experience, especially on the auto-start setting. Just trust me on this one, it’s not worth enabling those settings yet. I decided to disable them so I could rush out a new release, as the version in the market was gradually becoming archaic. Also, many additional abilities have been added, such as sending the clipboard/clippings as emails and text messages. If you’re wondering where the menus that were previously at the bottom of the screen no matter what went, they are now located in the context menu. You can access them by pressing the menu button. Also, you may notice that the icon in the applications drawer is now simply labeled “Clippy”. However, as you will immediately notice when you enter the application for the first time after upgrading, this is still a beta, and it’s not yet stable. I wish I could go into more detail about all the dramatic changes that I made in this new release, but I’m really tired at the moment, and I just got done working for hours on releasing a new version for you guys to play with. I’ll probably update this post later, and go into more specific details. Also, you’ll be glad to hear that I made no database changes at all in this version, so your data should be safe if you are upgrading from a previous version. Try the new version out, and let me know what you think! Screenshots coming soon!

New Clippy Release Coming Soon

I’ve been working hard on Clippy’s new look, and it’s getting better and more useful all the time! Expect to see a new major release in the Android market soon! There is still, however, some functionality that I don’t have implemented yet, that I hope to get working soon. However, I am unable to find any significant regressions in functionality since the current version in the market, so I don’t think I have much to worry about in terms of things not working right. However, I would like to get some more things working, and add some more features to the interface to make it easier to use. The interface is turning out really nicely so far. In fact, it’s getting so good that it might as well be a standalone text editor, as it’s quickly gaining quite a broad range of functionality. I was actually considering reusing a large portion of the code, and making another application dedicated to editing text, since they would share a common code base, but first I have to get more work done on Clippy.

UPDATE: I’m working on preparing the next iteration of the Clippy Public Beta for release right now. Expect to see it in the market soon.

Minor Clippy Regressions

I’m currently postponing the release of Clippy due to several small, but significant regressions that I am experiencing. I want to ensure that those of you who have downloaded and used a previous version of Clippy, such as the current version in the market feel comfortable using the new version that I am about to release. Because of some significant changes in the way I have Clippy written, such as using of XML-based menu resources instead of generating the menus using source code when the application runs, I have run into several problems that I am looking into. Rest assured, I will be releasing a new version of Clippy soon. However, at the moment, there are several regressions such as this one:

  • When there is no text in the text editor, the “Save”, “Edit”, and “Clear” buttons are no longer disabled. This worked perfectly while I was using menus generated using code, as I could set whether or not the menu items are enabled, however, when I switched to XML-based menus, attempting to set any attributes of the menu items results in the entire application crashing with a NullPointerException.

Once I get most of the regressions fixed, I will release an update of the code on the market.

UPDATE: I figured out how to set whether or not the MenuItems were enabled or not. Instead of using the findViewByID() method, I had to use menu.findItem().

UPDATE 2: Email sending now works properly, and I added a send button to the context menu of the “Current” tab.

Catch The Ball Resource Licensing

As you may or may not know, I licensed the source code of Catch The Ball under version 3 of the GNU General Public License. This is a free and open source license in the truest sense of those words. However, I completely forgot about the images and other resources used in the game, which are necessary in order to compile and play the game. Of course, it’s really easy to create similar images from scratch, but I decided to allow everyone to use and modify the images included with the game however they want to. Therefore, I am now licensing all images and other resources that I created under the Creative Commons Attribution 3.0 Unported License, which is also an extremely lenient content license. Although I’m not exactly sure what “Unported” means, the license is free, and I’m glad to let others use my work however they want to. If anyone with a legal background wants to clarify that, that would be great. Although I have a link to more information in this post, I’m going to attempt to summarize the license anyways. Basically, the license allows you to copy, distribute, modify, and transmit any of the resources in “Catch the Ball”, and you don’t have to pay me anything, what-so-ever in order to do so, as long as you give me credit for creating the resources. Giving me credit could be as simple as posting a link that looks something like “Dylan Taylor / CC BY 3.0” in a spot where users of the application that incorporates my work will see it, or simply mentioning that your application uses artwork by Dylan Taylor that is licensed under the Creative Commons Attribution 3.0 Unported License in your “README” file or included documentation. Anyways, here’s a Creative Commons badge that links to the full-page describing the license in more detail:
Creative Commons License

Clippy Public Beta is Up!

Clippy Public Beta is finally in the Android Market, and it doesn’t cost a cent! Go ahead and check it out, and let me know what you think! :) I’m particularly surprised at how well the artwork for this came out… I really didn’t expect it to end up as good as it did. Granted, the artwork could be significantly improved, I think it came out looking pretty nice. I’m going to update this post and add some screenshots, and I’ll add them to the Android market as well. I’ve been working on coding this for the past few days, and I really must say, I’m impressed with how well this is turning out. Perhaps this will turn into a really useful tool for power users. I plan on updating Clippy fairly frequently due to it’s extremely early state of development, so brace yourselves for a bunch of rapid user interface changes. Keep an eye out for the some of the following additions:

  • Additional text filters
  • Ability to view clipping information
  • Ability to edit the clipping without leaving the clippings tab and creating a new clipping
  • Additional clipping metadata such as “Creation Time” and “Last Modified”
  • Added clipping statistics, such as word count and character count
  • Ability to click URLs in clippings
  • Better clipping organization
  • The ability to rename clippings
  • And many more possible additions

EDIT: Here’s a QR Code to make downloading the public beta easier:

Clippy Public Beta Coming Soon

Clippy is almost ready to be released to the world, but there is still a lot of work left to do, and it can’t be done without the help of beta testers. Therefore, I’m soon going to be releasing a public beta version of Clippy that I will soon publish to the Android market. If you download and use Clippy, let me know about any bugs you find and feature requests you want. Clippy is a rather large project, and the beta is only scratching the surface of all the features I’m going to implement. Chances are, by the time I release the final version of Clippy, those of you who download the beta release will barely recognize it. I’d write more, but I’ve been busy getting this ready to put on the market. I’ll update you when the beta is up. Expect to see it within 24 hours.

FiOS WEP Calculator PRO is Back for Only $0.99!

If you’ve been wondering where the ad-free version of FiOS WEP Calculator went, well wonder no more! I removed the old Pro version because I originally published it for free, and I wasn’t making any money. I only made $0.57 so far with AdMob, and that’s almost nothing at all. I don’t really like charging very much for my applications, so the Pro version of FiOS WEP Calculator is now available for only $0.99! If you use/like this application, please consider purchasing the “PRO” version. The PRO version has all the same features as the Lite version, except it doesn’t have any advertisement, it uses absolutely no copy protection what-so-ever I don’t believe in locking down my products with worthless DRM — if you buy it, feel free to use it on as many phones as you want. I don’t mind that much if you pirate this application, but really, please consider purchasing it. It only costs $0.99, which is the minimum amount you can sell an application for on the app store, and of those $0.99, I only make $0.66 ($0.30 processing fee + 2.9% of sale price). Your purchase supports the development of this application, and all of the other Android projects I’m working on. I code applications as a hobby, and not just for profit. If you don’t pay for the application, please at least rate it and leave a positive review if you like it! Thanks for your support! :)

UPDATE: If you area looking for the free, but advertisement supported version, it’s called FiOS WEP Calculator Lite. Please consider purchasing the ‘Pro’ version to support future development. Thanks! :)