- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] CALL for GSoC project proposals

by Stephane Ducasse

Hi yuriy you could have done it a bit less brutal. Stef On Wed, Jan 25, 2017 at 10:52 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Dear all, this year we plan to apply again as a mentoring organization for > Google Summer of Code. However, we are going to follow a different strategy > regarding project proposals. Instead of having a swarm of small ideas we > want to end up with around ten well-described projects. > > This is why I cleaned the topics file, and I ask all interested people to > propose the best one of your topics here: > https://github.com/pharo-project/pharo-project- > proposals/blob/master/Topics.st > > There is a copy of the old file in case you want to remind what you > proposed last year: > https://github.com/pharo-project/pharo-project- > proposals/blob/master/Topics-old.st > > As we are going for well-described projects with links to related > resources, pictures, prototype videos, etc. you can also add a standalone > file with a project description in some rich format to this dir: > https://github.com/pharo-project/pharo-project- > proposals/tree/master/topics > > Again, we want around ten diverse and well-described projects with a > precise definition of the domain and the problem, possible solutions, and > expected benefits. So it also will be nice to have diverse projects, so if > you are collaborating with someone, please try to propose a joined project > that will have backup members (also crucial for the application) and do not > create multiple similar but less powerful projects. > > We heavily rely on the input of the community. > Letâs make Pharo great again ;P > Uko on behalf of the Pharo GSoC application team. >

Jan. 25, 2017

CALL for GSoC project proposals

by Yuriy Tymchuk

Dear all, this year we plan to apply again as a mentoring organization for Google Summer of Code. However, we are going to follow a different strategy regarding project proposals. Instead of having a swarm of small ideas we want to end up with around ten well-described projects. This is why I cleaned the topics file, and I ask all interested people to propose the best one of your topics here: https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics… <https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics…> There is a copy of the old file in case you want to remind what you proposed last year: https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics… <https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics…> As we are going for well-described projects with links to related resources, pictures, prototype videos, etc. you can also add a standalone file with a project description in some rich format to this dir: https://github.com/pharo-project/pharo-project-proposals/tree/master/topics <https://github.com/pharo-project/pharo-project-proposals/tree/master/topics> Again, we want around ten diverse and well-described projects with a precise definition of the domain and the problem, possible solutions, and expected benefits. So it also will be nice to have diverse projects, so if you are collaborating with someone, please try to propose a joined project that will have backup members (also crucial for the application) and do not create multiple similar but less powerful projects. We heavily rely on the input of the community. Letâs make Pharo great again ;P Uko on behalf of the Pharo GSoC application team.

Jan. 25, 2017

Re: [Pharo-dev] Google summer of code

by Serge Stinckwich

On Wed, Jan 25, 2017 at 7:38 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 24/01/17 10:11, Guillermo Polito wrote: >> >> Besides, I'm interested in knowing the official reasons for why we were >> rejected last years :P. > > > That's the always the same: we get many more applications than we can > sponsor, and we have to make a choice. +1 yes we receive this answer last year. One option to enhance the situation this year is maybe to have less projects proposed by Pharo community (10-12 ?) but with more detailed explanations. Apparently this is something important to be accepted as an organisation by Google. There is a small team with Jigyasa, Yuriy, Alexandre who is working on that. If you have ideas and want to help, you can join #gsoc-planning on Slack. Thank you. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 25, 2017

Re: [Pharo-dev] [ANN] TechTack today 24/01/2017 16h UTC Bloc/Brick links

by Tudor Girba

