September 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] "OS" and "OS-Windows" project on STHub

by StÃ©phane Ducasse

+1 On Sep 19, 2013, at 7:58 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > that's really great news, thank you very much for your work. Do you > already have continuous integration set up or do you want me to do it? > > On Wed, Sep 18, 2013 at 11:49 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >> Hi, >> >> with NativeBoost (NB) it is now possible to access not only external libraries but also the >> underlying operating system platform. Some examples are already included in the >> "NativeBoost-Win32", "NativeBoost-Unix" and "NativeBoost-Mac" categories within the NB project. >> >> But providing more and more examples and native API wrappers for the various platforms >> directly within the NativeBoost project itself would only bloat this project. NB should care >> about being a good external interface - nothing more. >> >> To keep NativeBoost clean with the basic functionality for a good foreign function >> interface Igor suggested to move specific API wrappers for the various operating systems into >> own project. To avoid duplicate effort in providing such wrappers it would IMHO make sense to >> host them in a central place. >> >> Therefore I created the "OS" Team on SmalltalkHub with a first project called >> "OS-Windows" allowing you to access Win32/Win64 functionality easily from within >> Pharo. It contains code, tests, many examples and documentation as a first contribution. >> >> With this initial project for Windows you can now work with the console, Shell, the internet >> explorer, GDI, windows processes, Control panel applets, ... >> >> I refer to the written documentation and many examples given at: >> >> http://smalltalkhub.com/#!/~OS/OS-Windows >> >> Provided code for Windows is stable and usable, if you have something to share to make >> it even more complete then you can easily contribute (how is described in the docu). >> >> Code is for Pharo 3.0 - you can load it easily from the config browser in a recent image. >> Try the examples given in the docu on the project page, look at the tests to get comfortable >> with it. >> >> Important: >> ========== >> Note that this idea is NOT LIMITED TO WINDOWS - it would be good if we could see pair >> projects like a "/~OS/OS-Mac", or "/~OS/OS-Linux" and others under the same umbrella >> so it follows a common pattern and is easier to access for people who require it. >> >> If someone asks if Pharo is platform independent I will answer: YES. If he asks if >> it is also playing nicely with the underlying platform to use platform dependent functionality >> I would also like to answer YES. >> >> If he wants to do some Mac stuff I would like to tell him: "just load "OS-Mac" from the >> config browser and start. Same for Linux, Windows, Android, YouNameIt, ... >> >> I can only provide a start for the basic framework with the hope that others will >> contribute as well and getting it into good shape as yet another good step for the >> possibilities in the Pharo universe. >> >> Side note: >> ========== >> You can read the docu online at the SmalltalkHub project page (http://smalltalkhub.com/#!/~OS/OS-Windows) >> - but also as a class comment on the ConfigurationOfOSWindows. If you have the "Pharo Online Help" >> loaded you can also view it there. >> >> Keep on talking small >> T. >> > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Sept. 19, 2013

Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3

by StÃ©phane Ducasse

>From what I understand: - on: do: register the block context as the receiver to kick in the block evaluation => weak registration is then not weak anymore - there was an old LegacyRegistrationMechanism that works (fallback for old VM that do not have the right way of managing weak structure) and the LegacyRegistration got some on:do: and grew grew grew. Stef On Sep 19, 2013, at 5:30 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 19/09/2013 17:20, Esteban Lorenzano a Ã©crit : >> Hi, >> >> I just submitted and integrated a fix for the leak problem. >> That should fix the problem we are having in Pharo3... now we need to work on a backport for Pharo2... any takers? :) > > I need some explanations :) > > Thierry > >> Esteban >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 19, 2013

Re: [Pharo-dev] configurationOfZincHTTPComponents does not load Neo JSON

by Sabine KnÃ¶fel

Hi Sven, thanks for the lesson. I see, this was a silly question :-). I have to define, which groups to load. Regards Sabine -- View this message in context: http://forum.world.st/configurationOfZincHTTPComponents-does-not-load-Neo-J… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

Re: [Pharo-dev] Stability of 3.0

by StÃ©phane Ducasse

On Sep 19, 2013, at 5:24 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Hi all, > > is it me or what? The latest 3.0 gives me a lot of red squares a bit everywhere around the place, making working with it a bit (a lot!) painful. I do not know because busy with lecture writing and managing mess. Can you grab the debug button (I know this is unclear) but if you get the faulty morph you can get a debugger and we can see what is the message that is failing. It saved lot of work and frsutration because you know why you get the red cross of death. Stef > > I'm on 30407, frech from get.pharo.org. > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 19, 2013

Stability of 3.0

by Goubier Thierry

Hi all, is it me or what? The latest 3.0 gives me a lot of red squares a bit everywhere around the place, making working with it a bit (a lot!) painful. I'm on 30407, frech from get.pharo.org. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 19, 2013

about the memory leak in Pharo2/Pharo3

by Esteban Lorenzano

Hi, I just submitted and integrated a fix for the leak problem. That should fix the problem we are having in Pharo3... now we need to work on a backport for Pharo2... any takers? :) Esteban

Sept. 19, 2013

[update 3.0] #30410

by Esteban Lorenzano

30410 ----- 11544 Memory leak when using weak announcements with blocks https://pharo.fogbugz.com/f/cases/11544 (step 3/3) Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-Tests-EstebanLorenza… http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-SystemIntegration-Es…

Sept. 19, 2013

Re: [Pharo-dev] About Morphic Documentation

by kilon

