February 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] TabbedPane Class/ Package / Workspace browsers
by Fernando Olivero Feb. 20, 2012

Feb. 20, 2012

Hi, i wanted to comment a bit on the proposed ui. The problem with this single-window with tab panes, is that it forces the user to have a single focus of attention, which produces an overhead in navigation for those programming tasks that require looking at more than one element at a time. Thats why i see more value in our current user interface, of course it can highly improved... Fernando On Thu, Feb 16, 2012 at 8:57 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Nice > > Stef > > On Feb 16, 2012, at 7:15 AM, S Krish wrote: > >> >> >> Just this quick n usable prototype.. ? >> >> Any comments of its utility.. I for one would rather prefer having everything navigable from one Tabbed Pane.. >> >> Panes capable of rendering about every window of the basic tools of Pharo.. workspace, Finder, ScriptManager, possibly Transcript as a console collapsible as reqd >> >> Akin to the eclipse but not really that intensively single windowed.. there are uses for spawning separate windows.. >> >> <PharoTabbedBrowsers.jpg> > >

7 10

[Pharo-project] Fwd: [Pharo-users] pharo & arduino
by StÃ©phane Ducasse Feb. 20, 2012

Feb. 20, 2012

HI since this can interest other peopleâ¦. Begin forwarded message: > From: Ricardo Moran <richi.moran(a)gmail.com> > Subject: Re: [Pharo-users] pharo & arduino > Date: February 20, 2012 12:15:07 AM GMT+01:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Cc: linedubeth(a)free.fr > > Hi Stef, > > You can look at the Arduino repository at squeaksource (http://www.squeaksource.com/Arduino.html) > Everything but the "Arduino-Etoys*" packages should work fine in Pharo. At least they worked the last time I checked but a lot has changed since then, so let me know if you encounter any problem, I'll be happy to help. > > Cheers, > Richo > > On Sat, Feb 18, 2012 at 6:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi ricardo > > do you have some information how to connect pharo to arduino? > Thanks in advance. > > Stef > > Begin forwarded message: > > > From: GÃ©rard Duteil <linedubeth(a)free.fr> > > Subject: [Pharo-users] pharo & arduino > > Date: February 18, 2012 9:42:02 AM GMT+01:00 > > To: pharo-users(a)lists.gforge.inria.fr > > Reply-To: A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> > > > > Hello,,,I search info about this subject., > > ,I'm interesting by picaxe also,,,, > > A beginner in object programmation,,, > > I wait the 25th may,,, > > Thanks in advance. > > > >

1 0

[Pharo-project] moved repos to gemstone
by Camillo Bruni Feb. 20, 2012

Feb. 20, 2012

If the corresponding project admins would agree it would be cool to move the development to ss3 on gemstone of the following projects I ported so far: - Citezen http://ss3.gemstone.com/ss/citezen - FSFilesystem http://ss3.gemstone.com/ss/fs - FSGit http://ss3.gemstone.com/ss/fs-git - PetitMarkdown http://www.squeaksource.com/PetitMarkdown - PharoRB http://ss3.gemstone.com/ss/rb-pharo - Refactoring Engine http://ss3.gemstone.com/ss/rb - Soup http://ss3.gemstone.com/ss/soup - XMLSupport http://ss3.gemstone.com/ss/xmlsupport I tried to add people from the old projects as admins Please let me know

6 10

[Pharo-project] HTTPS
by Robert Calco Feb. 20, 2012

Feb. 20, 2012

OK, since I mentioned this problem area as a relative weakness of Pharo in a separate list for the VW non-commercial, I suppose it would be right to close the loop and ask how people get HTTPS working on Pharo. I'm talking about both scenarios, as client and server. The client scenario is calling XMLRPC servers over HTTPS. I did not get this to work out of the box after installing XmlRpcClient libraries, as the underlying Http Client libraries in Pharo do not have SSL support. It seems the preferred answer is to use Apache to proxy the calls to any URL requiring SSL support. I know about Zodiac but could not get it working quickly and just went with VW for developing the first iteration of my integration with multiple XMLRPC APIs. The server scenario involves supporting calls over HTTPS using, say, Aida or Seaside. It's easy in this case to say just let the web server (Apache) handle that, but what if I want to use Swazoo (to keep moving parts to a minimum)? I do most development on Windows, where I usually have IIS installed (for .NET stuff), and that plays nice with absolutely no one. Specifically, I have to be able to support a site that variously accepts HTTP and HTTPS calls, so I'd have to run it on multiple ports, at a minimum. How can I get both scenarios to work in Pharo without involving Apache? -- Bob Calco bob.calco(a)softcraft-solutions.com

7 16

[Pharo-project] Crash dump Cog Linux for Debugger opening up
by S Krish Feb. 19, 2012

Feb. 19, 2012

Will dig in further.. but if anyone has seen this and already fixed for 1.4 ..

2 2

[Pharo-project] Who can help for the pharo web site
by stephane ducasse Feb. 19, 2012

Feb. 19, 2012

Hi guys Adrian left and now I cannot manage the pharo web site. I need help because I do not understand how to edit it. Today by accident I removed the (broken) twitter box. So what do we do? I was thinking to port everything in plain static html so that I can edit the pages fast and easy. I would like to add a how to contribute page. Our web site does not evolve anymore because nobody cares about it. So I can try to do it but I will port everything into html. Stef (tired to do too many things and fed up about systematic bashing).

5 5

[Pharo-project] where is ORChangesBrowser
by Fabrizio Perin Feb. 19, 2012

Feb. 19, 2012

Hi, There is some code in moose (in FMDefaultCodeGenerator) which use ORChangesBrowser but the class is not in the system. Was the class removed in 1.4 or we do not load the proper package? Cheers, Fabrizio

2 1

Feb. 19, 2012

Moose :) Stef > From: Tudor Girba <tudor(a)tudorgirba.com> > Subject: [Moose-dev] configuring moose > Date: February 19, 2012 11:16:37 AM GMT+01:00 > To: Moose-dev Moose Dev <moose-dev(a)iam.unibe.ch> > Reply-To: Moose-related development <moose-dev(a)iam.unibe.ch> > > Hi, > > We are looking into how to reconfigure Moose. > > The challenge is not that tiny. Here is the list of packages we currently load: > > > load : Moose-Tests-Core > load : Moose-Tests-SmalltalkImporter-KGB > load : Famix-Tests-Core > load : Moose-Tests-SmalltalkImporter-LAN > load : Moose-Tests-SmalltalkImporter-Core > load : Moose-TestResources-Reference-PackageTwo > load : Famix-Tests-Java > load : Moose-GenericImporter > load : Moose-SmalltalkImporter > load : Moose-MonticelloImporter > load : Moose-Hismo > load : Famix-Core > load : Dynamix-Core > load : Famix-SourceAnchor > load : Famix-C > load : Famix-Java > load : Famix-Implementation > load : Moose-Algos-Graph > load : Moose-Tests-Algos-Graph > load : Moose-Tests-Algos-LinearAlgebra > load : Moose-Tests-Algos-Clustering > load : Moose-Tests-Algos-InformationRetrieval > load : Moose-Tests-Algos-FormalConceptAnalysis > load : Moose-Algos-Clustering > load : Moose-Algos-LinearAlgebra > load : Moose-Algos-FormalConceptAnalysis > load : Moose-Algos-Lattice > load : Moose-Algos-InformationRetrieval > load : Famix-Extensions > load : PetitParser > load : PetitTests > load : PetitAnalyzer > load : CollectionExtensions > load : Glamour-Announcements > load : Glamour-Helpers > load : Glamour-Core > load : Glamour-Presentations > load : Glamour-Browsers > load : Glamour-Tests-Core > load : Glamour-Morphic-Theme > load : Glamour-Examples > load : Glamour-Tools > load : Glamour-Morphic-Widgets > load : Glamour-Morphic-Renderer > load : Keymapping-Shortcuts > load : BDDExtensions > load : Glamour-Tests-Morphic > load : HealthReportProducer > load : CollectionExtensions > load : Nile-Base > load : Mondrian-ComplexShape > load : Mondrian-Core > load : Mondrian-Layouts > load : Mondrian-Help > load : Mondrian-Easel > load : Mondrian-Pharo-Tests > load : Mondrian-Shapes > load : Mondrian-Events > load : Mondrian-Visitor > load : Mondrian-Util > load : Mondrian-Normalizers > load : Mondrian-Example > load : Mondrian-ShapeVisitor > load : Mondrian-Pharo-Morphic > load : Mondrian-Tests > load : Mondrian-FADELayout > load : Glamour-Mondrian-Presentations > load : Glamour-Tests-Mondrian > load : EyeSee-Events > load : EyeSee-Axis > load : EyeSee-Tests-Core > load : EyeSee-Support > load : EyeSee-Core > load : Glamour-EyeSee-Presentations > load : Glamour-Tests-EyeSee > load : Magritte-Model > load : Magritte-Pharo-Model > load : Magritte-Morph > load : Glamour-Magritte-Presentations > load : Magritte-Tests-Model > load : PetitGui > load : PetitSmalltalk > load : PetitJava > load : PetitMSE > load : PetitSQLite-Parser > load : PetitSQLite-AST > load : PetitSQLite-Tests-Parser > load : Moose-Finder > load : Moose-Tests-Finder > load : Arki-Reporter-Browser > load : Moose-Settings > load : Moose-MultiDimensionsDistributionMap > load : Moose-MondrianPaintings > load : Moose-Tests-MondrianPaintings > load : MondrianGraphVizLayout > load : Moose-DistributionMap > load : Moose-Tests-DistributionMap > load : Moose-Wizard > load : Famix-File > load : Moose-Algos-Dsm > load : Moose-Dsm-Core > load : Moose-CycleTable > load : Moose-Dsm-Visualization-Core > load : Moose-Dsm-Example > load : Moose-Dsm-Visualization-Famix > load : Moose-Dsm-Famix > load : ConfigurationOfMoose > load : SmallDude-Utils > load : SmallDude-Species > load : SmallDude-Tests-Text > load : RoelTyper > load : Nile-Base > load : Hashtable > load : OSProcess > load : CollectionExtensions > load : Moose-Help > load : Famix-Specifications > load : Arki-Reporter-Core > load : Arki-Tests-Reporter > load : Famix-Tests-C > load : Famix-Tests-Extensions > load : Dynamix-Tests-Core > load : Moose-Development-Tools > load : Moose-TestResources-Reference-Core > load : Moose-TestResources-Reference-PackageOne > load : Moose-TestResources-LAN > load : Moose-TestResources-KGB-P4FullInteracted > load : Moose-TestResources-KGB-P6InteractedReferee > load : Moose-TestResources-KGB-P5FullReferee > load : Moose-TestResources-KGB-P1FullReferencer > load : Moose-TestResources-KGB-P2InteractedReferencerReferee > load : Moose-TestResources-KGB-P3InteractedReferencer > load : Moose-TestResources-KGB-P7ReferencerReferee > load : Moose-TestResources-KGB-P8FullReferencer > load : Moose-TestResources-KGB-P9FullReferencer > load : Moose-TestResources-KGB-P10InteractedReferee > load : Moose-TestResources-KGB-P11FullReferee > load : Moose-TestResources-KGB-P12FullReferencer > load : Moose-TestResources-KGB-P13FullReferencer > load : Moose-TestResources-KGB-P14FullReferee > load : Moose-TestResources-KGB-PExtensions > load : Moose-TestResources-PackageBlueprint-P1 > load : Moose-TestResources-PackageBlueprint-P2 > load : Moose-TestResources-PackageBlueprint-P3 > load : Moose-TestResources-PackageBlueprint-P4 > load : Moose-Tests-MonticelloImporter > load : Fame-Core > load : Fame-Util > load : Fame-ImportExport > load : Fame-SmalltalkBinding > load : Fame-Example > load : Phexample > load : Fame-Tests-Core > load : Moose-Core > load : Moose-EyeSeeCharts > load : Moose-Tests-Core > load : Moose-Tests-SmalltalkImporter-KGB > load : Famix-Tests-Core > load : Moose-Tests-SmalltalkImporter-LAN > load : Moose-Tests-SmalltalkImporter-Core > load : Moose-TestResources-Reference-PackageTwo > load : Famix-Tests-Java > load : Moose-GenericImporter > load : Moose-SmalltalkImporter > load : Moose-MonticelloImporter > load : Moose-Hismo > load : Famix-Core > load : Dynamix-Core > load : Famix-SourceAnchor > load : Famix-C > load : Famix-Java > load : Famix-Implementation > load : Moose-Algos-Graph > load : Moose-Tests-Algos-Graph > load : Moose-Tests-Algos-LinearAlgebra > load : Moose-Tests-Algos-Clustering > load : Moose-Tests-Algos-InformationRetrieval > load : Moose-Tests-Algos-FormalConceptAnalysis > load : Moose-Algos-Clustering > load : Moose-Algos-LinearAlgebra > load : Moose-Algos-FormalConceptAnalysis > load : Moose-Algos-Lattice > load : Moose-Algos-InformationRetrieval > load : Famix-Extensions > load : PetitParser > load : PetitTests > load : PetitAnalyzer > load : CollectionExtensions > load : Glamour-Announcements > load : Glamour-Helpers > load : Glamour-Core > load : Glamour-Presentations > load : Glamour-Browsers > load : Glamour-Tests-Core > load : Glamour-Morphic-Theme > load : Glamour-Examples > load : Glamour-Tools > load : Glamour-Morphic-Widgets > load : Glamour-Morphic-Renderer > load : Keymapping-Shortcuts > load : BDDExtensions > load : Glamour-Tests-Morphic > load : HealthReportProducer > load : CollectionExtensions > load : Nile-Base > load : Mondrian-ComplexShape > load : Mondrian-Core > load : Mondrian-Layouts > load : Mondrian-Help > load : Mondrian-Easel > load : Mondrian-Pharo-Tests > load : Mondrian-Shapes > load : Mondrian-Events > load : Mondrian-Visitor > load : Mondrian-Util > load : Mondrian-Normalizers > load : Mondrian-Example > load : Mondrian-ShapeVisitor > load : Mondrian-Pharo-Morphic > load : Mondrian-Tests > load : Mondrian-FADELayout > load : Glamour-Mondrian-Presentations > load : Glamour-Tests-Mondrian > load : EyeSee-Events > load : EyeSee-Axis > load : EyeSee-Tests-Core > load : EyeSee-Support > load : EyeSee-Core > load : Glamour-EyeSee-Presentations > load : Glamour-Tests-EyeSee > load : Magritte-Model > load : Magritte-Pharo-Model > load : Magritte-Morph > load : Glamour-Magritte-Presentations > load : Magritte-Tests-Model > load : PetitGui > load : PetitSmalltalk > load : PetitJava > load : PetitMSE > load : PetitSQLite-Parser > load : PetitSQLite-AST > load : PetitSQLite-Tests-Parser > load : Moose-Finder > load : Moose-Tests-Finder > load : Arki-Reporter-Browser > load : Moose-Settings > load : Moose-MultiDimensionsDistributionMap > load : Moose-MondrianPaintings > load : Moose-Tests-MondrianPaintings > load : MondrianGraphVizLayout > load : Moose-DistributionMap > load : Moose-Tests-DistributionMap > load : Moose-Wizard > load : Famix-File > load : SmallDude-Core > load : SmallDude-Text > load : SmallDude-Tests-Core > load : SmallDude-Moose > load : Kumpel-Tests-Core > load : Kumpel-Tests-Importer > load : RoelTyper > load : Nile-Base > load : Hashtable > load : OSProcess > load : CollectionExtensions > load : Moose-Help > load : Famix-Specifications > load : Arki-Reporter-Core > load : Arki-Tests-Reporter > load : Famix-Tests-C > load : Famix-Tests-Extensions > load : Dynamix-Tests-Core > load : Moose-Development-Tools > load : Moose-TestResources-Reference-Core > load : Moose-TestResources-Reference-PackageOne > load : Moose-TestResources-LAN > load : Moose-TestResources-KGB-P4FullInteracted > load : Moose-TestResources-KGB-P6InteractedReferee > load : Moose-TestResources-KGB-P5FullReferee > load : Moose-TestResources-KGB-P1FullReferencer > load : Moose-TestResources-KGB-P2InteractedReferencerReferee > load : Moose-TestResources-KGB-P3InteractedReferencer > load : Moose-TestResources-KGB-P7ReferencerReferee > load : Moose-TestResources-KGB-P8FullReferencer > load : Moose-TestResources-KGB-P9FullReferencer > load : Moose-TestResources-KGB-P10InteractedReferee > load : Moose-TestResources-KGB-P11FullReferee > load : Moose-TestResources-KGB-P12FullReferencer > load : Moose-TestResources-KGB-P13FullReferencer > load : Moose-TestResources-KGB-P14FullReferee > load : Moose-TestResources-KGB-PExtensions > load : Moose-TestResources-PackageBlueprint-P1 > load : Moose-TestResources-PackageBlueprint-P2 > load : Moose-TestResources-PackageBlueprint-P3 > load : Moose-TestResources-PackageBlueprint-P4 > load : Moose-Tests-MonticelloImporter > load : Fame-Core > load : Fame-Util > load : Fame-ImportExport > load : Fame-SmalltalkBinding > load : Fame-Example > load : Phexample > load : Fame-Tests-Core > load : Moose-Core > load : Moose-EyeSeeCharts > load : Moose-Tests-Core > load : Moose-Tests-SmalltalkImporter-KGB > load : Famix-Tests-Core > load : Moose-Tests-SmalltalkImporter-LAN > load : Moose-Tests-SmalltalkImporter-Core > load : Moose-TestResources-Reference-PackageTwo > load : Famix-Tests-Java > load : Moose-GenericImporter > load : Moose-SmalltalkImporter > load : Moose-MonticelloImporter > load : Moose-Hismo > load : Famix-Core > load : Dynamix-Core > load : Famix-SourceAnchor > load : Famix-C > load : Famix-Java > load : Famix-Implementation > load : Moose-Algos-Graph > load : Moose-Tests-Algos-Graph > load : Moose-Tests-Algos-LinearAlgebra > load : Moose-Tests-Algos-Clustering > load : Moose-Tests-Algos-InformationRetrieval > load : Moose-Tests-Algos-FormalConceptAnalysis > load : Moose-Algos-Clustering > load : Moose-Algos-LinearAlgebra > load : Moose-Algos-FormalConceptAnalysis > load : Moose-Algos-Lattice > load : Moose-Algos-InformationRetrieval > load : Famix-Extensions > load : PetitParser > load : PetitTests > load : PetitAnalyzer > load : CollectionExtensions > load : Glamour-Announcements > load : Glamour-Helpers > load : Glamour-Core > load : Glamour-Presentations > load : Glamour-Browsers > load : Glamour-Tests-Core > load : Glamour-Morphic-Theme > load : Glamour-Examples > load : Glamour-Tools > load : Glamour-Morphic-Widgets > load : Glamour-Morphic-Renderer > load : Keymapping-Shortcuts > load : BDDExtensions > load : Glamour-Tests-Morphic > load : HealthReportProducer > load : CollectionExtensions > load : Nile-Base > load : Mondrian-ComplexShape > load : Mondrian-Core > load : Mondrian-Layouts > load : Mondrian-Help > load : Mondrian-Easel > load : Mondrian-Pharo-Tests > load : Mondrian-Shapes > load : Mondrian-Events > load : Mondrian-Visitor > load : Mondrian-Util > load : Mondrian-Normalizers > load : Mondrian-Example > load : Mondrian-ShapeVisitor > load : Mondrian-Pharo-Morphic > load : Mondrian-Tests > load : Mondrian-FADELayout > load : Glamour-Mondrian-Presentations > load : Glamour-Tests-Mondrian > load : EyeSee-Events > load : EyeSee-Axis > load : EyeSee-Tests-Core > load : EyeSee-Support > load : EyeSee-Core > load : Glamour-EyeSee-Presentations > load : Glamour-Tests-EyeSee > load : Magritte-Model > load : Magritte-Pharo-Model > load : Magritte-Morph > load : Glamour-Magritte-Presentations > load : Magritte-Tests-Model > load : PetitGui > load : PetitSmalltalk > load : PetitJava > load : PetitMSE > load : PetitSQLite-Parser > load : PetitSQLite-AST > load : PetitSQLite-Tests-Parser > load : Moose-Finder > load : Moose-Tests-Finder > load : Arki-Reporter-Browser > load : Moose-Settings > load : Moose-MultiDimensionsDistributionMap > load : Moose-MondrianPaintings > load : Moose-Tests-MondrianPaintings > load : MondrianGraphVizLayout > load : Moose-DistributionMap > load : Moose-Tests-DistributionMap > load : Moose-Wizard > load : Famix-File > load : Kumpel-Core > load : Kumpel-Importer > load : Magritte-Model > load : Magritte-Pharo-Model > load : Magritte-Morph > load : Magritte-Tests-Model > load : Fame-Core > load : Fame-Util > load : Fame-ImportExport > load : Fame-SmalltalkBinding > load : Fame-Example > load : Phexample > load : Fame-Tests-Core > load : Metanool-Core > load : Metanool-Tests-Core > > > Cheers, > Doru > > -- > www.tudorgirba.com > > "What we can governs what we wish." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

