March 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] OS question

by Pierce Ng

On Wed, Mar 05, 2014 at 09:21:05AM +0100, Friedrich Dominicus wrote: > Pierce Ng <pierce(a)samadhiweb.com> writes: > > I am a long time FreeBSD user. Right now an instance of my blog is running > > on Pharo 1.4 on CogVM on FreeBSD 8.x. > How did you build the Pharo VM? Used to need to patch the source. Here's an old post from me: http://forum.world.st/Building-Cog-on-FreeBSD-td3072348.html. Patching is no longer needed. Periodically, I build from source from both Git and SVN repositories. However, recently I'm somewhat confused which Git-based version to use, so I build from the SVN-based source. Basically, over time, I settled on this script, based on my experimentation and reading stuff I found on the net: #!/bin/sh ../../platforms/unix/config/configure \ CC="gcc -m32" CXX="g++ -m32" \ CFLAGS="-g -O -msse2 -DNDEBUG -DTIMER_HEARTBEAT=1 -DNO_VM_PROFILE=1 -DCOGMTVM=0 -DDEBUGVM=0 -DNOEXECINFO" \ --enable-mpg-mmx=no --enable-mpg-pthreads=no --without-npsqueak make There is some funny thing about the FFI: One particular version of the SqueakFFIPrims plugin works. But several other versions that I've built all fail. Also, NativeBoost doesn't work on FreeBSD. In terms of dlfcn.h constants such as RTLD_LAZY etc, FreeBSD is more like OSX than like Linux. (Or perhaps I should say OSX is like FreeBSD.) I have built a VM on FreeBSD in which "NativeBoost forCurrentPlatform" says "NativeBoostMac32" while "OSPlatform current" says "UnixPlatform" but the dynamic linking doesn't work yet. From reading assembly programming tutorials for FreeBSD, Linux and OSX, my current conjecture is around stack popping, but I've never done assembly programming for real on these Unixen, so this is just guesswork on my part. I hope NativeBoost will work on FreeBSD eventually. All the world's not just Linux, OSX and Windows. -- Pierce Ng http://samadhiweb.com/blog/

March 9, 2014

Re: [Pharo-users] OS question

by Pierce Ng

On Tue, Mar 04, 2014 at 05:25:20AM -0800, Sean P. DeNigris wrote: > Pierce Ng-3 wrote > > I am a long time FreeBSD user. Right now an instance of my blog is running > > on Pharo 1.4 on CogVM on FreeBSD 8.x. > > Cool! Pier? What's the url? Not Pier. Home-grown using Zinc. Uses Seaside to render the content. URL in my .sig. Right now that one points to the same combo running on Debian though. -- Pierce Ng http://samadhiweb.com/blog/

March 9, 2014

Re: [Pharo-users] Tiling Window Manager in 3.0: working but still issues with WorldMorph

by phil＠highoctane.be

And the keybindings are also kind of not working either. Help welcome. Phil On Sat, Mar 8, 2014 at 11:57 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > TWM works in 3.0 after some work on icons and updating menus. > > Gofer new > smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; > configuration; > load. > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > '3.0') load > > You can also use > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > #development) load > > but this will for sure change over time. > > There is the World management icon which is still there and it looks like > it can create worlds but switching between them just breaks havoc. > > Maybe should we just remove that feature from TWM as 3.0 doesn't seem to > be multiworld friendly. > > Nothing done on tests nor themeing (which appears to be not that working > well in 3.0 either due to theming changes); > > At least the thing is back :-) [I missed it...] > > Phil >

March 8, 2014

Tiling Window Manager in 3.0: working but still issues with WorldMorph

by phil＠highoctane.be

TWM works in 3.0 after some work on icons and updating menus. Gofer new smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; configuration; load. ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: '3.0') load You can also use ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: #development) load but this will for sure change over time. There is the World management icon which is still there and it looks like it can create worlds but switching between them just breaks havoc. Maybe should we just remove that feature from TWM as 3.0 doesn't seem to be multiworld friendly. Nothing done on tests nor themeing (which appears to be not that working well in 3.0 either due to theming changes); At least the thing is back :-) [I missed it...] Phil

March 8, 2014

Re: [Pharo-users] [Pharo-dev] Phratch one-click

by jannik laval

