As long as your having fun yourself, sounds like a good idea.  If you
manage a minimum viable product like example code, wider interest may
arise. Good luck.
cheers -ben

On Sat, Jun 3, 2017 at 4:00 AM, Dimitris Chloupis <kilon.al...@gmail.com>
wrote:

> There is a way to make this into a small task
>
> One of my experiments of testing my Pharo to Python bridge (What I have
> named project "Atlas") was to  build a QT hello world example. It created a
> problem because I was using python threads that QT does not like (it offers
> its own kind of threads) but after changing the code to use no threads, it
> worked.
>
> My bridge is not like UFFI where anything has to be wrapped because unlike
> C , Python is a dynamic language so there is no need for wrappers because
> Atlas allows dynamic execution of code. But of course there is the issues
> of data types and how they can be mapped to Pharo and the fact that PyQT
> free version is GPL and commercial is 500 dollars which sits of course on
> top of the commercial version of QT. So at the time I decided to not pursue
> it.
>
> I will give it a try and see how far it can goes, at worst I may offer a
> partial solution to using QT with Pharo. Then someone else can take it from
> there if there is genuine interest and expand it to more features.
>
> On Fri, Jun 2, 2017 at 12:01 AM Stephane Ducasse <stepharo.s...@gmail.com>
> wrote:
>
>> Hi dimitris
>>
>> We would love to have that. We could have a Spec binding and build
>> automatically applications in QT for people willing.
>> Esteban always wanted to have a Cocoa binding used the same way.
>> But this is large task
>>
>> Stef
>>
>> On Thu, Jun 1, 2017 at 2:44 PM, Hilaire <hila...@drgeo.eu> wrote:
>>
>>> A must for any serious dekstop application with Pharo, but it is a hudge
>>> task
>>>
>>>
>>> Le 29/05/2017 à 14:35, Dimitris Chloupis a écrit :
>>> > Is there an interest for working with QT from Pharo ? I make no
>>> > promises just something I was interested in trying.
>>>
>>> --
>>> Dr. Geo
>>> http://drgeo.eu
>>>
>>>
>>>
>>>
>>

Reply via email to