- Pharo-users - lists.pharo.org

Re: [Pharo-users] iceberg and private github repos

by Esteban Lorenzano

I guess is about credentials: you have the right user/pass, you will not have problemsâ¦ but thatâs just an âI guessâ :) (remember: iceberg just works with https security right nowâ¦ due current limitations on libgit2, not our fault :P) Esteban > On 19 Dec 2016, at 09:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I have to work with a private GitHub repo. Is there a way to tell Iceberg to load from such a private repo? > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "We cannot reach the flow of things unless we let go." > > > > >

Dec. 19, 2016

iceberg and private github repos

by Tudor Girba

Hi, I have to work with a private GitHub repo. Is there a way to tell Iceberg to load from such a private repo? Cheers, Doru -- www.tudorgirba.com www.feenk.com "We cannot reach the flow of things unless we let go."

Dec. 19, 2016

DNU on materializing a fueled out exception

by Holger Freyther

Hi, I showed Pharo to a friend and wanted to show the nice feature of fueling out an exception and then using FLMaterializer class>>#materializeFromFileNamed: to load it back and get a debugger up. In Pharo5 I am presented a DNU instead. The DNU is on GTGenericStackDebugger as it doesn't understand the message Fuel is sending. What to fix, Fuel to use the new protocol or GTGenericStackDebugger to honor the old protocol? FueldOutStackDebugAction>>#serializeTestFailureContext: aContext toFileNamed: aFilename | serializer | serializer := FLSerializer newDefault. self encodeDebugInformationOn: serializer. serializer addPostMaterializationAction: [ :materialization | Smalltalk tools debugger openOn: Processor activeProcess context: materialization root label: 'External stack' contents: nil fullView: false ]. So it looks like now it should create a debug session first and then pass it to the debugger? I think loading new fuel in Pharo3.x is still possible so maybe it is best to re-add that protocol? comments? holger

Dec. 19, 2016

Re: [Pharo-users] Hash collision

by Martin McClure

On 12/18/2016 02:29 AM, Andres Valloud wrote: > The primitive and the primitive failure code should behave the same? You think the primitive is faulty? I haven't looked at the primitive code, but it just fails when given a Float. From the name, I'd guess that it's designed for a byte object. The failure code certainly is. A new primitive designed for word objects, or new code such as I gave earlier (though ugly) would work, though. Regards, -Martin

Dec. 19, 2016

Re: [Pharo-users] Protego - smart way to manage NIL's in business calculations

by Ben Coman

