- Pharo-dev - lists.pharo.org

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

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

by Alain Plantec

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. Another solution is to evaluate ---- Author requestFullName ââ before you start a bloc space. Cheers Alain > 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 <mailto:stepharo@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 <mailto:alexandre.bergel@me.com>> wrote: > > Wow! Impressive!!! > > Alexandre > > > On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com>> wrote: > > Hello all, > > Iâve just uploaded a small demo of Bloc. > http://vimeo.com/115336678 <http://vimeo.com/115336678> > > > Cheers > Alain > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > >

Dec. 26, 2014

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

by Alain Plantec

> On 26 Dec 2014, at 07:09, Ben Coman <btc(a)openInWorld.com> wrote: >> >> see in TBlAthensWrapper>>unprotectedFullDrawOn: > > I can't see that class. I guess you mean BlAthensPasteUpMorph>>unprotectedFullDrawOn: Hi Ben, TBlAthensWrapper is the trait :) Alain > >> ---- >> self surface displayOnMorphicCanvas: aCanvas at: self position >> ââ >> It slows down the rendering very much. >> what would be cool would be to have a native Athens/Cairo vm display to really benefit from Athens. > >

Dec. 26, 2014

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

by Ben Coman

Alain Plantec wrote: >> On 25 Dec 2014, at 10:31, stepharo <stepharo(a)free.fr> wrote: >> >> >> 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? > > yes, almost everything is new or rewritten and you are right, its time to write documentation. > Now, there is one well identified issue. > Athens is used to render everything except > the Morphic world. > This is cool but at the end of the rendering, the vm Form based display is used by wrappers : > see in TBlAthensWrapper>>unprotectedFullDrawOn: I can't see that class. I guess you mean BlAthensPasteUpMorph>>unprotectedFullDrawOn: > ---- > self surface displayOnMorphicCanvas: aCanvas at: self position > ââ > It slows down the rendering very much. > what would be cool would be to have a native Athens/Cairo vm display to really > benefit from Athens.

Dec. 26, 2014

Re: [Pharo-dev] Building UI

by HernÃ¡n Morales Durand

Norbert, The standard image is using Spec in many places and there are examples (although pretty basic IMO). If you want to perform validation you can check a project I am working on, it's called "Query Builder" http://www.smalltalkhub.com/#!/~hernan/QueryBuilder but you may want to have it as last resource because it lacks tests and examples, although I have been using it for a while without problems. For the events you can check (at least in Pharo 3.0) : ProtocolViewer new openWithSpec For a basic form layout in rows you could start from a DynamicComposableModel and then grow from there by specializing required Spec methods in a ComposableModel (#defaultSpec, #initializeWidgets, #title, #extent, etc): " Configure the Spec models " view := DynamicComposableModel new instantiateModels: #(labelA LabelModel textA TextInputFieldModel labelB LabelModel textB TextInputFieldModel); extent: 500@200; title: 'Title' yourself. " Configure the Spec layout " layout := SpecLayout composed newColumn: [ : r | r add: #labelA; add: #textA; add: #labelB; add: #textB ]; yourself. " Set up the widgets " view labelA text: 'A'. view labelB text: 'B'. " Open the Window " (view openDialogWithSpecLayout: layout) centered; modalRelativeTo: World. Cheers, HernÃ¡n 2014-12-25 16:02 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: > > Hernan, > > Am 25.12.2014 um 19:23 schrieb HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com>: > > Hi Norbert, > Can you provide an example what do you expect to see? > > > nothing special. A windowed app with let's say 5 different text and other > entry fields (dates, numbers, geo coordinates,...). A modal dialog window > wouldn't harm. I want to see the way how to set up such an app, how the > layout is organized, how the components are wired for events and how the > input components are customized, > > Norbert > > Cheers, > > HernÃ¡n > > > 2014-12-25 13:32 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: > >> Is there a more complex example of a data entry ui in pharo? Spec would >> be ok but everything will do. >> >> thanks, >> >> Norbert >> >> >> >

Dec. 26, 2014

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

by Nicolai Hess

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. 25, 2014