- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About better communication in the community

by stepharo

Hi yuriy A package manifest is the place where we keep package rules and meta data. We should add documentation and others. I think that all the packages should have a XXXManifest. There we can define a method preUnload and after we can define a class PackageUnloader (or put the logic in the PackageOrganiser way better :)). So that we can say PackageOrganiser current unload: 'XXX' and the preUnload is executed. Stef Le 27/8/16 Ã 16:23, Yuriy Tymchuk a Ã©crit : >> On 27 Aug 2016, at 11:00, stepharo <stepharo(a)free.fr> wrote: >> >> You see hernan doing positively is the best way to make that things happen >> >> We can have a >> >> preUnload hook >> >> Now we should check how it fits with cleanForProduction and others. >> >> But we should definitively have a way to express this. >> >> So let us see how we can design it and then just implement it. I'm sure that GT people are open to such hooks >> >> and if you really want to get a better Pharo for you then talk to them and us. >> >> >> https://pharo.fogbugz.com/f/cases/18997/Add-unload-to-package-manifest-in-QA > I like the idea, but how should it work? What is the package manifest? And how the unload protocol looks like? Do I only add a method called #unload to somewhere? > > Uko > >> https://pharo.fogbugz.com/f/cases/18998/Add-unload-to-package-manifest-of-S… >> >> https://pharo.fogbugz.com/f/cases/18999/Add-unload-to-package-manifest-in-G… >> >> https://pharo.fogbugz.com/f/cases/19000/Add-unload-to-package-manifest-in-GT >> >> Stef >> > >

Aug. 27, 2016

Re: [Pharo-dev] About better communication in the community

by Yuriy Tymchuk

> On 27 Aug 2016, at 11:00, stepharo <stepharo(a)free.fr> wrote: > > You see hernan doing positively is the best way to make that things happen > > We can have a > > preUnload hook > > Now we should check how it fits with cleanForProduction and others. > > But we should definitively have a way to express this. > > So let us see how we can design it and then just implement it. I'm sure that GT people are open to such hooks > > and if you really want to get a better Pharo for you then talk to them and us. > > > https://pharo.fogbugz.com/f/cases/18997/Add-unload-to-package-manifest-in-QA I like the idea, but how should it work? What is the package manifest? And how the unload protocol looks like? Do I only add a method called #unload to somewhere? Uko > > https://pharo.fogbugz.com/f/cases/18998/Add-unload-to-package-manifest-of-S… > > https://pharo.fogbugz.com/f/cases/18999/Add-unload-to-package-manifest-in-G… > > https://pharo.fogbugz.com/f/cases/19000/Add-unload-to-package-manifest-in-GT > > Stef >

Aug. 27, 2016

Confused by remote logic ;)

by stepharo

KomitNewSlice>>remote ^ MCRepositoryGroup default repositories detect: [ :e | e description = 'http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main/' ] ifNone: [ MCRepositoryGroup default repositories detect: [ :e | e description = 'http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main' ] ] may be the first time one is magically created :) Stef

Aug. 27, 2016

Polymorphic results would be good

by stepharo

Hi I'm cleaning Smalltalk ui icons usage again and more :) I just want to share with you. I see code like that KomitDirectoryRemote>>icon ^ 'DIR' KomitGemstoneRemote>> icon ^ Smalltalk ui icons iconNamed: #komitterGemstoneRemote It would be nice if we could be cleaner and makes sure that we do not return totally different objects. Stef PS: Some of you can understand why I was not found of Komitter and suggested to remove it. So let us improve it.

Aug. 27, 2016

Re: [Pharo-dev] About Pharo 60

by Esteban Lorenzano

