Great!
I'll give this a try.
Thanks.

-s

sent from my droid

On Sun, Dec 30, 2018, 23:19 Andrew Williams <a...@andywilliams.me wrote:

> Hi,
>
> For anyone still interested in this project but held back by the EFL build
> or runtime dependency then I have good news:
> * Our new default driver does not rely on additional libraries * :)
>
> We have moved to an OpenGL driver - using go-gl and glfw so all you need
> is the system libraries - and nothing for the app users to install.
> There are a couple of performance issues that we will be working on but it
> is currently capable of running all the apps that were written with the
> previous driver.
>
> I hope this is helpful to some folk - apologies for reviving the old
> thread.
> Andrew
>
> On Fri, 12 Oct 2018 at 23:01 Andrew Williams <handya...@gmail.com> wrote:
>
>> Hi,
>>
>> Ah I see what you mean. The cross compiled windows file will rely on the
>> efl library, but that can be packaged. This means that it would need to be
>> a bigger distribution than just the exe if you want all deps shipped (I’m
>> not too familiar with the windows terms yet).
>>
>> I’ll try and get a document up about distribution which can explain
>> better and be kept up to date.
>>
>> Thanks,
>> Andrew
>> On 12 Oct 2018, 01:54 +0100, R Srinivasan <s...@srin.me>, wrote:
>>
>> Thanks a bunch. I will give a serious "go".
>>
>> Background - a tool that is command line now. Developed on Linux but
>> typical user in Windows. Just cross built for windows. Want to add a
>> minimal frontend - simple dialog. Being like a calculator - don't want to
>> have elaborate "install" procedures. In the case of the cli - one .exe is
>> all it takes.
>>
>> will experiment and report back.
>>
>> srini
>>
>> On Thursday, October 11, 2018 at 3:54:29 PM UTC-4, Andrew Williams wrote:
>>>
>>> Hi,
>>>
>>> Great questions, thanks!
>>>
>>> 1. We can bundle in the libraries for Windows and for macOS - but on
>>> linux probably not (unless your app is LGPL/GPL due to a licensing issue
>>> that I have not found a better solution to). But distribution on Linux it
>>> is normal to depend on external libraries :).
>>> There will be a tool included to package final binaries, but I have not
>>> got it to a satisfactory level to share yet.
>>>
>>> 2. Yes, we should be able to do cross-compilation using the standard Go
>>> tools. There is the usual challenge of enabling CGO for a GOOS build, but
>>> beyond that it should be OK. It's easier than, for example, andlabs UI as
>>> we are not linking to OS specific functionality, just the libefl
>>> abstraction.
>>>
>>> Point 2 may change over time - as we may wish to add certain OS
>>> abstraction directly which may make cross compilaton harder.
>>>
>>> What I was thinking about, however, was creating some app metadata
>>> format and a centralised build server to work around both build and package
>>> distribution issues...
>>>
>>> I hope that helps,
>>> Andrew
>>>
>>> On Sat, 6 Oct 2018 at 11:41 R Srinivasan <s...@srin.me> wrote:
>>>
>>>> 1. What are the "distribution" considerations?
>>>>
>>>>     Considering Windows targets - can we have all the required
>>>> libraries bundled in the final executable?
>>>>
>>>> 2. Can the apps be cross built? i.e. Built on Linux for macOS and
>>>> windows`targets?
>>>>
>>>> thanks for pointers, srini
>>>>
>>>>
>>>> On Friday, September 14, 2018 at 1:17:00 PM UTC-4, Andrew Williams
>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Some time ago I realised that Go was a great language for building new
>>>>> applications, as I wanted to use something powerful but fast to learn. I
>>>>> also wanted a really simple to use GUI toolkit that worked cross platform 
>>>>> -
>>>>> this was a little more difficult to satisfy!
>>>>>
>>>>> The aim was to create an API that was:
>>>>>
>>>>>    - Simple to learn
>>>>>    - Great looking with theme options
>>>>>    - Truly cross platform with identical look across platforms
>>>>>    - Solved all of the complicated GUI challenges (threading, scaling
>>>>>    etc)
>>>>>
>>>>> And so the Fyne project was created https://github.com/fyne-io/fyne !
>>>>> The design language is basically material design and the rendering is
>>>>> currently EFL with support for Windows, macOS and Linux.
>>>>> It's entirely vector based (though you can draw a Raster space if you
>>>>> need) and scales beautifully.
>>>>>
>>>>> For a taste of what that looks like here you go :)
>>>>>
>>>>> [image: widgets-dark.png]
>>>>>
>>>>> It's now well into development and ready for people to get involved.
>>>>> There is a long way to go but it feels like a solid base.
>>>>> Instructions for getting started, if you need them, are at
>>>>> https://github.com/fyne-io/bootstrap/blob/master/README.md .
>>>>> If you want to know more we're also in the #fyne channel on the gopher
>>>>> Slack server.
>>>>>
>>>>> Thanks in advance for your thoughts :)
>>>>> Andrew
>>>>>
>>>> --
>>>> 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...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>> http://andywilliams.me
>>> http://ajwillia.ms
>>>
>> --
>> 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.
>>
>> --
> http://andywilliams.me
> http://ajwillia.ms
>
> --
> 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.
>

-- 
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