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

Re: [Pharo-dev] About Morphic Documentation

by ClÃ©ment Bera

2013/9/19 kilon <thekilon(a)yahoo.co.uk> > 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. > >

Sept. 19, 2013

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

by Camillo Bruni

I made you admin under https://ci.inria.fr/pharo-contribution/? you should be able to follow the detailed instructions. Windows slave is ready under pharo-contribution. On 2013-09-19, at 03:21, "Torsten Bergmann" <astares(a)gmx.de> wrote: > Damien wrote: >> Do you already have continuous integration set up or do you want me to do it? > > No, not yet. I've a CI account but was not able to create projects with it. > > Would be nice if you could help setting it up. Obvious that it requires > a windows slave. > > The code already takes care that the tests run only on Windows (there is a class > WindowsSpecificTest as a subclass of TestCase overriding #isAbstract). > > Bye > T. >

Sept. 19, 2013

Re: [Pharo-dev] [update 3.0] #30407

by Mariano Martinez Peck

On Thu, Sep 19, 2013 at 6:10 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 30407 > ----- > > 11631 Disable History navigation buttons in Inspectors when not usable > https://pharo.fogbugz.com/f/cases/11631 > > 11413 Make a diff tool to show recategorization as a change properly > https://pharo.fogbugz.com/f/cases/11413 This is soooooo COOOOl!! THanks guys! > > > 11632 Add browse shortcut to critics browser > https://pharo.fogbugz.com/f/cases/11632 > > > Diff information: > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.7… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.11… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Tools-Diff-MarcusDe… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-MarcusDenker.865.d… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-Marcus… > > -- Mariano http://marianopeck.wordpress.com

Sept. 19, 2013

Re: [Pharo-dev] voyage/mongo reset vs. allInstancesDo: #reset

by Sabine KnÃ¶fel

yes it does! Thanks! Sabine :-) On Thu, Sep 19, 2013 at 1:41 PM, EstebanLM [via Smalltalk] < ml-node+s1294792n4709144h59(a)n4.nabble.com> wrote: > VORepository current > > should be an instance of VOMongoRepository, not the class > so, it should not be the same... and it should clean everything. > > Esteban > > On Sep 19, 2013, at 12:50 PM, Sabine KnÃ¶fel <[hidden email]<http://user/SendEmail.jtp?type=node&node=4709144&i=0>> > wrote: > > Hi Esteban, > > in my image, the result of > VORepository current is ==>> VOMongoRepository > > so, > > VORepository current reset. > it is the same as > VOMongoRepository reset > > Cheers > Sabine > > > On Thu, Sep 19, 2013 at 12:24 PM, EstebanLM [via Smalltalk] <<a > href="x-msg://9891/user/SendEmail.jtp?type=node&node=4709134&i=0" > target="_top" rel="nofollow" link="external">[hidden email]> wrote: > >> Hi Sabine, >> >> The right message to reset is: >> >> VORepository current reset. >> >> I don't know what "VOMongoRepository reset" does (I need to check it) :P >> >> Cheers, >> Esteban >> >> >> On Sep 19, 2013, at 11:38 AM, Sabine KnÃ¶fel <[hidden email]<http://user/SendEmail.jtp?type=node&node=4709130&i=0>> >> wrote: >> >> > Hi Esteban, all, >> > >> > in the mongo/voyage tutorial at ESUG, I understood, that >> > >> > "VOMongoRepository reset" can be used instead of >> > "VOMongoRepository allInstancesDo: #reset". >> > and the code looks like that ( flush...) >> > >> > It seems that I can't - I think, using "VOMongoRepository reset" does >> _not_ >> > reset the cache. >> > So, the objects are not read new from database. >> > Voyage does not enter the <mongoDescription> methods. >> > >> > This is not a problem for me, I can also use "VOMongoRepository >> > allInstancesDo: #reset", but I want to tell you about that. >> > >> > To reproduce I did the following, >> > 1) read objects from mongo (ClassXXX readAll) >> > 2) put halt in one of the <mongoDescription> methods >> > 3 a) do "VOMongoRepository reset" and then (ClassXXX readAll) again -> >> no >> > debugger >> > 3 b) do "VOMongoRepository allInstancesDo: #reset" and then (ClassXXX >> > readAll) again -> debugger comes up >> > ==> so, 3a does not work, 3b works >> > >> > Regards >> > Sabine >> > >> > >> > >> > -- >> > View this message in context: >> http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120.… >> > Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > >> >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the >> discussion below: >> >> http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120p… >> To unsubscribe from voyage/mongo reset vs. allInstancesDo: #reset, <a >> href="x-msg://9891/" target="_blank" rel="nofollow" link="external">click >> here. >> NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> > > > ------------------------------ > View this message in context: Re: voyage/mongo reset vs. allInstancesDo: > #reset<http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120p…> > Sent from the Pharo Smalltalk Developers mailing list archive<http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html>at > Nabble.com. > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120p… > To unsubscribe from voyage/mongo reset vs. allInstancesDo: #reset, click > here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