On Mon, Dec 19, 2016 at 2:43 AM, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> wrote: > Sorry, I'm not sure I fully understand your idea. > It looks like trying to make another implementation of UndefinedObject, is > it? Just that. But it contains only business logic. I'm inclined to say both are the Null Object Pattern, but I'm not sure if concept truly applies to the system nil. https://www.tutorialspoint.com/design_pattern/null_object_pattern.htm https://www.cs.oberlin.edu/~jwalker/nullObjPattern/ > > What is the main difference between proposed MissingValue and > UndefinedObject? > It's just UndefinedObject is "too system" to intervene? Or something else? It could be nil for many reasons. Perhaps an initialization was missed. Mainly MissingValue avoids cluttering nil with custom logic. When looking via the Inspector or Debugger, a MissingValue provides a better indication of the status than a regular nil. Now you may want to avoid creating a new instance for each missing value. Perhaps the methods could have been added to the class side of MissingValue. Or use a singleton instance in the initialization. But I'm not sure of the pros/cons of each approach. Now I'm not saying MissingValue is the best way to go. Smalltalk does have the advantage of being able to add behaviour to nil and that might be sufficient for you. Just providing an additional way to think about it. cheers -ben > > > 2016-12-18 18:12 GMT+03:00 Ben Coman <btc(a)openinworld.com>: >> >> Thanks for sharing. A similar thing might be useful for dealing with >> "quality" of Process Variable measurement in industrial situations - >> where instruments fail from time to time. >> >> I'm not sure of all the pros and cons, but btw an alternative to >> hanging special behaviour on a method, would be to hang special >> behaviour on a MissingValue class that you could #initialize any >> instance variable to. >> >> Object subclass: #MissingValue >> instanceVariableNames: '' >> classVariableNames: '' >> package: 'AAAA' >> >> MissingValue >> * dummyValue >> self inform: 'debug trace - got here'. >> ^self >> >> MissingValue >> adaptToNumber: rcvr andSend: selector >> ^self perform: selector with: rcvr >> >> Collection >> sumProtected >> ^ self >> inject: 0 >> into: [ :sum :each | sum + each value] >> >> Usage... >> >> c := {1.1 * MissingValue new. 1.2 * 10. MissingValue new * 1.3. 10 * >> 1.4}. >> "==> an Array(aMissingValue 12.0 aMissingValue 14.0)" >> >> c sumExcludeMissing >> "==> 26.0" >> >> cheers -ben >> >> On Sun, Dec 18, 2016 at 6:45 PM, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> >> wrote: >> > Imagine, you have some object with amount and price variables. >> > And you want to calculate total, put this totals to collection and >> > calculate >> > grand total. >> > >> > Naive implementation will be something like >> > total := amount * price for the first task >> > and something like >> > grandTotal := totals sum for the latter one. >> > >> > But what if amount or price are nil's? >> > You can add nil checks, of course: total := (amount ifNil:[0]) * (price >> > ifNil: [0]). >> > And then what if totals will be empty? More checks. >> > Is it really wise to have total to be zero if amount is nil? More >> > ifTrue:ifFalse: code. >> > And then you want to add amount := total / price calculation, and you >> > realize that both total and price may be nil, and price may be zero. >> > More and more and more checks. >> > >> > Protego (http://www.smalltalkhub.com/#!/~assargadon/Protego) adds >> > "protected" versions of common operators and methods. >> > >> > So, you just put >> > total := amount *@ price >> > and >> > grandTotal := totals sum_protected >> > into your code - and everything just works. >> > >> > total will be nil if any of the operands are nil. grandTotal will be >> > calculated normally, even for empty totals collection (will return nil >> > for >> > empty collection). >> > Collection can hold nil's and it will work anyway. If all elements of >> > the >> > collection is nil, result will be nil. >> > >> > Protected version of addition and subtraction will treat nil's as zeros >> > until both operands are nil - then it will return nil. >> > There are protected versions of comparisions, too. >> > >> > It's quite simple idea, which is still very useful, and it makes code >> > much >> > more readable, clean and self-commenting. >> > >> > That's why I have extracted this part of SmallPOS framework, and have >> > published it as separate package to use it in other, non-SmallPOS >> > applications. >> >

Dec. 19, 2016

whisper/porcini in Java

by Robert Withers

Voix-basse-mourde is whisper and herkutatti is porcini. I have the Java PBE working bit identical to Squeak, but the DBL_AESede protocol is not yet installing. Then the encoders for asn1der and json need implementation and Squeak and Java will work together again. find the code here, after logging in: https://gitlab.com/des-lapins-internationale best, Rabbit

Dec. 18, 2016

Re: [Pharo-users] Modeling a join table

by Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾

Are you going to use relational database to store this data? Or you goint to use image saving / object-oriented DB for persistence? Than, can you please describe your task / domain model with more details? Particularly: 1) Are there strong asymmetry in queries? Which kind of queries are more frequent: "give me tags of this radio" or "give me radios with this tag"? 2) Do you need to store other information EXCEPT fact that that radio is marked by this tag? For example, do you need to store the time tag was assigned to the station or the user who have assigned it? You got the idea, I believe. 3) Are queries simple "stations with tag X" / "tags of station X", or they may often looks like "stations with tag A or B, but not both" or something even more complicated. Best approach is strongly depends on the answers. "By default", however, I will make Station with collection of Tags as the "main information storage". And I will make some kind of "request" when asked about list of station with some tag. Cache this result, if needed for performance. But if you plan to use relational persistence backend, than collections on the either side will be the good idea. And you can use GLORP quite easy for this. 2016-12-13 23:59 GMT+03:00 sergio ruiz <sergio.rrd(a)gmail.com>: > Hello, all. > > This question is not as much a question about smalltalk as one about > modeling in smalltalk. > > I am currently writing an API using Teapot that will be serving up data > about internet radio stations. I want to be able to let users tag the > stations with arbitrary tags. Using a relational database, I would create > an object like "Tagging" with foreign keys pointing to the "Stations" class > and the "Tag" Class. It would have station_id and tag_id. > > If this was going to be even a tiny bit more complex, I would probably > just make it a polymorphic association. > > My question is, how would I approach this in smalltalk? Would I just make > methods on tag and station (and whatever else) that stored arrays of each > other? Would I create an intermediary model like "Tagging" and have that do > the heavy lifting? > > Ideas? Thanks!; > > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.Village-Buzz.com > http://www.ThoseOptimizeGuys.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 >

