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

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Benjamin

I do not want that end users to get expose to >> git on the command-line with different platforms. We should keep the simplicity of Pharo. >> Having an integration process based on git will expose only core-developpers ton git :) Not the end-users ;) Ben

Jan. 7, 2014

Re: [Pharo-dev] Athens SVG Import

by Igor Stasenko

On 6 January 2014 19:31, J.F. Rick <self(a)je77.com> wrote: > This message is mainly for Igor, who probably already curses every time he > sees my name on the development list. But, perhaps others have had some > experience with this as well. > > Quite opposite. You using Athens abd helping to polish it. What could be better? > I'm still working on moving my touch applications to Athens. I am running > into a major problem with icons. My applications tend to have quite a few > icons in them. In the old BitBlt versions, I just used forms for the icons. > That same approach fails with Athens as form rendering is time consuming. > With just ten medium-sized forms open in my AthensWrapMorph, the system > starts to crawl. My guess is that form rendering needs to be sped up before > Athens can be widely adopted. Using the form as a paint, while flexible, > seems pretty intense. > > Right. Converting Form(s) to paint(s) is memory intensive operation. Basically, it copies contents of the form to newly created surface. To avoid this, use caching. Here is an example from ImageMorph: drawOnAthensCanvas: aCanvas | cached | cached := aCanvas cacheAt: image ifAbsentPut: [ image asAthensPaintOn: aCanvas. ]. aCanvas setPaint: cached. aCanvas paintTransform restoreAfter: [ aCanvas paintTransform translateBy: self innerBounds origin "negated". aCanvas drawShape: self innerBounds. ]. without caching, rendering morphic desktop was very slow, since all icons is forms. Anyway, for most of my applications, switching over to vector-based > graphics would be a better choice as it would allow for me to more easily > scale to different screen sizes. So, I was excited to try the SVG import. > Now that the XMLParser is working, I am running into some problems with the > SVG import code. It seems that it doesn't support some of the features that > an SVG export from Illustrator produces. I was wondering if I could get > some help there. > > First, Illustrator tends to spit out SVGs that use #reflectedCubicBezier > curves, which is not yet implemented. > > Second, I found a small bug in ASPathConverter>>readPoint The "self > skipBlanks" has to be changed to "self skipBlanksAndComma" or multiple > points cannot be read in sequence. > > Can you submit the fix, please? Let me know if you need commit rights . > Third, while ASPathConverter supports vLineTo: and hLineTo:, > AthensCairoPathBuilder does not. I tried implementing these myself but they > apparently don't work the way I thought they should. > should be straightforward: vLineTo: number ^ self lineTo: (absolute ifTrue: [ endPoint x@number ] ifFalse: [ 0@number ]) hLineTo: number ^ self lineTo: (absolute ifTrue: [ number@endPoint y ] ifFalse: [ number@0 ]) > > Here are two examples of the kind of SVG files I would like to read: > button-swapShapes.svg<http://home.cc.gatech.edu/je77/uploads/1/button-swapShapes.svg> - > This one fails because of vLineTo: and hLineTo: > button-erase.svg<http://home.cc.gatech.edu/je77/uploads/1/button-erase.svg> - > This one fails because of reflectedCubicBezier curves. > > You mean this one?: *S/s * (shorthand/smooth CurveTo) x2,y2 x, y Draw a cubic Beizer curve from the current point to (x,y). The first control point is assumed to be the reflection of the second control point (x2, y2) on the previous command relative to the current point. Yes. Not supported. Yet :) But it should be quite easy to implement. Jochen, i need help with completing SVG importer. So, if you can help, please do. Can you tell me what is your login name on smalltalkhub, so i will add you to http://smalltalkhub.com/#!/~Pharo/Athens committers?

Jan. 7, 2014

Re: [Pharo-dev] Spotlight Demo

by Esteban Lorenzano

