OCR project started 2 years ago. Then there was no usable exp/shiny. 
I still think that GUI frameworks for Go are in baby stages even today. 

Why would I resort to some C libraries when "syscall" works with Windows 
API well?


On Tuesday, January 16, 2018 at 3:45:22 AM UTC-5, Egon wrote:
>
> As for getting andlabs/ui compiling the easiest I've found is to use 
> msys2...
>
>
> i.e. installation from scratch:
>
> 1. http://www.msys2.org/
> 2. open msys shell
> 3. pacman -Syu
> 3.1 close from X
> 4. pacman -Su
> 5. pacman -S mingw-w64-x86_64-go
> 6. pacman -S --needed base-devel mingw-w64-i686-toolchain 
> mingw-w64-x86_64-toolchain
>
> But, yeah... it could be much, much easier.
>
> On Tuesday, 16 January 2018 10:41:23 UTC+2, Egon wrote:
>>
>> Not sure why you had to build a GUI separately, there are already a few 
>> libs, although some of them are still barebones...
>>
>> https://github.com/lxn/walk
>> https://github.com/andlabs/ui
>>
>> Of course there are also bindings for gtk and qt.
>>
>> On Monday, 15 January 2018 22:32:33 UTC+2, Tad Vizbaras wrote:
>>>
>>> Experience Report building OCR in Go:
>>>
>>> http://recoink.com/goreport
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to