Hi Stef, Thanks for these questions. See some replies inline and we will also create threads with the larger topics to get people more engaged. > On Jan 25, 2017, at 9:32 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi bloc/brick guys > > I was a great talk. I had to run because I forgot my appointment to the doctor. > Now some points > > - first a meta point: we should check how we can get more people following the talks. > > Now related to bloc/bricks > > - we should pay really attention to the maintenance and deployment of the external libraries (I could ****never**** install GTK on my mac using darwin. Sure you can experiment but I think that bloc without a widget layer is a nice stuff but not usable. Definitely. The goal here is to get something that works without problems. GTK is an experiment only at this point to see how flexible we really are on the backend side. Moz2D is another problem that I will detail in a separate email. About Brick, see the end of the mail. > - what is the oldest machine it is working? This is an interesting question. One of the cool things about Moz2D is that it is actually another layer on top of concrete rendering backends while still being fast. The concrete rendering is flexible and decided based on the configuration of the machine depending on things like OS or hardware acceleration availability. Given that this engine is at the core of Firefox and they also have to address the problem of various hardware we are in a reasonable position. Nevertheless, it would be very cool to have people test this assumption on old machines. I think Thierry was saying that he has an old machine :). @Thierry? > What is the entrance barrier in terms of cost? Do you have another issue in mind beside the one above? > - So since you are basically two where is the roadmap? What is your visibility in terms of % of your time on the project because at the end of the day you should earn money. Letâs postpone this discussion for a bit longer. > - The question of the patterns used to build the widgets is important. The question of how to validate it for real is also important. Yes, definitely. The effort did not get at that point. Bloc went through an amazing journey and it got refined multiple times by exercising it with rather crazy ideas such as effects, composition, layouts and now we think it reached a point in which the main structure is stable. I am sure we can still find smaller points to refine but the overall structure looks quite robust now. So, the next point is definitely Brick. > - Do you plan commenting/cleaning categorisation for real? I still do not get how you can design something without writing the assumptions of the design into class comments. > Then with such systematic lack of comments you cannot benefit from the "no broken window effect". Now this is more if I see a comments it is either old, bad or useless "I'm an abstract class". At least it was like that the last time I checked. And they are certainly many many concerns that are hidden everywhere and are undocumented. Yes. This is a focus point. Right now, there are assertions in the code for pre-conditions, there are tests and there are examples. The documentation is less advanced, but it is a focus point. For example, the new editor work is commented quite thoroughly and these comments will start to appear through the rest of the infrastructure. But, it would be very cool to have more people to start asking questions as this will help us drive documentation. > - How do you want to get people involved? To me this is totally unclear. Especially with the previous point in mind. I mean for real not just "oh yes we need usersâ I think it is hard to get people involved without providing some benefit. As you noted above, without having working widgets, there is almost no value. That is why it is critical to get to Brick, and once we will get there the feedback will come. It was really hard to get to the state of current Bloc. Glenn and Alex did a really amazing job especially if you look at how many times they iterated over the details and put up with that uncertainty. But, the results are quite incredible and now we can shift our focus to Brick. Now, Brick worked in several incarnations, the last ones being done by Glenn. And the code is there, but the blocker was text support. That is why we had all this investment in Moz2D (the only reason why we have the patching is because of the text support) and in the editor. It was not clear at all that the idea of representing a text as a plain layout of elements will work, but since a week or so we know that it does and now we can commit to it. So, the next focus is to get the editor working and then we will iterate on that. Of course, the patterns of how we compose widgets to models is important, too and this will be on focus. MVC/MVP are options, but I am also interested to see how we can get reactive programming closer to the widgets. Cheers, Doru > Stef > > > > > On Tue, Jan 24, 2017 at 5:00 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > this is going to start now :) > >> On 24 Jan 2017, at 14:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hello, >> >> We will handle the techtalk as latest one: One video streaming and questions/discussion over our discord channel. >> So here are the links: >> >> stream: https://www.youtube.com/watch?v=fvpfr6OJ0mM >> discord: https://discord.gg/88sbn83 >> >> See you there in 3hs! >> Esteban > > -- www.tudorgirba.com www.feenk.com "No matter how many recipes we know, we still value a chef."

Jan. 25, 2017

Re: [Pharo-dev] Google summer of code

by Thierry Goubier