Hi Hilaire, Hum, probably this comes from there... Could you explain a bit more how to change it ? Cheers, Jannik 2014-03-05 11:19 GMT+01:00 Hilaire Fernandes <hilaire.fernandes(a)gmail.com>: > For event, how is it developed? > > I remember, when I started developing DrGeo I used the change/update > event mecanism. Then I dropped it for a simple linear top/down update of > the geometric tree model, it becames much faster after that. > > Hilaire > > Le 05/03/2014 10:44, jannik laval a Ã©crit : > > > > I think now that we need some profiling. > > Any expert for that ? > > > > -- > Dr. Geo http://drgeo.eu > > > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

March 6, 2014

Re: [Pharo-users] Configuration of Smalltalkhub

by Stephan Eggermont

And we have a green build. Anyone want to try it? Stephan

March 6, 2014

Re: [Pharo-users] Configuration of Smalltalkhub

by Damien Cassou

On Thu, Mar 6, 2014 at 1:07 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > - added a new baseline, referring to smalltalkhub instead of squeaksource > and ConfigurationOfSeaside3 with newer versions. Couldn't save it to the > repository though. I pushed your mcz -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

March 6, 2014

Configuration of Smalltalkhub

by Stephan Eggermont

I have taken a look at the configuration of Smalltalkhub and started making some changes to make it work in Pharo 3. - added a new baseline, referring to smalltalkhub instead of squeaksource and ConfigurationOfSeaside3 with newer versions. Couldnât save it to the repository though. - the same changes needed to be made to ConfigurationOfKaliningrad - ConfigurationOfSeasideRest is recent, but still refers to an older Seaside when I used 0.22 with Seaside 3.1.0 the image was able to load and get to the point where it expects to connect to mongodb. Remaining issues: - 2 versions of Mongo-BSON (30,31), Mongo-Core (26,35) and Mongo-Squeak (12,13) - 2 versions of Seaside-REST-Core (39, 52)

March 6, 2014

Re: [Pharo-users] some collection observations

by Werner Kassens

> I don't know what you are trying to achieve, but it looks like you want to do conversions. Have you considered this ? Hi Sven, yes, i have. i simply noticed this, when i tried to speed up a program and thought, i should mention it. werner

March 5, 2014

Re: [Pharo-users] some collection observations

by Sven Van Caekenberghe

Hi Werner, I don't know what you are trying to achieve, but it looks like you want to do conversions. Have you considered this ? (Bag with: 1 with: 2) asArray. (Bag with: 1 with: 2) asOrderedCollection. These both work. I personally never noticed or used #newFrom: As for #as: some people consider it not the cleanest way to do things. But since the API is there, it should work I guess. Sven On 05 Mar 2014, at 16:28, Werner Kassens <wkassens(a)libello.com> wrote: > Hi, > > 1. i do this in pharo 2.0: > b:=Bag newFrom: #(1 2). > OrderedCollection newFrom: b."works nicely" > Array newFrom: b."error" > the error happens because ArrayedCollection>>newFrom: inherited by Array expects a SequenceableCollection that has 'at:' implemented. but the first line of ArrayedCollection>>newFrom: says: > newFrom: aCollection > it would be more clear,if it would say: > newFrom: aSequenceableCollection > > 2. this also produces an error: > b as: Array. > because Object>>as: uses newFrom:. and since as: is a very general method, i'd guess that ArrayedCollection>>newFrom: should have an implementation that does not throw an exception. if changing a Bag to an OrderedCollection works, this should also work with an Array. or does this make much sense: <grin> > (b as: OrderedCollection) as:Array "this way it works" > > 3. withAll: does essentially the same as newFrom: and has the same problem with the argument naming. but Array>>withAll: is much much faster than Array>>newFrom:. try: > b:=Array new:100000. > [Array withAll: b]timeToRun. > [Array newFrom: b]timeToRun. > perhaps one could differentiate the two methods in such a way, that withAll: is the occasionally faster method that for some collections only accepts aSequenceableCollection as argument and newFrom: accepts any aCollection. This way also Object>>as: would work as expected. if one does not want to change this in my opinion slightly inconsistent behaviour, then <grin> it would make sense to implement > Array>>newFrom: aSequenceableCollection > ^Array withAll: aSequenceableCollection. > simply for speed reasons. and of course a consistent argument naming would be nice. > werner >

March 5, 2014