June 2015 - Pharo-users - lists.pharo.org

DNS level changes for smalltalkhub.com Friday

by Marcus Denker

Hello, Friday morning we will do some DNS level changes for smalltalkhub.com. This should normally have no impact on the server, as the new DNS server will point to the same IP as the old. Marcus

June 25, 2015

Re: [Pharo-users] the importance of your story

by Thierry Goubier

2015-06-25 15:56 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Thanks Doru for your inspiring words. > > Recently I had a âcoup de bluesâ because Pharo is completely absent from > the StackOverflow and Github scene. I feel it is like a researcher without > a webpage. Without a webpage, he does not exist. > Well, we could put Roassal on github ;) > > But I have faith things will soon change... > I hope so. It would make Roassal configurations and versions a tad easier :) If I was to use Roassal in a professionnal product, I'd be really tempted to do a freeze of Roassal on github along with a few of its dependencies :P Thierry > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Jun 25, 2015, at 8:39 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". > While the talk is less technical, I did exemplified the message by demoing > Spotter in comparison with the search support from Eclipse. > > There are several things I would like to emphasize. > > I compared our solution with an "industry standard" one. We often think > our system as being niche and perhaps not mature enough. We need to change > that perception about our work. We build state of the art. > > One thing that I did not mention explicitly in the talk is the size of the > implementation. The Spotter implementation is 3500 lines of code -- and > that it is so large because it currently comes with its own widgets. > Furthermore, the extensions average 8 lines per custom processor (including > the method header and the pragma). This is orders of magnitude smaller than > what is typically out there, and it is precisely the reason why we can > compete even if we are fewer. > > But, to get out there and compete we have to set that high goal for > ourselves. For example, with GT we do not want to compete. We want to > outcompete. So can you. > > While details are important, high goals require us to get away from those > details. Only polishing details will tend to limit you to incremental > improvements. We need to jump from time to time. But, these jumps are hard. > On the one hand, it is hard to find the right jump and convince people to > jump with you. On the other hand, they are hard to predict. For example, > Spotter would have not been predictable one year ago. > > Yet, dry goals are not enough to keep us going. We need stories that make > us dream. And the beauty is that Pharo breaths such a story. We should not > limit ourselves to that story only. For example, with GT we want to > reinvent the developer experience by making the developer be able to mold > visual tools to her context because that is the only effective way to build > sustainable systems. This little point of view will turn the IDE upside > down, and this is only possible in a system like Pharo. > > Choose your high goal and tell its story through the system that you > build. And remember that Pharo already offers a beautiful story to start > from. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > >

June 25, 2015

Re: [Pharo-users] the importance of your story

by Alexandre Bergel

Thanks Doru for your inspiring words. Recently I had a âcoup de bluesâ because Pharo is completely absent from the StackOverflow and Github scene. I feel it is like a researcher without a webpage. Without a webpage, he does not exist. But I have faith things will soon change... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 25, 2015, at 8:39 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse. > > There are several things I would like to emphasize. > > I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art. > > One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer. > > But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you. > > While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago. > > Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo. > > Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from. > > Cheers, > Doru > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

June 25, 2015

Re: [Pharo-users] Morphs automatic repositioning (and resizing)

by Denis Kudriashov

Hello. You can play with any visible morphs with halo menu "layout" to change layouting strategy for it children. And you will see livelly what supported. 2015-06-25 15:49 GMT+03:00 Mark Rizun <mrizun(a)gmail.com>: > Hello, everyone! > > Let's say I have morph which contains few other morphs. > Is there any way to reposition all these submorphs (if needed resize, but > it's optional), so that they do not intersect with each other? > > Thanks in advance, > Mark > > > > -- > View this message in context: > http://forum.world.st/Morphs-automatic-repositioning-and-resizing-tp4834043… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 25, 2015

Re: [Pharo-users] Morphs automatic repositioning (and resizing)

by Thierry Goubier

2015-06-25 15:32 GMT+02:00 Mark Rizun <mrizun(a)gmail.com>: > you can compose by putting your morphs into AlignmentMorph instances >> (order them by rows or columns), and you add the AlignmentMorph instances >> to your top level morph. You'll have to play with the #spaceFill or >> #shrinkWrap layout resizing options for your morphs to handle filling the >> available space. >> > > I'll try this approach first. > I forgot that I used the SmaCC GUI code as a reference to remember, because I find the API confusing. So, have a look at those methods: https://github.com/ThierryGoubier/SmaCC/blob/master/SmaCC-Development-UI.pa… https://github.com/ThierryGoubier/SmaCC/blob/master/SmaCC-Development-UI.pa… Any of the addXXX methods in there does some stuff: you have a tabbed GUI, mix of buttons and labels, multiple text areas... Things missing are a menu bar and drop down menus :) > > >> This answer applies to bare, good old Morphic. Spec is something else if >> this is what you are using, Bloc as well. >> > > Yes, I'm working with bare Morphic. At least for now :) > Once you get the hang of it, it clearly works. But, at the same time, the API seems very painfull to use, full of strange symbols and very long methods. And additionnally you get into layout bugs if you spend time resizing too many times :( I'd dream of being able to write something like: [button1]-12-[button2][1] But even if the tech is Smalltalk-originated[2], it seems we won't see it anytime soon. [1] https://developer.apple.com/library/ios/documentation/UserExperience/Concep… [2] https://constraints.cs.washington.edu/cassowary/ > > Thanks a lot! > You're welcome, Thierry

