- Pharo-dev - lists.pharo.org

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

by Alain Plantec

> 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: ---- 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. Cheers Alain > > 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

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

by stepharo

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

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

by Ben Coman

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? 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. "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

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

by Sven Van Caekenberghe

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

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

by Hilaire

Wonderful! Thanks Le 24/12/2014 15:19, Alain Plantec a Ã©crit : > Hello all, > > Iâve just uploaded a small demo of Bloc. > http://vimeo.com/115336678 > > > Cheers > Alain > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Dec. 24, 2014

Re: [Pharo-dev] Hash questions

by Max Leske

Are you sure that your hash is stable (e.g. none of the objects are ever nil)? If the hash changes, the hash table might âlooseâ entries. > On 24 Dec 2014, at 12:13, Dario Trussardi <dario.trussardi(a)tiscali.it> wrote: > > Ciao, > > I wrok into Pharo Pharo1.4 Latest update: #14445 > > I have a strange behavior relative to hash and = methods into one class. > > Sometimes when i do the code aBag occurrencesOf: anItem the system answer 0 but into the bag there's the relative anItem instance. > > The problem is generated when in the anItem class definitions method, > > i do reference to a instance variable ( consumer ) setting to a Symbol. > > The hash method is: > > hash > > ^item hash > bitXor:( opzioniVoce hash > bitXor:( referenceTime hash > bitXor:( consumer hash > bitXor:( newEntry hash )))) > > > The = method is: > > = anItem > > | rslPrz | > anItem ifNil:[^false]. > > self class = anItem class ifFalse:[ ^false]. > > rslPrz:= ( item = anItem item > and:[ opzioniVoce = anItem opzioniVoce > and:[ referenceTime = anItem referenceTime > and:[ consumer = anItem consumer > and:[ newEntry = anItem newEntry ]]]]). > > ^ rslPrz > > > If i remove the consumer instance reference in the two methods all work fine. > > any ideas about it ? > > Thanks, > > Dario > > > >

Dec. 24, 2014

Re: [Pharo-dev] Old inspector and explorer

by Norbert Hartl

> Am 23.12.2014 um 22:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > The Raw view is a tree :) > It looks like shallow tree :) Maybe I miss the point but my appearance to this is something like that. Let's have a class Object subclass: #TTT instanceVariableNames: 'col' classVariableNames: '' category: 'ZZZ' and TTT>>#initialize col := OrderedCollection new addAll: (1 to: 10); yourself If I inspect "TTT new" I get With the intention to examine the elements of the collection I unfold (1) the col So instead of the elements I get the internal representation of OrderedCollection. Clicking array (2) I get a new column with the representation of array (same as on the left side). And here Clement is right because it would be helpful to see the elements in the right column. By clicking the "10 items" tab (3) and then an element (4) I can see the content of that. So what I wanted to say is that I found it a lot of clicks necessary to get the information I want. I see it is a raw view and from that POV everything seems right. Coming from the old tools it is not a point of getting used to it or not. This raw view is not an improvement over the old it is a completely different view. As Ben sad it might good to think about providing a view compatible with the old explorer view (fast drill down). Having that view be a default could be left to the user as it could be a setting. Does that makes sense? Norbert P.S.: Are the miller columns configurable. I want to play with amount of columns. Until now I preferred three columns if space is available. Any pointers to that would be great. > Doru > > On Tue, Dec 23, 2014 at 10:44 PM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: > Sven Van Caekenberghe wrote: > On 23 Dec 2014, at 19:13, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: > > Hi, > > What does a basic inspector mean for you? It's not a rhetorical question. I am actually interested in what you miss. > > What took you so long, Doru ? Haha ;-) > > Seriously, I think that the 'Raw' tab of GT-Inspector actually covers the key old inspector *and* inspector behaviour quite well. I guess that was/is also the design goal. > > The rest is mostly a reaction to something new and unfamiliar. GT takes some getting used to. > > But we need concrete use cases that give people trouble to be able to improve. > > I miss the Tree View - being able to drill down in a _compact_ way. Could that be a tab of its own? I actually think this "might" have great potential - being able to navigate in both a vertical and horizontal direction - allowing you to skip some levels between opening a new pane horizontally. > > cheers -ben > > > > Doru > > On Tue, Dec 23, 2014 at 6:06 PM, ClÃ©ment Bera <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>> wrote: > Yes. > > World Menu >> Settings >> Glamourous toolkit > then you can uncheck GTInspector and GTPlayground. > > I also need to do that very often as GTInspector does not have a basic inspector. > > 2014-12-23 11:50 GMT+01:00 Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>>: > 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 <http://www.tudorgirba.com/> > > "Every thing has its own flow" > > > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

