November 2016 - Pharo-users

Re: [Pharo-users] About balkanisation

by Tudor Girba

Hi Dale, I think I missed your mails. I would be interested in hearing your opinion. Letâs aim for a chat sometime next week. Would this work for you? Cheers, Doru > On Nov 7, 2016, at 6:30 AM, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > > > On 11/6/16 1:12 PM, Tudor Girba wrote: >> Hi Stef, >> >> I think that you are raising a valid point, and I actually agree with it. >> >> But I think there is another side of the coin as well. >> >> I think that right now we are in between worlds and this is not quite beneficial. Switching to GitHub is a significant effort, and treating it as business as usual will not work. That is why I think it is so important that we committed to the move for Pharo 7 and that we invest in the infrastructure. But, this will not be enough either if we do not get people to exercise it as soon as possible. > Doru, there are also holes in the tool set that are not being addressed ... there are a number of critical tools that need to be created and I don't see anyone working on them .... > > I went through this transition 5 years ago with my tool set and with the proper set of tools approach the difficult transition will be a bit easier ... > > As it stands Pharo is standing with one foot in two boats ... there are the old Monticello tools and the new Git/Filetree tools and what is needed is a tool or two that can unify to both tool sets so that the transition between the two can be seamless ... these two sets of tools are not complicated and there working implementations that can be adapted to Pharo or used as a fairly detailed guide ... > > The confusion and frustration that I see now is not a surprise to me ... I wrote" the emails" at the beginning of this year because I saw that Pharo was finally reaching a critical point in its move to integrate git into the mainstream development environment and I knew that these types of issues were going to come up where Monticello and Git were going to create friction --- friction that can be reduced by creating some simple "unifying tools" ... > > I want to help, I have tried to help and I am still willing to help, but I cannot write the tools for Pharo ... > > Dale > -- www.tudorgirba.com www.feenk.com "There are no old things, there are only old ways of looking at them."

Nov. 7, 2016

Re: [Pharo-users] About balkanisation

by Dale Henrichs

On 11/6/16 1:12 PM, Tudor Girba wrote: > Hi Stef, > > I think that you are raising a valid point, and I actually agree with it. > > But I think there is another side of the coin as well. > > I think that right now we are in between worlds and this is not quite beneficial. Switching to GitHub is a significant effort, and treating it as business as usual will not work. That is why I think it is so important that we committed to the move for Pharo 7 and that we invest in the infrastructure. But, this will not be enough either if we do not get people to exercise it as soon as possible. Doru, there are also holes in the tool set that are not being addressed ... there are a number of critical tools that need to be created and I don't see anyone working on them .... I went through this transition 5 years ago with my tool set and with the proper set of tools approach the difficult transition will be a bit easier ... As it stands Pharo is standing with one foot in two boats ... there are the old Monticello tools and the new Git/Filetree tools and what is needed is a tool or two that can unify to both tool sets so that the transition between the two can be seamless ... these two sets of tools are not complicated and there working implementations that can be adapted to Pharo or used as a fairly detailed guide ... The confusion and frustration that I see now is not a surprise to me ... I wrote" the emails" at the beginning of this year because I saw that Pharo was finally reaching a critical point in its move to integrate git into the mainstream development environment and I knew that these types of issues were going to come up where Monticello and Git were going to create friction --- friction that can be reduced by creating some simple "unifying tools" ... I want to help, I have tried to help and I am still willing to help, but I cannot write the tools for Pharo ... Dale

Nov. 7, 2016

Re: [Pharo-users] About balkanisation

by Dale Henrichs

On 11/6/16 9:05 AM, stepharo wrote: > Hi > > I would like that you think a bit about our community and that there > is a value in using common tools > > to share and develop common libraries. Because to me it feels like we > are getting balkanize. > > > It may look super cool and be hyper trendy to use github (because like > that you can say that you use latest hyper cool > > features), but I would like to ask especially people building > libraries to pay attention that it is important > > that other people can contribute back easily and that there is an easy > way to load/contribute. > > Today I experienced Bloc > > - I cannot load code and I cannot contribute. > > - I saw mdl with a mixture between smalltalkhub and github (sounds > super hyper cool) and I saw paul not being able to contribute :( Stef, I have been working with git/monticello projects for about 5 years now and have been using a "mixed system" during that entire time ... My message has been consistent that in order to make a smooth transition that you need some specific tools, now the fact that you guys are _not_ building those tools has been concerning me for some time now ... I sent mails at the beginning of this year a) describing the tools to the best of my ability and b) offering to help ... it seems that you are somehow blaming git/github for this problem ... and as I come to this discussion late others are blaming smalltalkhub ... I don't think it is necessary to move everything to github, as I said, I have been using a "mixed system" for 5 years ... and I think that the problem lies in the lack of the proper tools ... of course your problems with Bloc may be actually totally unrelated to packages, but it is clear to me that you are frustrated with the environment ... and that is a tools problem! I can and want to help. I have had good discussions with the Pharo team, but I am afraid that I am not able to get my ... to me ... simple points across ... and it is frustrating to me that I am not able to successfully communicate the simple solutions that I see ... I will repeat that Pharo is missing some very critical tools that I consider to be absolutely required (in some form) to be able to be successful ... the required tools do not take a phd to implement, they are very straightforward and simple ... perhaps they are not sexy and complicated so noone is interested, but they are required ... If you want to have a conversation about this I am willing ... now it happens that I am in Buenos Aires (soon to be Tucuman) so this week is not convenient for me to talk ... If you don't want to talk to me then look at the series of messages that I wrote last winter/spring to this mailing list (or pharo dev) where I described what I think you guys are missing ... and then ask me questions ... Dale