June 25, 2015

Re: [Pharo-users] Morphs automatic repositioning (and resizing)

by Yuriy Tymchuk

> On 25 Jun 2015, at 15:32, Mark Rizun <mrizun(a)gmail.com> wrote: > > you can compose by putting your morphs into AlignmentMorph instances (order them by rows or columns), and you add the AlignmentMorph instances to your top level morph. You'll have to play with the #spaceFill or #shrinkWrap layout resizing options for your morphs to handle filling the available space. > > I'll try this approach first. > > This answer applies to bare, good old Morphic. Spec is something else if this is what you are using, Bloc as well. > > Yes, I'm working with bare Morphic. At least for now :) Welcome to the club. > > Thanks a lot!

June 25, 2015

Re: [Pharo-users] Morphs automatic repositioning (and resizing)

by Mark Rizun

> > you can compose by putting your morphs into AlignmentMorph instances > (order them by rows or columns), and you add the AlignmentMorph instances > to your top level morph. You'll have to play with the #spaceFill or > #shrinkWrap layout resizing options for your morphs to handle filling the > available space. > I'll try this approach first. > This answer applies to bare, good old Morphic. Spec is something else if > this is what you are using, Bloc as well. > Yes, I'm working with bare Morphic. At least for now :) Thanks a lot!

June 25, 2015

Re: [Pharo-users] Morphs automatic repositioning (and resizing)

by Thierry Goubier

Hi Mark, you can compose by putting your morphs into AlignmentMorph instances (order them by rows or columns), and you add the AlignmentMorph instances to your top level morph. You'll have to play with the #spaceFill or #shrinkWrap layout resizing options for your morphs to handle filling the available space. An alternative is to work the positions and proportions by hand with layout frames (x pixels from the left, etc...), as if you were doing a MVC view in VisualWorks :) You can also have slider objects to be able to change proportions interactively, but I've never found the container API understandable (and the hack so ugly when looking how it is implemented) that I create those by hand and add them to the view when I need them. And it has bugs... This answer applies to bare, good old Morphic. Spec is something else if this is what you are using, Bloc as well. Thierry 2015-06-25 14:49 GMT+02:00 Mark Rizun <mrizun(a)gmail.com>: > Hello, everyone! > > Let's say I have morph which contains few other morphs. > Is there any way to reposition all these submorphs (if needed resize, but > it's optional), so that they do not intersect with each other? > > Thanks in advance, > Mark > > > > -- > View this message in context: > http://forum.world.st/Morphs-automatic-repositioning-and-resizing-tp4834043… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 25, 2015

Morphs automatic repositioning (and resizing)

by Mark Rizun

Hello, everyone! Let's say I have morph which contains few other morphs. Is there any way to reposition all these submorphs (if needed resize, but it's optional), so that they do not intersect with each other? Thanks in advance, Mark -- View this message in context: http://forum.world.st/Morphs-automatic-repositioning-and-resizing-tp4834043… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 25, 2015

Re: [Pharo-users] the importance of your story

by Tudor Girba

And here is the video: https://vimeo.com/131632605 On Thu, Jun 25, 2015 at 1:39 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". > While the talk is less technical, I did exemplified the message by demoing > Spotter in comparison with the search support from Eclipse. > > There are several things I would like to emphasize. > > I compared our solution with an "industry standard" one. We often think > our system as being niche and perhaps not mature enough. We need to change > that perception about our work. We build state of the art. > > One thing that I did not mention explicitly in the talk is the size of the > implementation. The Spotter implementation is 3500 lines of code -- and > that it is so large because it currently comes with its own widgets. > Furthermore, the extensions average 8 lines per custom processor (including > the method header and the pragma). This is orders of magnitude smaller than > what is typically out there, and it is precisely the reason why we can > compete even if we are fewer. > > But, to get out there and compete we have to set that high goal for > ourselves. For example, with GT we do not want to compete. We want to > outcompete. So can you. > > While details are important, high goals require us to get away from those > details. Only polishing details will tend to limit you to incremental > improvements. We need to jump from time to time. But, these jumps are hard. > On the one hand, it is hard to find the right jump and convince people to > jump with you. On the other hand, they are hard to predict. For example, > Spotter would have not been predictable one year ago. > > Yet, dry goals are not enough to keep us going. We need stories that make > us dream. And the beauty is that Pharo breaths such a story. We should not > limit ourselves to that story only. For example, with GT we want to > reinvent the developer experience by making the developer be able to mold > visual tools to her context because that is the only effective way to build > sustainable systems. This little point of view will turn the IDE upside > down, and this is only possible in a system like Pharo. > > Choose your high goal and tell its story through the system that you > build. And remember that Pharo already offers a beautiful story to start > from. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

June 25, 2015