Re: [Pharo-users] Pharo-Launcher Windows 8.1
I think that we should have a Pharo-bugs mailing list that gets notified for each bug that is filled in fogbugz 2015-03-21 4:54 GMT-03:00 kilon alios kilon.al...@gmail.com: Bottom line is that reporting a problem in the mailing list first makes much more sense because a) Way more likely to get an answer b) Avoid adding to the list on non existent bugs in fogbugz c) Bring the bug if it really exists to the attention of more people, hence increase that chance of the bug getting a fix. d) Far easier to remind people of the bug later on by just bumping on the thread which everyone on the list will get notified compared to fogbugz that if you are not subscribed to a bug you wont be notified. So yes definitely want to discourage people from starting from fogbugz. Also personally I dont like fogbugz because its so isolated. On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman b...@openinworld.com wrote: On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink shei...@yahoo.de wrote: Hi, I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1 Turned out I just needed to download the PharoV30.sources file and place into the installation folder. Now everything seems fine. Is this also a topic for the pharo bug list, or is there another place where I can mention this? Sebastian On Sat, Mar 21, 2015 at 1:46 AM, kilon alios kilon.al...@gmail.com wrote: there is also an options in settings that downloads and install sources for you automagically. This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz 100% is a bit strong and sounds a bit discouraging :).As long as you can list the detailed steps reproduce the problem, then its worth putting in fogbugz. However fogbugz has a lot of old issues and sometimes a new issue is like a lost tree in the forrest. Its generally beneficial if you socialise it on the mail list as well. A good workflow is: 1. Search fogbugz for similar issues. 2. Ask on the mail list if its a known issue, or if you should create a new one. List your steps to reproduce and ideally a solution. 3. Log a new issue on fogbugz, copying the mail list discussion there. Paste the link back to the mail list thread. So in general: * the mail list has a broader audience and gets a better triage * fogbugz tracks history to ensure it doesn't get lost - and nothing happens except what goes through the tracker. (btw, set Project=Launcher) cheers -ben
Re: [Pharo-users] Pharo-Launcher Windows 8.1
Bottom line is that reporting a problem in the mailing list first makes much more sense because a) Way more likely to get an answer b) Avoid adding to the list on non existent bugs in fogbugz c) Bring the bug if it really exists to the attention of more people, hence increase that chance of the bug getting a fix. d) Far easier to remind people of the bug later on by just bumping on the thread which everyone on the list will get notified compared to fogbugz that if you are not subscribed to a bug you wont be notified. So yes definitely want to discourage people from starting from fogbugz. Also personally I dont like fogbugz because its so isolated. On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman b...@openinworld.com wrote: On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink shei...@yahoo.de wrote: Hi, I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1 Turned out I just needed to download the PharoV30.sources file and place into the installation folder. Now everything seems fine. Is this also a topic for the pharo bug list, or is there another place where I can mention this? Sebastian On Sat, Mar 21, 2015 at 1:46 AM, kilon alios kilon.al...@gmail.com wrote: there is also an options in settings that downloads and install sources for you automagically. This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz 100% is a bit strong and sounds a bit discouraging :).As long as you can list the detailed steps reproduce the problem, then its worth putting in fogbugz. However fogbugz has a lot of old issues and sometimes a new issue is like a lost tree in the forrest. Its generally beneficial if you socialise it on the mail list as well. A good workflow is: 1. Search fogbugz for similar issues. 2. Ask on the mail list if its a known issue, or if you should create a new one. List your steps to reproduce and ideally a solution. 3. Log a new issue on fogbugz, copying the mail list discussion there. Paste the link back to the mail list thread. So in general: * the mail list has a broader audience and gets a better triage * fogbugz tracks history to ensure it doesn't get lost - and nothing happens except what goes through the tracker. (btw, set Project=Launcher) cheers -ben
Re: [Pharo-users] Git overriding repo load from different source
Hi Peter, I'm not sure how to answer all those cases (did I remember a conversation during PharoDays?). Can you elaborate on a) and the failure? Because I remember looking at the ability to override conflicts in Metacello by just saying: onConflict: [:ex | ex allow ] (for example: Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; onConflict: [:ex | ex allow]; load ) But, overall, for such a need, I would see two approaches: - a cache-type repository which overrides loads, as the MC package-cache is doing, based on package name and version (which is bad). - Metacello overrides, which may already exist but I'm not knowledgeable enough. Thierry Le 21/03/2015 14:41, Peter Uhnák a écrit : Hi, I'm trying to load local package over git one... basically: Projects A and B. A depends on B. A loads B from its BaselineOfA, the reference points to github. Now I have also local copy of B git repository, and I would like to either a) Override the load of B with local B (so the packages will point to local instead of remote). Currently it fails on MetacelloRepositorySpechasNoLoadConflicts: because each (local and git) repo points to different place. This would be useful if I want to make change to B AFTER the project B is already loaded. b) Add all packages from B to local B repo (same as manually using add to package... in Monticello Browser) This will work only if both the repos have the same packages, so probably not that useful. (i.e. no code differences) c) Override the GitHub B repository in the BaselineOfA BEFORE the project is loaded. This would require some mapping in Monticello browser, I've seen something like repositoryOverrides: but I don't know how it works. This would be useful if I knew beforehand that I want to make changes also to B. So how would one go about this? Having option c) would be probably the best; I can live without a). :) Any pointers appreciated, Peter
Re: [Pharo-users] Logic in Pharo ?
here's another one http://www.smalltalkhub.com/mc/goonsh/Prolog/main works in pharo 2.0. I think they are copies of AOKI Atsushi's version. On Fri, Mar 20, 2015 at 1:58 AM, Hernán Morales Durand hernan.mora...@gmail.com wrote: I don't know Prolog, but I have some links you may like: http://squeaksource.blueplane.jp/JgProlog/ http://wiki.squeak.org/squeak/1000 http://www.cs.middlebury.edu/~briggs/Courses/CS313-F12/smalltalk/stx/goodies/prolog/ http://www.smalltalkhub.com/#!/~SergiReyner/Prolog https://code.google.com/p/prolog-for-squeak-smalltalk/ There is also Prolog.st (but check the license) Prolog Goodies for VisualWorks 2.5/2.5J and VisualWave 1.0 Copyright (C) 1995-1997 AOKI Atsushi 1997/02/21 Some of them could be repeated/cloned/forked. Cheers, Hernán 2015-03-19 2:34 GMT-03:00 Alain Busser alain.bus...@gmail.com: Hello, I am currently working on mechanical means to solve Aristotle's syllogisms. My project is here: https://github.com/AlainBusser/LogicGame (programmed in CoffeeScript for a webApp). When I will present it (in a little more than two months) I plan to solve the same syllogisms with a software tool which must be free, of course. I am thinking about a lightweighted Prolog. Does this exist on Pharo? Or anything which would be similar (computing in a boolean algebra, something like alt-ergo etc)... and, if it runs on Raspbian it will be even better ;-) Alain -- Bernardo E.C. Sent from a cheap desktop computer in South America.
Re: [Pharo-users] Pharo-Launcher Windows 8.1
Nice idea! I think that we should have a Pharo-bugs mailing list that gets notified for each bug that is filled in fogbugz 2015-03-21 4:54 GMT-03:00 kilon alios kilon.al...@gmail.com mailto:kilon.al...@gmail.com: Bottom line is that reporting a problem in the mailing list first makes much more sense because a) Way more likely to get an answer b) Avoid adding to the list on non existent bugs in fogbugz c) Bring the bug if it really exists to the attention of more people, hence increase that chance of the bug getting a fix. d) Far easier to remind people of the bug later on by just bumping on the thread which everyone on the list will get notified compared to fogbugz that if you are not subscribed to a bug you wont be notified. So yes definitely want to discourage people from starting from fogbugz. Also personally I dont like fogbugz because its so isolated. On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman b...@openinworld.com mailto:b...@openinworld.com wrote: On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink shei...@yahoo.de mailto:shei...@yahoo.de wrote: Hi, I recently mentioned issues with the installation of the pharo-launcher on Windows 8.1 Turned out I just needed to download the PharoV30.sources file and place into the installation folder. Now everything seems fine. Is this also a topic for the pharo bug list, or is there another place where I can mention this? Sebastian On Sat, Mar 21, 2015 at 1:46 AM, kilon alios kilon.al...@gmail.com mailto:kilon.al...@gmail.com wrote: there is also an options in settings that downloads and install sources for you automagically. This is the right place to report issues and if you are 100% sure its a bug you can report it also in the pharo fogbuz 100% is a bit strong and sounds a bit discouraging :).As long as you can list the detailed steps reproduce the problem, then its worth putting in fogbugz. However fogbugz has a lot of old issues and sometimes a new issue is like a lost tree in the forrest. Its generally beneficial if you socialise it on the mail list as well. A good workflow is: 1. Search fogbugz for similar issues. 2. Ask on the mail list if its a known issue, or if you should create a new one. List your steps to reproduce and ideally a solution. 3. Log a new issue on fogbugz, copying the mail list discussion there. Paste the link back to the mail list thread. So in general: * the mail list has a broader audience and gets a better triage * fogbugz tracks history to ensure it doesn't get lost - and nothing happens except what goes through the tracker. (btw, set Project=Launcher) cheers -ben
[Pharo-users] Git overriding repo load from different source
Hi, I'm trying to load local package over git one... basically: Projects A and B. A depends on B. A loads B from its BaselineOfA, the reference points to github. Now I have also local copy of B git repository, and I would like to either a) Override the load of B with local B (so the packages will point to local instead of remote). Currently it fails on MetacelloRepositorySpechasNoLoadConflicts: because each (local and git) repo points to different place. This would be useful if I want to make change to B AFTER the project B is already loaded. b) Add all packages from B to local B repo (same as manually using add to package... in Monticello Browser) This will work only if both the repos have the same packages, so probably not that useful. (i.e. no code differences) c) Override the GitHub B repository in the BaselineOfA BEFORE the project is loaded. This would require some mapping in Monticello browser, I've seen something like repositoryOverrides: but I don't know how it works. This would be useful if I knew beforehand that I want to make changes also to B. So how would one go about this? Having option c) would be probably the best; I can live without a). :) Any pointers appreciated, Peter
Re: [Pharo-users] [Pharo-dev] The Grapher charting engine
Nice work. I will reply about improvements separately. Cheers. Doru On Fri, Mar 20, 2015 at 10:18 PM, Alexandre Bergel alexandre.ber...@me.com wrote: Dear all, As many of you know, Grapher is a über-cool charting engine, part of Roassal. For people who do not know what Grapher is, here is a (compelling we hope) example: Which is obtained by the following script: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | b colors points ds pts dec lb | b := RTGrapher new. colors := Array with: Color red with: Color blue. points := OrderedCollection new. colors do: [ :c | ds := RTStackedDataSet new. pts := ((1 to: 100) collect: [ :i | 50 atRandom - 25 ]) cumsum. points add: pts. ds points: pts. dec := RTDevVarDecorator new. dec moveBehind; desviation: 0.5; color: (c alpha: 0.3); points: pts. ds connectUsing: (RTLine new color: (c alpha: 0.5); width: 1 ). b add: ds. b addDecorator: dec. ]. b axisX; axisY. b build. lb := RTLegendBuilder new. lb view: b view. colors doWithIndex: [ :c :i | lb addColor: c text: 'Series ', i printString ]. lb build. b view @ RTZoomableView. b view -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= In our grand vision of making Roassal the best visualizing engine of the Universe (we also know to be modest time to time, but not today :-), Grapher will play a very important role. We would like to stabilize Grapher and make it sure it happily fits everybody needs. You can help on it: - When you are tempted to look at the dark side of the planet (this is where R, JFreeChart, gnuplot, D3 and all their friends live), let us know. We will make sure to make you are happy again. - Share your wishlist with us. We already have a long todo list, but your opinion does matter and will take it seriously - we are open to contributions, which could be financial, bug fixe, enhancement, or simply encouragement. I am very happy to be surrounded by very smart engineers. Your encouragement are making them happy :-) Cheers, Alexandre, in the name of the Object Profile Team NB: sorry for the cross-list posting, but this email is very important for us, and for you we hope. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- www.tudorgirba.com Every thing has its own flow
[Pharo-users] The Grapher charting engine
Alex
Roassal is really cool now I have one question
why we cannot say
serie1pointsAndVariations :- given
series2pointsAndVariations := given
RGrapher new
axisX; axisY;
seriesWithDeviation: {serie1pointsAndVariations .
serie2pointsAndVariations};
maxXAxis: 100;
My point is why the line connection is not hidden from the user.
I think that roassal is a cool scripting engine but it got ***trapped***
there.
A primary user wants to have abstractions
Then in a second time he wants to open the trunk and script its own.
also why don't you have nice default
dec := RTDevVarDecorator new.
dec moveBehind;
desviation: 0.5;
color: (c alpha: 0.3);
points: pts.
=
dec := RTDevVarDecorator new.
desviation: 0.5;
color: c;
points: pts.
why the decorator should be added to the builder?
So see what I mean why do you expose to the user all the design challenges?
I strongly suggest that during 1 month you stop to think in term of script.
Imagine that you do not have a workspace anymore.
Stef
On 20 Mar 2015, at 22:18, Alexandre Bergel alexandre.ber...@me.com wrote:
Dear all,
As many of you know, Grapher is a über-cool charting engine, part of
Roassal.
For people who do not know what Grapher is, here is a (compelling we
hope) example:
Screen Shot 2015-03-20 at 6.12.22 PM.png
Which is obtained by the following script:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| b colors points ds pts dec lb |
b := RTGrapher new.
colors := Array with: Color red with: Color blue.
points := OrderedCollection new.
colors do: [ :c |
ds := RTStackedDataSet new.
pts := ((1 to: 100) collect: [ :i | 50 atRandom - 25 ]) cumsum.
points add: pts.
ds points: pts.
dec := RTDevVarDecorator new.
dec moveBehind;
desviation: 0.5;
color: (c alpha: 0.3);
points: pts.
ds connectUsing: (RTLine new color: (c alpha: 0.5); width: 1 ).
b add: ds.
b addDecorator: dec.
].
b axisX; axisY.
b build.
lb := RTLegendBuilder new.
lb view: b view.
colors doWithIndex: [ :c :i |
lb addColor: c text: 'Series ', i printString ].
lb build.
b view @ RTZoomableView.
b view
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
In our grand vision of making Roassal the best visualizing engine of the
Universe (we also know to be modest time to time, but not today :-),
Grapher will play a very important role. We would like to stabilize
Grapher and make it sure it happily fits everybody needs. You can help
on it:
- When you are tempted to look at the dark side of the planet (this
is where R, JFreeChart, gnuplot, D3 and all their friends live), let us
know. We will make sure to make you are happy again.
- Share your wishlist with us. We already have a long todo list,
but your opinion does matter and will take it seriously
- we are open to contributions, which could be financial, bug fixe,
enhancement, or simply encouragement.
I am very happy to be surrounded by very smart engineers. Your
encouragement are making them happy :-)
Cheers,
Alexandre, in the name of the Object Profile Team
NB: sorry for the cross-list posting, but this email is very important
for us, and for you we hope.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
___
vwnc mailing list
v...@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
[Pharo-users] adding local repos to configuration browser
Hi, is it possible to hijack Configuration Browser and put there references to my own _local_ projects? Thanks, Peter
Re: [Pharo-users] Git overriding repo load from different source
d) unload all B packages, remove B github repo, load B locally However currently I can only unload packages one at a time manually, instead of all related to a repo. Peter
[Pharo-users] Threadsafe orderedCollection
Hi guys I'm looking for a thread safe simple orderedcollection to be able to concurrent add:. We have atomicSharedQueue but it does not support access to a given element. Stef
Re: [Pharo-users] Git overriding repo load from different source
e) having separate baseline method which does not load github packages and expects that they are already loaded But since baseline only uses single method I don't see how this could be done.
Re: [Pharo-users] The Grapher charting engine
Hi,
I fully agree with your API suggestions, but I do not quite understand why
you say that it is because of the scripting that the API does not look like
this. It's the opposite I think.
When you script you want as succinct as possible (so, no moveBehind: and
stuff). And you want to gradually add details and not be forced to specify
them from the very beginning (so, good defaults). In fact, the rule of
thumb that I argue for is that a good scripting (and in fact any API)
interface is one that allows you to make a difference with any new line of
code. That means that, ideally, we would want every line to be able to live
on its own and not require another one. It's obviously not always possible,
but I find it helps me when I grow an API.
Cheers,
Doru
On Sat, Mar 21, 2015 at 12:23 PM, stepharo steph...@free.fr wrote:
Alex
Roassal is really cool now I have one question
why we cannot say
serie1pointsAndVariations :- given
series2pointsAndVariations := given
RGrapher new
axisX; axisY;
seriesWithDeviation: {serie1pointsAndVariations .
serie2pointsAndVariations};
maxXAxis: 100;
My point is why the line connection is not hidden from the user.
I think that roassal is a cool scripting engine but it got ***trapped***
there.
A primary user wants to have abstractions
Then in a second time he wants to open the trunk and script its own.
also why don't you have nice default
dec := RTDevVarDecorator new.
dec moveBehind;
desviation: 0.5;
color: (c alpha: 0.3);
points: pts.
=
dec := RTDevVarDecorator new.
desviation: 0.5;
color: c;
points: pts.
why the decorator should be added to the builder?
So see what I mean why do you expose to the user all the design challenges?
I strongly suggest that during 1 month you stop to think in term of script.
Imagine that you do not have a workspace anymore.
Stef
On 20 Mar 2015, at 22:18, Alexandre Bergel alexandre.ber...@me.com
wrote:
Dear all,
As many of you know, Grapher is a über-cool charting engine, part of
Roassal.
For people who do not know what Grapher is, here is a (compelling we hope)
example:
Screen Shot 2015-03-20 at 6.12.22 PM.png
Which is obtained by the following script:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| b colors points ds pts dec lb |
b := RTGrapher new.
colors := Array with: Color red with: Color blue.
points := OrderedCollection new.
colors do: [ :c |
ds := RTStackedDataSet new.
pts := ((1 to: 100) collect: [ :i | 50 atRandom - 25 ]) cumsum.
points add: pts.
ds points: pts.
dec := RTDevVarDecorator new.
dec moveBehind;
desviation: 0.5;
color: (c alpha: 0.3);
points: pts.
ds connectUsing: (RTLine new color: (c alpha: 0.5); width: 1 ).
b add: ds.
b addDecorator: dec.
].
b axisX; axisY.
b build.
lb := RTLegendBuilder new.
lb view: b view.
colors doWithIndex: [ :c :i |
lb addColor: c text: 'Series ', i printString ].
lb build.
b view @ RTZoomableView.
b view
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
In our grand vision of making Roassal the best visualizing engine of the
Universe (we also know to be modest time to time, but not today :-),
Grapher will play a very important role. We would like to stabilize Grapher
and make it sure it happily fits everybody needs. You can help on it:
- When you are tempted to look at the dark side of the planet (this is
where R, JFreeChart, gnuplot, D3 and all their friends live), let us know.
We will make sure to make you are happy again.
- Share your wishlist with us. We already have a long todo list, but
your opinion does matter and will take it seriously
- we are open to contributions, which could be financial, bug fixe,
enhancement, or simply encouragement.
I am very happy to be surrounded by very smart engineers. Your
encouragement are making them happy :-)
Cheers,
Alexandre, in the name of the Object Profile Team
NB: sorry for the cross-list posting, but this email is very important for
us, and for you we hope.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
___
vwnc mailing list
v...@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
--
www.tudorgirba.com
Every thing has its own flow
Re: [Pharo-users] Pharo-Launcher Windows 8.1
Le 21/03/2015 14:08, stepharo a écrit : Nice idea! I think that we should have a Pharo-bugs mailing list that gets notified for each bug that is filled in fogbugz Yes that would be nice, when you look at bugs on fogbugz site, you do not always see that it is discussed in the list (lot of threads) -- Regards, Alain
Re: [Pharo-users] The Grapher charting engine
Hi Stef, On Sat, Mar 21, 2015 at 8:52 PM, stepharo steph...@free.fr wrote: Le 21/3/15 13:58, Tudor Girba a écrit : Hi, I fully agree with your API suggestions, but I do not quite understand why you say that it is because of the scripting that the API does not look like this. It's the opposite I think. When you script you want as succinct as possible (so, no moveBehind: and stuff). And you want to gradually add details and not be forced to specify them from the very beginning (so, good defaults). In fact, the rule of thumb that I argue for is that a good scripting (and in fact any API) interface is one that allows you to make a difference with any new line of code. That means that, ideally, we would want every line to be able to live on its own and not require another one. It's obviously not always possible, but I find it helps me when I grow an API. use the technique you want but to not dillute my point. I do not care how you do it. I care about having details away. To me the feel that roassal gives me is that this is a tool to make demo to impress audience as to grow something, while I think that it could be a killer app with two faces: predefined compact api and a scripting way where you open the trunk and build your own. A long script will not impress any audience. These are the same goals, not different. The idea of builders (Grapher is such a builder) is supposed to provide those levels (the basic engine can do everything, and the builder provides a more constrained higher level API). I fully agree that the current builders are not expressive enough. And I also agree that we need a dedicated effort to just making them more compact. We are fully in sync and I do not dilute your point, but I do not want to leave the impression that scripting is something bad, or secondary :). Cheers, Doru S. -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-users] The Grapher charting engine
Le 21/3/15 13:58, Tudor Girba a écrit : Hi, I fully agree with your API suggestions, but I do not quite understand why you say that it is because of the scripting that the API does not look like this. It's the opposite I think. When you script you want as succinct as possible (so, no moveBehind: and stuff). And you want to gradually add details and not be forced to specify them from the very beginning (so, good defaults). In fact, the rule of thumb that I argue for is that a good scripting (and in fact any API) interface is one that allows you to make a difference with any new line of code. That means that, ideally, we would want every line to be able to live on its own and not require another one. It's obviously not always possible, but I find it helps me when I grow an API. use the technique you want but to not dillute my point. I do not care how you do it. I care about having details away. To me the feel that roassal gives me is that this is a tool to make demo to impress audience as to grow something, while I think that it could be a killer app with two faces: predefined compact api and a scripting way where you open the trunk and build your own. S.
[Pharo-users] Cleaning/Simplifying Nautilus
Hi I want to clean Nautilus and to simplify its code and functionality. In addition I want to reduce to student load in the context of the Mooc we will start to work on. So I want to remove the lock mechanism and the multiple methods. This was an experience that did not really work. It was nice to try but it is time to remove that. So I hope that not many people use this feature. https://pharo.fogbugz.com/default.asp?15199 After I will start to clean the group to keep a consistent and useful subset. Stef
Re: [Pharo-users] [Pharo-dev] Cleaning/Simplifying Nautilus
But seriously, for 4.0 ? Now ? On 22 Mar 2015, at 00:04, Nicolai Hess nicolaih...@web.de wrote: 2015-03-21 23:02 GMT+01:00 stepharo steph...@free.fr: Hi I want to clean Nautilus and to simplify its code and functionality. In addition I want to reduce to student load in the context of the Mooc we will start to work on. So I want to remove the lock mechanism and the multiple methods. This was an experience that did not really work. It was nice to try but it is time to remove that. +1 (I never understood how to use this lock) So I hope that not many people use this feature. https://pharo.fogbugz.com/default.asp?15199 After I will start to clean the group to keep a consistent and useful subset. Stef
Re: [Pharo-users] [Pharo-dev] Cleaning/Simplifying Nautilus
2015-03-21 23:02 GMT+01:00 stepharo steph...@free.fr: Hi I want to clean Nautilus and to simplify its code and functionality. In addition I want to reduce to student load in the context of the Mooc we will start to work on. So I want to remove the lock mechanism and the multiple methods. This was an experience that did not really work. It was nice to try but it is time to remove that. +1 (I never understood how to use this lock) So I hope that not many people use this feature. https://pharo.fogbugz.com/default.asp?15199 After I will start to clean the group to keep a consistent and useful subset. Stef
Re: [Pharo-users] adding local repos to configuration browser
There is probably not a built in way - but its open source so definitely possible to hijack it in any way you please. You just need to do some digging. Here is how... 1. Bring up halos on a useful button of Configuration Browser. Keep clicking to cycle through LabelMorph, AlignmentMorph until you get to PLuggableButtonMorph. 2. Click the spanner Debug icon and select Inspect Morph. 3. Find somewhere to break the message sent when the button is clicked, which will vary with widget. In this case, you might change the /actionSelection/ from #action to #breakMe. Note to devs: It seems setting a value is a little broken in cleanly displaying the new value as it is typed. Only a blank field is shown, but the value still gets set with enter. 4. Now click the button (btw, make sure a package is selected).A debugger will open with MNU #breakMe at a #perform: message. 5. In the debugger, set /actionSelection/ back to #action, then Restart and step down to and then into the the #perform: message. Continue stepping to dig in behind the app. In this case you get to something interesting stepping into actionHolder value value , and further on where #selectedItem is sent searching on senders of #configurationList gives you a class of interest to look into. Look on the class-side of this to discover methods returning default values and put halts in these to see where they are called from when Configuration Browser initialises, and work out how to add your own. 6. Work out how to make it easier for others to add their our _local_ projects and contribute back for inclusion into Pharo. cheers -ben On Sat, Mar 21, 2015 at 8:19 PM, Peter Uhnák i.uh...@gmail.com wrote: Hi, is it possible to hijack Configuration Browser and put there references to my own _local_ projects? Thanks, Peter
Re: [Pharo-users] adding local repos to configuration browser
Note to devs: It seems setting a value is a little broken in cleanly displaying the new value as it is typed. Only a blank field is shown, but the value still gets set with enter. This only happened one time. I cannot reproduce again. cheers -ben
Re: [Pharo-users] Pharo-Launcher Windows 8.1
On Sat, Mar 21, 2015 at 9:55 PM, Alain Rastoul alf.mmm@gmail.com wrote: Le 21/03/2015 14:08, stepharo a écrit : Nice idea! I think that we should have a Pharo-bugs mailing list that gets notified for each bug that is filled in fogbugz Yes that would be nice, when you look at bugs on fogbugz site, you do not always see that it is discussed in the list (lot of threads) It would be nice, but btw will not address that situation. Parties interested in the issue woudl still need to copy mail list discussion there, or link to the mail archive of the discussion. Fogbugz should hold case history. cheers -ben
Re: [Pharo-users] Pharo-Launcher Windows 8.1
Le 22/03/2015 03:36, Ben Coman a écrit : It would be nice, but btw will not address that situation. Parties interested in the issue woudl still need to copy mail list discussion there, or link to the mail archive of the discussion. Fogbugz should hold case history. cheers -ben You are right if you see the discussion in the list. I recently added a note to a case without seeing it was discussed in the list and think it was not the good place. A separate list for bugs (threads in the list do not allways clearly link to the bugs and they are lot of various threads) may have helped. With a tag in the title in case of opened bugs. I agree that fogbugz should hold the history. -- Regards, Alain
