mikelove said:Sure, it's probably just a bug - Pinyin renders with tone marks in Tuttle example sentences but with numbers in dictionary headwords, correct?
Yes, thats right.
mikelove said:Sure, it's probably just a bug - Pinyin renders with tone marks in Tuttle example sentences but with numbers in dictionary headwords, correct?
mikelove said:johnh113 - thanks for the detailed feedback.
On #1, the positioning of the audio button isn't ideal but I'm not quite sure how we could relocate it without having to redesign the entire flashcard user interface. Part of the reason for having it in that out-of-the-way location is so that we can have it stay in the same place in any test mode; sticking it in the middle of the screen might work in a self-graded test, but in fill-in-the-blanks it would often be covered by the drawing box and in multi-choice there wouldn't be enough room for it. Would it help any if we made the Settings / Flashcards / Left-handed interface option also swap the locations of the [X] and audio buttons?
As far as the audio button jumping around on other screens, if you turn on the "Arrows on top" option under Settings / General / Popup Reader, that should get the audio button to stay consistently on the bottom of the screen when you're not in flashcards. We normally put the popup reader arrow toolbar on the bottom of the screen and the commands like audio / > / etc on top because the arrow buttons are a bit more heavily- / repeatedly-used than the others.
#2 is a good point - going back to a previous card is sufficiently nondestructive that we don't really have to worry too much about people hitting it by accident, so we might as well trigger it automatically when you select the back tab. Forward turning into skip is one of those cases where I think the logical thing didn't turn out to be the right thing - it seems natural that you'd have one button to advance cards regardless of where you are in the session, but it would probably be better if we swapped it with the (always-disabled-when-you're-on-the-current-card) undo button so that once you got back to the current card you'd have to move over to start skipping. Though FWIW if you just tap on the lightbulb icon you'll go right back to the current card.
A bunch of people have mentioned wanting to set a new score for the card after "undo"ing - I think we'd want to have a separate popup menu for that rather than giving you the regular score buttons, though, otherwise it would be way too easy to get confused and end up applying a new score to the current card instead of the one you've backtracked to.
Not sure what's happening with #3 - sounds like a bug of some kind. #4 is probably just a case of the ABC not having a definition for that word - the system is fussy about Pinyin in those cases, so it could be that it's not remapping to the ABC because they used slightly different pronunciation / slightly different tones than the dictionary that you're remapping from. #5 sounds like another bug, as does #6 - audio playback being inconsistent is a long-running issue we're still trying to get to the bottom of. Bluetooth headset code doesn't have anything to do with us, though I suppose there might be some alternate audio playback mechanism in iPhone OS that we could use that wouldn't introduce as many delays - not sure which framework that would be, though.
As far as doing repetition-spaced cards early in #7, according to the "theory" behind spaced repetition study that's actually a big no-no; if you review at less than the optimal interval the cards won't necessarily be committed to memory as effectively. I suppose we could add an option to look just a day or two forward, though it would be a bit more work than just setting the clock forward since we'd have to deal with cases like cards that you just reviewed 10 minutes ago but remembered incorrectly and therefore left on a 1-day interval.
#8 visible scroll bars are a big iPhone UI no-no, though I suppose we break enough of Apple's rules anyway that one more isn't likely to get us into trouble - in general, though, I'd rather find some other way to indicate that there's more information visible. If you just adjust the font size in the popup reader by a few points, that might get it to a place where you'd clearly see the top half of the next line of text on the screen, though I recognize that's not a perfect solution.
#9 should be fixed once we add support for regular iPhone-style text selection (still coming, just very tricky).
On #10, does "relevancy" = frequency, i.e. you'd like the most common characters containing a particular component first?
#11 it's very very dicey to have two rows of buttons stacked on the screen - we did some experimenting with this early on in the design of Pleco on iPhone and it really didn't work well at all, it was way too easy to hit one button when you wanted to hit another. The tappable area of toolbars at the bottom of the screen should actually extend a bit beyond the visible top of the toolbar, though - if you tap a bit higher on the screen, do your taps still register?
On #12, it would certainly be possible to mix font sizes but I really hate the look of that on the screen - you end up with lines that are either inconsistently spaced (contains characters -> taller) or lines that are too widely spaced in some places. I guess we could make it an option but it's not something I'd be inclined to turn on by default.
Good point on #13, though to make this work correctly we'd need to remove those post-/ characters in the actual search.
johnh113 said:I use the audio on every card, many times many times per card as I drill the sounds and tones into my feeble brain. Swapping it with the [x], which have have never in my life used and could simply be eliminated, would be better for me when I'm using my left hand, but when my left hand gets tired I switch to my right hand and would want the audio button back on the right. Can you detect which hand I'm using and switch appropriately? If not, I don't want the audio button on top at all. I want it in a consistent position on the bottom.
johnh113 said:What I would like is for the audio button to find a home on one of the lower rows and stay there, forever.
johnh113 said:Yes, I use the lightbulb button for that purpose, but it still requires extra care to switch to the lightbulb while I'm using the forward button.
johnh113 said:Not me. I just want to get back the state I was in before I hit the wrong button. I can take it from there.
johnh113 said:I suspect the audio subsystem on the iPhone is inferior to what I'm used to the Palm. I know this isn't your fault but I though I'd bring up the audio problems anyway. ( I find the analog subsystems on the iPhone to be worse than the analogous functions on my Palm. The iPhone audio has problems mentioned above, the phone has trouble holding a signal as I drive from tower to tower, the phone has trouble reacquiring a signal after losing a signal (I often have to turn on airplane mode and then turn it off to get the iPhone to reacquire a signal), etc. I think they need to hire a new engineer to design their analog systems.)
johnh113 said:But for the vast majority of my cards, one day will be a very small percentage as I don't consider a card learned until it is over 72000. So if the card was supposed to come up in a year and instead came up in a year and a day I don't think it's going to do much harm. Even if it were supposed to come up in 4 days and instead came up in 3 or 5 or 2 or 6, I don't think it's much of a problem. It will come up again soon enough and I either get it right or wrong and the system will give it an appropriate score at that time.
johnh113 said:Yes, that will be nice. I find that I spend a lot of time looking up the word that I incorrectly guessed. The incorrect guess might have been a homonym, in which case the selecting the pinyin will be much faster than calling up the dictionary.
johnh113 said:The buttons all register fine. It was just a philosophical point that I would put infrequently used buttons either on the top toolbar or on the bottom toolbar. I would put buttons that are frequently used up a little higher.
johnh113 said:Well, we certainly have different font size at the beginning of the line when it is a head word, but I realize that is a special case. It would be interesting to see how bad it looks if the Chinese is font is just a few font sizes larger, like 24 on Chinese and 20 on roman or 24 on Chinese and 22 for roman?
johnh113 said:Question, is there a way so that at the end of a flashcard session it doesn't ask me if I want to continue with cards that aren't due? I never want to do that and would like it to just quit rather than offering to continue. I have my repetition spacing set up so that when I get a word wrong it falls to 50, so it will come up today when I restart the flashcard session which is what I always do until I've answered them all correctly.
johnh113 said:In list view after a search, if I tap and hold (accidentally, I'm just moving the screen and it's interpreted as a tap and hold) it adds a flashcard. I have added several unwanted flashcards this way, and have never actually wanted to add a flashcard from that screen. I only add flashcards from a dictionary or popup reader screen where there is already a +.
johnh113 said:On the list view after a search I find the relationship between the blue arrows on the right and the dian at the bottom to be very non-intuitive. I think that the previous (Palm) version of the toggling between dian and guo was better although still not great.
johnh113 said:In flashcards I often go to the dictionary to look up a word that I confused with the current flashcard. If the confused word has the same pinyin being able select the pinyin, which I know you are working on, will be helpful. But often times it's a different character entirely and I need to bring up the dictionary. This happens a lot for me. So what I would like is to eliminate the fan button that brings up the bottom menu, and just leave the bottom menu on all the time so that I can easily switch between the flashcards, dictionary, reader and settings. You can see a preview of this by going into flashcard mode before doing the reveal, and then hitting the fan button. The big buttons move up a little bit and the menu toolbar is consistently visible until I hit the fan button again. I like this, except I think it should be permanent and we just get rid of the fan buttons forever. And while we're at it, I would get rid of the add-on button and put that under settings, and perhaps put the permanent audio button in one corner of this row, either corner is fine with me. I would also move the 3 tabs to be bottom tabs for the big reveal, right and wrong buttons, and put those right above the permanent menu toolbar at the bottom. I know you hate this. But I've run with the menu toolbar visible and it seems to work just fine and looks fine too.
johnh113 said:Sometimes in a 4 character phrase the actual word is split into characters 2 and 4 (无情无义)or in characters 1 and 4 (乱七八糟)and the other characters are just intensifiers. It would be nice to have some way of selecting two characters that are separated to find that word. Or like 千变万化. I would like to be able to look up bianhua.
johnh113 said:In the Dictionary settings, entry list Chinese-English, I select "head pron def" and change the font sizes but changing the font sizes for pron and def has no effect. All 3 font sizes are determined by the head font size. If I look at the list in the character page under "chars", it uses the same font settings except this time the "def" font size actually has an effect. But the head and pron are determined by the head font size. In the same character section if I switch to words, all the font sizes are determined by the head font size. I would like in all 3 lists to be able to have the head, pron and def font sizes affect the font sizes, rather than having them all determined by head, or by head and def.
gato said:Is it possible to have the night mode be activated only in the reader? I think most people would only need the night mode for the reader. It doesn't make as much sense for the dictionary or flashcards. I personally find it easier on the eyes to read text against a black background on the screen because it reduces the glare.
gato said:If a user exits Pleco while reading a document in the reader, I think Pleco should automatically enter the reader in that document upon the next start. Right now, one would have to go through several menus to start reading the same document again. What do you think?
Any chance that you can implement this "restart with reader" feature for those of us who haven't been able to upgrade to iOS 4, yet? I haven't been able to find an easy jailbreak for iOS4, yet. There must be millions who haven't upgraded, particularly those of us have to use jailbreak iPhones in China.Now that iOS 4 automatically supports resuming to exactly where you were when you exited an app, I'm not sure if that's necessary anymore - if you don't open Pleco for a while and it's forcibly unloaded in the background, you might have to go through three taps (menu / reader tab / open last document) to get back to the reader, but at least in the very common interrupted-by-a-phone-call-case you can go back to where you left off very easily.
Joshi said:What I would really like to see is an option that displays my flashcard characters as a slideshow. I just recently got pleco on the iPad and it would help my studying a lot if i could place my iPad in the living room or office and just have the characters I'm studying flashing by for quick recaps when I'm doing other things.
gato said:Any chance that you can implement this "restart with reader" feature for those of us who haven't been able to upgrade to iOS 4, yet? I haven't been able to find an easy jailbreak for iOS4, yet. There must be millions who haven't upgraded, particularly those of us have to use jailbreak iPhones in China.
rcloud said:One small feature I'd love to see added is the option to have the pasteboard automatically look up the first word.
I know this seems like a small thing, but I am constantly switching between Pleco and other programs copying in sentences and this would make the process much more efficient. Since your thumb is naturally at the bottom of the screen to both change apps and to scroll through the sentence in the pasteboard, it is much faster for single sentences to just scroll to the words you need rather than to click on them.
Are you referring to "jailbreakme" that used the PDF exploit? I think it's been fixed by Apple.There was actually a very widely-distributed one a few weeks ago - can't remember the name though.
By "resuming to exactly where you were when you exited an app", do you mean iOS now allows you to automatically resume your place in a closed program upon restart? Or are you referring to resuming place in a program that's been put in the background under new iOS4 multitasking? If the latter, doesn't that mean you have to keep Pleco open forever (either in foreground or background) in order for this to work?Now that iOS 4 automatically supports resuming to exactly where you were when you exited an app, I'm not sure if that's necessary anymore - if you don't open Pleco for a while and it's forcibly unloaded in the background, you might have to go through three taps (menu / reader tab / open last document) to get back to the reader, but at least in the very common interrupted-by-a-phone-call-case you can go back to where you left off very easily.
gato said:Are you referring to "jailbreakme" that used the PDF exploit? I think it's been fixed by Apple.
gato said:By "resuming to exactly where you were when you exited an app", do you mean iOS now allows you to automatically resume your place in a closed program upon restart? Or are you referring to resuming place in a program that's been put in the background under new iOS4 multitasking? If the latter, doesn't that mean you have to keep Pleco open forever (either in foreground or background) in order for this to work?
That's unfortunately my current primary use.Which to me seems almost ideal, though if your primary use for Pleco is the document reader I suppose it might be preferable to default to that all the time.
gato said:I think Pleco will be more and more the reader app of choice for reading Chinese material. Will be nice if the reader's features get more fleshed out as we go on. There are readers that have already built in English language dictionaries, but no built-in Chinese dictionary yet. That'll be something to watch out for.
mikelove said:How about if we just added a Settings option in the next update to always open Pleco to the reader tab? (leaving you one tap away from reopening the last document) If we can't manage to get the whole thing implemented for 2.2 we might at least be able to do that.
ben_gb said:Maybe another way of doing this would be to have separate icons on the iphone home screen for the main functions of Pleco. EG one each for dictionary, reader and flashcards...?
This way, if you press the 'reader' button, it ALWAYS opens in the reader, and the same with flashcards and dictionary icons.
Not sure if this can be done on the iphone without splitting them into separate programs, or maybe each icon could call the main program with a different command line switch.