Re: [Pharo-users] Pharo and QT

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 wrote: > There is a way to make this into a small

[Pharo-users] Analyzing Fuel Problem

I had an object graph that was pulling in all sorts of unrelated classes when serialized with Fuel. I was trying to find the offending object, and came up with the following: ``` (FLAnalyzer newDefault analysisFor: root) clusterization globalsBucket ``` This worked, but I was wondering if that's

Re: [Pharo-users] Deprecation Warning

Thanks ! -- View this message in context: http://forum.world.st/Deprecation-Warning-tp4949096p4949098.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Deprecation Warning

World>>System>>Settings Tools>>Debugging>>Deprecation handling Raise a blocking dialog if true, then a dialog is popup for each deprecated method invocation hth On Fri, Jun 2, 2017 at 7:28 PM, Georges wrote: > Hello, > > Is there somewhere a setting to turn off the

[Pharo-users] Deprecation Warning

Hello, Is there somewhere a setting to turn off the Deprecation Warning debugger? Georges -- View this message in context: http://forum.world.st/Deprecation-Warning-tp4949096.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Porting Transducers to Pharo

Hi Stephane & Damien! The short answer is that the compact notation turned out to work much better for me in my code, especially, if multiple transducers are involved. But that's my personal taste. You can choose which suits you better. In fact, 1000 take. just sits on top and simply

Re: [Pharo-users] Porting Transducers to Pharo

Hi Stephane! This is a great news. We need cool frameworks. I am really curious how well it will work for others. =) - There is a package on cincom store to support the migration from VW to Pharo. FileOuter something. The name escapes my mind now. We updated it last year to help porting one

Re: [Pharo-users] [Deploy] Deploying application - New Best Practices?

Where can i find a current RFBServer? Right now, I don't want to blow away what's currently running as it is an image with data.. will figure out persistence later.. -- View this message in context: http://forum.world.st/Deploy-Deploying-application-New-Best-Practices-tp4948399p4949080.html

Re: [Pharo-users] Pharo and QT

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)

Re: [Pharo-users] Porting Transducers to Pharo

If I recall correctly, there is an alternate protocol that looks more like xtreams or the traditional select/collect iterations. On 2 June 2017 at 21:12, Stephane Ducasse wrote: > I have a design question > > why the library is implemented in functional style vs

Re: [Pharo-users] Porting Transducers to Pharo

I have a design question why the library is implemented in functional style vs messages? I do not see why this is needed. To my eyes the compact notation goes against readibility of code and it feels ad-hoc in Smalltalk. I really prefer square := Map function: #squared. take := Take number:

Re: [Pharo-users] Porting Transducers to Pharo

Hi steffen This is a great news. We need cool frameworks. - There is a package on cincom store to support the migration from VW to Pharo. FileOuter something. The name escapes my mind now. We updated it last year to help porting one application to Pharo. - I can help producing a nice document :)

Re: [Pharo-users] Porting Transducers to Pharo

To get the extension methods into the Transducers package, the following worked for me - edit the category to have the prefix '*Transducers-' 2710c2710 < !Number methodsFor: 'transforming' stamp: ' 2/6/17 15:38'! --- > !Number methodsFor: '*Transducers-transforming' stamp: ' 2/6/17 15:38'!

Re: [Pharo-users] Can we auto translate Python to Smalltalk?

Hello, Actually I did the opposite to be able to use Python 3 libraries from Pharo. It is not complete, but you may want to take a look at it [1]. Using this lib you can craft a Python 3 AST and generate its source code. I guess there is a way to access the AST of a Python program using the

[Pharo-users] Can we auto translate Python to Smalltalk?

Python and JavaScript are driving the movement to Dynamic Languages. In particular, Python is the language of choice to teach students programming in universities. So, Smalltalk stands to gain from this shift. We all know that Smalltalk has the best environment. But we lack the diverse code base.

Re: [Pharo-users] Porting Transducers to Pharo

Dear all, thanks for the many suggestions. I didn't had time to test all import/export ways yet. But for now, I can report on two: 1) NGFileOuter Unfortunately It raised several MNUs in my image. I'll investigate them later. 2) FileOut30 (VW Contributed) I was able to file out the code

Re: [Pharo-users] Morphic or forking bug?

Hi Horrido, It is very hard to follow what you are exactly doing or trying to do. Here is the simplest example I can think of that updates something in Morphic on a regular basis. StringMorph subclass: #MyClock instanceVariableNames: '' classVariableNames: '' package:

Re: [Pharo-users] Morphic or forking bug?

Sorry, I could be mistaken. I just checked my notes. The *0 asString* test failed once, but I've not been able to replicate it. I might've been working with an unclean image. So perhaps it is related to Morphic, after all. horrido wrote > Yup, they all fail. Interesting that * > 0 asString * >

Re: [Pharo-users] Morphic or forking bug?

Yup, they all fail. Interesting that *0 asString* fails. This means it has NOTHING to do with Morphic (or Morphic being thread-unsafe). Ben Coman wrote > On Wed, May 31, 2017 at 10:23 PM, horrido > horrido.hobbies@ > wrote: > > Can you try a few other variations... >[ [ true ]

[Pharo-users] Other halt messages

Hi I would love to have

Re: [Pharo-users] Porting Transducers to Pharo

There is a package for that NGFileOuter or something like that on cincom store. We used it for mobydic code. On Wed, May 31, 2017 at 6:35 PM, Alexandre Bergel wrote: > If I remember correctly, there is a parcel in VisualWorks to export a file > out (Squeak format). > >