July 2014 - Pharo-dev - lists.pharo.org

Project Watch on SThub

by Torsten Bergmann

STHub allows one to "watch" a project, meaning one can get infos on the commits and history of watched projects under in his own home section in "Recent watched events". Unfortunately it does not update, always displays events from 2013 and either it is my profile or a general bug in STHub... Any comments?

July 23, 2014

[ANN] ODBC package on STHub

by Torsten Bergmann

The ODBC package is now migrated from SqueakSource to SmalltalkHub and available under http://smalltalkhub.com/#!/~PharoExtras/ODBC I also cleaned up a little bit and made some stuff working on Pharo 3.0 again. You can now als easily load it from the config browser. Repo is open for contributions. Have fun. Thanks T.

July 23, 2014

Re: [Pharo-dev] transformmorph and submorph bounds

by Tudor Girba

Hi, On Wed, Jul 23, 2014 at 11:45 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > > > > 2014-07-23 11:10 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi, >> >> >> >> >> >>> This seems correct to me: a transformMorph is the one which shift its >>> contents (and reset the origin to its top left corner ?). >>> >> >> Not really. The contract of submorphBounds should be that it returns an >> absolute coordinate, as far as I understand. >> > > In owner coordinates it says. (TransformMorph) > > However, it effectively returns a 0@0 origin. > > >> >> >>> Why do you use a TransformMorph there? >>> >> >> It is used for example in ScrollPane. This means that if you embed a >> TextMorph inside a ScrollPane, you will have the same problem with >> completion: >> >> scrollPane := ScrollPane new. >> pasteUpMorph := PasteUpMorph new. >> scrollPane scroller addMorph: pasteUpMorph. >> scrollPane openInWindow top: 100; left: 100. >> >> pasteUpMorph submorphBounds "(0@0) corner: (50@40)" >> > > Yes. > > What do you want to do about it? Rewrite a scroll pane in a different way? > Or make sure that everything which creates over-morphs ask for global > coordinates? > Ahh. I found it. The proper selector should not be submorphBounds but positionInWorld. This one works properly. > I guess this has also something to do with the glamour bug inside tabs, no? > Not inside tabs, but inside the a Finder or a Pager. Now, completion work properly! Cheers, Doru > Thierry > > -- www.tudorgirba.com "Every thing has its own flow"

July 23, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Tudor Girba

