Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-09 Thread stepharo
Maybe this could become some kind of pillar file... But things are changing a lot these days with SDL2 etc. It is converging - SDL2 stabilisation - Sparta integrated into Bloc - TxText optimisation - Bloc stabilization Thales guys are starting to use it. Stef Any

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-09 Thread p...@highoctane.be
Maybe this could become some kind of pillar file... But things are changing a lot these days with SDL2 etc. Any roadmap of these somewhere? Phil On Sat, Oct 8, 2016 at 7:03 PM, stepharo wrote: > Thibault > > you should talk also with Glenn and Alain to get feedback. They

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-08 Thread stepharo
Thibault you should talk also with Glenn and Alain to get feedback. They will visit us in Nov. Stef Le 7/10/16 à 15:14, Thibault Raffaillac a écrit : Thanks for these mails, that's actually very helpful! I am working on a shorter syntax for animations at the moment (than GLMAnimation,

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-07 Thread Ben Coman
On Fri, Oct 7, 2016 at 9:14 PM, Thibault Raffaillac wrote: > Thanks for these mails, that's actually very helpful! > I am working on a shorter syntax for animations at the moment (than > GLMAnimation, Viva, Bloc-Animation), and could not find a proper equivalent >

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-07 Thread Thibault Raffaillac
Thanks for these mails, that's actually very helpful! I am working on a shorter syntax for animations at the moment (than GLMAnimation, Viva, Bloc-Animation), and could not find a proper equivalent to requestAnimationFrame (i.e. that would be independent of any UI yet in sync with display, and

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread stepharo
ere is some interesting event loop stuff from Tcl. http://wiki.tcl.tk/2567 I wish we had some easy Tk UI building things in Pharo. Me too :) First I want Bloc to get out and be ready for integration to Pharo but it takes time. Spec is okay but not intuitive. As it is the only thing that

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread stepharo
Thanks Ben. I can tell you that we want to remove all such activeHand. :) One day it will come. Stef Le 3/10/16 à 12:25, Ben Coman a écrit : On Mon, Oct 3, 2016 at 6:08 PM, Ben Coman wrote: On Mon, Oct 3, 2016 at 3:49 PM, CodeDmitry wrote: a

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread stepharo
Le 3/10/16 à 17:25, p...@highoctane.be a écrit : Case in point, I am submitting a proposal here: https://devfest.be/blog/posts/cfp/ That's Google tech event here. I proposed to showcase MDL in Pharo along with workshop. Let's see how it goes... Nice :) Cyril will be happy :) Stef Phil

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
Cool. Now, I think we should do: WorldState MinCycleLapse: 16. So that we get a real 60FPS when moving windows around instead of the default 20 which is 50FPS, and not as smooth. Set it at 10 and it is too much, but hey, we have a lot of power these days. Try to set it to 200 and suffer :-p

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread CodeDmitry
You seem to have answered my question as I was revising it D: -- View this message in context: http://forum.world.st/Intro-to-Microsoft-COM-for-Smalltalkers-tp4917738p4917916.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
Also, check MorphicUIManager>>#spawnNewProcess UIProcess := [ [World doOneCycle. Processor yield. false] whileFalse: []. ] newProcess priority: Processor userSchedulingPriority. UIProcess name: 'Morphic UI Process'. UIProcess resume digging into doOneCycle, you'll find: #doOneCycleFor:

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
On Mon, Oct 3, 2016 at 6:47 PM, CodeDmitry wrote: > LOL (in GrowlMorph): > is: rect saneWithRespectTo: morphs > > ^(morphs anySatisfy: [ :morph | morph owner isNotNil and: [morph > bounds > intersects: rect]]) not > > for some reason I find this method name quite

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread CodeDmitry
LOL (in GrowlMorph): is: rect saneWithRespectTo: morphs ^(morphs anySatisfy: [ :morph | morph owner isNotNil and: [morph bounds intersects: rect]]) not for some reason I find this method name quite amusing :3 Let me guess; 1. "World defer: aBlock." defers the event to be called as

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
Case in point, I am submitting a proposal here: https://devfest.be/blog/posts/cfp/ That's Google tech event here. I proposed to showcase MDL in Pharo along with workshop. Let's see how it goes... Phil On Mon, Oct 3, 2016 at 4:43 PM, Offray Vladimir Luna Cárdenas < offray.l...@mutabit.com>

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
On Mon, Oct 3, 2016 at 3:00 PM, Thibault Raffaillac < thibault.raffail...@inria.fr> wrote: > I am not very fond of event loops in general, because they imply "many > inputs, one output" (process all pending events, then update screen). > For Morphic this is fine, because it displays on one

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread Thibault Raffaillac
I am not very fond of event loops in general, because they imply "many inputs, one output" (process all pending events, then update screen). For Morphic this is fine, because it displays on one screen, refreshing at/around its frequency. But there might be other screens, or network-output,

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
Here is some interesting event loop stuff from Tcl. http://wiki.tcl.tk/2567 I wish we had some easy Tk UI building things in Pharo. Spec is okay but not intuitive. As it is the only thing that exposes the myriad of various Morphs we have and shields us (somewhat) from the underlying details, we

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
A good trick is to use raw Display output. Display getCanvas drawString: 'hello' from: 1 to: 5 autoBoundAt: 0 @ 0 font: nil color: Color black. On Mon, Oct 3, 2016 at 12:25 PM, Ben Coman wrote: > On Mon, Oct 3, 2016 at 6:08 PM, Ben Coman wrote: >

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
There has been some serious refactoring occuring in these specific bowels of the beast. Phil On Mon, Oct 3, 2016 at 1:08 PM, Denis Kudriashov wrote: > Hi Ben. > > 2016-10-03 12:37 GMT+02:00 Ben Coman : > >> A further curiousity occurs to me. With

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
UIManager>>#defer: aBlock can be useful too. defer: aBlock " Evaluate the given Block in the UI thread as soon as there is nothing scheduled. Evaluate immediately when there is no UI" aBlock value For some fun, check also GrowlMorph 10 timesRepeat: [ (GrowlMorph openWithLabel: 'The time'

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread Denis Kudriashov
Hi Ben. 2016-10-03 12:37 GMT+02:00 Ben Coman : > A further curiousity occurs to me. With this being executed 20 times > a second or more, how can the active hand ever be anything other than > the primary hand? > Why isn't the active hand stored, all hands cycled through

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread Ben Coman
On Mon, Oct 3, 2016 at 6:25 PM, Ben Coman wrote: > On Mon, Oct 3, 2016 at 6:08 PM, Ben Coman wrote: >> On Mon, Oct 3, 2016 at 3:49 PM, CodeDmitry wrote: >>> a JavaScript timeout is a function that takes a block and a period of

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread Ben Coman
On Mon, Oct 3, 2016 at 3:49 PM, CodeDmitry wrote: > a JavaScript timeout is a function that takes a block and a period of time, > and after this period of time, puts the block at the end of the event > queue, to be executed as soon as the runtime is done performing the

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread p...@highoctane.be
And if this just for a graphical clock, a morph with step should be doing the trick. stepTime can be set as well. Phil On Mon, Oct 3, 2016 at 10:09 AM, Denis Kudriashov wrote: > Hi. > > 2016-10-03 9:49 GMT+02:00 CodeDmitry : > >> a JavaScript

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread CodeDmitry
Interesting, I got to play around with these, do some async morph animations. -- View this message in context: http://forum.world.st/Intro-to-Microsoft-COM-for-Smalltalkers-tp4917738p4917839.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread Denis Kudriashov
Hi. 2016-10-03 9:49 GMT+02:00 CodeDmitry : > a JavaScript timeout is a function that takes a block and a period of time, > and after this period of time, puts the block at the end of the event > queue, to be executed as soon as the runtime is done performing the tasks >

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread Dimitris Chloupis
of course Pharo has an event queue, we call them announcements. That implies however that you want the code to execute as soon as something else happens. If you don't , fork and delay should be enough. With fork you dont need to wait for othet tasks to finish to execute your code, it will just put

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-03 Thread CodeDmitry
a JavaScript timeout is a function that takes a block and a period of time, and after this period of time, puts the block at the end of the event queue, to be executed as soon as the runtime is done performing the tasks in front of it. I am not sure if Pharo has an event queue, so it's a bit

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread stepharo
+1 We want to support Windows! But ... 64 bits, FFI++, ARM ... well you know. Gimme 10 Millions or just one million and the situation will be really different. Stef By the way I am all for COM for Pharo, the issue is that 2/3 of our community are MacOS and Linux users , I dont even remember

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread Ben Coman
On Mon, Oct 3, 2016 at 2:52 AM, CodeDmitry wrote: > @kilon.alios > > [1] > I like C++/CLI more than C# because it is very refreshing to use a > language capable of using managed memory and unmanaged memory. > > I am too used to being in languages where garbage collection is

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread p...@highoctane.be
Ok. Fine points. Want to contribute? Easy: https://pharo.fogbugz.com/ Even more easy: join the association @ http://association.pharo.org/ Being using it for serious stuff and make money out of it? Join the consortium : http://consortium.pharo.org/ Discover some little interesting gem or way

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread Dimitris Chloupis
you dont need to have a lot of experience to contribute, even with zero experience as a coder if you understand the basics you can at least contribute class comments. Contribution wise Pharo is quite flexible and if one is lost in the process people are more than happy to help him/her out. When I

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread CodeDmitry
Contribution is something I've been thinking about for quite some time because it's interesting how a lot of software is declared "open" but make it not obvious what you can do to help, or at least participate, or just take a glimpse at the code to see if something stands out. I am a believer

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread Dimitris Chloupis
I don't speak for the pharo community but even when I was new to smalltalk back 4 years ago if I have read a comment like "Smalltalk is dead, why are we studying this useless language" I would keep my distance from that person. Because a) calling something "dead" in software is stupid b) calling

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread p...@highoctane.be
On Sun, Oct 2, 2016 at 8:52 PM, CodeDmitry wrote: > @kilon.alios > > [1] > I like C++/CLI more than C# because it is very refreshing to use a > language capable of using managed memory and unmanaged memory. > > I am too used to being in languages where garbage collection

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread CodeDmitry
@kilon.alios [1] I like C++/CLI more than C# because it is very refreshing to use a language capable of using managed memory and unmanaged memory. I am too used to being in languages where garbage collection is forced on you and everything must be done via new or stack types such as Java, most

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread p...@highoctane.be
I would for sure second that. I am using COM for dealing with this thing: http://www.sparxsystems.com/ about all day long a couple days a week. Bridging this with Roassal/Moose for additional visualisations would be super (I am going to look at that one in the coming weeks to help with the

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread Dimitris Chloupis
Well first of all what you linked supports my claim that 2/3 of Pharo users are MacOS and Linux users which I based on another survey which pretty much verifies what you linked. Second the vast majorities of libraries out other for any programming language are cross platform so I am willing to

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread Esteban A. Maringolo
2016-10-02 10:57 GMT-03:00 Dimitris Chloupis : > By the way I am all for COM for Pharo, the issue is that 2/3 of our > community are MacOS and Linux users , I dont even remember the last time we > had a Windows only topic in the mailing list. Modern languages generally >

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread Dimitris Chloupis
By the way I am all for COM for Pharo, the issue is that 2/3 of our community are MacOS and Linux users , I dont even remember the last time we had a Windows only topic in the mailing list. Modern languages generally avoid using OS specific libraries, the last exceptions be C# and Swift and C#

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread Dimitris Chloupis
Well that is not fair because C++ CLI is basically C++ .NET which is another language altogether baring some resemblance to C++. And you dont need C++ CLI to sit on barrier of runtime and compile , C++ can do this just fine. I found this recently trying to experiment at whether its possible to

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread CodeDmitry
To be fair, C++CLI is quite a pleasure to code, it's a very refreshing technology that sits nicely on the barrier of runtime and compiletime, similar to Objective C; eg still has access to unmanaged resources, while still having managed resources in contrast to Java/C# which kinda go one step

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread Esteban Lorenzano
> On 2 Oct 2016, at 07:09, stepharo wrote: > > ;) > > > btw are working on a com lib for pharo because we were discussing it with > esteban yes, Pablo already has a prototype working :) Esteban > > > > Le 2/10/16 à 04:09, CodeDmitry a écrit : >> Just made this image,

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-02 Thread John Pfersich
Hey, all you have to do is reboot your computer (often). Sent from my iPhone > On Oct 1, 2016, at 22:53, Dimitris Chloupis wrote: > > Ah the ugliness of Windoom programming has not changed since the last time I > tried to learn MFC 20 years ago.it melts my eyes. > >

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-01 Thread Dimitris Chloupis
Ah the ugliness of Windoom programming has not changed since the last time I tried to learn MFC 20 years ago.it melts my eyes. COM is an IPC tool, Windows registry is still a horrible idea. No connection with Smalltalk whatsoever . And of course we don't worry about memory leaks. On Sun, 2 Oct

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-01 Thread stepharo
;) btw are working on a com lib for pharo because we were discussing it with esteban Le 2/10/16 à 04:09, CodeDmitry a écrit : Just made this image, I thought it would be fun to share :3 (Yes there are a few memory leaks there due to no SysFreeString to match SysAllocString, but

[Pharo-users] Intro to Microsoft COM for Smalltalkers

2016-10-01 Thread CodeDmitry
Just made this image, I thought it would be fun to share :3 (Yes there are a few memory leaks there due to no SysFreeString to match SysAllocString, but regardless... http://i.imgur.com/Fz36SHU.png COM to Microsoft Windows seems to be like Smalltalk to Smalltalk Runtime, with Object Browser