- Pharo-dev - lists.pharo.org

Incorrect Class Variable Highlighting?

by Sean P. DeNigris

Looks like a bug... Shall I open an issue? <http://forum.world.st/file/n4828900/Screenshot_2015-05-27_09.png> ----- Cheers, Sean -- View this message in context: http://forum.world.st/Incorrect-Class-Variable-Highlighting-tp4828900.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 27, 2015

Re: [Pharo-dev] translateBy: vs translatedBy:

by Damien Pollet

There is a discussion of such idioms in the I will present at ESUG. I only looked at the API of String, but I'm sure most naming idioms apply to any class. The question is, how do you ensure they are applied and complete? On 27 May 2015 at 01:14, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Tue, May 26, 2015 at 6:14 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> > >> On Tue, May 26, 2015 at 9:38 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> >> I vote for renaming to Rectangle>>translatedBy:, because it returns a > >> >> new > >> >> translated rectangle instance. > >> > > >> > > >> > -1 > >> > There is no benefit in renaming a single method, apart from creating > >> > more > >> > confusion. > >> > >> I wouldn't say "no benefit". Consistent conventions are beneficial. > >> It could be useful to bring these into line with the general "-ed" > >> convention of returning a new object. I don't see how this would > >> create confusion, though it might create work. Whether its worth the > >> work is a slightly different question. > >> > >> > If anything, the whole Rectangle API would have to be changed, as > there > >> > is > >> > plethora of similar methods (expandBy:, extendBy:, merge:, etc.) > >> > >> For a better feel of the work involved... > >> > >> Rectangle methods select: [ :m | m sourceCode includesSubstring: '^ > >> Rectangle ' ]. > >> Rectangle>>#intersect: > >> Rectangle>>#quickMerge: > >> Rectangle>>#encompass: > >> Rectangle>>#intersect:ifNone: > >> > >> Rectangle methods select: [ :m | m sourceCode includesSubstring: > >> '^Rectangle ' ]. > >> Rectangle>>#intersect: > >> Rectangle>>#translateBy: > >> Rectangle>>#scaleBy: > >> Rectangle>>#merge: > >> Rectangle>>#compressTo: > >> Rectangle>>#expandTo: > >> Rectangle>>#roundTo: > >> Rectangle>>#truncateTo: > >> > >> The following already follow the convention... > >> Rectangle>>#compressed > >> Rectangle>>#expanded > >> Rectangle>>#rounded > >> Rectangle>>#truncated > >> > >> > Pretty much all Rectangle messages are immutable and create new > >> > Rectangle, > >> > thus I feel it is unnecessary to state it explicitly. > >> > > >> > In VW there is plenty of methods (e.g. left:) that mutates it, thus > >> > unlike > >> > Pharo a clear distinction is required. > >> > >> Still, it is reasonable to consider the impact of inconsistent > >> conventions on the rest of the system outside of Rectangle. > >> > >> cheers -ben > >> > > > > > On Wed, May 27, 2015 at 1:16 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > That's not all, many methods return new rectangles via Point's API, > namely > > Point>>{#corner: #extent: #rectangle:} > > > > I don't know if I can perform static analysis of the code (are there > tools > > for that in Pharo?) to see which methods exactly return Rectangle > > > > rectMethods := #(#corner: #extent: #rectangle:). > > (Point methods select: [ :m | rectMethods includes: m selector ] > > thenCollect: [ :m | m senders ]) flattened select: [ :s | s className = > > #Rectangle ]. "an Array( > > Rectangle>>#areasOutside: > > Rectangle>>#withSideOrCorner:setToPoint:minExtent:limit: > > Rectangle>>#withBottom: > > Rectangle>>#bottom: > > Rectangle>>#areasOverlapingOutside: > > Rectangle>>#floor > > Rectangle>>#allAreasOutsideList:startingAt:do: > > Rectangle>>#scaledAndCenteredIn: > > Rectangle>>#squishedWithin: > > Rectangle>>#ceiling > > Rectangle>>#withHeight: > > Rectangle>>#rectanglesAt:height: > > Rectangle>>#scaleFrom:to: > > Rectangle>>#withLeft: > > Rectangle>>#left: > > Rectangle>>#withTop: > > Rectangle>>#right: > > Rectangle>>#top: > > Rectangle>>#innerCorners > > Rectangle>>#interpolateTo:at: > > Rectangle>>#withWidth: > > Rectangle>>#quickMergePoint: > > Rectangle>>#withRight: > > Rectangle>>#rotateBy:centerAt: > > Rectangle>>#withSideOrCorner:setToPoint:minExtent:limit: > > Rectangle>>#flipBy:centerAt:) > > " > > > > This list is maybe a bit excessive (sometimes it returns self, sometimes > new > > rectangle -- e.g. floor). > > > > Good Point ;) > > However the "-ed" convention doesn't make sense for many of those... > #areasdOutside: , #areasedOutside , #areaOutsided: ? > ... and #areasOutside is obviously a different rectangle than the original. > > The scope might be restricted to only those where the usual convention > makes the names misleading, for example: > #merge > > cheers -ben > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 27, 2015

