Giraffe said:I've installed it on a Samsung Captivate i896 and everything that's supposed to be working at this point seems to be working. I was a little bummed to find that I'm not yet able to load my old flashcards and get flashing but I can wait, if I have to.
Giraffe said:The only thing that threw me slightly when I first opened the program was that I couldn't just start typing, I had to find the keyboard input button. A little later I found the setting to default to having the keyboard on program open. I would have thought that would be the default behavior.
Giraffe said:Other than that, it looks gorgeous, runs smoothly, and has not, at least to this moment, turned my phone into a smoking puddle of plastic and toxic metals. What's not to like?
hejincong said:There currently is no hardware "Search" button support. This is probably because there is none on iOS devices, but it would be nice if this put the focus on the text entry box, and popped up the keyboard.
benzhen said:if would be amazing to have volume key scroll for the reader (i dont have directional keys on my device are these supported?)
benzhen said:clipboard auto detect: there is this feature in Fora dictionary that will detect anything in the clipboard and open the app and look it up automatically.
knerz said:just wanted to say "Thank you!" I got an Android phone since this year and I was quite disappointed that only came across pleco after having decided to get a HTC Desire - if I knew that this wonderful app was only working on iPhone and that there virtually is nothing comparable out there I would have bought an iPhone. And now you guys did it! It's working on my HTC Desire as far as I can tell now. For me the two most important features are working smoothly: OCR and HWR - both at an extraodinary speed.
Thanks again! Looking forward to the stable version including the flash cards.
bodybag77 said:Looks very promising on asus eee pad , for me it was love at first sight:-D
Is there a way to decreasefont size to avoid wasting reading space on a big tablet screen?
Thanks for this new app!!
mikelove said:The directional keys are indeed supported, but yes, we probably should add volume too (though it seems like an increasingly high percentage of new Android devices are button-less, or nearly so).
mikelove said:This is a bit of a hack but it looks theoretically doable - basically we just run in the background and pop up something when we detect that the clipboard has changed. I'm wondering whether it might raise some hackles with Android Market, though - people could theoretically be putting passwords and such on their clipboard and they don't necessarily want those passing through our app.
sfrrr said:I can't believe it. I now own a license for every mobile platform i've ever owned. (I want to keep pleco on my new ipad 2, so I bought a new license for android today.)
benzhen said:therefore adding scrolling buttons on screen somehow might also be a good idea? i'd be perfectly happy with just the volume key scroll.
benzhen said:you should check out the app "Fora Dictionary." it is on the market and has a mode in which it sits in the background and waits for clipboard input. it shows up in the notification bar so the user knows whats going on and can switch it off easily as well.
benzhen said:that dictionary app also integrates with ereaders (Cool Reader being one) so that it will automatically pop-up when i select text in said ereader. that would be nice because of all the great ereader options i can have that you probably won't offer in pleco?
benzhen said:anyway, overall experience is WAY better than the early days of 2.0 on wm/palm!!!!
haraldalbrecht said:First, I'm really glad to see PlecoDict for Android being available with modest Androis OS requirements. That's great, after all the discussions. In the end, we now see the product coming along nicely and being deployable on recent devices. For me as a Galaxy Tab user an old dream has become true (albeit the tab may not be ideal for Beijing transport ). My old and dead Tungsten T has now a proper successor.
haraldalbrecht said:You are just at the beginning of the beta programme so I hope I'm allowed to ask nevertheless: what about a manual? What I would like to see is some context-sensitive manual which can optionally be installed side-by-side as an additional app. So it doesn't eat any space for those who do not require it.
haraldalbrecht said:From my own experience with an open source project where I did this I could offer the technology for free in the hope that it does not only benefit me but also others. You basically just need to include a small package (consisting of two classes implementing just a convenience manual launcher based on Intents). The manual itself is authored using an ordinary decent web browser in form of a self-contained single-file dynamic HTML wiki. For easy distribution you can pack this in a convenient (even multi-language) apk.
mikelove said:Not until the finished version - the UI is likely to change significantly (incorporating the changes we're in the midst of designing / implementing on iOS, most importantly the new merged multi-dictionary search feature) and we'd rather not have to create it twice.
mikelove said:Thanks for the offer - is this an Open Intents thing? I'm certainly interested in hearing more, but in general I'm inclined to rely on external intents for critical functions like this as little as possible, basically because of the strong possibility that we'll eventually be running this in some decidedly non-standard environments (BlackBerry, virtual machine on Windows, etc) where it may not be feasible to install / access those external packages.