- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] DSM in Roassal

by Alexandre Bergel

Ok, super! Let us know how it goes Alexandre On Sep 5, 2013, at 9:51 AM, Volkert Barr <volkert(a)nivoba.de> wrote: > Today i tried again with a fresh pharo 2.0 image and loaded the latest version of "Roassal" and "RoassalProposals". > > Now it works ... will now dig a bit deeper .... :-) > > Thank you, > Volkert > > On 02.09.2013, at 09:38, Volkert Barr <volkert(a)nivoba.de> wrote: > >> Dear Alexandre, >> >> which Pharo and Roassal Version? I am loading the packages in Pharo 2.0 (Summer), but the >> examples did not work (ROLabel class(Object)>>doesNotUnderstand: #verticalText). >> >> Gofer new >> squeaksource: 'Roassal'; >> package: 'ConfigurationOfRoassal'; >> load. >> (Smalltalk at: #ConfigurationOfRoassal) project lastVersion load. >> >> Gofer new >> smalltalkhubUser: 'JurajKubelka' project: 'RoassalProposals'; >> package: 'RoassalGraphBuilders'; >> load. >> (Smalltalk globals at: #RODependencyMatrixBuilderTest) browse. >> >> No, i am not at the ESUG. >> >> BW, >> Volkert >> >> >> On 01.09.2013, at 19:38, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >>> Hi Volkert, >>> >>> Yes, we started an effort on that. >>> >>> Consider: >>> >>> | view builder | >>> view := ROView new. >>> builder := RODependencyMatrixBuilder new. >>> builder model: (Array with: true with: false). >>> builder dependencyBoolean: #xor:. >>> builder gapSize: 0. >>> >>> builder on: view. >>> view open >>> >>> <Screen Shot 2013-09-01 at 12.04.56 PM.png> >>> >>> Another example: >>> | view builder objects | >>> objects := ROShape withAllSubclasses. >>> view := ROView new. >>> view @ RODraggable. >>> >>> builder := RODependencyMatrixBuilder new. >>> builder model: objects. >>> " builder noVerticalShape." >>> builder dependency: #superclass. >>> builder gapSize: 0. >>> builder on: view. >>> view open >>> <Screen Shot 2013-09-01 at 12.06.55 PM.png> >>> >>> If you are working on something similar, it would be great to join forces... >>> >>> how to load Juraj's code: >>> Gofer new >>> smalltalkhubUser: 'JurajKubelka' project: 'RoassalProposals'; >>> package: 'RoassalGraphBuilders'; >>> load. >>> (Smalltalk globals at: #RODependencyMatrixBuilderTest) browse. >>> >>> Look at the ROMatrixExample class >>> >>> Will you be at ESUG? >>> >>> Cheers, >>> Alexandre >>> >>> > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 5, 2013

Re: [Pharo-dev] [smaltalk-gsoc-students] Some news of the UIPainter project

by GastÃ³n Dall' Oglio

Hello. I try to first load on pharo 2.0 and I spend the same, then in 3.0 and ran smoothly. It might be good to clarify this in the blog :) Regards. 2013/9/5 Erwan Douaille <douailleerwan(a)gmail.com> > You have to use the latest Pharo 3.0 version: > http://files.pharo.org/image/30/latest.zip > It looks like Spec isn't loaded in your image. I didn't add any Spec > dependencies in the Configuration due than Spec is loaded by default in > Pharo 3.0 > Hope it will work :) > > > > 2013/9/5 Alexandre Bergel <alexandre.bergel(a)me.com> > >> Hi Erwan, >> >> I've tried to load your work using the configuration, but I got: >> >> This package depends on the following classes: >> TreeNodeModel >> TabModel >> WorldModel >> TabManagerModel >> You must resolve these dependencies before you will be able to load these >> definitions: >> properties >> uiPainter >> activeTab >> properties >> uiPainter >> isActive >> panelMorph >> properties >> uiPainter >> properties >> uiPainter >> >> >> Select Proceed to continue, or close this window to cancel the operation. >> >> Cheers, >> Alexandre >> >> >> On Sep 5, 2013, at 3:16 PM, Erwan Douaille <douailleerwan(a)gmail.com> >> wrote: >> >> > Hi, >> > >> > The GSoC deadlines is 16 september. It means than i have one week to >> fix bugs and implements some new features. The best way to find bugs is >> user feedbacks. >> > >> > I will be glad to fix many bugs than you will find. (many bugs found in >> 5 minutes with my mentor ...) >> > >> > Here is instructions to load UIPainter : >> > >> > Gofer new >> > smalltalkhubUser: 'ErwanDouaille' project: 'UIPainter'; >> > configurationOf: 'UIPainter'; >> > load. >> > ConfigurationOfUIPainter load >> > >> > >> > Here is my blog: http://uipainter-gsoc.over-blog.com >> > >> > Thanks for testing, feedbacks and ideas :) >> > >> > -- >> > Best regards, >> > >> > Douaille Erwan <douaille.erwan(a)gmail.com> >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Smalltalk GSoC students" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to smalltalk-gsoc-students+unsubscribe(a)googlegroups.com. >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com> >