Nov. 7, 2016

Re: [Pharo-users] about balkanisation

by Igor Stasenko

On 6 November 2016 at 17:21, Stephan Eggermont <stephan(a)stack.nl> wrote: > Kilon wrote: > > If you really want to embrace Github , kill Smalltalkhub > > We are not close to doing that. We'll need > Monticello support indefinitely, and at least a few years two-way. And > that assumes we automatically migrate all open projects. > > First we need good workflows that also work for complex projects. That > includes cross-platform projects like Seaside > > Oh, come on! Throw away everything you had.. and start using something new and trendy, rinse and repeat. Profit! :) > Stephan > > > > -- Best regards, Igor Stasenko.

Nov. 7, 2016

Re: [Pharo-users] may I please be added to the Mercap/HighchartsSt repo

by Mariano Martinez Peck

Paul, Quick comment: I was about to make an ANN soon but.... I have been refactoring it a LOT these last days and I did: 1) make it fully the auto-generation code (already done) 2) making it work for highcharts 5.0.2 (already done) 3) start supporting highstocks (was going to start this this week). Please please please grab the very last version. What are your plans with it? I just added you. Cbest On Sat, Nov 5, 2016 at 3:24 PM, PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: > I'd like to add code that allows the creation of boxplots: > > http://www.highcharts.com/docs/chart-and-series-types/box-plot-series > > > my username is pdebruic > > > Thanks > > -- Mariano http://marianopeck.wordpress.com

Nov. 7, 2016

Re: [Pharo-users] Pharo desktop UI

by vikenti