Iâm experimenting with separate the widget from the skinâ¦ problem is sometimes theming is just change colors, but some others is widget building it self, so we will need widget factories (for theme), etc. all is doable, but all implies time :) On 07 Jan 2014, at 11:07, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >> >> I think this is too convoluted because, like Estaban says, you want to keep the theming orthogonal with widget definition. > > Yes I do not like it either. > >> But, you gave me an idea: >> >> If we implement in Morph the followings: >> >> Morph>>themer >> ^ themer ifNil: [self themerFor: self theme] > > what would be self theme I do not really like the idea to have all the morph talking to UITheme > theme > ^ UITheme current > is not sexy to me > >> Morph>>themerFor: aTheme >> ^ self subclassResponsibility >> >> And then in a morph we would have something like this: >> >> SpotlightItemMorph>>themerFor: aTheme >> ^ aTheme spotterThemer >> >> SpotlightItemMorph>>onSelected >> self themer configureSelectedItemMorph: self >> >> >> Then we could simply do pretty much what you want: >> >> SpotlightItemMorph new themer: MySpotterThemer new. >> >> I like this idea. What do you think? > > I do not know. Now what is clear is that we need strategy as in your original design. I was thinking about that too. > > Stef >

Jan. 7, 2014

Re: [Pharo-dev] [Pharo-users] Two videos to explain what we do when integrating a fix.

by StÃ©phane Ducasse

> Thanks, Stef, I will have a look in the coming days. > Now I wonât have many excuses not to try ;-) except a slow network :) I will add one of these days a rollback behavior because from home I get regular problems to be point I will simply stop even trying anymore. Stef

Jan. 7, 2014

Re: [Pharo-dev] fixing the search in the MC browser would be sooooo cool

by StÃ©phane Ducasse

Sometimes I type Morphic to see all the packages of morphic and I do not get them at all just Polymorph after if I type Polymorph I do not see Polymorph same with ScriptLoader Sometimes I have to look by hand in the right pane + plus click on it then filter on the left pane So this is totally bogus to me. Stef > Hi Stef, > > what is the problem exactly? It seems to work as expected. > > Thierry > > Le 07/01/2014 09:53, StÃ©phane Ducasse a Ã©crit : >> Hi guys >> >> if you want to help, the search (left) in the mCBrowser (once we do Open) is totally broken. >> It is a pain to look for packages when we have to check things. >> There is a bug entry (I od not remember its number). >> Stef >> >> > > -- > 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 >

Jan. 7, 2014

Re: [Pharo-dev] Spotlight Demo

by StÃ©phane Ducasse

> > I think this is too convoluted because, like Estaban says, you want to keep the theming orthogonal with widget definition. Yes I do not like it either. > But, you gave me an idea: > > If we implement in Morph the followings: > > Morph>>themer > ^ themer ifNil: [self themerFor: self theme] what would be self theme I do not really like the idea to have all the morph talking to UITheme theme ^ UITheme current is not sexy to me > Morph>>themerFor: aTheme > ^ self subclassResponsibility > > And then in a morph we would have something like this: > > SpotlightItemMorph>>themerFor: aTheme > ^ aTheme spotterThemer > > SpotlightItemMorph>>onSelected > self themer configureSelectedItemMorph: self > > > Then we could simply do pretty much what you want: > > SpotlightItemMorph new themer: MySpotterThemer new. > > I like this idea. What do you think? I do not know. Now what is clear is that we need strategy as in your original design. I was thinking about that too. Stef

Jan. 7, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Sven Van Caekenberghe

Thanks, Stef, I will have a look in the coming days. Now I wonât have many excuses not to try ;-) On 06 Jan 2014, at 16:18, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I produced two videos to show how simple is an integration now (It could be better see below). > This can influence some of you to help us: sven, ben, igor :)? > > First one: install some scripts > http://stephane.ducasse.free.fr/Videos/PharoIntegration/DownloadingScripts.… > > Second one > http://stephane.ducasse.free.fr/Videos/PharoIntegration/integratingAChange.… > > ./prepare > start menu > merge 9look at the fixâ¦.) > freeze menu > publish menu > ./publish > > I do not think that Monticello is the best tool for managing our changes and code (and I asked money in the past to get an engineer but it was refused and I spent the holiday building a new case to ask money to pay an engineer to > get a real integration with Git) but for now this is what we have and it is working. I do not want that end users to get expose to > git on the command-line with different platforms. We should keep the simplicity of Pharo. > > Stef > >