> On 27 Aug 2016, at 14:40, stepharo <stepharo(a)free.fr> wrote: > > Hi esteban > > I think that we should identify the main hook points and slowly prepare them. > > The system should be prepared for that so that we just need to pass a context to configure it. .. I should have that old package somewhereâ¦ it will not work, and it was not very subtleâ¦ but it has to be somewhere :) Esteban > > Stef > > > Le 27/8/16 Ã 14:32, Esteban Lorenzano a Ã©crit : >> yes, some years ago I made a package for this. >> later Ben tried something similar with the user manager. >> none of those approaches worked as general approach because you need to âcloseâ a lot of thingsâ¦ (not just the spotterâ¦ which by the way, NEEDS to have a setting, no idea who answered you that but he is wrong), and image is not prepared for that. >> >> of course is still possible :) >> >> anyway, today I would tackle a solution in a different way: I would open my app morph on an SDL2 window and not touch the word at all (opening a headless image). This is not possible in windows because when you do âheadlessâ it just laugh at you, but is doable in the not-so-long term. >> >> Esteban >> >>> On 27 Aug 2016, at 13:39, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >>> >>> Le 27/08/2016 Ã 13:18, stepharo a Ã©crit : >>>> >>>> YES!!! >>>> >>>> Do you know how Settings works? >>>> We can adapt it this way. >>> When I improved the deployment of Synectique Tools I asked to get a >>> simple way to disable Spotter via a setting but I got as answer "No >>> because you can do it by removing a global shortcut so it is not needed.". >>> >>> People in companies don't have the time to learn how shortcuts work and >>> how to remove one without impacting something else. And they don't have >>> the time to check Spotter code to know how it is call. >>> >>> If the image is able to have a deployment mode then I don't care how >>> Spotter is disabled (setting or removing a shortcut). But for now we >>> don't have it. :) >>> >>>> I mean the User approach that Benjmain proposed and was pushed in Pharo >>>> was not good because it was not modular. Now each part of the system >>>> should be >>>> defined in way that it can be set just as a setting. >>>> We should not have >>>> >>>> World .... >>>> User current = ifTrue >>>> >>>> But >>>> >>>> World use: userSetting >>>> >>>> and World should handle it. >>>> There is way more to do :) >>>> When you deploy on linux you should be able to say beSilent to the >>>> system (do not write on places that you cannot). >>>> Valentin works on it and we should continue >>>> >>>> Stef >>>> >>> The fact that there is much more to do is the main reason for Pharo to >>> do it and not the developer. The developer cannot know all the system >>> and will not be able to protect the code of his company well because he >>> will forget something as to disable ctrl+o+p (or he is a god developer! >>> But everyone is not). >>> >>> This is a large thing to do, so it would be cool that everyone keep that >>> in mind to allow it little by little (as with the work of Valentin). >>> >>> -- >>> Cyril Ferlicot >>> >>> http://www.synectique.eu >>> >>> 165 Avenue Bretagne >>> Lille 59000 France >>> >> >> > >

Aug. 27, 2016

Re: [Pharo-dev] About better communication in the community

by stepharo

So I think that I will keep Eyeinspector for Spec because it works well using Spec. I will package BasicInspector Then we will see. I think that Smalltalk tools inspector is not good because it is yet another global while the tools should have a tool context (but with a registration mechanism to get refreshed in case). Stef Le 27/8/16 Ã 10:51, stepharo a Ã©crit : > I took the inspector from Pharo20 and I will check if it is working in > Pharo. > Then I will > - check EyeInspector from a package perspective (extensions and > the rest) > - make sure that we can remove EyeInspector > - package the attached file as BasicInspector. > > Now if you want to help you are welcome. > > Stef

Aug. 27, 2016

Re: [Pharo-dev] About Pharo 60

by stepharo

Hi esteban I think that we should identify the main hook points and slowly prepare them. The system should be prepared for that so that we just need to pass a context to configure it. Stef Le 27/8/16 Ã 14:32, Esteban Lorenzano a Ã©crit : > yes, some years ago I made a package for this. > later Ben tried something similar with the user manager. > none of those approaches worked as general approach because you need to âcloseâ a lot of thingsâ¦ (not just the spotterâ¦ which by the way, NEEDS to have a setting, no idea who answered you that but he is wrong), and image is not prepared for that. > > of course is still possible :) > > anyway, today I would tackle a solution in a different way: I would open my app morph on an SDL2 window and not touch the word at all (opening a headless image). This is not possible in windows because when you do âheadlessâ it just laugh at you, but is doable in the not-so-long term. > > Esteban > >> On 27 Aug 2016, at 13:39, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >> >> Le 27/08/2016 Ã 13:18, stepharo a Ã©crit : >>> >>> YES!!! >>> >>> Do you know how Settings works? >>> We can adapt it this way. >> When I improved the deployment of Synectique Tools I asked to get a >> simple way to disable Spotter via a setting but I got as answer "No >> because you can do it by removing a global shortcut so it is not needed.". >> >> People in companies don't have the time to learn how shortcuts work and >> how to remove one without impacting something else. And they don't have >> the time to check Spotter code to know how it is call. >> >> If the image is able to have a deployment mode then I don't care how >> Spotter is disabled (setting or removing a shortcut). But for now we >> don't have it. :) >> >>> I mean the User approach that Benjmain proposed and was pushed in Pharo >>> was not good because it was not modular. Now each part of the system >>> should be >>> defined in way that it can be set just as a setting. >>> We should not have >>> >>> World .... >>> User current = ifTrue >>> >>> But >>> >>> World use: userSetting >>> >>> and World should handle it. >>> There is way more to do :) >>> When you deploy on linux you should be able to say beSilent to the >>> system (do not write on places that you cannot). >>> Valentin works on it and we should continue >>> >>> Stef >>> >> The fact that there is much more to do is the main reason for Pharo to >> do it and not the developer. The developer cannot know all the system >> and will not be able to protect the code of his company well because he >> will forget something as to disable ctrl+o+p (or he is a god developer! >> But everyone is not). >> >> This is a large thing to do, so it would be cool that everyone keep that >> in mind to allow it little by little (as with the work of Valentin). >> >> -- >> Cyril Ferlicot >> >> http://www.synectique.eu >> >> 165 Avenue Bretagne >> Lille 59000 France >> > >

