December 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Engage on "Where Smalltalk Went Wrong (2004)"

by Sebastian Sastre

yeah hehe, the Hacker News popularity mysteries Still, a couple of guys mention they are curious to try it > On Dec 26, 2014, at 9:57 AM, Craig Latta <craig(a)netjam.org> wrote: > > > 2004? Spontaneously rehashing 2004 is interesting now? Must be the > end of the year. :) > > > -C > > -- > Craig Latta > netjam.org > +31 6 2757 7177 (SMS ok) > + 1 415 287 3547 (no SMS) > >

Dec. 26, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by Tudor Girba

Very nice work! Thanks for pushing this. I think you will not be alone in working on Bloc for long :) Doru On Wed, Dec 24, 2014 at 3:41 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Wow! Impressive!!! > > Alexandre > > > > On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec(a)yahoo.com> > wrote: > > > > Hello all, > > > > Iâve just uploaded a small demo of Bloc. > > http://vimeo.com/115336678 > > > > > > Cheers > > Alain > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 26, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by Nicolai Hess

2014-12-26 9:37 GMT+01:00 Alain Plantec <alain.plantec(a)yahoo.com>: > Hi Nicolai, > > Yes, youâre right. There is this issue in 3.0. > In a fresh image, the Author requestFullname dialog is opened at > Bloc starting (because of Athens if I remember well). > Maybe you tried with a 3.0. > This issue has been fixed in 4.0 since few months. > Try with the last Pharo 4 and it should be ok. > I always use pharo4 :) > Another solution is to evaluate > ---- > Author requestFullName > no change, cmd+enter for opening spotter works, but I can not type any character > ââ > before you start a bloc space. > > Cheers > Alain > > > Why does it open another window? (see screenshot, the left pharo windows opens after switching to bloc world. Only the right window acts to mouse and keyboard (cmd+enter). The left window looks like a "mirror", just shows what happens in the right window. > > On 25 Dec 2014, at 20:57, Nicolai Hess <nicolaihess(a)web.de> wrote: > > I tried both, loadDevelopment and loadBleedingEdget, but > I can not get it to work like in the video. > For me, the keyboard input stop working as soon as I start the bloc world. > And for me it opens another window in the background, what is it for? > > BTW how many developers working on bloc, just you two ? > > nicolai > > > > 2014-12-25 10:31 GMT+01:00 stepharo <stepharo(a)free.fr>: > >> >> Le 25/12/14 03:04, Ben Coman a Ã©crit : >> >>> Really nice to see your progress. Now do you have some sketches that >>> show how it relates to the components of the existing Morphic? What is >>> being disposed of, what reimplemented, what ported? >>> >> >> I'm writing class comments and soon a chapter. But it takes time because >> I have to also do a bit of reverse engineering. >> Now Bloc does not relate to Morphic :) Everything is rewritten from >> scratch and we will rewrite everything. >> We will try to reuse Spec. >> Now for default Morphic, rewritting all the morphs to use Athens >> is a huge tasks considered the current logic of certain morphic elements >> Since Bloc is fully athens-based, it may be better to only work on Bloc. >> Now the trick is that we can use the morphic elements. >> >>> This would really help to understand where contributions might be useful. >>> >>> >>> btw, with Build 40419, "ConfigurationOfBloc load" warns that >>> it depends on BlEllipseShape which must be resolved before #drawOn: and >>> #drawOnAthensCanvas: can be resolved. >>> >> >> Yes this is normal, you should load bleedingEdge. >> >> >>> "ConfigurationOfBlock loadDevelopment" works fine. >>> >>> cheer -ben >>> >>> Sven Van Caekenberghe wrote: >>> >>>> Yes, a nice X-Mas present ! >>>> >>>> On 24 Dec 2014, at 15:41, Alexandre Bergel <alexandre.bergel(a)me.com> >>>>> wrote: >>>>> >>>>> Wow! Impressive!!! >>>>> >>>>> Alexandre >>>>> >>>>> >>>>> On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec(a)yahoo.com> >>>>>> wrote: >>>>>> >>>>>> Hello all, >>>>>> >>>>>> Iâve just uploaded a small demo of Bloc. >>>>>> http://vimeo.com/115336678 >>>>>> >>>>>> >>>>>> Cheers >>>>>> Alain >>>>>> >>>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> > >

Dec. 26, 2014

Re: [Pharo-dev] Old inspector and explorer

by Tudor Girba

Hi, I think there must be a misunderstanding. There can be a good reason for having a basic inspector around, but I think the reason is not because people cannot choose what to use. There is a toggle to enable/disable the GTInspector. But, even without it, the main feature of the GTInspector is exactly to be extended the way people want and not impose a fixed way. This is completely different from what existed before. In fact, half a year ago there was no problem that people could neither choose nor extend anything. In the meantime, we can extend our workflows significantly. Adding the various flavors of browsing objects is perhaps a couple of lines long and each of us can tweak it because there is no higher entity that should decide anymore. What I cannot quite grasp is that while we pride ourselves with working on a reflective language, when we have reflective tools, we seem to not be able to take half an hour to build the tool that fits our needs. I am still wondering what is needed to improve this. I think that it's a problem of exercise or of communication, but it seems that just providing the examples that I linked before is not enough and most people look at the inspector still as a black box tool. I will try to work on a tutorial to see if it gets better, but do you find the moldability proposition not valuable or just unclear? But, as I said, there can still be a valid reason to enable a basic inspector that relies on a minimal of libraries (so, definitely not the Spec one) for the same reason we have an emergency debugger. Cheers, Doru On Thu, Dec 25, 2014 at 11:43 AM, stepharo <stepharo(a)free.fr> wrote: > I will add basicInspect in Object so that we can get access to the old > inspector. > I like that people can choose their tools! > I mentioned that 20 times but people do not care apparently. > > Stef > > Le 23/12/14 11:50, Norbert Hartl a Ã©crit : > > Is there a way to get the old tools via shortcut? >> >> I started something new with pharo 4.0 today. I discovered a bug in >> Nautilus where every rename or deletion of a method raises a debugger. I >> tried finding the bug but struggled because to me the new inspector is >> really confusing. If I "just" want to unfold a few levels of references to >> get a glimpse of the structure the new tool prevents me from doing that. >> There is just to much information in this window and too much happening to >> me. >> To me it looks like a power tool you need to get used to. So it is >> probably not the best tool for simple tasks and people new to this >> environment might be overwhelmed. At least I would like to be able to use >> the old tools. >> >> Norbert >> >> >> >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 26, 2014

Re: [Pharo-dev] Old inspector and explorer

by Tudor Girba

Hi, Binding "self" to a selection in the tree will likely not happen within this interface self has the clear meaning of "the object behind the current pane". This is a simple thing to remember and making it depend on the selection from the Raw view would make it more confusing. Keep in mind that having it depend on the selection was a solution for the interface that provided only one playground per inspector, but now as you get one per pane/object we do not have that restriction. Cheers, Doru On Wed, Dec 24, 2014 at 12:17 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-12-23 22:46 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> The Raw view is a tree :) >> >> Doru >> >> > > > It would be good if "self", in the bottom panel, is bound to the current > selected item in the tree. > And a "compact" tree view does not need to create a new pane to the right. > > ( I am still unfamilliar with the behavior: select an element and the > whole tab scrolls to the left. > For example, If you have more than one tab and you want to select an item > in the right most > tab for opening a new inspector on that item, the pane with the selected > item scrolls away). > > nicolai > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 26, 2014