Jan. 7, 2014

Re: [Pharo-dev] fixing the search in the MC browser would be sooooo cool

by Goubier Thierry

Hi Stef, what is the problem exactly? It seems to work as expected. Thierry Le 07/01/2014 09:53, StÃ©phane Ducasse a Ã©crit : > Hi guys > > if you want to help, the search (left) in the mCBrowser (once we do Open) is totally broken. > It is a pain to look for packages when we have to check things. > There is a bug entry (I od not remember its number). > Stef > > -- 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

Jan. 7, 2014

Re: [Pharo-dev] Spotlight Demo

by Tudor Girba

Ok. I am renaming it and will publish it in PharoExtras. Doru On Tue, Jan 7, 2014 at 9:59 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > for me, thatâs the new spotlight, and should replace the old one (in Pharo > 4)â¦ so +1 for âSpotlight2â :) > > On 07 Jan 2014, at 04:32, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > Tudor Girba-2 wrote > >> First, would it be Ok with you to move the project to a more public > place > > > > Great, whereever you think... > > > > > > Tudor Girba-2 wrote > >> Second, I created a configuration with a development and stable version. > > > > Cool, thanks :) > > > > > > Tudor Girba-2 wrote > >> Please note that I named the configuration Spotter, > >> because there already exists a ConfigurationOfSpotlight for the widget > of > >> Esteban. Would it be Ok to change the name of the classes, too, to avoid > >> confusion? > > > > I would prefer ConfigurationOfNewSpotlight or ConfigurationOfSpotlight2. > > Spotlight is what we are modeling, and introducing a new term will I > think > > generate more confusion (i.e. "what the heck is a Spotter" vs. "oh, cool, > > just like the Mac Spotlight that I already use"). > > > > > > Tudor Girba-2 wrote > >> Third, I think we should not mix the morph with the global shortcut. I > >> understand this is convenient, but these should pretty much be different > >> projects. Is that Ok with you? > > > > I guess as a compromise I can just extract the shortcut into another > > package, so the default will not integrate with the system, and loading > the > > additional package will. For me, I want this widget to come up on shift + > > cr. > > > > > > Tudor Girba-2 wrote > >> Fourth, I would like to theme this morph, too :). With this occasion, I > >> would like to try a slightly different design for handling the theme > code. > > > > This is exciting. I found Polymorph / Themes to be very confusing. I > welcome > > another look at this. > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Spotlight-Demo-tp4733076p4734781.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 7, 2014

Re: [Pharo-dev] Spotlight Demo

by Esteban Lorenzano

for me, thatâs the new spotlight, and should replace the old one (in Pharo 4)â¦ so +1 for âSpotlight2â :) On 07 Jan 2014, at 04:32, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote >> First, would it be Ok with you to move the project to a more public place > > Great, whereever you think... > > > Tudor Girba-2 wrote >> Second, I created a configuration with a development and stable version. > > Cool, thanks :) > > > Tudor Girba-2 wrote >> Please note that I named the configuration Spotter, >> because there already exists a ConfigurationOfSpotlight for the widget of >> Esteban. Would it be Ok to change the name of the classes, too, to avoid >> confusion? > > I would prefer ConfigurationOfNewSpotlight or ConfigurationOfSpotlight2. > Spotlight is what we are modeling, and introducing a new term will I think > generate more confusion (i.e. "what the heck is a Spotter" vs. "oh, cool, > just like the Mac Spotlight that I already use"). > > > Tudor Girba-2 wrote >> Third, I think we should not mix the morph with the global shortcut. I >> understand this is convenient, but these should pretty much be different >> projects. Is that Ok with you? > > I guess as a compromise I can just extract the shortcut into another > package, so the default will not integrate with the system, and loading the > additional package will. For me, I want this widget to come up on shift + > cr. > > > Tudor Girba-2 wrote >> Fourth, I would like to theme this morph, too :). With this occasion, I >> would like to try a slightly different design for handling the theme code. > > This is exciting. I found Polymorph / Themes to be very confusing. I welcome > another look at this. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Spotlight-Demo-tp4733076p4734781.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Jan. 7, 2014