|
|
 Originally Posted by rockula
The Browser- I bought this because I thought WebOS would support most of the websites that I frequent for my job. I interface with with a lot of secure servers that run off of an extension aspx. I was told this is some sort of .Net or Java server language that is out dated. However, these are big "insurance company servers" (I'm an agent and have to log in to rate and service policies). HTML5 is the future, but I can tell you that insurance companies aren't going to make the switch any time soon because most of their agents use PC's.
Safari doesn't jive at all with my Insurance company interfaces. So, doing my job on a "Mac" is impossible. I use a Mac, but I run Parallels Desktop for my work stuff. Even Firefox on the Mac side doesn't work. WebOS is no better. It's no supported usually, but that doesn't mean it won't work. Usually if it gives me that error message, it won't work.
For sites that ARE supposed to work, insurance or not, I find myself pressing on a link with nothing happening. OVER AND OVER this happens. It's like the TP isn't responding to my tough. I recalibrate the touch constantly, and it's usually never off.
I frequently visit ESPN and Yahoo Sports to manage my fantasy line ups. Yahoo's site is the worst to deal with, but I can deal with it. Still lots of unresponsive finger touches. Another site I like to visit is Youtube. That can be hit or miss as well. I also enjoy Cracked.com for a good laff, and I enjoy reading the Huffington Post. Both sites can be NIGHTMARES to navigate. I notice that the progress bar at the top of many of these sites fails to actually complete it's progress or only gets 15% into the progress and stalls. Also, Facebook is horrible to use. I was told that the WebOS is the only OS that has the Facebook app written specifically for it, but I'm not at all impressed with the performance. If it's not "touch inputs" that fail to respond, it's a wacky layout that doesn't make sense. But bottlenecking of online data is what bothers me the most because it's prevalent on MANY sites. This tells me that something may wrong with the WebOS, or site, or...
First .aspx is ASP.NET which is the .NET version of Microsoft's Active Server Pages. This is the Microsoft server side scripting engine. Since .asp and .aspx are server side scripts they only return flat HTML which is supported by all browsers, including webOS. Now that flat HTML can include some client side scripting such as Javascript, which should also be supported by the webOS browser but those imbedded client side scripts are not dependent on the file extension and could cause the same problem if embedded in .php, .html, or any other type of file.
That said some site developers decide that it is easier to check what browser a person is using and block all browsers that the developer was either too lazy to test for compatibility, or just didn't want to put in the effort to make it work. Sadly if they do this, then you just have to use a supported browser. Thankfully this is getting a bit more rare, but nothing would **** me off more back in the day than hitting a website that required Internet Exploder when I was not even using a Windows platform much less IE.
Originally Posted by rockula
Networking/WiFi: For instance at church... there are 750, per service, half of which know the password to access the router. So, it can be slow. I have no problems on my Android phone, but on the Touchpad, it's a nightmare. I'm a musician at church, and many times I need to quickly connect to a website that we use called planningcenteronline to download sheet music to my TP. I usually do this before service, put the set list I'm playing in order in a folder on Box.net, then I open each pdf file one after another, so that as we finish with a song, I can load the next easily. Half the time, I can't access any info on Planning Centers site, because the browser is frozen. But I could turn around and pull it up on my phone in no time usually. So, what is it with the Wifi of the TP that makes it totally bottleneck and fail?
Working with Documents: I work with PDF files a lot, which is no problem on the TP. Sometimes, if I'm singing a song, I'll type up the lyrics in Word and email them to myself, or upload them to Box.net. But when I pull one up using QuickOfficeHD, not only are the fonts different, but it seems like I can't properly edit the file. If I send it to myself in all caps, it shows up "proper" and there is no way for me to adjust margins, highlight the text and change it to all caps, nothing. In fact, pulling up the "select/select all" field at times is a trick. It'll flash, but go away immediately, or if I cut/copy something, it won't copy. It's literally like anything you pull up in QuickOffice HD is uneditable and ends up crashing the app. Another AMAZINGLY annoying thing is when I download a file that I email myself, like this .doc file, or even a PDF... most of the time, WebOS doesn't know what to do with it, and the MIME type is not recognized. This forces me to use file manager app to go in and find the file (which usually gets renamed to something crazy), rename it, add the extension, then open it. And sometimes it still won't work. It just doesn't make sense!
I also don't like the way that WebOS handles "selecting/highlighting" things. I don't understand if I select a paragraph how to move it? Apparently you can't. You always have to cut and past. You can't drag a "selection" around. That is just WACK to me!? I swear, for "cool" as WebOS supposedly is, it's shockingly limited all the same.
As others have mentioned, it doesn't matter if you use the Touchpad, iPad, or Android Tablet. None of them can compete in the document editing dept. with a full blown OS with a mouse and full function KB. I have an Android phone and I find it just as hard to edit stuff on it as the TP. I do agree that QuickOfficeHD leaves a LOT to be desired but that is not the operating system. I think there is a better paid office application available, but I have not used it and can not vouch for it.
Originally Posted by rockula
I've got half a mind to totally reset it back to factory and install only a few of the Preware tweaks... but NOT UberKernal or Govnah. I personally think my TP performs worse OC'd.
Considering it seems that most of your problems (at least those that are not browser related) seem to be related to some touches not being detected. I had the same problem until I ran the 3.04 doctor to reset everything. I used it for about 24 hours without installing anything and the problem seemed to be fixed. Then I installed everything recommended by the starter guides EXCEPT Uberkernal (though I did install Govnah before I decided not to install UberK) and the problem came back but MUCH less than before. I am currently in the process of uninstalling and testing the recommended tweaks one by one to see if maybe one of them is causing this issue. Perhaps you actually SHOULD doctor it back to factory 3.04 settings and then see if you have better results too.
I think you might be expecting a bit much out of any tablet for editing purposes, but I don't think anyone should have to put up with a touch screen that doesn't detect touches properly. That said I have submitted some mock ups for additional features for the built Virtual KB that should help the editing problems a LOT.
You can take a look at my proposed version of the virtual KB HERE.
I hope I have helped in some way.
|
|
|
