- Pharo-dev - lists.pharo.org

Re: [Pharo-project] TORCH: supporting source-code change integration

by Veronica Isabel Uquillas Gomez

On 19 May 2010, at 00:47, Tudor Girba wrote: > Hi Veronica, > > A bit of feedback: > - After loading Torch, the package contextual menu seems to crash the Monticello Browser i found and solved this problem... > - You extend isSuper in RBProgramNode and RBVariableNode, which generates an override conflict with methods in Moose-Core. solved by using AST-Semantics > - The Glamour tags look different, so I guess you also have some Glamour overrides. That should not happen :). Maybe you have some suggestions for improvement, or maybe you just need the border for the [i] icon? > Cheers, > Doru > > > On 18 May 2010, at 15:16, Veronica Isabel Uquillas Gomez wrote: > >> Hi Tudor, >> >> thank you :D >> >> sure!!! >> >> cheers, >> Veronica >> >> >> On 18 May 2010, at 11:39, Tudor Girba wrote: >> >>> Hi Veronica, >>> >>> It is pretty impressive :). >>> >>> Would it be Ok if I added this on the Moose page? >>> >>> Cheers, >>> Doru >>> >>> >>> On 18 May 2010, at 11:21, StÃ©phane Ducasse wrote: >>> >>>> Thanks veronica. >>>> lukas said that he was impressed this is a complement :) >>>> >>>> On May 18, 2010, at 11:00 AM, Veronica Isabel Uquillas Gomez wrote: >>>> >>>>> Dear all, >>>>> >>>>> I would like to announce Torch, a tool for supporting source-code change integration. For now, it offers visualizations of the changes and enhanced change lists. >>>>> Torch can be accessed through Monticello (in the main MC browser, in the repository browser or in the history browser). Selecting a version or slice, you can view the changes with Torch using the contextual menu. >>>>> Once you open the Torch dashboard, you can access the enhanced change list or a detailed visualization via the contextual menu as well. >>>>> >>>>> Torch is available on SqueakSource, the repository is named Torch, and you need to load the ConfigurationOfTorch package. >>>>> It runs in a dev or core image. >>>>> >>>>> For a dev image. >>>>> - ConfigurationOfTorch loadVersion10 >>>>> >>>>> For a core image. >>>>> 1) Set fonts - described in the attached file. >>>>> 2) ConfigurationOfTorch loadDefault >>>>> >>>>> I would appreciate comments and feedback! >>>>> >>>>> Best Regards, >>>>> VerÃ³nica Uquillas GÃ³mez >>>>> Vrije University Brussel - SOFT Lab >>>>> University of Lille - RMOD Team >>>>> >>>>> <torchFontsScript.st> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> www.tudorgirba.com >>> >>> "Problem solving efficiency grows with the abstractness level of problem understanding." >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 28, 2010

Re: [Pharo-project] FWD: Re: [squeak-dev] [ANN] Croquet OpenGL on Squeaksource (Re: Trying to load ALienOpenGL into 4.1 alpha...)

by StÃ©phane Ducasse

If you want us to help may be you should start to tell us exactly what you tried to do. Without that then we cannot. Stef On May 28, 2010, at 5:35 AM, Lawson English wrote: > (Andreas Raab responded to this with: > > > This is your problem. CroquetGL has not been tested on Pharo. I suspect Pharo 1.0 has still the dreadful "SmalltalkImage current platformName". ) > > > Is AlienOpenGL still an option? > > > Lawson > > > > On 5/27/10 7:54 PM, Lawson English wrote: >> Darn, tried that with the latest update of Seaside 3.0a. I had to use Monticello directly, rather than Installer. 'OpenGL example." returned the error MessageNotUnderstood: SystemDictionary>>platformName >> >> >> >> On 3/22/10 11:04 PM, Andreas Raab wrote: >>> On 3/22/2010 7:27 PM, Lawson English wrote: >>>> Croquet OpenGL is dependent on all sorts of things. Have you managed to >>>> get Croquet working in a modernish version of Squeak/Pharo? >>> >>> (you will need an updated 4.1 trunk image - I've promoted Form>>flipVertically to core in the process of making this package) >>> >>> From http://www.squeaksource.com/CroquetGL >>> >>> The OpenGL interface from Croquet for consumption in other contexts. Supports OpenGL 1.4 plus extensions. >>> >>> To install, first load the FFI via: >>> >>> (Installer repository: 'http://source.squeak.org/FFI') >>> install: 'FFI-Pools'; >>> install: 'FFI-Kernel'; >>> install: 'FFI-Tests'. >>> >>> then load CroquetGL: >>> >>> (Installer repository: 'http://www.squeaksource.com/CroquetGL') >>> install: '3DTransform'; >>> install: 'OpenGL-Pools'; >>> install: 'OpenGL-Core'. >>> >>> When everything has loaded, try the example: >>> >>> OpenGL example. >>> >>> Important Windows Note: >>> >>> In order to use Croquet on Windows, you must make sure your VM is set to support OpenGL instead of D3D by default. To do this, press F2 or go to the system menu, into the "Display and Sound" section and ensure the preference "Use OpenGL (instead of D3D" is ENABLED. >>> >>> Cheers, >>> - Andreas >>> >>> >> >> >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 28, 2010