Hi guys, what I noted from the last attempts is that the Pharo proposal goes like that: - here is a nice list of project ideas - newcomers just have to use our current set of tools for interacting and producing code (that is slack / mailing list / smalltalkhub / github / fogbugz / medium / etc...) Maybe preparing something (or planning to) a bit centralized and dedicated to GSoC for the last point could be nice, just to explain that we're paying attention to GSoC participants. Regards, Thierry 2017-01-25 9:21 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Yuriy I cleaned many of the proposal > could you do a pass on yours and keep max 4-5 of them? > > On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> I can also update my projects and help with the application if needed (I >> was a part of the application team for the last two years I think) >> >> Uko >> >> On 22 Jan 2017, at 16:33, Jigyasa Grover <grover.jigyasa1(a)gmail.com> >> wrote: >> >> Also, a good application is equally important as the list of clearly >> defined projects. >> >> - J >> >> On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich < >> serge.stinckwich(a)gmail.com> wrote: >> >>> The list of previous projects is here: >>> https://github.com/pharo-project/pharo-project-proposals >>> >>> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover >>> <grover.jigyasa1(a)gmail.com> wrote: >>> > Dear Prof Serge >>> > >>> > Thanks for the introduction. >>> > >>> > Dear Alexandre >>> > I have been a past Google Summer of Code student and also mentor >>> budding >>> > developers in Google Code-In. >>> > This time, I was hoping to plug-in the loopholes which might have been >>> > present in last year's organisation application. >>> > Kindly let me know how can we collaborate further on this. >>> > Looking forward to your response. >>> > Thanks and Regards >>> > Jigyasa >>> > >>> > >>> > On Sat, Jan 21, 2017 at 9:06 AM, <serge.stinckwich(a)gmail.com> wrote: >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> EnvoyÃ© de mon iPhone >>> >> Le 20 janv. 2017 Ã 22:21, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> a >>> Ã©crit : >>> >> >>> >> What do we do? >>> >> >>> >> >>> >> >>> >> We have to apply ! ;-) >>> >> >>> >> We talk with Jigyasa Grover who is doing an internship in my lab at >>> the >>> >> moment and she is willing to help. Jigyasa was a student in a former >>> Google >>> >> Summer of code and is involved in several open-source initiative like >>> Women >>> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn. >>> >> >>> >> You can find a small presentation during last FOSSASIA : " >>> >> >>> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA >>> >> 2016" >>> >> >>> >> https://m.youtube.com/watch?v=uLIzylxvIz4 >>> >> >>> >> She has done a streaming video this morning also: >>> http://goo.gl/UyclKP >>> >> http://youtube.com/watch?v=2iRG_jpOL54 >>> >> >>> >> Anyone to help her setup a small team for Pharo proposal to Google >>> Summer >>> >> of Code this year ? >>> >> >>> >> >>> >> On 20 Jan 2017, at 20:38, Alexandre Bergel <alexandre.bergel(a)me.com> >>> >> wrote: >>> >> >>> >> Hi everyone- >>> >> >>> >> Google Summer of Code 2017 has officially begun! Organization >>> applications >>> >> open today, Thursday January 19 and are open through Thursday, >>> February 9th. >>> >> Please see our program site, official timeline and FAQ for more >>> details. >>> >> >>> >> What makes a good organization application? Take a look at our >>> manuals for >>> >> tips and best practices. >>> >> >>> >> We look forward to seeing each of your applications and kicking off >>> >> another great year of GSoC. If you have any questions, donât hesitate >>> to >>> >> reach out to gsoc-support(a)google.com. Weâre here to help! >>> >> >>> >> Google Open Source Programs Office >>> >> -- >>> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> >> Alexandre Bergel http://www.bergel.eu >>> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >> >>> >> >>> >> >>> >> >>> > >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UCBN & UMI UMMISCO 209 (IRD/UPMC) >>> Every DSL ends up being Smalltalk >>> http://www.doesnotunderstand.org/ >>> >>> >> >> >

Jan. 25, 2017

Re: [Pharo-dev] [ANN] TechTack today 24/01/2017 16h UTC Bloc/Brick links

by Stephane Ducasse

Hi bloc/brick guys I was a great talk. I had to run because I forgot my appointment to the doctor. Now some points - first a meta point: we should check how we can get more people following the talks. Now related to bloc/bricks - we should pay really attention to the maintenance and deployment of the external libraries (I could ****never**** install GTK on my mac using darwin. Sure you can experiment but I think that bloc without a widget layer is a nice stuff but not usable. - what is the oldest machine it is working? What is the entrance barrier in terms of cost? - So since you are basically two where is the roadmap? What is your visibility in terms of % of your time on the project because at the end of the day you should earn money. - The question of the patterns used to build the widgets is important. The question of how to validate it for real is also important. - Do you plan commenting/cleaning categorisation for real? I still do not get how you can design something without writing the assumptions of the design into class comments. Then with such systematic lack of comments you cannot benefit from the "no broken window effect". Now this is more if I see a comments it is either old, bad or useless "I'm an abstract class". At least it was like that the last time I checked. And they are certainly many many concerns that are hidden everywhere and are undocumented. - How do you want to get people involved? To me this is totally unclear. Especially with the previous point in mind. I mean for real not just "oh yes we need users" Stef On Tue, Jan 24, 2017 at 5:00 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > this is going to start now :) > > On 24 Jan 2017, at 14:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hello, > > We will handle the techtalk as latest one: One video streaming and > questions/discussion over our discord channel. > So here are the links: > > stream: https://www.youtube.com/watch?v=fvpfr6OJ0mM > discord: https://discord.gg/88sbn83 > > See you there in 3hs! > Esteban > > >

Jan. 25, 2017

Re: [Pharo-dev] Google summer of code

by Stephane Ducasse

