Re: [Pharo-dev] [Pharo-users] [ANN} Pharo Consultants
On 17 Jul 2013, at 07:47, Damien Cassou damien.cas...@gmail.com wrote: On Tue, Jul 16, 2013 at 7:39 PM, Sven Van Caekenberghe s...@stfx.eu wrote: Cool, right ? indeed, very cool. Should I add a link in the Community section of the pharo.org website? Yes please, I think just a link in the left menu would be enough Damien, was it also you who initially did the contributors page ? Any ideas of how we could extract the data quickly in a structured format ? -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-dev] Penelope - Fail to create account
Just write your mail without dots, its the same for gmail (I've been there already) Sent from Gmail for Android On 17 Jul 2013 01:14, Carla F. Griggio carla.grig...@gmail.com wrote: Me :( I could see the issues by entering each category listed in the home page, but still it was uncomfortable to feel that I should know before hand in which category the issue I was looking for could be listed. I wanted to register to post issues with my name and I couldn't (and in the login form there should be a link explaining how to register, not only for asking a lost password). Cheers, Carla On Wed, Jul 17, 2013 at 1:06 AM, Mariano Vicente m.vic...@gmail.comwrote: Hi. I tried create my user in penelope [1], so I can see the issues in fogbugz. and this fails when i added the email, I think the problems are the dots in my email adress. Anybody have had the same problem? [1] http://bugs.pharo.org/issues?_k=DBsCrRwP1TgaBEDb Regards, Mariano
Re: [Pharo-dev] [Pharo-users] [ANN} Pharo Consultants
On Wed, Jul 17, 2013 at 8:14 AM, Sven Van Caekenberghe s...@stfx.eu wrote: Yes please, I think just a link in the left menu would be enough That's not possible. But I added a page, referenced from the menu on the left that show this page: http://www.pharo-project.org/community/consultants Damien, was it also you who initially did the contributors page ? Any ideas of how we could extract the data quickly in a structured format ? You may want to ask Laurent Laffont -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-dev] [Pharo-users] [ANN} Pharo Consultants
On 17 Jul 2013, at 10:10, Damien Cassou damien.cas...@gmail.com wrote: On Wed, Jul 17, 2013 at 8:14 AM, Sven Van Caekenberghe s...@stfx.eu wrote: Yes please, I think just a link in the left menu would be enough That's not possible. But I added a page, referenced from the menu on the left that show this page: http://www.pharo-project.org/community/consultants That is OK, thanks. Maybe I can add a little section on that page describing what you have to do to get on the list. Damien, was it also you who initially did the contributors page ? Any ideas of how we could extract the data quickly in a structured format ? You may want to ask Laurent Laffont Yes, of course. I will ask him. -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-dev] [Pharo-users] [ANN} Pharo Consultants
On Wed, Jul 17, 2013 at 10:22 AM, Sven Van Caekenberghe s...@stfx.eu wrote: Maybe I can add a little section on that page describing what you have to do to get on the list. either that or we keep this page as short as possible and put everything on consultants.pharo.org. As you wish -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-dev] Open GL and Athens?
Ok, Thanks Igor Alexandre On 16 Jul 2013, at 06:43, Igor Stasenko siguc...@gmail.com wrote: On 15 July 2013 20:05, Alexandre Bergel alexandre.ber...@me.com wrote: Hi! Milton, Ronie and I had a very fun programming session. Here some random screenshots during our programming session. Igor, would it be possible to have in the same window Athens and OpenGL? Maybe the question does not make sense, just I prefer the ask. On some point we would like to some popup in 2D above a 3D scene. your question makes perfect sense. sure, you can combine drawings from both of them and blit things together. The only little problem is that Cairo pixel buffer (surface) is premultiplied with alpha (R*A, G*A, B*A, A) while Form is not (RGBA). And we don't have such blending rule in bitblt to combine pixels of such formats correctly. All the examples are available on: http://smalltalkhub.com/#!/~ronsaldo/roassal3d You need to download first NBOpenGL to play with Roassal3d Cheers, Ronie, Milton Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. Screen Shot 2013-07-15 at 2.03.30 PM.png Screen Shot 2013-07-15 at 1.36.46 PM.png -- Best regards, Igor Stasenko.
[Pharo-dev] Spec delete method
Hi ben I would like to unsubscribe announcement when the window is closed. Is there a hook for that in Spec? Stef
Re: [Pharo-dev] [Pharo-users] [DOC] Building and deploying your first web app with Pharo
On Jul 15, 2013, at 6:41 PM, Sven Van Caekenberghe s...@stfx.eu wrote: Igor, On 15 Jul 2013, at 17:48, Igor Stasenko siguc...@gmail.com wrote: since you gave listing at the end of page, i wonder, how much PHP (yes! :) code it would take to implement same app? :) of course , PHP is not really fair comparison, since it doesn't implements full HTTP stack, nor it deals with HTTP requests directly as Zinc does, and runs on top of web server which does that for it. I don't know enough about PHP to really comment, but do you mean it would be (much) shorter ? I wonder and would certainly like to see. Just don't forget to include the full upload validation and parsing logic, as well as the default image. All lines of all files count: code, html, css, js, … Anyway, the tutorial was not meant as a 'see how few lines we need'. I once did that in Reddit.st - In 10 elegant Smalltalk classes - Implementing a Reddit style web application in Smalltalk - Using Seaside, Glorp and PostgreSQL, but it is no longer available online, I should revive it. Yes and we turn it into a chapter :) Sven On 15 July 2013 13:12, Sven Van Caekenberghe s...@stfx.eu wrote: Hi, I wrote a new tutorial, Building and deploying your first web app with Pharo - Understanding HTTP fundamentals through Zinc HTTP Components. By chronologically following the development process, you will see a small web app growing from something trivial to the final result. Finally, we will save our source code in a repository and deploy for real in the cloud. http://zn.stfx.eu/zn/build-and-deploy-1st-webapp Pharo 2.0/3.0 features such as Nautilus, SmalltalkHub, Metacello Configurations, Zeroconf Scripts and of course Zinc HTTP Components are used while highlighting traditional strengths such as incremental, live interactive development in a rich environment. Enjoy, Sven PS: Feedback is welcome, the source document lives here https://github.com/svenvc/zinc/blob/master/build-and-deploy-1st-webapp/build-deploy-1st-webapp.md - pull requests appreciated. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org -- Best regards, Igor Stasenko.
[Pharo-dev] Config browser with filter
screen attached Pharo 2.0: Slice and issue 11179 together with a fix for broken buttons Pharo 3.0: Slice and issue 11180 attachment: configbrowserfilter.png
[Pharo-dev] CameraPlugin for (Pharo) VM
We once had a discussion already, to summarize: - the camera plugin from scratch worked according to Bernat Romagosa [1] - Stef checked the scratch license and said this license is not MIT so he do not want to see it in Pharo [2] [3] We didnt move on with this since we thought it is covered by Scratch license or since nobody really cared. But it looks like the Camera stuff is indeed released with MIT license (even before the discussion) I just found by accident this old issue: http://bugs.squeak.org/view.php?id=7654 quotes two plugins that should be made available for standard VMs Per communication from Bert Freudenberg, source for CameraPlugin is now available under MIT license: Here is the CameraPlugin code under MIT license. /quote Acccording to this issue the camera code was opened with MIT. The issue also includes the code. Can we check again - default support for camera would be a nice addition to our Pharo universe. Thx T. [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051826.html [2] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051838.html [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051843.html
Re: [Pharo-dev] Spec delete method
I guess what Stef means is that he would like to know if there is a way specify custom behavior when a window closes, and then use this for his purpose of unregistering from some announcer. Cheers, Doru On Wed, Jul 17, 2013 at 2:36 PM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: I do not think it's a UI framework concern to handle model behaviour (like registration to announcement) Ben On Jul 17, 2013, at 9:40 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi ben I would like to unsubscribe announcement when the window is closed. Is there a hook for that in Spec? Stef -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Spec delete method
Ok :) Then there is a hook in Morph for that I think :) (and an announcement in Spec when a widget is built) Ben On Jul 17, 2013, at 3:37 PM, Tudor Girba tu...@tudorgirba.com wrote: I guess what Stef means is that he would like to know if there is a way specify custom behavior when a window closes, and then use this for his purpose of unregistering from some announcer. Cheers, Doru On Wed, Jul 17, 2013 at 2:36 PM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: I do not think it's a UI framework concern to handle model behaviour (like registration to announcement) Ben On Jul 17, 2013, at 9:40 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi ben I would like to unsubscribe announcement when the window is closed. Is there a hook for that in Spec? Stef -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] CameraPlugin for (Pharo) VM
On 17 July 2013 15:30, Torsten Bergmann asta...@gmx.de wrote: We once had a discussion already, to summarize: - the camera plugin from scratch worked according to Bernat Romagosa [1] - Stef checked the scratch license and said this license is not MIT so he do not want to see it in Pharo [2] [3] We didnt move on with this since we thought it is covered by Scratch license or since nobody really cared. But it looks like the Camera stuff is indeed released with MIT license (even before the discussion) I just found by accident this old issue: http://bugs.squeak.org/view.php?id=7654 quotes two plugins that should be made available for standard VMs Per communication from Bert Freudenberg, source for CameraPlugin is now available under MIT license: Here is the CameraPlugin code under MIT license. /quote Acccording to this issue the camera code was opened with MIT. The issue also includes the code. Can we check again - default support for camera would be a nice addition to our Pharo universe. If we include that plugin into VM, then there should be someone , who will take responsibility for maintaining and improving it. And that means: - making sure it works on all 3 major platforms (at least) and not breaks with new version(s) releases - updates the code, improves it etc - keep image-side code in good shape covered by tests and updated regularly , as Pharo make progress - have a good documentation any volunteers? I could, but i can't , because i already have multiple projects to care about. And i am close to limits of personal physical capabilities to keep things up. I didn't wanted to discourage anyone, but just wanted to remind that 'including into pharo' means a lot more than 'copying files there', otherwise it is not 'including', but planting timebomb which will explode eventually. Thx T. [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051826.html [2] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051838.html [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051843.html -- Best regards, Igor Stasenko.
Re: [Pharo-dev] Spec delete method
You can add this to the initialize method of your widget, and in the close method unregister all announcers self whenWindowChanged: [:w | w whenClosedDo: [ self close ] ]. Andrei On Wed, Jul 17, 2013 at 3:42 PM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: Ok :) Then there is a hook in Morph for that I think :) (and an announcement in Spec when a widget is built) Ben On Jul 17, 2013, at 3:37 PM, Tudor Girba tu...@tudorgirba.com wrote: I guess what Stef means is that he would like to know if there is a way specify custom behavior when a window closes, and then use this for his purpose of unregistering from some announcer. Cheers, Doru On Wed, Jul 17, 2013 at 2:36 PM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: I do not think it's a UI framework concern to handle model behaviour (like registration to announcement) Ben On Jul 17, 2013, at 9:40 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi ben I would like to unsubscribe announcement when the window is closed. Is there a hook for that in Spec? Stef -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] CameraPlugin for (Pharo) VM
On Jul 17, 2013, at 3:51 PM, Igor Stasenko siguc...@gmail.com wrote: On 17 July 2013 15:30, Torsten Bergmann asta...@gmx.de wrote: We once had a discussion already, to summarize: - the camera plugin from scratch worked according to Bernat Romagosa [1] - Stef checked the scratch license and said this license is not MIT so he do not want to see it in Pharo [2] [3] We didnt move on with this since we thought it is covered by Scratch license or since nobody really cared. But it looks like the Camera stuff is indeed released with MIT license (even before the discussion) I just found by accident this old issue: http://bugs.squeak.org/view.php?id=7654 quotes two plugins that should be made available for standard VMs Per communication from Bert Freudenberg, source for CameraPlugin is now available under MIT license: Here is the CameraPlugin code under MIT license. /quote Acccording to this issue the camera code was opened with MIT. The issue also includes the code. Can we check again - default support for camera would be a nice addition to our Pharo universe. If we include that plugin into VM, then there should be someone , who will take responsibility for maintaining and improving it. And that means: - making sure it works on all 3 major platforms (at least) and not breaks with new version(s) releases - updates the code, improves it etc - keep image-side code in good shape covered by tests and updated regularly , as Pharo make progress - have a good documentation any volunteers? I could, but i can't , because i already have multiple projects to care about. And i am close to limits of personal physical capabilities to keep things up. I didn't wanted to discourage anyone, but just wanted to remind that 'including into pharo' means a lot more than 'copying files there', otherwise it is not 'including', but planting timebomb which will explode eventually. amen Thx T. [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051826.html [2] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051838.html [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051843.html -- Best regards, Igor Stasenko.
[Pharo-dev] buttons for browsing in the debugger
Hi, If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons. Do you use this feature? Do we want it in the new debugger? Andrei
Re: [Pharo-dev] buttons for browsing in the debugger
-1 but i don't like it in form of extra buttons row, which makes debugger UI too bloated. They will be accessible from the context menu of the stack. Andrei -- Best regards, Igor Stasenko.
Re: [Pharo-dev] buttons for browsing in the debugger
In general what I learned: You find an obscure, not useful, not used feature in the code base that complexities everything. option 1) Ask the list. Result: 5 people will suddenly realize that they can not live without that strange feature they never heard about before. option 2) Just kill it. Result: the World is a happier place. ;-) But seriously I used that Strategy 2) a lot in the past :-) Sounds like a good plan :)
Re: [Pharo-dev] buttons for browsing in the debugger
On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis chisvasileand...@gmail.com wrote: Hi, If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons. Do you use this feature? I don't think so. Do we want it in the new debugger? I would not bother… things like that are to be removed to gain clarity. Marcus
Re: [Pharo-dev] buttons for browsing in the debugger
On Jul 17, 2013, at 4:11 PM, Marcus Denker marcus.den...@inria.fr wrote: On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis chisvasileand...@gmail.com wrote: Hi, If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons. Do you use this feature? I don't think so. In general what I learned: You find an obscure, not useful, not used feature in the code base that complexities everything. option 1) Ask the list. Result: 5 people will suddenly realize that they can not live without that strange feature they never heard about before. option 2) Just kill it. Result: the World is a happier place. ;-) But seriously I used that Strategy 2) a lot in the past :-) Marcus
[Pharo-dev] [update 3.0] #30276
30276 - 7300 Finder raise an error on asking for implementors https://pharo.fogbugz.com/f/cases/7300 10348 GroupAlreadyExists vs. GroupsAlreadyExists confusion https://pharo.fogbugz.com/f/cases/10348 11180 Add a filter to the config browser https://pharo.fogbugz.com/f/cases/11180 11172 notEmpty should be isNotEmpty https://pharo.fogbugz.com/f/cases/11172 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1177.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-MarcusDenker.492.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/GroupManager-MarcusDenker.43.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Abstract-MarcusDenker.216.diff
Re: [Pharo-dev] Penelope - Fail to create account
In my case is a spanish art seller. Saludos, Mariano On Wed, Jul 17, 2013 at 2:36 PM, Carla F. Griggio carla.grig...@gmail.comwrote: Not in my case, carlagrig...@gmail.com is a biologist from Brazil :P On Wed, Jul 17, 2013 at 3:40 AM, Clara Allende clari.alle...@gmail.comwrote: Just write your mail without dots, its the same for gmail (I've been there already) Sent from Gmail for Android On 17 Jul 2013 01:14, Carla F. Griggio carla.grig...@gmail.com wrote: Me :( I could see the issues by entering each category listed in the home page, but still it was uncomfortable to feel that I should know before hand in which category the issue I was looking for could be listed. I wanted to register to post issues with my name and I couldn't (and in the login form there should be a link explaining how to register, not only for asking a lost password). Cheers, Carla On Wed, Jul 17, 2013 at 1:06 AM, Mariano Vicente m.vic...@gmail.comwrote: Hi. I tried create my user in penelope [1], so I can see the issues in fogbugz. and this fails when i added the email, I think the problems are the dots in my email adress. Anybody have had the same problem? [1] http://bugs.pharo.org/issues?_k=DBsCrRwP1TgaBEDb Regards, Mariano
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/348/ 1 regressions found. Tests.Release.ReleaseTest.testUndeclared
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/348/ 1 regressions found. Tests.Release.ReleaseTest.testUndeclared
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/348/ 1 regressions found. Tests.Release.ReleaseTest.testUndeclared
Re: [Pharo-dev] Spec delete method
I do not think it's a UI framework concern to handle model behaviour (like registration to announcement) Ben I notice that more frequently in your replies. To not judge people. We do not need it. We are all good programmers. I need to know if there is a hook not that you explain me that my design is bad, because it is not ;) I think that I know what are layer, MVP, MVC and little friends are. This is not my model behavior. I want my ui not to get notification from my model anymore. So to me this is the responsibility of the UI to unregister itself and I do not see who else could do it. I have again the same problem that my Spec UI instance is not garbage collected and I only use weak announcements and I need to understand why. Stef Ben On Jul 17, 2013, at 9:40 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi ben I would like to unsubscribe announcement when the window is closed. Is there a hook for that in Spec? Stef
Re: [Pharo-dev] [DOC] Building and deploying
On Jul 16, 2013, at 4:42 PM, Sven Van Caekenberghe s...@stfx.eu wrote: On 15 Jul 2013, at 20:19, Paul Davidowitz pdavi...@fastmail.fm wrote: Very nice, but perhaps in a future tutorial the mode of presentation can be TDD… Thanks. Yes, it would be good if someone wrote a beautiful tutorial with a focus on TDD. For this subject and this tutorial, the tests are more functional tests than unit tests. I feel that it would be hard to do a web app fully TDD. But who knows, I like to read nice tutorials and learn something new as well ;-) +1 I know this feeling. Sven
Re: [Pharo-dev] Spec delete method
SOrry, it was not my intention :( Ben On Jul 17, 2013, at 8:07 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote: I do not think it's a UI framework concern to handle model behaviour (like registration to announcement) Ben I notice that more frequently in your replies. To not judge people. We do not need it. We are all good programmers. I need to know if there is a hook not that you explain me that my design is bad, because it is not ;) I think that I know what are layer, MVP, MVC and little friends are. This is not my model behavior. I want my ui not to get notification from my model anymore. So to me this is the responsibility of the UI to unregister itself and I do not see who else could do it. I have again the same problem that my Spec UI instance is not garbage collected and I only use weak announcements and I need to understand why. Stef Ben On Jul 17, 2013, at 9:40 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi ben I would like to unsubscribe announcement when the window is closed. Is there a hook for that in Spec? Stef
Re: [Pharo-dev] Config browser with filter
:) I have a catalogBuilder that starts to work so we will use configurations for generating some nice information. Stef On Jul 17, 2013, at 2:55 PM, Torsten Bergmann asta...@gmx.de wrote: screen attached Pharo 2.0: Slice and issue 11179 together with a fix for broken buttons Pharo 3.0: Slice and issue 11180 configbrowserfilter.png
Re: [Pharo-dev] Config browser with filter
honestly... I'm thinking that it was not a good idea to backport the spec conf browser to 2.0. looks to me that is not ready for production, and we need time to make it ready (time that we have for 3.0, but not for a bugfix release). just my opinion Esteban On Jul 17, 2013, at 8:43 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote: :) I have a catalogBuilder that starts to work so we will use configurations for generating some nice information. Stef On Jul 17, 2013, at 2:55 PM, Torsten Bergmann asta...@gmx.de wrote: screen attached Pharo 2.0: Slice and issue 11179 together with a fix for broken buttons Pharo 3.0: Slice and issue 11180 configbrowserfilter.png
Re: [Pharo-dev] Config browser with filter
On 2013-07-17, at 20:59, Esteban Lorenzano esteba...@gmail.com wrote: honestly... I'm thinking that it was not a good idea to backport the spec conf browser to 2.0. looks to me that is not ready for production, and we need time to make it ready (time that we have for 3.0, but not for a bugfix release). I agree
Re: [Pharo-dev] Penelope - Fail to create account
thanks Esteban :) Saludos, Mariano On Wed, Jul 17, 2013 at 3:09 PM, Esteban Lorenzano esteba...@gmail.comwrote: ok, I added both of you :) On Jul 17, 2013, at 7:43 PM, Mariano Vicente m.vic...@gmail.com wrote: In my case is a spanish art seller. Saludos, Mariano On Wed, Jul 17, 2013 at 2:36 PM, Carla F. Griggio carla.grig...@gmail.com wrote: Not in my case, carlagrig...@gmail.com is a biologist from Brazil :P On Wed, Jul 17, 2013 at 3:40 AM, Clara Allende clari.alle...@gmail.comwrote: Just write your mail without dots, its the same for gmail (I've been there already) Sent from Gmail for Android On 17 Jul 2013 01:14, Carla F. Griggio carla.grig...@gmail.com wrote: Me :( I could see the issues by entering each category listed in the home page, but still it was uncomfortable to feel that I should know before hand in which category the issue I was looking for could be listed. I wanted to register to post issues with my name and I couldn't (and in the login form there should be a link explaining how to register, not only for asking a lost password). Cheers, Carla On Wed, Jul 17, 2013 at 1:06 AM, Mariano Vicente m.vic...@gmail.comwrote: Hi. I tried create my user in penelope [1], so I can see the issues in fogbugz. and this fails when i added the email, I think the problems are the dots in my email adress. Anybody have had the same problem? [1] http://bugs.pharo.org/issues?_k=DBsCrRwP1TgaBEDb Regards, Mariano
Re: [Pharo-dev] [update 3.0] #30276
So you would be ready to change notNil - isNotNil and become a bit more incompatible with the rest of the world? I understand that the pair isEmpty/isNotEmpty may seem a bit more homogeneous, but I see no other selector constructed with (isNot isnt) while I see many others where is is omitted. I wonder what this kind of change really serve... Nicolas 2013/7/17 Marcus Denker marcus.den...@inria.fr 30276 - 7300 Finder raise an error on asking for implementors https://pharo.fogbugz.com/f/cases/7300 10348 GroupAlreadyExists vs. GroupsAlreadyExists confusion https://pharo.fogbugz.com/f/cases/10348 11180 Add a filter to the config browser https://pharo.fogbugz.com/f/cases/11180 11172 notEmpty should be isNotEmpty https://pharo.fogbugz.com/f/cases/11172 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1177.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-MarcusDenker.492.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/GroupManager-MarcusDenker.43.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Abstract-MarcusDenker.216.diff
Re: [Pharo-dev] [update 3.0] #30276
On 2013-07-17, at 22:32, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: So you would be ready to change notNil - isNotNil and become a bit more incompatible with the rest of the world? that method is already present in the image. I understand that the pair isEmpty/isNotEmpty may seem a bit more homogeneous, but I see no other selector constructed with (isNot isnt) while I see many others where is is omitted. I wonder what this kind of change really serve... For me they are consistent with all the other is* methods out there returning booleans.
Re: [Pharo-dev] [update 3.0] #30276
I wonder what is the decision process behind such change. Do you put in balance what you gain and what you loose? To me gain is near zero and these little changes stacked together put a useless burden on package maintenance. 2013/7/17 Camillo Bruni camillobr...@gmail.com On 2013-07-17, at 22:32, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: So you would be ready to change notNil - isNotNil and become a bit more incompatible with the rest of the world? that method is already present in the image. I understand that the pair isEmpty/isNotEmpty may seem a bit more homogeneous, but I see no other selector constructed with (isNot isnt) while I see many others where is is omitted. I wonder what this kind of change really serve... For me they are consistent with all the other is* methods out there returning booleans.
Re: [Pharo-dev] [update 3.0] #30276
there have been many similar decisions in the past, I remember for instance the move from #and:and:and: or #or:or:or: which weighs around the same as the #isNotNil. FileSystem or Slots are even on a bigger scale. Package maintenance in which sense, across different Pharo versions or different Smalltalk versions? Between Pharo versions should be more or less ok, since such changes (#isNotNil and Co) usually come with a proper deprecation. AFAIK there is someone working on detecting much more subtle changes in Pharo and provide lint rules on top. So I think we have to embrace changes. On 2013-07-17, at 22:49, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: I wonder what is the decision process behind such change. Do you put in balance what you gain and what you loose? To me gain is near zero and these little changes stacked together put a useless burden on package maintenance. 2013/7/17 Camillo Bruni camillobr...@gmail.com On 2013-07-17, at 22:32, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: So you would be ready to change notNil - isNotNil and become a bit more incompatible with the rest of the world? that method is already present in the image. I understand that the pair isEmpty/isNotEmpty may seem a bit more homogeneous, but I see no other selector constructed with (isNot isnt) while I see many others where is is omitted. I wonder what this kind of change really serve... For me they are consistent with all the other is* methods out there returning booleans.
Re: [Pharo-dev] [update 3.0] #30276
For FileSystem, there is a clear win, so I'd say the change is really worth. 1) you add more capabilities 2) more logical/convenient API 3) more efficient implementation 4) more scalable implementation The optional compatibility layer you offered is the exact solution to the upgrade problem (you give a bit of time to maintainers) I buy it. For and:and:and: etc... I agree with deprecation because such selector adds near to null (I personnally changed many senders in Squeak, so I'm totally biased here). For isNotNil I'm not convinced at all. To me, it's not much but noise. There are currently 3 senders vs 890 for notNil. I imagine many more in many packages. Think in mid/long term. What's your plans? Wait for the balance to slowly inverse? Rename all? For notEmpty, it's worse: 6 implementors. So what's the new contract? any new implementor of notEmpty shall also implement isNotEmpty? Or isNotEmpty is implemented in term of notEmpty in Object? Currently, 5 out of 6 implementors of notEmpty do not implement isNotEmpty and 1 out of 2 implementor of isNotEmpty does not implement notEmpty. It's not just noise, it's currently a mess! As for an automated rewrite rule, yes, this is some very usefull features for supporting such refactorings. I'd say a pre-requisite. But that force using several branches for cross version support, or worse, cross dialect support. If all diffs are automated, that's ok, if some of the changes are manual, it's a pain (backport etc...) 2013/7/17 Camillo Bruni camillobr...@gmail.com there have been many similar decisions in the past, I remember for instance the move from #and:and:and: or #or:or:or: which weighs around the same as the #isNotNil. FileSystem or Slots are even on a bigger scale. Package maintenance in which sense, across different Pharo versions or different Smalltalk versions? Between Pharo versions should be more or less ok, since such changes (#isNotNil and Co) usually come with a proper deprecation. AFAIK there is someone working on detecting much more subtle changes in Pharo and provide lint rules on top. So I think we have to embrace changes. On 2013-07-17, at 22:49, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: I wonder what is the decision process behind such change. Do you put in balance what you gain and what you loose? To me gain is near zero and these little changes stacked together put a useless burden on package maintenance. 2013/7/17 Camillo Bruni camillobr...@gmail.com On 2013-07-17, at 22:32, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: So you would be ready to change notNil - isNotNil and become a bit more incompatible with the rest of the world? that method is already present in the image. I understand that the pair isEmpty/isNotEmpty may seem a bit more homogeneous, but I see no other selector constructed with (isNot isnt) while I see many others where is is omitted. I wonder what this kind of change really serve... For me they are consistent with all the other is* methods out there returning booleans.