Re: [Pharo-project] Fwd: [Vm-dev] Squeak removed from Gentoo Linux

by StÃ©phane Ducasse

On May 28, 2010, at 4:51 AM, Serge Stinckwich wrote: > On Fri, May 28, 2010 at 1:07 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Reading the complete thread is quite interesting. > > > Yes definitely. They do not all wrong. It is not necessary to > duplicate the external code. > If i read correctly, there is some security issues with the current > Squeak/Pharo VM. Exact! Stef

May 28, 2010

Re: [Pharo-project] plan for 1.1

by StÃ©phane Ducasse

do you have a stack trace? Stef On May 28, 2010, at 12:57 AM, Torsten Bergmann wrote: > Updating the 1.1. core on Windows brings a SyntaxError (FormCanvas drawing-support arch) while processing 11377: > > "archNothing more expected ->/Pharo/Pharo/PharoHarvestingFixes/PharoCore-1.1-11375-Beta.7.image" > > > > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 28, 2010

[Pharo-project] [update 1.1] #11377

by StÃ©phane Ducasse

11377 ----- - Issue 2460: NewTextMorphTests #testClassDefinitionMorphCreation and #testMethodMorphCreation fails Rethought the CodeMorph class hierarchy, removed the subclasses and added CodeMorph class methods for creating MethodMorph and ClassDefinitionMorph. Thanks Fernando. - Issue 2182: Testing if a class is obsolete. Part One. Thanks alex. - Issue2458: ChooseColorDefaults. Thanks Henrik. - Issue 1832: remove unnecessary halt or convert them into error. Thanks Guille Stef

May 28, 2010

Re: [Pharo-project] how to add an entry in World Menu (was: CommandShell)

by Alain Plantec

Le 27/05/2010 23:02, laurent laffont a Ã©crit : > See http://book.pharo-project.org/book/TipsAndTricks/WorldMenuRegistration yep! > > Can someone write a little example on how to add Settings ? I need this :) ok, I will. Cheers Alain > > Cheers, > > Laurent > > On Thu, May 27, 2010 at 9:56 PM, laurent laffont > <laurent.laffont(a)gmail.com <mailto:laurent.laffont@gmail.com>> wrote: > > On Thu, May 27, 2010 at 4:45 PM, David T. Lewis > <lewis(a)mail.msen.com <mailto:lewis@mail.msen.com>> wrote: > > On Thu, May 27, 2010 at 09:04:37AM +0200, laurent laffont wrote: > > Hi Dave, > > > > I've managed to make it running in Pharo (remove all > isMorphic ifFalse ... > > stuff, change menu registration, a little work is needed to > adapt to Pharo > > new settings system). It works (I can publish a package when > back at home). > > > > Now I suppose you want to keep it running on Squeak, I don't > know how to > > handle differences on world menu and preferences. > > > > For the MVC part, is there some value in keeping it ? > > Hi Laurent, > > Thanks, I would be very interested in seeing your changes, > especially the > menu registration fixes. > > > For menu registration, add > > CommandShell class>>#menuCommandOn: aBuilder > <worldMenu> > (aBuilder item: #'Command Shell') > parent: #Tools; > action:[self open]; > help: 'Smalltalk simulation of a Unix command shell '. > > and comment / remove Preferences in CommandShell class>>#initialize. > > > Laurent > > > I do want to keep this working on MVC and on other Squeak > images. What > I really need to do is repackage CommandShell and OSProcess so > that > everything is not all in two giant packages. I originally > "packaged" > these many years ago before Squeak had real packages and > Monticello, > so I basically separated things into two completely separate > SAR packages > that could be independently maintained (even though > CommandShell and > OSProcess were intended to work together). That was quite a > project > at the time, but it is badly out of date now, so I need to go back > and make this stuff work properly with Metacello configurations. > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 28, 2010

Re: [Pharo-project] difference between Sequenceable and Ordered

by Julian Fitzell

Take a look at the ANSI standard - it has the collection behaviour already broken up into "traits" that are multiply-inherited to define the protocols of each class. Julian On Thu, May 27, 2010 at 10:32 AM, Tristan Bourgois <tr.bourgois(a)laposte.net> wrote: > > Thanks, that's very interesting but not really help me sorry! > Sorry may be the question are not very precise. > My question is about the behavior so I put it in the context: > > I refactoring the collection in trait and I search if > there are a difference between a Sequenceable and > Ordered behavior. Because if there are not difference > I don't create trait for the Ordered behavior. > > So do you think there are difference between the two behavior? > > -- > View this message in context: http://forum.world.st/difference-between-Sequenceable-and-Ordered-tp2231718… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 28, 2010

Re: [Pharo-project] A port of Pharo: Redline Smalltalk ...

by skrish

