- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Roassal 1.28

by StÃ©phane Ducasse

Thanks alex and others. Now did you have a look at Athens? Because you have vector graphics inside the image **now**. And this is working. Stef > Dear Fellow, > > A couple of weeks ago we have released the Roassal visualization engine. Many of you gave us feedback and we are deeply grateful for this. > > Since we released the first version, we have closed 25 issues [*]. Many things are left to do, especially to satisfy all the requirements from the Moose community. > > We are currently working on an HTML exporter for Roassal. We know this is a highly wanted feature. In a couple of weeks we should be able to deliver it. > > Since the first release of Roassal, we have worked very hard on it and we will continue to do so. > > Thanks to all of you! > Alexandre, Vanessa, Juan Pablo > > [*] http://code.google.com/p/objectprofile/issues/list?can=1&q=status=Fixed%20c… > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

June 4, 2012

Re: [Pharo-project] ClassBoxes... bitrotted, or usable?

by Jan Vrany

Hi - having a class Selector that get evaluated into a symbol. You can then achieved selector namespaces, which does not incur a cost at execution. I do not understand the idea. Could you give an example? Cheers, Jan > > Cheers, > Alexandre > > > On Jun 1, 2012, at 10:55 AM, Frank Shearar wrote: > >> I mused with a colleague about how I'd like to see "lexically scoped >> monkey patching", and he pointed me to some guys that want to add that >> to Ruby (http://timelessrepo.com/refinements-in-ruby) Note the >> inspiration for their work: ClassBoxes! >> (http://scg.unibe.ch/research/classboxes) >> >> I remember reading the paper years ago, and started working through it >> again now. Something that's not clear to me is this: does ClassBoxes >> require VM-side changes? (Because it changes the method lookup, after >> all, searching packages for methods before working up the inheritance >> tree.) If so, how invasive are they? If not, do we have a ball-park >> estimate of how much work it would be to update ClassBoxes to a more >> recent Squeak/Pharo? >> >> I'm more than happy to do the dogwork. I'd just like to know whether >> I'm signing up for months of work or not. >> >> Thanks! >> >> frank >> >

June 4, 2012

Re: [Pharo-project] mixing open and closed source within Pharo

by Igor Stasenko

On 3 June 2012 18:01, Phil (list) <pbpublist(a)gmail.com> wrote: > On Jun 3, 2012, at 11:31 AM, Marcus Denker wrote: > >> >> How do people do it with Java? Java .jar files are as easy to decompile as Smalltalk bytecode... >> > > ProGuard (http://proguard.sourceforge.net/) is a popular method. Â In its obfuscation phase it will rename most class and method names (i.e. anything that doesn't need to be externally visible) to meaningless names so MyClass.MyMethod becomes something like a.a. Â It can also generate a mapping file so that when bug reports / crashes occur, the developer can map the gibberish names back to the original names. Â Before the obfuscation phase, it has optimization and shrinking phases to eliminate code that doesn't need to be included for release (debugging code etc.) > so, what prevents others from writing de-obfuscating tool and then read nice sources? no matter what you do, as long as you distribute executable code to masses, it can be reverse-engineered. You can only make it harder. But there is good way to prevent this from happening: stop selling binary files, start selling real support for your software, ship updates regularly, make customers happy. Then you will be immune from any piracy, because nobody will think pirating your software, because it is useless without your support. >> Â Â Â Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > > Thanks, > Phil -- Best regards, Igor Stasenko.

June 4, 2012

Re: [Pharo-project] McHttpRepository and text/plain

by Stuart Herring

Hi Sven, > -1 > > #asByteArray does an implicit text to bytes conversion (granted, a stupid one). > This will (and had conflicted in the past) with the text conversion done automatically by the HTTP client. > The response simply has to be binary because the data is binary. Yes, I understand. The important thing is that at the moment is that a misconfigured server results in something that gives the appearance of a Pharo bug. >> Failing that, the condition should probably be explicitly checked for >> and a more useful error message given, as the cause is far enough away >> from the symptom that it takes a bit of digging to find out what went >> wrong. > > +1 > > Yes, the error should be reported better. As it is today is not acceptable. > > Normally, the ZnClient>>#accept: option (in combination with #systemPolicy) would do the trick. > However, while a ZnMimeType text wildcard (text/*) is useful to require textual responses, no such general wildcard exists for (all) binary responses. We could try with (application/*) and hope that enough MC servers comply (I think most will use application/octet-stream or application/x-monticello anyway). > > I could try to make a 2.0 patch and see what happens. Excellent! Regards, Stuart

June 4, 2012

Re: [Pharo-project] [ConcreteTypeInference] news.

by Santiago Bragagnolo

In order to order my work i opened an issue tracker at google code. If you see any bug or somethig let me know it here http://code.google.com/p/concrete-type-inference 2012/6/3 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> > Hi all! > > > I'm announcing four new posts on the blog, > > Concrete types - A little brief about concrete types to understand the > mechanisms > http://concretetypeinference.blogspot.com.ar/2012/06/concrete-types.html > > About mechanisms part 1 - talking about problems getting green the tests > :). This revision is about contexts of block evaluation > > http://concretetypeinference.blogspot.com.ar/2012/06/about-mechanisms-part-… > > About mechanisms part 2 - This revision is about a pretty weird scenario > > http://concretetypeinference.blogspot.com.ar/2012/06/about-mechanisms-part-… > > Metacello configuration - nothing to add to the title. > > http://concretetypeinference.blogspot.com.ar/2012/06/metacello-concretetype… > > > Good week. >

June 4, 2012

[Pharo-project] [ConcreteTypeInference] news.

by Santiago Bragagnolo

Hi all! I'm announcing four new posts on the blog, Concrete types - A little brief about concrete types to understand the mechanisms http://concretetypeinference.blogspot.com.ar/2012/06/concrete-types.html About mechanisms part 1 - talking about problems getting green the tests :). This revision is about contexts of block evaluation http://concretetypeinference.blogspot.com.ar/2012/06/about-mechanisms-part-… About mechanisms part 2 - This revision is about a pretty weird scenario http://concretetypeinference.blogspot.com.ar/2012/06/about-mechanisms-part-… Metacello configuration - nothing to add to the title. http://concretetypeinference.blogspot.com.ar/2012/06/metacello-concretetype… Good week.

June 4, 2012

Re: [Pharo-project] [Pharo-users] [PharoCasts] Athens + NativeBoost how to

by Igor Stasenko

Thanks, Laurent! -- Best regards, Igor Stasenko.

June 3, 2012

Re: [Pharo-project] Log fwk

by Santiago Bragagnolo

I have added a metacello configuration for the project: There's only one version, so bleeding edge. Gofer new squeaksource3: 'PaulLePoulpe'; package: 'ConfigurationOfPaulLePoulpe'; load. ConfigurationOfPaulLePoulpe project bleedingEdge load 2012/6/3 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> > Im really happy. I just merged my old logs with the fwk on the concrete > type inference project in just 30'. :) > > > > > 2012/6/2 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> > >> I just refactor the hold logEntity for a announcer on the filter object >> (thanks Guille for the feedback :) ). But right now is based on TAnnouncer, >> an enhancement to announcements, that i recently commit. For a right-now >> functionaly log, checkout the 3rd commit! and not the last one, or, >> download the slice from PharoInbox previously. >> >> >> >> 2012/6/2 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> >> >>> i'm forking the thread to open it for feedback. (Sorry for the spam >>> repeating my self, but gmail is working funny :S) >>> >>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >>> >>> Hi all! Sorry for making you wait, here is the promised post about >>> logger. >>> >>> >>> http://concretetypeinference.blogspot.com.ar/2012/06/pharo-logger-aka-paul-…<http://concretetypeinference.blogspot.com.ar/2012/06/pharo-logger-aka-paul-…> >>> >>> Sorry for the awful text-format, blogger is really ugly. I'll be opening >>> a wordpress blog and migrating all the posts the sooner as i can. >>> >>> Try to use it if you need a logger and please, send feedback! >>> >>> The needed code to addit to any project is really few, for an easy >>> example, download the project and see at examples :). >>> >>> >>> >> >