Sept. 5, 2013

Re: [Pharo-dev] [smaltalk-gsoc-students] Some news of the UIPainter project

by Erwan Douaille

You have to use the latest Pharo 3.0 version: http://files.pharo.org/image/30/latest.zip It looks like Spec isn't loaded in your image. I didn't add any Spec dependencies in the Configuration due than Spec is loaded by default in Pharo 3.0 Hope it will work :) 2013/9/5 Alexandre Bergel <alexandre.bergel(a)me.com> > Hi Erwan, > > I've tried to load your work using the configuration, but I got: > > This package depends on the following classes: > TreeNodeModel > TabModel > WorldModel > TabManagerModel > You must resolve these dependencies before you will be able to load these > definitions: > properties > uiPainter > activeTab > properties > uiPainter > isActive > panelMorph > properties > uiPainter > properties > uiPainter > > > Select Proceed to continue, or close this window to cancel the operation. > > Cheers, > Alexandre > > > On Sep 5, 2013, at 3:16 PM, Erwan Douaille <douailleerwan(a)gmail.com> > wrote: > > > Hi, > > > > The GSoC deadlines is 16 september. It means than i have one week to fix > bugs and implements some new features. The best way to find bugs is user > feedbacks. > > > > I will be glad to fix many bugs than you will find. (many bugs found in > 5 minutes with my mentor ...) > > > > Here is instructions to load UIPainter : > > > > Gofer new > > smalltalkhubUser: 'ErwanDouaille' project: 'UIPainter'; > > configurationOf: 'UIPainter'; > > load. > > ConfigurationOfUIPainter load > > > > > > Here is my blog: http://uipainter-gsoc.over-blog.com > > > > Thanks for testing, feedbacks and ideas :) > > > > -- > > Best regards, > > > > Douaille Erwan <douaille.erwan(a)gmail.com> > > > > -- > > You received this message because you are subscribed to the Google > Groups "Smalltalk GSoC students" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to smalltalk-gsoc-students+unsubscribe(a)googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

Sept. 5, 2013

Re: [Pharo-dev] [smaltalk-gsoc-students] Some news of the UIPainter project

by Alexandre Bergel

Hi Erwan, I've tried to load your work using the configuration, but I got: This package depends on the following classes: TreeNodeModel TabModel WorldModel TabManagerModel You must resolve these dependencies before you will be able to load these definitions: properties uiPainter activeTab properties uiPainter isActive panelMorph properties uiPainter properties uiPainter Select Proceed to continue, or close this window to cancel the operation. Cheers, Alexandre On Sep 5, 2013, at 3:16 PM, Erwan Douaille <douailleerwan(a)gmail.com> wrote: > Hi, > > The GSoC deadlines is 16 september. It means than i have one week to fix bugs and implements some new features. The best way to find bugs is user feedbacks. > > I will be glad to fix many bugs than you will find. (many bugs found in 5 minutes with my mentor ...) > > Here is instructions to load UIPainter : > > Gofer new > smalltalkhubUser: 'ErwanDouaille' project: 'UIPainter'; > configurationOf: 'UIPainter'; > load. > ConfigurationOfUIPainter load > > > Here is my blog: http://uipainter-gsoc.over-blog.com > > Thanks for testing, feedbacks and ideas :) > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com> > > -- > You received this message because you are subscribed to the Google Groups "Smalltalk GSoC students" group. > To unsubscribe from this group and stop receiving emails from it, send an email to smalltalk-gsoc-students+unsubscribe(a)googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 5, 2013