Re: [Pharo-dev] OSWindow VM event creation

by stepharo

Last time when I took notes I wrote https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/Events.md but we are wondering how the VM event (not the SDL2 events) are passed to the OSWindow VM driver. but it looks that this is not done. Le 27/5/15 14:30, stepharo a Ã©crit : > Hi guys > > with alain we are looking for the place where events are created in > OSWindow. > We are looking for the the event created by the visitor on top of SDL2 > event but > for the compatible version ie the event created by the default vm. > We are looking for the place where the event created by the vm are > passed to OSWindow. > We saw that there is > OSVMDriver and friends but we could not see how the OSVM is fed > with the > default inputSensor or inputFetcherEvent of Pharo. > > Stef > >

May 27, 2015

OSWindow VM event creation

by stepharo

Hi guys with alain we are looking for the place where events are created in OSWindow. We are looking for the the event created by the visitor on top of SDL2 event but for the compatible version ie the event created by the default vm. We are looking for the place where the event created by the vm are passed to OSWindow. We saw that there is OSVMDriver and friends but we could not see how the OSVM is fed with the default inputSensor or inputFetcherEvent of Pharo. Stef

May 27, 2015

Re: [Pharo-dev] Cross platform key modifiers

by Sean P. DeNigris

SergeStinckwich wrote > how Emacs solve this keybinding issue For one thing, Emacs gives the underlying platform the finger and institutes the same set of unintelligible keybindings regardless of platform conventions ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Cross-platform-key-modifiers-tp4828113p4828893.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 27, 2015

Re: [Pharo-dev] Inconsistent number comparison?

by Sean P. DeNigris

Nicolas Cellier wrote > Also because it's good to know that 1/10 ~= 0.1 Why? It's an implementation detail. #= unlike #== is IIUC supposed to be logical to the domain, and math doesn't make any distinction about how bits are stored ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Inconsistent-number-comparison-tp4828795p4828892.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 27, 2015

Re: [Pharo-dev] Is there an official JSON parser/writer?

by Stephan Eggermont

On 26-05-15 21:37, Esteban A. Maringolo wrote: > 2015-05-26 16:15 GMT-03:00 Stephan Eggermont <stephan(a)stack.nl>: >> On 26/05/15 18:40, Esteban A. Maringolo wrote: >>> >>> I'm modifying the PostgresV2 package to support JSON datatype but >>> instead of using the JSON package from PharoExtras I'm trying to use >>> NeoJSON. > >> Is there a specific reason not to move to PostgresV3? > > I'd love to do so. But where is it? It is not in SmalltalkHub certainly. > It would also require to adapt/implement GLORP's adaptor for PostgresV3. > Or is it a plug-in replacement? > > Please provide me with pointers, now is when :) Source is http://www.squeaksource.com/PostgresV3 Some discussions http://forum.world.st/Status-of-PostgresV3-td4780110.html http://forum.world.st/Parsing-SQL-in-a-Pharo-system-td4781777.html#a4781896 http://forum.world.st/Prepared-Statements-on-PostgresV2-td4798714.html#a479… (older) http://forum.world.st/status-of-PostgresV3-package-td3600415.html Stephan

May 27, 2015

Re: [Pharo-dev] Inconsistent number comparison?

by Sean P. DeNigris

Nicolas Cellier wrote > we want to have this property a=b & (a=c) ==> (b=c). If IUC it sounds more inconsistent because (5463/20) = (10926/40) "true" ----- Cheers, Sean -- View this message in context: http://forum.world.st/Inconsistent-number-comparison-tp4828795p4828890.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 27, 2015

Re: [Pharo-dev] Inconsistent number comparison?

by Nicolas Cellier

2015-05-27 11:00 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > Because there are infinitely many fractions that are approximately equal > to 273.15 (the float). > and because we want to have this property a=b & (a=c) ==> (b=c). > > Nicolas > > Also because it's good to know that 1/10 ~= 0.1 But maybe the question is why 1=1.0 ? Because we want to have the numbers sortable... Would 1<1.0 or 1>1.0 be better? If you can't compare, then be prepared to change hierarchy (what's the sole purpose of Magnitude) and also rewrite a lot of code... Nicolas > 2015-05-27 5:00 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > >> Why does "1 = 1.0" but "273.15 ~= (5463/20)"? You must send #asFloat to >> the >> fraction to answer true... >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Inconsistent-number-comparison-tp4828795.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >

May 27, 2015

Re: [Pharo-dev] Inconsistent number comparison?

by Nicolas Cellier

Because there are infinitely many fractions that are approximately equal to 273.15 (the float). and because we want to have this property a=b & (a=c) ==> (b=c). Nicolas 2015-05-27 5:00 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Why does "1 = 1.0" but "273.15 ~= (5463/20)"? You must send #asFloat to the > fraction to answer true... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Inconsistent-number-comparison-tp4828795.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

May 27, 2015