4 3

[Pharo-project] debugger menu items inconsistent with buttons ( & "Begin Debugging Again" enhancement )
by Ben Coman Feb. 19, 2012

Feb. 19, 2012

I notice that the function of debugger menu items Step, Step through & Send seem to correspond respectively to debugger buttons Over, Through & Into but the text doesn't really align. Perhaps better menu items would be: Step Over, Step through block, Step Into. On another topic, once you have stepped past the point where the debugger opened, is there any way the debugger might be returned to the context where it initially opened? For instance, if you are debugging your startup script by putting a halt in the script, then then if you accidentally step past where the debugger opened, you can no longer use the <Restart> button and have to quit and restart Pharo to get back to the same debugging point. A menu item to "Begin Debugging Again At The Same Initial Point" would be nice but perhaps this is not feasible, or I've missed something cheers, -ben

2 1

[Pharo-project] Need help with OpenGL visual creation on linux
by Javier PimÃ¡s Feb. 19, 2012

Feb. 19, 2012

I'm trying to create an OpenGL context on linux but glxChooseVisual fails. Maybe there's someone there experienced with this that can help. The code I'm trying is: display := NBXLibDisplay open. window := display defaultRootWindow. visualInfo := NBXLibVisualInfo fromPointer: (gl chooseVisual: display screen: display defaultScreen attributes: {GLX_RGBA. GLX_DEPTH_SIZE. 24. GLX_DOUBLEBUFFER. 0} asWordArray). ... but chooseVisual returns a null pointer. I even tried putting an array with only 0 on attributes but didn't work either (and these attributes should be supported). Any idea of what could be wrong? The code is available to test in squeaksource, you need nativeboost+NBXLib to try Cheers, Javier -- Lic. Javier PimÃ¡s Ciudad de Buenos Aires

3 10