Re: [Pharo-dev] [smaltalk-gsoc-students] Some news of the UIPainter project

by StÃ©phane Ducasse

thanks erwan It is nice to see that you are making progress. Stef On Sep 5, 2013, at 9:16 PM, Erwan Douaille <douailleerwan(a)gmail.com> wrote: > Hi, > > The GSoC deadlines is 16 september. It means than i have one week to fix bugs and implements some new features. The best way to find bugs is user feedbacks. > > I will be glad to fix many bugs than you will find. (many bugs found in 5 minutes with my mentor ...) > > Here is instructions to load UIPainter : > > Gofer new > smalltalkhubUser: 'ErwanDouaille' project: 'UIPainter'; > configurationOf: 'UIPainter'; > load. > ConfigurationOfUIPainter load > > > Here is my blog: http://uipainter-gsoc.over-blog.com > > Thanks for testing, feedbacks and ideas :) > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com> > > -- > You received this message because you are subscribed to the Google Groups "Smalltalk GSoC students" group. > To unsubscribe from this group and stop receiving emails from it, send an email to smalltalk-gsoc-students+unsubscribe(a)googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out.

Sept. 5, 2013

Re: [Pharo-dev] NeoJSONCustomMapping>>#mapWithValueSchema:

by StÃ©phane Ducasse

great! tx >> sven can you add it to the readme so that when I turn it into a pier chapter we get it :) > > https://github.com/svenvc/docs/blob/master/neo/neo-json-paper.md has been updated > >>> Using the newly added NeoJSONCustomMapping>>#mapWithValueSchema: this is now possible, as the following unit test shows: >>> >>> testDictionaryOfObject2 >>> | data json reader | >>> data := Dictionary new. >>> data >>> at: #one put: NeoJSONTestObject2 example1; >>> at: #two put: NeoJSONTestObject2 example1. >>> json := NeoJSONWriter toString: data. >>> reader := NeoJSONReader on: json readStream. >>> reader for: #DictionaryOfObject2 customDo: [ :mapping | >>> mapping mapWithValueSchema: NeoJSONTestObject2 ]. >>> self >>> assert: (reader nextAs: #DictionaryOfObject2) >>> equals: data >>> >>> Note that the mapping mechanism in NeoJSON is optional. Without mapping you get Arrays and Dictionaries back, that you can then convert to your domain objects in the a next step. With mapping however, these intermediary representations are not used and maps or lists are parsed while creating and populating your domain objects directly, which should be more efficient. This does of course introduce the necessity of adding some form of static typing. >> > >

Sept. 5, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by StÃ©phane Ducasse

>>>> >>> >>> >>> I am also checking the platform subtype implementation (OSProcess platformSubtype). >>> >>> In Pharo: >>> >>> Smalltalk os subtype ==> 'i686' >>> >>> This reflects the processor type, not the os subtype (it should be 'x86_64' on my PC). >>> >>> Is this intentional? >>> >> I don't think so. >> >> Marcus >> > > Thanks Goubier and Marcus, > > I made the updates to OSProcess and CommandShell to handle system version and subtype > in Pharo 3.0. Excellent. > I did not yet update ConfigurationOfOSProcess or ConfigurationOfCommandShell, but the > latest versions for Squeak/Pharo are in OSProcess-dtl.83 and CommandShell-dtl.73 in > the SqueakSource repositories. If you need help let me know. Stef

Sept. 5, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by StÃ©phane Ducasse