Yuriy I cleaned many of the proposal could you do a pass on yours and keep max 4-5 of them? On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > I can also update my projects and help with the application if needed (I > was a part of the application team for the last two years I think) > > Uko > > On 22 Jan 2017, at 16:33, Jigyasa Grover <grover.jigyasa1(a)gmail.com> > wrote: > > Also, a good application is equally important as the list of clearly > defined projects. > > - J > > On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > >> The list of previous projects is here: >> https://github.com/pharo-project/pharo-project-proposals >> >> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover >> <grover.jigyasa1(a)gmail.com> wrote: >> > Dear Prof Serge >> > >> > Thanks for the introduction. >> > >> > Dear Alexandre >> > I have been a past Google Summer of Code student and also mentor budding >> > developers in Google Code-In. >> > This time, I was hoping to plug-in the loopholes which might have been >> > present in last year's organisation application. >> > Kindly let me know how can we collaborate further on this. >> > Looking forward to your response. >> > Thanks and Regards >> > Jigyasa >> > >> > >> > On Sat, Jan 21, 2017 at 9:06 AM, <serge.stinckwich(a)gmail.com> wrote: >> >> >> >> >> >> >> >> >> >> >> >> EnvoyÃ© de mon iPhone >> >> Le 20 janv. 2017 Ã 22:21, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> a >> Ã©crit : >> >> >> >> What do we do? >> >> >> >> >> >> >> >> We have to apply ! ;-) >> >> >> >> We talk with Jigyasa Grover who is doing an internship in my lab at the >> >> moment and she is willing to help. Jigyasa was a student in a former >> Google >> >> Summer of code and is involved in several open-source initiative like >> Women >> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn. >> >> >> >> You can find a small presentation during last FOSSASIA : " >> >> >> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA >> >> 2016" >> >> >> >> https://m.youtube.com/watch?v=uLIzylxvIz4 >> >> >> >> She has done a streaming video this morning also: http://goo.gl/UyclKP >> >> http://youtube.com/watch?v=2iRG_jpOL54 >> >> >> >> Anyone to help her setup a small team for Pharo proposal to Google >> Summer >> >> of Code this year ? >> >> >> >> >> >> On 20 Jan 2017, at 20:38, Alexandre Bergel <alexandre.bergel(a)me.com> >> >> wrote: >> >> >> >> Hi everyone- >> >> >> >> Google Summer of Code 2017 has officially begun! Organization >> applications >> >> open today, Thursday January 19 and are open through Thursday, >> February 9th. >> >> Please see our program site, official timeline and FAQ for more >> details. >> >> >> >> What makes a good organization application? Take a look at our manuals >> for >> >> tips and best practices. >> >> >> >> We look forward to seeing each of your applications and kicking off >> >> another great year of GSoC. If you have any questions, donât hesitate >> to >> >> reach out to gsoc-support(a)google.com. Weâre here to help! >> >> >> >> Google Open Source Programs Office >> >> -- >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >> Alexandre Bergel http://www.bergel.eu >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> >> > >> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >> > >

Jan. 25, 2017

Re: [Pharo-dev] Google summer of code

by Stephane Ducasse