June 3, 2012

Re: [Pharo-project] Some steps towards headless on OS X

by Stefan Marr

Guys, you are probably better off on the VM mailing list. And I am certainly also interested in a headless Cocoa VM. (Esteban already forgot about my nagging apparently :-P) FW: On 04 Jun 2012, at 00:02, Sean P. DeNigris wrote: > > Mark Smith wrote >> >> The obvious thing to try (which I tried ;) is to not create a window >> > > For giggles, I changed main() to: > ... > #import <sqSqueakOSXApplication.h> > > int main(int argc, char **argv, char **envp) > { > extern int argCnt; > extern char **argVec; > extern char **envVec; > > argCnt = argc; > argVec= argv; > envVec = envp; > > NSAutoreleasePool * pool = [NSAutoreleasePool new]; > > NSRunLoop *runLoop = [NSRunLoop mainRunLoop]; > sqSqueakOSXApplication* app = [sqSqueakOSXApplication new]; > [app setupEventQueue]; > [runLoop performSelector: @selector(runSqueak) > target: app > argument: nil > order: 1 > modes: [NSArray arrayWithObject: NSDefaultRunLoopMode]]; > > [runLoop run]; > > [pool release]; > return 0; > } > > This starts the interpret loop, but seems to get stuck in > primitiveFindHandlerContext(), which gets called from > initStackPagesAndInterpret() > > p.s. for testing, you can pass in the headless flag and image file via > Product->Edit Scheme->Arguments > > -- > View this message in context: http://forum.world.st/Some-steps-towards-headless-on-OS-X-tp4633047p4633080… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

June 3, 2012

[Pharo-project] [ANN] Roassal 1.28

by Alexandre Bergel

Dear Fellow, A couple of weeks ago we have released the Roassal visualization engine. Many of you gave us feedback and we are deeply grateful for this. Since we released the first version, we have closed 25 issues [*]. Many things are left to do, especially to satisfy all the requirements from the Moose community. We are currently working on an HTML exporter for Roassal. We know this is a highly wanted feature. In a couple of weeks we should be able to deliver it. Since the first release of Roassal, we have worked very hard on it and we will continue to do so. Thanks to all of you! Alexandre, Vanessa, Juan Pablo [*] http://code.google.com/p/objectprofile/issues/list?can=1&q=status=Fixed%20c… -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 3, 2012