>>>> >>>> > > No. Just admit that you have productions 1.4 (and maybe 1.3) hanging around, that 2.0 is the main development platform for Pharo users, 3.0 is where you make interesting stuff. Yes we admit it and then? We are concerned to help people. Did you run the rules generated from 1.4-2.0 activity because we are creating to help people migrating. We are fthinking about having better support to automatically migrate code based on changes (but for that we need manpower). > And that Pharo users are at least one version behind you, and that they would like a bit of smoothness in the way it evolves... 3.0 gives directions; but a bit of backport to help with the transition would be, what, just friendly to your users. This is what we are doing. > For example, for things I am aware of: > - backport ensureDelete to 2.0 > - backport the replacement of Keymapping on:do: Open bug entries and propose some code. > You have 2.0 users who have things to say and who are able to correct things as well; don't belittle them by saying "All software development should be done on 3.0" [Camillo Bruni]. Give us any ideas how to help you and we will. This is why I propose to even undeprecate certain key features if it helps providing more stability from the users side. I understand that not everybody is working in 3.0. Stef > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 5, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by StÃ©phane Ducasse

>>> >> >> Who says that? We always said that we will back-port all imported fixes to 2.0. We will not back-port *everything*, especially >> not improvements that are not fixes, because then there would be no difference between Pharo3 and Pharo2 (and these >> tend to introduce new problems, making it very hard to stabilize). > > Are you afraid that by improving Pharo2 on a production-level, you would remove incentives to move to pharo3? No just that we do not want to stop 3.0. Because changing 20 will introduce bug we are 100% convinced about that. The system is still not in a situation where changes are simple and with limited impact. >> But it is clear that this is a fine line: one persons fix is the others persons bug, so we tend to be conservative. >> But nevertheless, all show-stopping bugs should be fixed. > > I'm OK with that. It's just that I'm updating a fix for a bug on both Pharo2 and Pharo3 by myself just to be able to open a file browser and get correct file permissions. > > I'm also unable to be sympathetic to a situation where I have two versions of a code just because when deprecating ensureDeleted in 3.0, nobody thought usefull to backport ensureDelete so that we could ensure that code using ensureDelete could work on both versions. This is simple nobody told us. Open an issue and tag it 20 + code and it will be in the batch of 2.0. > >> In general: It is *a lot* of work, and it is hard to get right in all cases. But considering that: do we really do that badly? > > I can undestand that. I'm not sure :) Because I regularly figure out that **I** do NOT understand how exactly it is difficult and demanding energy to produce something good. > I also understand that you need 3.0 to be declared unstable to be able to make the necessary improvements in it. > > But this has the following consequences for non-core development, say SmaCC for example: 2.0 is the platform for unstable, No it is not 2.0 is stable. We have production code with it. Now it is not bug free and 1.4 is far from bug free. It is just that you do not get touched by these bugs. > 1.4 is where your stuff is stable (2.0 if you're lucky), and 3.0 is don't develop until it has reached a sufficient level of maturity. > I will do things on SmaCC in the near future, but not on 3.0. this is a mistake to me. Because if you discover bugs we will fix them. Now if you wait one year to move to 3.0 we will be working on 4.0 and the story will never ends. Stef > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 5, 2013

Re: [Pharo-dev] [About Documentation] Teach, Don't Tell / Steve Losh

by StÃ©phane Ducasse

On Sep 5, 2013, at 10:25 AM, kilon <thekilon(a)yahoo.co.uk> wrote: > A big thank you from me as well , PBE definetly made possible to use Pharo. > If I had to read pharo code to understand how to work I would be right back > with python by now. thanks. > Pharo can learn tons of things from the success of python , I am very glad > to see that you guys put big priority on Documentation as python does. > Youtube also has loads of squeak and pharo video tutorials. So thing > actually are much better than I initially feared. > > The problems is that smaltlalkers tend to overestimate smalltalk and not > document their code. They believe too much into "self documented" nonesense > and this article hits the nail on the head concerning this problem. AFAIK > the best way to code is by writting documentation at the same time. Unless > you are the type of coder that tends to rewrite his library 10 times before > releasing, which I seriously doubt. Python has been a huge success as a > language because developer take documentation extremely seriously. Yes I would love that Pharoers have the same spirit. > I have not forget about documenting nativeboost, I will try to write a small > article on my blog about nativeboost and the things I learned which may help > you use it as part of the nativeboost documentation. If you have any request > dont forget to ping me. We want the blog :) And also your feedback on the nativeBoost chapter. > > > > -- > View this message in context: http://forum.world.st/About-Documentation-Teach-Don-t-Tell-Steve-Losh-tp470… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Sept. 5, 2013