I look at my smartphone today and it has never felt as good as that CLIÉ or Axim.Overview: iReader is a e-book reader support online ebook libraries. I've rathered stick to webdev and make whatever I need as mobile responsive PWAs. ![]() I've never really had an impetus to push me to chug through the learning curve, plus I already knew it didn't have to be that stupid. I think that's why I never really bothered to learn Android development. Completely unlike trying to figure out Android development today. NET Micro Framework were significantly much lower barrier to entry. If you wanted to develop for them, you either got stuck using J2ME (which was hot garbage), or you had to pay to get access to a C compiler. Actually, I experimented for a while with writing apps that ran on both desktop Windows and Windows Mobile and it was quite a fascinating experience. I could program for it in C#, and it was very easy, no more difficult than programming on desktop. The WiFi wasn't as flaky and it even had a basic 3D graphics accelerator. They had CF card slots for removable storage and peripheral devices. I switched to PocketPC/Windows Mobile shortly after that, though. You could roll it with your thumb to move menu selections up and down, then press it in to click. It had this beautifully tactile selector dial on the side. WiFi, this newfangled thing called Bluetooth that I could use to transfer files to the Nobody Else I Knew Who Had Bluetooth, digital camera (it wasn't too bad for the time), MP3 player, and a Memory Stick Pro slot for removable storage for all those MP3s and pictures. I had a couple of PalmOS devices back 20 years ago. They seem to have a different focus, and way too many clicks to go through. I just can't find anything with the same easy functionality on Android or elsewhere. When the time comes to input all of that into the corporate time system TimeSheet presents me with the total sum of all work packages for each day (and other ways, if I need them). I have a list of those projects and work packages in TimeSheet. The TimeSheet app does that in the simplest way possible - I do exactly one click, and it tracks the other project.ĭuring the day I may have to work on a number of projects, for shorter or longer periods. I may be working on project 1234, then someone wants me in a meeting on project 6566 work package 312, and my time app must keep track of that. The needs I have for a time sheet app is to simply keep track whenever I change what I work on during the day. Palm had a set of "rules" for programmers as to how the UI should work - and one was that nothing should take more than 3 clicks, IIRC. But now it's just that TimeSheet application, and I'll probably continue using that for years to come. ![]() In the past I used the T3 for many things, with a wifi adapter it was my wireless email/network gadget, I used TomTom software for navigation, etc. So now the other one is the one I use - and the battery is still fine. I actually have two T3, the one I use now is one I bought new in 2004, the other one I bought used around the same time (that one has the Sanyo (I think) LCD, this one the Sony LCD).įor the second hand T3 I bought a Lithium Poly battery with slightly higher capacity and replaced the original one (there was a huge thread about the procedure on BrightHand at the time), and used that T3 most of the time for many years, until the battery gave out. It's still going strong, original battery from 2004. There's a TimeSheet application for PalmOS which I've never been able to replace with anything for Android or anything else. I still use my Palm T3 every day (well, every working day at least).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |