- Pharo-users - lists.pharo.org

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

the importance of your story

by Tudor Girba

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] Proposed fix for RFB. Please review

by stepharo

Welcome christer and thanks for sharing your fix. I hope a guy will reply to you. To me it looks ok :) but I never looked at RFB Stef Le 22/6/15 18:29, Christer Assmundsson a Ã©crit : > Hi all, > > I have fixed (?) an issue in RFB server that seems to solve a problem > I had with initiating a session. After the fix it works at least with > UltraVnc. Still not with tightVnc though, has to be some other problem > with that. > > As I'm not very experienced with pharo I'd like to have somebody elses > eyes on it before checking it in to SmaltalkHub (if I even have access > to that). Quality status on the fix is "works on my machine" > > At the start of RFBSession>> sendFramebufferUpdate > > | updateRegion nRects sendCursor sendPosition | > preferredEncoding ifNil: [^self]. > "<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< new code" > self beginUpdate. > ... > > Reasoning: Until we know what encoding to use, we can't send updates. > Just discard them. It will be picked up later. > Technical: Futher down in the method we call "countRects" which is not > set until we set encoding, and therefore the method fails with DNU. > > Please let me know how I should proceed. > > Best regards, > Christer > >

June 25, 2015

Re: [Pharo-users] OpenCL problems since we switch to OS X 10.10.3

by Ben Coman

Just some random ideas... Seems some others are having problems... http://preta3d.com/os-x-users-unite/ Only a shot in the dark, not sure if it relates (search for OpenCL and Chrome)... https://forums.adobe.com/thread/1393885?start=120&tstart=0 Another shot in the dark, just looking for things you might turn off: * https://developer.apple.com/library/mac/documentation/Performance/Conceptua… * When it crashes, does it list come file/libraries with OpenCL in their name. Use some system tool like `lsof` to see if there are other program is using those files, and see if you can identify something to turn off. Alternate drivers http://www.tonymacx86.com/graphics/161334-nvidia-releases-alternate-graphic… cheers -ben On Wed, May 20, 2015 at 11:05 PM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > Hi Ronie, > > since we switch here from OS X 10.10.2 to 10.10.3, your OpenCL > framework doesn't not work anymore ... We crash Pharo everytime we try > to use GPU. > > This is an except of the crash log: > > Process: Pharo [21039] > Path: /Applications/Pharo.app/Contents/MacOS/Pharo > Identifier: org.pharo.Pharo > Version: Pharo 0.2.7-2015.04.20 (21.0) > Code Type: X86 (Native) > Parent Process: ??? [1] > Responsible: Pharo [21039] > User ID: 502 > > Date/Time: 2015-05-20 16:50:33.740 +0200 > OS Version: Mac OS X 10.10.3 (14D136) > Report Version: 11 > Anonymous UUID: 53101D99-4009-6151-7D46-D4F943A588CF > > Sleep/Wake UUID: D65CFFA9-9DD4-490B-99A5-D5A3F37C8649 > > Time Awake Since Boot: 240000 seconds > Time Since Wake: 19000 seconds > > Crashed Thread: 0 Dispatch queue: opencl_runtime > > Exception Type: EXC_BAD_ACCESS (SIGABRT) > Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020 > > What can we do ? Apparently this is difficult to downgrade back to 10.10.2 > > Regards > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

June 24, 2015