On 24 November 2016 at 19:55, tim Rowledge <[hidden email]> wrote:
In Pharo we did a special OSWindow layer, that allows platform-independent access to host window setup & manipulation etc. There are multiple drivers , each for own platform/implementation, like SDL2, as well as a special NullWindowDriver, that simply passing all UI-related requirests to /dev/null .. This is done so, to ensure that image could run fine even if VM is missing host window support or can't find any plugins etc, since historically too much code in image is done with assumption, that its always there.. In that case, we can always switch to null-window driver so all user-code would still function without knowing that there's actually no host window created etc. tim Best regards,
Igor Stasenko. |
In reply to this post by Ronie Salgado
On Thu, Nov 24, 2016 at 10:06 PM, Ronie Salgado <[hidden email]> wrote:
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. cheers -ben |
On 29 November 2016 at 14:43, Ben Coman <[hidden email]> 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. Best regards,
Igor Stasenko. |
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. 2016-11-29 14:22 GMT-03:00 Igor Stasenko <[hidden email]>:
|
On 29 November 2016 at 19:30, Ronie Salgado <[hidden email]> wrote:
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.
Best regards,
Igor Stasenko. |
On 29 November 2016 at 19:42, Igor Stasenko <[hidden email]> wrote:
that's why, for instance i was pursuing the idea of implementing process scheduling in a language itself, leaving very small part of required logic on VM side - mostly stripping a logic that switches process(es) to specially registered 'interrupt' process, when signal from semaphore arrived, while leaving the rest of logic on hands of image-side implementation. Best regards,
Igor Stasenko. |
On Wed, Nov 30, 2016 at 1:49 AM, Igor Stasenko <[hidden email]> wrote: > > > > On 29 November 2016 at 19:42, Igor Stasenko <[hidden email]> wrote: >> >> >> >> On 29 November 2016 at 19:30, Ronie Salgado <[hidden email]> 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. okay. thanks for the insight. >>> >>> 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. >> > > that's why, for instance i was pursuing the idea of implementing process scheduling in a language itself, leaving very small part of required logic on VM side > - mostly stripping a logic that switches process(es) to specially registered 'interrupt' process, when signal from semaphore arrived, while leaving the rest of logic on hands > of image-side implementation. Would it make sense to mix that in with DelayScheduler running at priority 80? Use the same Semaphore that is already signalled from the VM. cheers -ben |
In reply to this post by Igor Stasenko
Whats so special about pharo context and process and how is that related to embedding pharo ?
On Tue, Nov 29, 2016 at 7:22 PM Igor Stasenko <[hidden email]> wrote:
|
On 29 November 2016 at 22:51, Dimitris Chloupis <[hidden email]> wrote:
in short: scheduling , and top-level infinite loop.
Best regards,
Igor Stasenko. |
Free forum by Nabble | Edit this page |