> > Thread will be required for sure, and please give me one platform for example > where Qt can't compile (And please, don't tell me some propriétarry os such > as old Nokia, because nothing would compile here. Even C++ CRT and runtimes > aren't there). >
Qt doesn't target Windows Azure (the cloud OS) and Windows Mobile 7 Include thread in an OCR would add so much complexity and is really not needed. OCR is not a very long process on modern computer. I think the simplest C++ code is the better, because we don't need a lot for an OCR. I do image processing for 15 years and sometime use STL string, vector and map. Nothing else is needed. You want to link on Qt (and it's a heavy piece of code) for using 1% (not talking JPEG/TIFF/... and thread support) Let the final developer decide what he want to use and how. Give him DoOCR method and let him choose is image lib, is threading model, is I/ O container (file, db, stream). Perhaps a two level lib can do the trick : CoreOCR only do OCR, absolutely nothing else. FullOCR gives an higher level with thread and image container lib and link with CoreOCR and Qt. Remi -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en.