Re: [Pharo-dev] Engage on "Where Smalltalk Went Wrong (2004)"

by Craig Latta

2004? Spontaneously rehashing 2004 is interesting now? Must be the end of the year. :) -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Dec. 26, 2014

Re: [Pharo-dev] Engage on "Where Smalltalk Went Wrong (2004)"

by kilon alios

Just a word of warning, such posts are click baits and I think the best way we as community can deal with them is to just ignore them. We should not forget that it was a few years ago that internet was littered with posts about JAVA demise , actually even today the "Java is dead" is a very popular topic probably more than any other popular language out there. Still here we are today Java is going strong and powerful. Personally I dont recommend Pharo or Smalltalk as an ideal solution, for me Smalltalk is a very specific solution to a very specific problem and thats is the connection between the machine and the user and of course it comes with its drawbacks. Depending on your style of coding you may or may not like Smalltalk / Pharo / Amber etc. In my case as a coder I was always thinking in smalltalk way even though I am very recently introduced to it. For what some other people seemed for me it looked a natural way of doing it. So when people ask me about Pharo I try to keep my emotions at bay offer an objective look in what I like and I don't like about Pharo. The problem with such blog posts is not that they offer a negative opinion but that they try based on some fact to also pass secondary opinions as facts too underestimating how people think differently , have different priorities and just like different things. I have recommended Pharo to several people trying to be as objective as possible. I got one very negative response from a person that was more like a troll and seemed to hate anything having to do with OO. Others found Pharo from interesting to very good. A minority of them chose to embrace Pharo as a platform for coding because they were tied to different technologies that Pharo did not support as well. On Fri, Dec 26, 2014 at 1:28 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > Hi guys, > > That post is more emotional than rational and when it tries to be rational > a careful read reveal basic misconceptions. > > If you are up to it, I suggest to engage in the YC thread (not here) in > smart ways to add value to those that are authentically curious > > Here is the link to the discussion: > https://news.ycombinator.com/item?id=8797522 > > sebastian <https://about.me/sebastianconcept> > > o/ > > > > >