Hi James, Just wondering why not port to Groovy and it would be lot easier. Though building a proper bridge like JNIPort, XMLRPC, full blown WS, RMI like more native interoperability along with a VW like optimized VM would be nicer than really translating code.. Atleast Synchrony Systems has done this with VA Smalltalk to Java for close to 6+ years now.. and I do not see the results very nice in the ported apps.. they are pain to maintain and extend eventually. If Java is the world I want to deploy and live in.. better develop in it.. not that difficult at all with Groovy / Ruby and now the up coming Java 7 dynamic language hooks.. Polyglot programming is best.. they can thrive on their own runtimes if so reqd rather than targetting the same VM. I am not sure if I would consider JVM necessarily better than an optimized Smalltalk VM like VW if Pharo can reach their with Eliot's assistance.. Ruby or Groovy like ability to call Java framework APIs with just an import statement and automatic marshalling/ unmarshalling of values will be a boon to Smalltalk programmers to plug in to the width Java does provide from its various sources viz: Spring/ Apache / Oracle-Sun / IBM.. for everything from MQ, JMS, ESBs, simple parsers/ builders and the whole slew of stuff.. -Skrish -- View this message in context: http://forum.world.st/A-port-of-Pharo-Redline-Smalltalk-tp1749812p2234090.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 28, 2010

[Pharo-project] FWD: Re: [squeak-dev] [ANN] Croquet OpenGL on Squeaksource (Re: Trying to load ALienOpenGL into 4.1 alpha...)

by Lawson English

(Andreas Raab responded to this with: This is your problem. CroquetGL has not been tested on Pharo. I suspect Pharo 1.0 has still the dreadful "SmalltalkImage current platformName". ) Is AlienOpenGL still an option? Lawson On 5/27/10 7:54 PM, Lawson English wrote: > Darn, tried that with the latest update of Seaside 3.0a. I had to > use Monticello directly, rather than Installer. 'OpenGL example." > returned the error MessageNotUnderstood: SystemDictionary>>platformName > > > > On 3/22/10 11:04 PM, Andreas Raab wrote: >> On 3/22/2010 7:27 PM, Lawson English wrote: >>> Croquet OpenGL is dependent on all sorts of things. Have you managed to >>> get Croquet working in a modernish version of Squeak/Pharo? >> >> (you will need an updated 4.1 trunk image - I've promoted >> Form>>flipVertically to core in the process of making this package) >> >> From http://www.squeaksource.com/CroquetGL >> >> The OpenGL interface from Croquet for consumption in other contexts. >> Supports OpenGL 1.4 plus extensions. >> >> To install, first load the FFI via: >> >> (Installer repository: 'http://source.squeak.org/FFI') >> install: 'FFI-Pools'; >> install: 'FFI-Kernel'; >> install: 'FFI-Tests'. >> >> then load CroquetGL: >> >> (Installer repository: 'http://www.squeaksource.com/CroquetGL') >> install: '3DTransform'; >> install: 'OpenGL-Pools'; >> install: 'OpenGL-Core'. >> >> When everything has loaded, try the example: >> >> OpenGL example. >> >> Important Windows Note: >> >> In order to use Croquet on Windows, you must make sure your VM is set >> to support OpenGL instead of D3D by default. To do this, press F2 or >> go to the system menu, into the "Display and Sound" section and >> ensure the preference "Use OpenGL (instead of D3D" is ENABLED. >> >> Cheers, >> - Andreas >> >> > > >

May 28, 2010

Re: [Pharo-project] [squeak-dev] Re: New weak finalization support. Implementation

by Igor Stasenko

Guys, it looks like i found an elegant solution. Please check the new-finalization-auto.2.cs, which i uploaded to http://bugs.squeak.org/view.php?id=7473. It adds just a few things: initTestPair TestItem := WeakFinalizerItem new list: TestList object: Object new. checkTestPair HasNewFinalization := TestList swapWithNil notNil. These two method is then sent from within WeakArray's finalization process: finalizationProcess [true] whileTrue: [ WeakFinalizationRegistry initTestPair. FinalizationSemaphore wait. FinalizationLock critical: [ WeakFinalizationRegistry checkTestPair. FinalizationDependents do: [:weakDependent | weakDependent ifNotNil: [weakDependent finalizeValues]]] ifError: [:msg :rcvr | rcvr error: msg]. ]. And so, at each GC cycle, a new registry it knows exactly if it allowed to do a shortcut, or not. And if not, then it behaves in same way as old registry - it starts scanning the whole dictionary to clean graveyard. So, in summary: running on older VMs , a WeakFinalizationRegistry will behave exactly as old WeakRegistry. While on VMs, which supporting new finalization, it will do a shortcut. This is at cost of extra 2 objects, allocated per GC cycle, to detect if new finalization is supported. P.S. oops, actually it could be just one object.. just need to change two methods at WeakFinalizationRegistry class side: initialize TestList := WeakFinalizationList new. TestItem := WeakFinalizerItem new. initTestPair TestList swapWithNil. "make sure list is empty" TestItem list: TestList object: Object new. -- Best regards, Igor Stasenko AKA sig.

May 28, 2010