Aug. 27, 2016

Re: [Pharo-dev] About Pharo 60

by stepharo

Cyril what would be good is to share what you are disabling and to tunr such points into points that can be turned but inside Pharo like that you push the logic to the system. Now this is important to see that if people for which the value is high do not work on something why others would do it. >> YES!!! >> >> Do you know how Settings works? >> We can adapt it this way. > When I improved the deployment of Synectique Tools I asked to get a > simple way to disable Spotter via a setting but I got as answer "No > because you can do it by removing a global shortcut so it is not needed.". I do not know how to do it either. So we should document that. > People in companies don't have the time to learn how shortcuts work and > how to remove one without impacting something else. And they don't have > the time to check Spotter code to know how it is call. > > If the image is able to have a deployment mode then I don't care how > Spotter is disabled (setting or removing a shortcut). But for now we > don't have it. :) No you should care because one day you will come with a new requirement :) I understand what you mean but the point is that Pharo is our common architecture so we should just all pay attention and we cannot ask people to do everything because we all have 24 h a day. So we should be smart, share and build together. > >> I mean the User approach that Benjmain proposed and was pushed in Pharo >> was not good because it was not modular. Now each part of the system >> should be >> defined in way that it can be set just as a setting. >> We should not have >> >> World .... >> User current = ifTrue >> >> But >> >> World use: userSetting >> >> and World should handle it. >> There is way more to do :) >> When you deploy on linux you should be able to say beSilent to the >> system (do not write on places that you cannot). >> Valentin works on it and we should continue >> >> Stef >> > The fact that there is much more to do is the main reason for Pharo to > do it and not the developer. The developer cannot know all the system > and will not be able to protect the code of his company well because he > will forget something as to disable ctrl+o+p (or he is a god developer! > But everyone is not). > > This is a large thing to do, so it would be cool that everyone keep that > in mind to allow it little by little (as with the work of Valentin). >

Aug. 27, 2016

Re: [Pharo-dev] About Pharo 60

by Esteban Lorenzano

yes, some years ago I made a package for this. later Ben tried something similar with the user manager. none of those approaches worked as general approach because you need to âcloseâ a lot of thingsâ¦ (not just the spotterâ¦ which by the way, NEEDS to have a setting, no idea who answered you that but he is wrong), and image is not prepared for that. of course is still possible :) anyway, today I would tackle a solution in a different way: I would open my app morph on an SDL2 window and not touch the word at all (opening a headless image). This is not possible in windows because when you do âheadlessâ it just laugh at you, but is doable in the not-so-long term. Esteban > On 27 Aug 2016, at 13:39, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 27/08/2016 Ã 13:18, stepharo a Ã©crit : >> >> >> YES!!! >> >> Do you know how Settings works? >> We can adapt it this way. > > When I improved the deployment of Synectique Tools I asked to get a > simple way to disable Spotter via a setting but I got as answer "No > because you can do it by removing a global shortcut so it is not needed.". > > People in companies don't have the time to learn how shortcuts work and > how to remove one without impacting something else. And they don't have > the time to check Spotter code to know how it is call. > > If the image is able to have a deployment mode then I don't care how > Spotter is disabled (setting or removing a shortcut). But for now we > don't have it. :) > >> I mean the User approach that Benjmain proposed and was pushed in Pharo >> was not good because it was not modular. Now each part of the system >> should be >> defined in way that it can be set just as a setting. >> We should not have >> >> World .... >> User current = ifTrue >> >> But >> >> World use: userSetting >> >> and World should handle it. >> There is way more to do :) >> When you deploy on linux you should be able to say beSilent to the >> system (do not write on places that you cannot). >> Valentin works on it and we should continue >> >> Stef >> > > The fact that there is much more to do is the main reason for Pharo to > do it and not the developer. The developer cannot know all the system > and will not be able to protect the code of his company well because he > will forget something as to disable ctrl+o+p (or he is a god developer! > But everyone is not). > > This is a large thing to do, so it would be cool that everyone keep that > in mind to allow it little by little (as with the work of Valentin). > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France >

Aug. 27, 2016

Re: [Pharo-dev] SmalltalkHub over https

by Max Leske

Weâve set up Letâs Encrypt on our servers and while itâs cool it also requires some work around it. Most importantly you have to set up auto renewal (every 30 days). And if you donât get it right it will suck. Also: use VPN :) > On 27 Aug 2016, at 13:07, stepharo <stepharo(a)free.fr> wrote: > > Time and ressources. > We cannot do more else it will damage what we are doing. > Now if somebody wants to help he is more than welcome. > > Stef >> since Let's Encrypt offers free certs, is there any reason why smalltalkhub is not yet served over https? Maybe limitation of Zinc? >> >> I guess that's one benefit that we are such a small community that nobody nuked us yet... (e.g. every time you commit from free wifi (hotel, airport, caffee, ...) you give up your password). >> >> Peter >> >> > >

Aug. 27, 2016