Dec. 26, 2014

Engage on "Where Smalltalk Went Wrong (2004)"

by Sebastian Sastre

Hi guys, That post is more emotional than rational and when it tries to be rational a careful read reveal basic misconceptions. If you are up to it, I suggest to engage in the YC thread (not here) in smart ways to add value to those that are authentically curious Here is the link to the discussion: https://news.ycombinator.com/item?id=8797522 <https://news.ycombinator.com/item?id=8797522> sebastian <https://about.me/sebastianconcept> o/

Dec. 26, 2014

[pharo-project/pharo-core] bc7563: 40423

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: bc75634e2d3b36fad98f372d3c2ad72f7c2e7d01 https://github.com/pharo-project/pharo-core/commit/bc75634e2d3b36fad98f372d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-26 (Fri, 26 Dec 2014) Changed paths: A Chroma-CubeHelix.package/CubeHelix.class/README.md A Chroma-CubeHelix.package/CubeHelix.class/class/class initialization/initialize.st A Chroma-CubeHelix.package/CubeHelix.class/class/instance creation/hueShift_rotations_saturation_.st A Chroma-CubeHelix.package/CubeHelix.class/definition.st A Chroma-CubeHelix.package/CubeHelix.class/instance/accessing/at_.st A Chroma-CubeHelix.package/CubeHelix.class/instance/accessing/gamma_.st A Chroma-CubeHelix.package/CubeHelix.class/instance/accessing/hueShift_.st A Chroma-CubeHelix.package/CubeHelix.class/instance/accessing/rotations.st A Chroma-CubeHelix.package/CubeHelix.class/instance/accessing/rotations_.st A Chroma-CubeHelix.package/CubeHelix.class/instance/accessing/saturation_.st A Chroma-CubeHelix.package/CubeHelix.class/instance/conversion - athens/asColorStops_on_.st A Chroma-CubeHelix.package/CubeHelix.class/instance/initialization/initialize.st M NautilusCommon.package/NautilusHistoryEntry.class/instance/accessing/selectedMethod.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script423.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40423.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/NewVersionBrowser.class/class/api/browseVersionsForClass_selector_.st M Spec-Tools.package/NewVersionBrowser.class/definition.st R Spec-Tools.package/NewVersionBrowser.class/instance/copy and paste/scanVersionsOf_class_meta_category_selector_.st A Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/browseVersionsOf_.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/browseVersionsOf_class_meta_category_selector_.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/buildBrowser.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/buildChangeList.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/revert_.st M Spec-Tools.package/NewVersionBrowser.class/instance/menu/browseImplementors.st M Spec-Tools.package/NewVersionBrowser.class/instance/menu/browseSenders.st M Spec-Tools.package/NewVersionBrowser.class/instance/menu/compareToCurrentVersion.st A Spec-Tools.package/NewVersionBrowser.class/instance/private/scanVersionsOf_class_meta_category_selector_.st Log Message: ----------- 40423 14644 Make NewVersionBrowser using a RingDefinition instead of class/selector https://pharo.fogbugz.com/f/cases/14644 14648 Include CubeHelix gradient definition https://pharo.fogbugz.com/f/cases/14648 14653 removeing or renaming raises an exception https://pharo.fogbugz.com/f/cases/14653 http://files.pharo.org/image/40/40423.zip

Dec. 26, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40423 Home: https://github.com/pharo-project/pharo-core

Dec. 26, 2014