Dec. 18, 2016

Re: [Pharo-users] Protego - smart way to manage NIL's in business calculations

by Denis Kudriashov

2016-12-18 20:19 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> What is the main difference between proposed MissingValue and >> UndefinedObject? > > > MissingValue you will set up according to your business logic. While nil > is just default value of variable which could be in your object by some > incident, bug of application. And it makes impossible to distinguish bug from normal application state related to missing value

Dec. 18, 2016

Re: [Pharo-users] Protego - smart way to manage NIL's in business calculations

by Denis Kudriashov

2016-12-18 19:43 GMT+01:00 Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com>: > Sorry, I'm not sure I fully understand your idea. > It looks like trying to make another implementation of UndefinedObject, is > it? > > What is the main difference between proposed MissingValue and > UndefinedObject? MissingValue you will set up according to your business logic. While nil is just default value of variable which could be in your object by some incident, bug of application.

Dec. 18, 2016

Re: [Pharo-users] Protego - smart way to manage NIL's in business calculations

by Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾

Sorry, I'm not sure I fully understand your idea. It looks like trying to make another implementation of UndefinedObject, is it? What is the main difference between proposed MissingValue and UndefinedObject? It's just UndefinedObject is "too system" to intervene? Or something else? 2016-12-18 18:12 GMT+03:00 Ben Coman <btc(a)openinworld.com>: > Thanks for sharing. A similar thing might be useful for dealing with > "quality" of Process Variable measurement in industrial situations - > where instruments fail from time to time. > > I'm not sure of all the pros and cons, but btw an alternative to > hanging special behaviour on a method, would be to hang special > behaviour on a MissingValue class that you could #initialize any > instance variable to. > > Object subclass: #MissingValue > instanceVariableNames: '' > classVariableNames: '' > package: 'AAAA' > > MissingValue >> * dummyValue > self inform: 'debug trace - got here'. > ^self > > MissingValue >> adaptToNumber: rcvr andSend: selector > ^self perform: selector with: rcvr > > Collection >> sumProtected > ^ self > inject: 0 > into: [ :sum :each | sum + each value] > > Usage... > > c := {1.1 * MissingValue new. 1.2 * 10. MissingValue new * 1.3. 10 * > 1.4}. > "==> an Array(aMissingValue 12.0 aMissingValue 14.0)" > > c sumExcludeMissing > "==> 26.0" > > cheers -ben > > On Sun, Dec 18, 2016 at 6:45 PM, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> > wrote: > > Imagine, you have some object with amount and price variables. > > And you want to calculate total, put this totals to collection and > calculate > > grand total. > > > > Naive implementation will be something like > > total := amount * price for the first task > > and something like > > grandTotal := totals sum for the latter one. > > > > But what if amount or price are nil's? > > You can add nil checks, of course: total := (amount ifNil:[0]) * (price > > ifNil: [0]). > > And then what if totals will be empty? More checks. > > Is it really wise to have total to be zero if amount is nil? More > > ifTrue:ifFalse: code. > > And then you want to add amount := total / price calculation, and you > > realize that both total and price may be nil, and price may be zero. > > More and more and more checks. > > > > Protego (http://www.smalltalkhub.com/#!/~assargadon/Protego) adds > > "protected" versions of common operators and methods. > > > > So, you just put > > total := amount *@ price > > and > > grandTotal := totals sum_protected > > into your code - and everything just works. > > > > total will be nil if any of the operands are nil. grandTotal will be > > calculated normally, even for empty totals collection (will return nil > for > > empty collection). > > Collection can hold nil's and it will work anyway. If all elements of the > > collection is nil, result will be nil. > > > > Protected version of addition and subtraction will treat nil's as zeros > > until both operands are nil - then it will return nil. > > There are protected versions of comparisions, too. > > > > It's quite simple idea, which is still very useful, and it makes code > much > > more readable, clean and self-commenting. > > > > That's why I have extracted this part of SmallPOS framework, and have > > published it as separate package to use it in other, non-SmallPOS > > applications. > >

Dec. 18, 2016