[Vm-dev] Removing most of the windowing code

[Igor Stasenko]

On 29 November 2016 at 19:30, Ronie Salgado <roniesalg at gmail.com> wrote:

>
>
>> well, the problem is that we're in a bit more difficult situation that
>> Lua.. in Lua there's no processes/contexts..
>> and if we would want implement an external message send i.e.  send
>> message - get result, things not so straightforward as in Lua.
>> it's all because it was never designed to be run in a host environment
>> and be open from that end.
>> that's why it is much easier to implement FFI, that C -> smalltalk API.
>>
> Currently, I am going to focus on making a standard interface for
> initializing the VM, loading the image, passing the command line arguments,
> running the interpreter and shutting down. This seems easy to do, and it
> allows me to unify the platform specific versions of the VM.
>
> For more complicated stuffs such as calling Smalltalk from C, or a
> standard interface for defining primitives in C( for doing things such as
> moving unessential VM plugins outside of the main VM source code tree). We
> should have a proper discussion on the mailing list.
>
> My priority with removing the windowing code is getting OSWindow working
> well in Windows. Currently it is having conflicts with the main loop
> provided by the VM, which makes it unusable.
>
> right, this main loop concept is a first thing, that goes in a conflict
with host application, that wants to control what it wants to run or not
and when.



> 2016-11-29 14:22 GMT-03:00 Igor Stasenko <siguctua at gmail.com>:
>
>>
>>
>>
>> On 29 November 2016 at 14:43, Ben Coman <btc at openinworld.com> wrote:
>>
>>>
>>>
>>>
>>> On Thu, Nov 24, 2016 at 10:06 PM, Ronie Salgado <roniesalg at gmail.com>
>>> wrote:
>>>
>>>>
>>>> It is still needed to define a proper interface for embedding the VM.
>>>> This interface should be a single .h file, with the highest level of
>>>> abstraction possible. There are some other issues such as potential name
>>>> clashes, and the fact that the VM symbols are public by default. At the
>>>> bare minimum, it has to provide functions for initializing the VM, passing
>>>> command line arguments, loading an image, running the image, and shutting
>>>> down.
>>>>
>>>
>>> I don't know if its really suitable, but since Lua is the incumbent
>>> embedded gaming language, perhaps echoing it would make it easier to
>>> substitute ours for theirs.
>>> https://www.lua.org/pil/24.2.html
>>>
>>> cheers -ben
>>>
>>>
>> well, the problem is that we're in a bit more difficult situation that
>> Lua.. in Lua there's no processes/contexts..
>> and if we would want implement an external message send i.e.  send
>> message - get result, things not so straightforward as in Lua.
>> it's all because it was never designed to be run in a host environment
>> and be open from that end.
>> that's why it is much easier to implement FFI, that C -> smalltalk API.
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>>
>
>


-- 
Best regards,
Igor Stasenko.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20161129/0e6f54e2/attachment-0001.html>