Yes please. I can do a pass also. I started on some private projects. I would like to propose to build a make based on a graph library. they have a nice lib in Python and this way we would avoid to rely on make for pillar and others On Tue, Jan 24, 2017 at 10:11 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Hi, > > I would like to help in cleaning, composing and enhancing the ideas page. > I already see some old projects whose mentors either left the community or > may not be 100% available for mentoring (like Camille Teruel). > We should clean that page. > > Besides, I'm interested in knowing the official reasons for why we were > rejected last years :P. > > Guille > > On Mon, Jan 23, 2017 at 7:02 PM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > >> Thank you Uko to join the team :-) >> >> On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> > I can also update my projects and help with the application if needed >> (I was >> > a part of the application team for the last two years I think) >> > >> > Uko >> > >> > On 22 Jan 2017, at 16:33, Jigyasa Grover <grover.jigyasa1(a)gmail.com> >> wrote: >> > >> > Also, a good application is equally important as the list of clearly >> defined >> > projects. >> > >> > - J >> > >> > On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich >> > <serge.stinckwich(a)gmail.com> wrote: >> >> >> >> The list of previous projects is here: >> >> https://github.com/pharo-project/pharo-project-proposals >> >> >> >> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover >> >> <grover.jigyasa1(a)gmail.com> wrote: >> >> > Dear Prof Serge >> >> > >> >> > Thanks for the introduction. >> >> > >> >> > Dear Alexandre >> >> > I have been a past Google Summer of Code student and also mentor >> budding >> >> > developers in Google Code-In. >> >> > This time, I was hoping to plug-in the loopholes which might have >> been >> >> > present in last year's organisation application. >> >> > Kindly let me know how can we collaborate further on this. >> >> > Looking forward to your response. >> >> > Thanks and Regards >> >> > Jigyasa >> >> > >> >> > >> >> > On Sat, Jan 21, 2017 at 9:06 AM, <serge.stinckwich(a)gmail.com> wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> EnvoyÃ© de mon iPhone >> >> >> Le 20 janv. 2017 Ã 22:21, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> a >> Ã©crit >> >> >> : >> >> >> >> >> >> What do we do? >> >> >> >> >> >> >> >> >> >> >> >> We have to apply ! ;-) >> >> >> >> >> >> We talk with Jigyasa Grover who is doing an internship in my lab at >> the >> >> >> moment and she is willing to help. Jigyasa was a student in a former >> >> >> Google >> >> >> Summer of code and is involved in several open-source initiative >> like >> >> >> Women >> >> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn. >> >> >> >> >> >> You can find a small presentation during last FOSSASIA : " >> >> >> >> >> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - >> FOSSASIA >> >> >> 2016" >> >> >> >> >> >> https://m.youtube.com/watch?v=uLIzylxvIz4 >> >> >> >> >> >> She has done a streaming video this morning also: >> http://goo.gl/UyclKP >> >> >> http://youtube.com/watch?v=2iRG_jpOL54 >> >> >> >> >> >> Anyone to help her setup a small team for Pharo proposal to Google >> >> >> Summer >> >> >> of Code this year ? >> >> >> >> >> >> >> >> >> On 20 Jan 2017, at 20:38, Alexandre Bergel <alexandre.bergel(a)me.com >> > >> >> >> wrote: >> >> >> >> >> >> Hi everyone- >> >> >> >> >> >> Google Summer of Code 2017 has officially begun! Organization >> >> >> applications >> >> >> open today, Thursday January 19 and are open through Thursday, >> February >> >> >> 9th. >> >> >> Please see our program site, official timeline and FAQ for more >> >> >> details. >> >> >> >> >> >> What makes a good organization application? Take a look at our >> manuals >> >> >> for >> >> >> tips and best practices. >> >> >> >> >> >> We look forward to seeing each of your applications and kicking off >> >> >> another great year of GSoC. If you have any questions, donât >> hesitate >> >> >> to >> >> >> reach out to gsoc-support(a)google.com. Weâre here to help! >> >> >> >> >> >> Google Open Source Programs Office >> >> >> -- >> >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >> >> Alexandre Bergel http://www.bergel.eu >> >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> -- >> >> Serge Stinckwich >> >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> >> Every DSL ends up being Smalltalk >> >> http://www.doesnotunderstand.org/ >> >> >> > >> > >> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >> >

Jan. 25, 2017

Re: [Pharo-dev] Google summer of code

by Stephan Eggermont

On 24/01/17 10:11, Guillermo Polito wrote: > Besides, I'm interested in knowing the official reasons for why we were > rejected last years :P. That's the always the same: we get many more applications than we can sponsor, and we have to make a choice. Stephan

Jan. 25, 2017

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

by Ben Coman

On Wed, Jan 25, 2017 at 4:27 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Thank's to all :). > > 2017-01-24 14:29 GMT+01:00 Ben Coman <btc(a)openinworld.com>: >> >> >> Amazing stuff Denis. It will be very interesting over time to hear of how >> people's workflows adapt to use this. > > > I am going to work such way. I will develop completely from remote IDE. > Mostly it will be experiment to discover possible problems. But at the end > it will lead to real live remote programming. > So we will be able to develop RPi, Beaglebone, Android/IOS devices in > natural Pharo way. You could imaging difference to XCode or Eclipse. > >> >> >> One thought while I was watching the video, it might be useful if the >> remote images were named somehow, which could appear in the title bar of the >> remote tools in addition to IPaddress/DNSname:port. I can imagine having >> several images of different purposes running on one remote host and having >> multiple open from the one client and needing to keep track better. So for >> example @4:37, instead of the inspector showing "SeamlessProxy(42)" it would >> show "MyRemoteImage(42)" > > > Problem that now I not completely hook into inspector and debugger. So it is > shown with such strange names but it points to non local nature without any > effort. > In future it will be handled better of course Don't throw away the host/IP and port from the title bar. They will remain useful. Its just to have an additional ID. cheers -ben

Jan. 24, 2017