Maybe you can give some brief explanaition how to create Spec-compatible custom UI control? (Like TextModel or ButtonModel, etc.) How to create model class, corresponding adapter and how to process common and custom UI events (mouse\keyboard\focus ordering\changing). I think such guide should also be included in Spec booklet. On Sun, 6 Nov 2016 10:01:39 -0800 (PST) "jfabry [via Smalltalk]" <ml-node+s1294792n4921932h57(a)n4.nabble.com> wrote: > > > Hello Vikenti, > > I think that you are using the SpecAdapter for morphs in ways it has never been tried or used. So the problems you are having reveal bugs in the SpecAdapter. Please file a bug report, and feel free to contribute a fix as well of course ;-) (more about bugreports here: http://pharo.org/contribute ) > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org <http://emailcharter.org/> . > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > > On 05 Nov 2016, at 21:37, vikenti <vikenti.potapov(a)gmail.com> wrote: > > > > > > New problem with Spec. > > > > Layout consists of menu and custom control (subclass of Morph created by asSpecAdapter): > > initializeWidgets > > menu := self instantiate: MenuModel. > > self setupMenu. > > menu applyTo: self. > > locationField := LocationFieldMorph new asSpecAdapter. > > > > defaultSpec > > <spec: #default> > > ^ SpecLayout composed > > newColumn: > > [ :col | > > col > > add: #menu height: self toolbarHeight; > > add: #locationField > > ] yourself > > > > My custom control doesn't automatically resize to fill the area reserved to it by layout spec. > > I've tried different existed controls instead of mine but didn't find any solution. Some controls resized (TextModal) some didn't (Morph, BorderedMorph, EllipseMorph). > > > > I did a dirty hack: in onDraw: of my custom control i set bounds: to aCanvas clipRect and it works fine. > > > > drawOn: aCanvas > > self bounds: aCanvas clipRect . > > .... other code .... > > > > But i think it is a wrong solution and there is somewhere a simple property to setup ( or something like it ). > > > > Any ideas? > > > > > > _______________________________________________ > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/Pharo-desktop-UI-tp4921212p4921932.html > > To unsubscribe from Pharo desktop UI, visit http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no… -- Ð¡ ÑÐ²Ð°Ð¶ÐµÐ½Ð¸ÐµÐ¼, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² http://vikenti.ru ÑÐµÐ».: +7 (917) 880 25 07 (Ð³. ÐÐ°Ð·Ð°Ð½Ñ) -- View this message in context: http://forum.world.st/Pharo-desktop-UI-tp4921212p4921958.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 6, 2016

Re: [Pharo-users] Pharo Shared Memory with C++ executable

by Esteban Lorenzano

> On 6 Nov 2016, at 22:17, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > > "Now my challenges after reading the UFFI documentation are the following oh crapâ¦ I forget I have to finish that :( UFFO doc: back to my TODO list... Esteban > > 1) How I can pass things like O_CREAT , MAP_SHARED > 2) How I cast a void pointer (its what mmap returns) to a C++ string or C++ int" > > After carefully re-reading the documentation its seems the answer to question 1 is that I will have to take the constant values from the header and follow the instructions of the section "passing variables" > > About question 2, I could fetch the void pointer as return type , I know that what returns is ExternalAdress pointer but have no idea how to fetch the contents that the pointer points to. Maybe ByteArray>>integerAt:size:signed: is what I am looking for ? > > Will give it a try tomorrow. In the meanwhile I am open to suggestions.

Nov. 6, 2016

Re: [Pharo-users] Pharo Shared Memory with C++ executable

by Dimitris Chloupis

"Now my challenges after reading the UFFI documentation are the following 1) How I can pass things like O_CREAT , MAP_SHARED 2) How I cast a void pointer (its what mmap returns) to a C++ string or C++ int" After carefully re-reading the documentation its seems the answer to question 1 is that I will have to take the constant values from the header and follow the instructions of the section "passing variables" About question 2, I could fetch the void pointer as return type , I know that what returns is ExternalAdress pointer but have no idea how to fetch the contents that the pointer points to. Maybe ByteArray>>integerAt:size:signed: is what I am looking for ? Will give it a try tomorrow. In the meanwhile I am open to suggestions.

Nov. 6, 2016

Re: [Pharo-users] How to consume the MOOC?

by Luke Gorrie

Hi Stepharo, On 5 November 2016 at 18:14, stepharo <stepharo(a)free.fr> wrote: > you can use the webportal (it supports subtitles in french and english - > but read carefully what we wrote because we got trapped into a bug with > certain configurations). > > http://rmod-pharo-mooc.lille.inria.fr/MOOC/WebPortal/co/pharo.html Thanks for this link! I had somehow missed the webportal and this looks like the right thing for me.

Nov. 6, 2016

Re: [Pharo-users] [ALERT] Pharo by Example version 5 is about to be released

by Dimitris Chloupis

yeah as I said the chapter needs a complete rewrite. I am not even it is necessary to exist separately. On Sun, Nov 6, 2016 at 9:27 PM Nicolai Hess <nicolaihess(a)gmail.com> wrote: > 2016-11-03 15:11 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > > 2016-11-03 15:02 GMT+01:00 stepharo <stepharo(a)free.fr>: > > Hi nicolai > > I started to work on the reflection chapter. > > > > The reflection chapter (and maybe some other too) could new some new > screenshots. > > > Actually, the reflection chapter needs some more rewrites (not only > updated screenshots). Some examples just aren't > applicable anymore because we don't have refactoring browser preinstalled > and although Nautilus can do alot, its missing > the full set of menus for creating scoped environments. > I'll try to rewrite those parts. > > > Now hacking PharoDoc :) > > Stef > > Le 3/11/16 Ã 14:29, Nicolai Hess a Ã©crit : > > > > 2016-10-27 13:32 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > > In case someone missed it I will be doing a release for version 5 (pharo > version = pbe version) this weekend , since we had Pharo 7 initiated few > days ago. > > Essentially that means that the repo will be tagged for version 5, which > means a git commit is associated as a last commit for that version and > there will be a frozen release - download for Pharo by Example version 5. > After that we move to Pharo By Example version 6 or PBE6 for short > > The repo wont change otherwise and the process of submitting commits, pull > requests and issues remains the same. > > If you have found a flaw of any sort in the documentation , please open an > issue in the github issue tracker that can be found here > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues > > I will try to fix any problem reported but if I cannot , the fix will have > to move to version 6 > > As always thanks to all people contributing into the impossible .... > making Pharo more amazing > > If you want to contribute feel free to do so with a pull request. > > Does not matter if you are beginner because even minor corrections like > correcting mistakes in the grammar or content of the text, updated > pictures, or just a few lines of extra info are more than enough and more > than welcomed. Many Pharo beginners have already done so . > > -Salute to fellow Guardians of The Light > > > I found some problems, but I don't have time to report/fix them now, I 'll > try to report them > later (today or tomorrow). > > > > >

Nov. 6, 2016