Just a point. We should definitely not throw away TxText :). My message was that we should stop investing in the TextMorph. I suggested Rubric because it is available now and can be integrated with visible improvements over what exists. But, TxText should be the future. Perhaps we can already commit to it for Pharo 4.0 and then we make it a goal for the whole community to get it finished. I would be supportive for such a decision. Doru On Wed, Jul 23, 2014 at 11:46 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Not yet :(. It's the first thing after releasing the current > implementation of GT and Moose. > > Doru > > > On Wed, Jul 23, 2014 at 11:22 AM, stepharo <stepharo(a)free.fr> wrote: > >> >> On 22/7/14 14:43, Tudor Girba wrote: >> >> First of all: Excellent job! >> >> About the editor: I would indeed suggest adopting Rubric as a solution >> for now (until the new Text widget comes around). We use it extensively in >> GT and I can attest that it is better than PluggableTextMorph. >> >> >> doru did you loaded TxText? >> and TxViewContainer example2 >> >> >> Doru >> >> >> On Tue, Jul 22, 2014 at 2:05 PM, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >> >>> >>> On 22 Jul 2014, at 13:57, stepharo <stepharo(a)free.fr> wrote: >>> >>> >>> On 22/7/14 10:41, Clara Allende wrote: >>> >>> Hi guys! >>> Finally the metaLink-based breakpoints are "ready". I have made some >>> explanations on my blog >>> <https://clariallende.wordpress.com/2014/07/21/smartbreakpoints-alpha-releas…>, >>> but basically now you have the option "break here" in SmartSuggestions menu. >>> So it's still experimental, and even though I have some tests, it would >>> be nice if you can test it, because I can't cover all possible use cases :) >>> And any feedback is most appreciated! >>> >>> Specially, since eventually we will have several kinds of breakpoints, >>> I would like to ask in which way would you like to choose them (a pop menu? >>> a sublist?) >>> >>> Thanks in advance! >>> >>> PS: The script for downloading the code is in the blog post :P >>> PS2: After talking with Anne and Baptiste, things that are not there >>> *yet* but I want to have: >>> * a highlight on the method/messageSend where the breakpoint is inserted >>> * expose persistent breakpoints (it is there but the default is to halt >>> once) >>> * line breakpoints (not sure when, for now the breakpoints are AST based) >>> * integration with TextEditor, once it is done ;) >>> >>> >>> Can you grab igor and sit with him to get this point? >>> >>> Another idea would be to use the editor in Moose (Rubrik?). >>> Better a solution now than to wait forever for perfectionâ¦ >>> >>> Marcus >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

July 23, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Tudor Girba

Hi, Not yet :(. It's the first thing after releasing the current implementation of GT and Moose. Doru On Wed, Jul 23, 2014 at 11:22 AM, stepharo <stepharo(a)free.fr> wrote: > > On 22/7/14 14:43, Tudor Girba wrote: > > First of all: Excellent job! > > About the editor: I would indeed suggest adopting Rubric as a solution > for now (until the new Text widget comes around). We use it extensively in > GT and I can attest that it is better than PluggableTextMorph. > > > doru did you loaded TxText? > and TxViewContainer example2 > > > Doru > > > On Tue, Jul 22, 2014 at 2:05 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> On 22 Jul 2014, at 13:57, stepharo <stepharo(a)free.fr> wrote: >> >> >> On 22/7/14 10:41, Clara Allende wrote: >> >> Hi guys! >> Finally the metaLink-based breakpoints are "ready". I have made some >> explanations on my blog >> <https://clariallende.wordpress.com/2014/07/21/smartbreakpoints-alpha-releas…>, >> but basically now you have the option "break here" in SmartSuggestions menu. >> So it's still experimental, and even though I have some tests, it would >> be nice if you can test it, because I can't cover all possible use cases :) >> And any feedback is most appreciated! >> >> Specially, since eventually we will have several kinds of breakpoints, >> I would like to ask in which way would you like to choose them (a pop menu? >> a sublist?) >> >> Thanks in advance! >> >> PS: The script for downloading the code is in the blog post :P >> PS2: After talking with Anne and Baptiste, things that are not there >> *yet* but I want to have: >> * a highlight on the method/messageSend where the breakpoint is inserted >> * expose persistent breakpoints (it is there but the default is to halt >> once) >> * line breakpoints (not sure when, for now the breakpoints are AST based) >> * integration with TextEditor, once it is done ;) >> >> >> Can you grab igor and sit with him to get this point? >> >> Another idea would be to use the editor in Moose (Rubrik?). >> Better a solution now than to wait forever for perfectionâ¦ >> >> Marcus >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

July 23, 2014

Re: [Pharo-dev] transformmorph and submorph bounds

by Thierry Goubier

2014-07-23 11:10 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > > > > >> This seems correct to me: a transformMorph is the one which shift its >> contents (and reset the origin to its top left corner ?). >> > > Not really. The contract of submorphBounds should be that it returns an > absolute coordinate, as far as I understand. > In owner coordinates it says. (TransformMorph) However, it effectively returns a 0@0 origin. > > >> Why do you use a TransformMorph there? >> > > It is used for example in ScrollPane. This means that if you embed a > TextMorph inside a ScrollPane, you will have the same problem with > completion: > > scrollPane := ScrollPane new. > pasteUpMorph := PasteUpMorph new. > scrollPane scroller addMorph: pasteUpMorph. > scrollPane openInWindow top: 100; left: 100. > > pasteUpMorph submorphBounds "(0@0) corner: (50@40)" > Yes. What do you want to do about it? Rewrite a scroll pane in a different way? Or make sure that everything which creates over-morphs ask for global coordinates? I guess this has also something to do with the glamour bug inside tabs, no? Thierry

July 23, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by stepharo

On 22/7/14 14:43, Tudor Girba wrote: > First of all: Excellent job! > > About the editor: I would indeed suggest adopting Rubric as a solution > for now (until the new Text widget comes around). We use it > extensively in GT and I can attest that it is better than > PluggableTextMorph. doru did you loaded TxText? and TxViewContainer example2 > > Doru > > > On Tue, Jul 22, 2014 at 2:05 PM, Marcus Denker <marcus.denker(a)inria.fr > <mailto:marcus.denker@inria.fr>> wrote: > > > On 22 Jul 2014, at 13:57, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > >> >> On 22/7/14 10:41, Clara Allende wrote: >>> Hi guys! >>> Finally the metaLink-based breakpoints are "ready". I have made >>> some explanations on my blog >>> <https://clariallende.wordpress.com/2014/07/21/smartbreakpoints-alpha-releas…>, >>> but basically now you have the option "break here" in >>> SmartSuggestions menu. >>> So it's still experimental, and even though I have some tests, >>> it would be nice if you can test it, because I can't cover all >>> possible use cases :) >>> And any feedback is most appreciated! >>> >>> Specially, since eventually we will have several kinds of >>> breakpoints, I would like to ask in which way would you like to >>> choose them (a pop menu? a sublist?) >>> >>> Thanks in advance! >>> >>> PS: The script for downloading the code is in the blog post :P >>> PS2: After talking with Anne and Baptiste, things that are not >>> there *yet* but I want to have: >>> * a highlight on the method/messageSend where the breakpoint is >>> inserted >>> * expose persistent breakpoints (it is there but the default is >>> to halt once) >>> * line breakpoints (not sure when, for now the breakpoints are >>> AST based) >>> * integration with TextEditor, once it is done ;) >> >> Can you grab igor and sit with him to get this point? > Another idea would be to use the editor in Moose (Rubrik?). > Better a solution now than to wait forever for perfectionâ¦ > > Marcus > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

July 23, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by stepharo

>> Can you grab igor and sit with him to get this point? > Another idea would be to use the editor in Moose (Rubrik?). > Better a solution now than to wait forever for perfectionâ¦ We can also abandon TxText but after we should not cry that it does not scale (be prepared to fork a lot of processes in the background). But I think that it would be stupid so we should push igor to deliver. And if I'm alone pushing then this is not fun. Have a look at TxViewContainer example2 Stef > > Marcus >

July 23, 2014

Re: [Pharo-dev] First attempt at submitting a simple contribution

by stepharo

Thanks tim. Usually the monkey will tag your entry to ready to integrate and we harvest them. After this is also nice to write a comment saying that your change is ok in the latest image and we will integrate. We would like to change the integration process but we are not yet there. Git is needed first. We are getting more integrator: clement (on the compiler domain), nicolai and this is good. Sven is integrating changes related to the network Stef On 22/7/14 17:48, Tim Mackinnon wrote: > Hi guys - Iâve tried to submit a very simple contribution for Pharo. I followed the steps in the video about submitting on Fogbugz - although I wonder if I missed a step by not asking for commit rights to the Pharo40Inbox? As I already had a smalltalk hub account - it asked for that name and password and it didnât complain when I entered them and pressed accept in Pharo. > > The issue is: 13653 > > Its a very simple contribution, just a class with some wiki help and the wiki method pragma to get it to appear in the System help. > > As I didnât know if there was already a class that might better hold this text, I created a new one - but happy to move it onto something else if there is somewhere obvious (or maybe its cleaner that it lives in its own place?). > > Tim >

July 23, 2014

Re: [Pharo-dev] future of Nautilus (the non package tree version)

by stepharo

Yes but I think that it is necessary. What esteban introduced was nice: a design with less conditional. Stef > > On 22 Jul 2014, at 14:26, Nicolai Hess <nicolaihess(a)web.de > <mailto:nicolaihess@web.de>> wrote: > >> From time to time it happens that we introduce bugs in the "old" >> Nautilus >> browser if we do changes for the default browser >> (PackageTreeNautilus) >> For example: >> 13640 <https://pharo.fogbugz.com/default.asp?13640> >> no menu on package pane in Nautilus (the non package tree nautilus) >> >> Is a working "old" Nautilus on high priority? Or should we consider >> PackageTreeNautilus as a replacement for Nautilus? > > yes. > I made the PackageTreeNautilus as a replacement, but an extension > because I was using Nautilus to develop Nautilus. > Now we should merge it. > > > This might be a big effort, but this also gives us the opportunity to > clean up. > > > > Esteban > >> >> nicolai >> >> > >

July 23, 2014