Regarding Qt, I’m sure that Boost has many advantages over it. Some (and the most important) Boost libraries have been approved for incorporation into the C++0x spec. So, in the future, that code will be pure C++. Some of these, for example: threads and shared pointers. And regarding platforms, if you can use a GCC on it, it should work (it works on many compilers, but complicated platforms like embedded usually run GCC). I’m very experienced with Qt, but I prefer to use it just in GUIs…what would happen if I want to run the library in some ARM9 architecture like this one: http://www.friendlyarm.net/products/mini2440 ? I will have to compile Qt in that platform…it won’t even fit into my disk storage…and I’m not sure, but for some platforms like these you have to use QTopia instead of Qt, which now is something like discontinued.
I think that a good option would be to use just the set of Boost libraries approved for C++0x. Regarding threads: I don’t know the implementations of the algorithms in Tesseract, but I’m sure that for certain operations it will be a pro to increment the granularity and parallelize with threads (instead of parallelizing the processes), at least to take advantage of certain particularities of hyper-threading. If some of you people have good experience on this, it would be interesting to me to share some thoughts because I'll have to face an optimization of a computer vision algorithm with that. Cheers, Andres -- 2010/4/11 MARTIN Pierre <[email protected]> > > Qt is a great library but it's not a good strategic choice > > - You need a license for commercial products (and the price is high) > Wrong. It's LGPL now. > > > - It doesn't target all C++ platforms > Almost all. Basically all linux, windows, and macs distros. > > > - You can't guarantee it'll exist and being maintained in 20 years > Same thing for any other. i doubt any current software will still "exist" > in 20 years, chances are most likely for everything to be rewrote adapting > to upcoming technologies. > > > - Some other technical issue list below > > Let's be less technical to expose my point of view: > > - If you want to do OCR this mean you have images, and you certainly > > have the lib to open them. Why include JPEG, TIFF or anything else > > functions? I already have this and it's so simple and fast to convert > > my image into a RAW 24 bits image array. > i partially agree here. As i said, libraries should not be used in the core > (Which can compile as standalone pure C++), but in the surrounding layer for > low-skill developers (A+B). > > > - Some platform doesn't like STL, some other BOOST, because we need > > very basic wstring (unicode), vector, map, no I/O, no thread we can > > offer to avoid STL, BOOST and really being compatible with all > > platforms > 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). > > > - Future is multicore processors, how take advantage of them? With an > > OCR it's simple, open 8 image and do 8 OCR at a time. Splitting OCR > > process for one image would be too complex and useless because on > > today processors OCR is fast enough for one image. > That's a perfect example where threading commes in handy, and the splitting > isn't that copmplex once we have the distinct workflows in mind. > > > - I don't want to reinvent an OCR, I want to reverse engineer > > Tesseract and rewrite only the OCR part. > Exactly. > > > - A "pure" C++ library can very easily being transpose in Java, C# or > > same family language. It's important for future : next Windows Mobile > > 7 machine can't run C++ code. Windows Azure prefer manage code. > > Android... I think future is managed OS. > Why transpose if the library is clean enough for making wrappers / > bindings? > > -- > 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]<tesseract-ocr%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/tesseract-ocr?hl=en. > > -- 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.