*As long as I can view the documentation inside Pharo , thats perfectly fine for me. * When I said I will extend the pharo help tool, I only meant it in a minimum kinda of way. Small convenience like basic navigation, shortcut bindings, possibly embedding in with system browser and debugger , index search , links (not www links, but links to the documentation) and images. These things don't exist now, and I dont see anyone working on such features, so I decided it was time for DIY. I prefer my documentation the Spartan way, simple and straight to the point. I think 99% of the issue here is finding people willing to document Pharo. I will most certainly do my part, but we need to motivate people to document at least libraries they make , in a single place. Whether that is the image , or the web, makes small diffirence. What matters is documentation itself. I don't have unrealistic expectations of pharo in general , I know we are small but active community , but still small. >From my side, I will document NBOpenGL with my GLTutorials , Nativeboost and Morphic. All that documentation will be of course gradual , slow and partial as to be expected from a person with very limited free time. I also don't care about wikis as much I care about internal documentation. Its a matter of convenience. But I have been using wikis and google searches when internal docs were simply not an option. So there is definitely room for everything here and I would never even dream of discouraging anyone from trying his own idea of how to do stuff. As matter of fact I love variation and original ideas :) ClÃ©ment Bera-4 wrote > 2013/9/19 kilon < > thekilon@.co > > > >> This is why I insist on collecting things on one place, inside pharo. Web >> is >> all over the place, its great for finding information and for getting >> people >> work together , but not great learning things you are not familiar with. >> >> Why not having the documentation the same way as in Eclipse ? > > I mean the documentation would be on the web, available to anyone, > and each class / each package inside Pharo has a link towards its online > documentation. > This way the image size does not grow because of massive documentation. > It could be that showing the documentation of a class / package in Pharo > would directly > show inside Pharo a view of the web page corresponding to its actual > documentation. > > >> Actually GUI wise Mophics is one the best examples. Think about it, if >> you >> try to use any GUI in python for example, you are out of luck it has >> none. >> Even Tkinter which is the gui it comes with cpython is not coded in >> python >> , >> its coded in tk a scripiting language. Python GUI APIs widely used >> include >> PyGTK , PyQT , WxPython , all of them wrappers for C/C++ libraries. Other >> dynamic languages follow the same recipe. >> >> Of course these frameworks are much more documented than morphic , but >> unlike morphic they follow a monolithic widget architecture, and >> modifying >> the source in any way requires a mandatory knowledge of C/C++. And we >> should exclude their myriad of problem , GTKs notorious buginess on macos >> and windows , QT massive complexity for big GUIs up to the point it offer >> a >> dedicated programming language QML just for designing GUIs. >> >> On the other hand morphic is to a very large extend smalltalk. So you get >> a >> lot of power but also a lot more simplicity. Some areas however are in >> need >> for some more love and of course documentation is lacking and the speed >> of >> the gui is far from breathtaking. >> >> Morphic is a very big reason why I am with pharo, to be exact I find its >> ability to do visual coding and transform a smalltalk object to a visual >> element very appealing and I would love to work on that. Morphic halos is >> another very nice feature. The other reason is live coding of course. >> >> I will try to add to the documentation of morphic, I agree 100% we need >> more >> of it. >> >> FDominicus wrote >> > kilon < >> >> > thekilon@.co >> >> > > writes: >> > >> >> How does "extending Pharo help tool " sounds ? :) >> >> >> >> I am struggling to learn how morphic really works, especially >> >> TreeMorph. >> > Well that is a thing I tried more than once, but somehow I never >> > understood on how to make good use for Morphic for me. I checked a lot >> > of tutorial but then even simple things like menues seem to be doable >> > but not for me.. >> > >> > It is strange and not "nice". >> > >> > Regards >> > Friedrich >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709143.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> -- View this message in context: http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709184.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

Better text needed for contributions

by Stephan Eggermont

>Track and tag your change/Fix/Enhancement: > â¢ Add an entry to the Issues tracker describing your change (include the package version name of the package). Set the status to "Fixed". That doesn't work. Possible status changes are 'Working on' and 5 variations on 'Work needed'. And 11628 is fixed Stephan

Sept. 19, 2013

Re: [Pharo-dev] configurationOfZincHTTPComponents does not load Neo JSON

by Sven Van Caekenberghe

Sabine, On 19 Sep 2013, at 12:42, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Sven, all, > > I just found out, that one class I use, NeoJSONReader suddenly is missing > after loading new. > > Then I recognised, that in configurationOfZincHTTPComponents>>baseline24: > > there is a project 'XMLSupport' and 'Neo Json' (with NeoJSONReader) Indeed, 'Neo JSON' is declared as a sub project there. But it is only used as a dependency for a number of groups (look further down), namely 'Zinc-REST', 'Zinc-SSO-OAuth1-Core' and 'Zinc-SSO-OAuth2-Core'. But these groups are not loaded by default. So unless you load any of those groups, NeoJSON will not be loaded. Since you indicate that you did #loadStable only the default group was loaded. Sven > but if I load the configurationOfZincHTTPComponents, > ==>> both are not loaded. > > baseline24: spec > .... > spec project: 'XML Support' with: [ > spec > className: 'ConfigurationOfXMLSupport'; > versionString: #'stable'; > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > spec project: 'Neo JSON' with: [ > spec > className: 'ConfigurationOfNeoJSON'; > versionString: #'stable'; > repository: 'http://mc.stfx.eu/Neo' ]. > > For test, I used load with: > Gofer it > smalltalkhubUser: 'SvenVanCaekenberghe' project: 'ZincHTTPComponents'; > configurationOf: 'ZincHTTPComponents'; > loadStable. > > I am just reading the great new deep into pharo book and the chapter about > metacello. > It is very helpful to make my own configurationOf in the right way. > > But in this case, I dont see the reason, why this does not work :-) > Can you have a look at it, please? > > Sabine > > > > > > > > -- > View this message in context: http://forum.world.st/configurationOfZincHTTPComponents-does-not-load-Neo-J… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Sept. 19, 2013