Dec. 24, 2014

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

by Alexandre Bergel

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

[Ann] a short Bloc demo

by Alain Plantec

Hello all, Iâve just uploaded a small demo of Bloc. http://vimeo.com/115336678 <http://vimeo.com/115336678> Cheers Alain

Dec. 24, 2014

Re: [Pharo-dev] [Pharo-users] [ann] moose 5.0

by Tudor Girba

Hi Giorgio, Thanks for the kind words. Cheers, Doru On Wed, Dec 24, 2014 at 1:20 AM, giorgio ferraris < giorgio.ferraris(a)gmail.com> wrote: > Hi, Guys, > > I'm not (yet) working on Pharo (still VW and some VisualSmalltalk in the > few time left free from my main job), but I follow what you do (not just > you but all the community) and I have to admit you (all) work really hard. > Bergel is doing a fantastic job, and your Moose is very nice, etc. > But, I really liked the presentation of the GT stuff, I can understand the > energy you put behind your work. > > Great work. I'm happy you are on the ST community and working on the > language (ST) i like the most. Thanks! > (Oh, I know you don't like to have Pharo called Smalltalk, but I don't > like religion's wars, so that is yet smalltalk, for me). > > BTW: Happy Holidays to all. > > Giorgio > > On Wed, Dec 24, 2014 at 12:09 AM, Tudor Girba <tudor(a)tudorgirba.com> > wrote: > >> We are happy to announce Moose 5.0: >> *http://moosetechnology.org/#install* >> >> >> Description >> --- >> >> This is by far the most extensive Moose release to date. Just take a look >> at these two trailers. >> - Spotter: https://vimeo.com/113832673 >> - Inspector: https://vimeo.com/103463364 >> >> The key highlights are: >> - It is based on Pharo 3.0. >> - Roassal2 is a complete reimplementation of the core visual engine of >> Moose. >> - Roassal2 replaced Roassal, EyeSee and Graph-ET, and it features many >> new things including smooth animations, new composeable builders and >> several new layouts. >> - All built-in Moose visualizations use Roassal2. >> - Glamour has been extended with a Pager browser and with Rubric as the >> main text editor. >> - GTSpotter is a new tool that makes it possible to find objects fast. >> - GTInspector saw major usability improvements based on the Pager >> browser, and it now comes with many object specific extensions. >> - GTPlayground provides a new way to handle scripts and when combined >> with GTInspector, it can replace the dedicated easels and editors. >> - Moose Finder has been extended with the ability of handling in place >> visualizations. >> - GTDebugger has been strengthen and was made more robust. >> - PetitParser has been extended with the notion of context which enables >> elegant island parsing. >> >> A list of issues addressed in this release can be found at: >> >> http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… >> >> >> Installation >> --- >> >> The Moose Suite 5.0 comes for each platform as a separate bundle: >> - *Moose Suite 5.0 for Mac>http://moosetechnology.org/res/download/ >> moose_suite_5_0-mac.zip >> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-mac.zip> >> * >> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-mac.zip*> >> - *Moose Suite 5.0 for Windows>http://moosetechnology.org/res/download/ >> moose_suite_5_0-win.zip >> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-win.zip> >> * >> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-win.zip*> >> - *Moose Suite 5.0 for Linux>http://moosetechnology.org/res/download/ >> moose_suite_5_0-linux.zip >> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-linux.zip> >> * >> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-linux.zi…> >> >> The Moose Suite 5.0 can also be loaded in a Pharo 3.0 image either from >> the Configuration Browser, or by executing the following script: >> >> ==Gofer new >> == smalltalkhubUser: 'Moose' project: 'Moose'; >> == configuration; >> == loadStable >> >> >> Happy holidays! >> The Moose team >> > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 24, 2014