Re: [Pharo-dev] Can't correctly inspect ring definitions

by Martin Dias

>> To me it looks wrong for RGClassDefinition implementing #instVarNamed:. > > probably (this is the question of layering) now it also means that we should have a look at the class protocol to access instance variables > so that we have an Object API but also a good Class/RingClass API. > > Stef I didn't understand what you said. I think this is false polymorphism here: Object >> instVarNamed: ---> answers the value of the inst var (or raises an error if it doesn't exist) RGClassDescriptionDefinition >> instVarNamed: ---> answers a RGInstanceVariableDefinition (or nil if it doesn't exist) MartÃn

Sept. 19, 2013

Re: [Pharo-dev] voyage/mongo reset vs. allInstancesDo: #reset

by Esteban Lorenzano

VORepository current should be an instance of VOMongoRepository, not the class so, it should not be the same... and it should clean everything. Esteban On Sep 19, 2013, at 12:50 PM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Esteban, > > in my image, the result of > VORepository current is ==>> VOMongoRepository > > so, > > VORepository current reset. > it is the same as > VOMongoRepository reset > > Cheers > Sabine > > > On Thu, Sep 19, 2013 at 12:24 PM, EstebanLM [via Smalltalk] <[hidden email]> wrote: > Hi Sabine, > > The right message to reset is: > > VORepository current reset. > > I don't know what "VOMongoRepository reset" does (I need to check it) :P > > Cheers, > Esteban > > > On Sep 19, 2013, at 11:38 AM, Sabine KnÃ¶fel <[hidden email]> wrote: > > > Hi Esteban, all, > > > > in the mongo/voyage tutorial at ESUG, I understood, that > > > > "VOMongoRepository reset" can be used instead of > > "VOMongoRepository allInstancesDo: #reset". > > and the code looks like that ( flush...) > > > > It seems that I can't - I think, using "VOMongoRepository reset" does _not_ > > reset the cache. > > So, the objects are not read new from database. > > Voyage does not enter the <mongoDescription> methods. > > > > This is not a problem for me, I can also use "VOMongoRepository > > allInstancesDo: #reset", but I want to tell you about that. > > > > To reproduce I did the following, > > 1) read objects from mongo (ClassXXX readAll) > > 2) put halt in one of the <mongoDescription> methods > > 3 a) do "VOMongoRepository reset" and then (ClassXXX readAll) again -> no > > debugger > > 3 b) do "VOMongoRepository allInstancesDo: #reset" and then (ClassXXX > > readAll) again -> debugger comes up > > ==> so, 3a does not work, 3b works > > > > Regards > > Sabine > > > > > > > > -- > > View this message in context: http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120.… > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120p… > To unsubscribe from voyage/mongo reset vs. allInstancesDo: #reset, click here. > NAML > > > View this message in context: Re: voyage/mongo reset vs. allInstancesDo: #reset > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

About Morphic Documentation

by kilon

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. 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.

Sept. 19, 2013

Re: [Pharo-dev] Please help us by buying the book

by kilon

Damien Cassou wrote > On Tue, Sep 17, 2013 at 12:22 AM, kilon < > thekilon@.co > > wrote: >> how long for the amazon version ? I am Greek and I am not sure if the >> first >> choice delivers here. > > > the amazon version is there: http://deepintopharo.com/. > > Still, we get more money if you go through lulu. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill fair enough I will get it through lulu, I already have the pdf version anyway so its not that I can't wait. -- View this message in context: http://forum.world.st/Please-help-us-by-buying-the-book-tp4708575p4709141.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

Re: [Pharo-dev] Please help us by buying the book

by Damien Cassou

On Tue, Sep 17, 2013 at 12:22 AM, kilon <thekilon(a)yahoo.co.uk> wrote: > how long for the amazon version ? I am Greek and I am not sure if the first > choice delivers here. the amazon version is there: http://deepintopharo.com/. Still, we get more money if you go through lulu. -- 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] [OT] Pharo lighthouse wallpaper

by kilon

Not quite similar to the pharo logo , but more beautiful ;) here is a greek "ÏÎ±ÏÎ¿Ï" pharo in island of Andros <http://forum.world.st/file/n4709139/assets_LARGE_t_420_9515549.jpg> <http://forum.world.st/file/n4709139/pharos.jpg> Its also how I picture pharo in general, virtually unknown, isolated yet surrounded by beauty and elegance ;) -- View this message in context: http://forum.world.st/OT-Pharo-lighthouse-wallpaper-tp4709069p4709139.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013