February 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ||

by stepharo

Le 6/2/15 19:15, Thierry Goubier a Ã©crit : > The good old finder has a pragmas search mode which allows for a bit > of discoverability (pragma users), but it doesn't link to the code > exploiting the pragmas. > > Do you know if we have something specific on SmartSuggestions for pragmas? point taken. Indeed it would would be nice. Stef

Feb. 6, 2015

Re: [Pharo-dev] Howto create a new configuration?

by Juraj Kubelka

I have changed two methods of the configuration: -=-=- stable: spec <symbolicVersion: #stable> spec for: #'pharo2.x' version: '2.1'. "after some modification in NB made it incompatible with 3.0" spec for: #'pharo3.x' version: '2.3'. spec for: #'pharo4.x' version: '2.7â. â<<== added, maybe instead of pharo4.x could be common" -=-=- development: spec <symbolicVersion: #'development'> spec for: #'common' version: '2.3-baselineâ. â<<== it is likely not necessary" -=-=- I have changed it, because I think there should be two lines in Versioner: one with development label, second with stable label. Then everything works. Let me know if it helps. Juraj > 6. 2. 2015 v 17:28, Nicolai Hess <nicolaihess(a)web.de>: > > 2015-02-06 1:40 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)gmail.com <mailto:juraj.kubelka@gmail.com>>: > Well, then I cannot see packages that are not included in the version 2.7. Can you mention some? I will try to make a new version. > > I want to include the latest versions of > Athens-Cairo: Athens-Cairo-NicolaiHess.82 > and > Athens-Text: Athens-Text-NicolaiHess.16 > > The other packages hasn't change since version 2.7 > > > nicolai > > > > Juraj > >> 5. 2. 2015 v 20:07, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>>: >> >> >> 2015-02-05 23:06 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)gmail.com <mailto:juraj.kubelka@gmail.com>>: >> I have downloaded the latest Pharo 4 and it looks like Esteban Lorenzano did the job. There is a new 2.7 version. >> >> No, the version 2.7 is not new, I have some changes that came after that version. >> >> >> Cheers, >> Juraj >> >>> 5. 2. 2015 v 18:28, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>>: >>> >>> 2015-02-05 21:56 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)gmail.com <mailto:juraj.kubelka@gmail.com>>: >>> I am just guessing: try to click on âdevelopmentâ item on the left side. >>> >>> >>> -> "Information: Nothing to save" >>> >>> Already tried :) >>> >>> >>> Cheers, >>> Juraj >>> >>> > 5. 2. 2015 v 17:13, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>>: >>> > >>> > Hello, >>> > >>> > I fixed some issues for Athens and upload the changes to the >>> > repository. Now, I want to use Versionner to create a new configuration. >>> > What I tried: >>> > >>> > Open a fresh image >>> > Open the Athens repository and load the new changesets >>> > -> There are some merge conflicts. Why? There shouldn't be >>> > any conflicts. How do you do this? >>> > >>> > After merging the changes I open Versionner. >>> > I thought I have to make a new Release but the button "Release Version" is >>> > disabled. >>> > What did I miss? >>> > >>> > >>> > >>> > nicolai >>> >>> >> >> > >

Feb. 6, 2015

Re: [Pharo-dev] ||

by stepharo

Really interesting discussion. I like pragmas but this is interesting to see them challenged. > Yes, but there end up being lots of naming conventions and they are > non-obvious. Whereas pragmas, because they are in-your-face in the > methods in question, don't need conventions. They just need > documenting ;-). Thierry I'm skeptical that multiple protocol will save the problem because you will rely on coding conventions. And pragma is a clever tagging. Stef

Feb. 6, 2015

Re: [Pharo-dev] ||

by stepharo

Le 5/2/15 22:47, Eliot Miranda a Ã©crit : > Yes, but that's because of historical accident and the difficulty of > keeping docs up to date. Perhaps Pharo By Example can fix this? Yes we should. My writing todo is a bit huge :)

Feb. 6, 2015

Re: [Pharo-dev] SmallInteger asByteArray for negative numbers

by stepharo

I would have like to know when I wrote the chapter in deepinto pharo about 2 complement... Stef >> (These kinds of questions should be asked on pharo-users(a)lists.pharo.org) >> >> You can only represent positive numbers as ByteArrays, because to represent negative numbers you have to decide how to do that. The most common solution is to use 2-complement. To do this you also need to decide on the number of bytes to use. >> >> Here is an example using 4 bytes: >> >> | integer size mask | >> integer := -123. >> size := 4. >> mask := (2 raisedTo: size * 8) - 1. >> (mask bitAnd: ((integer abs bitXor: mask) + 1)) >> asByteArrayOfSize: 4. >> >> => #[255 255 255 133] >> >> => FF FF FF 85 >> >> The reverse is: >> >> | integer size mask | >> integer := #[255 255 255 133] asInteger. >> size := 4. >> mask := (2 raisedTo: size * 8) - 1. >> (mask bitAnd: ((integer abs bitXor: mask) + 1)) >> negated >> >> This is for negative numbers. >> >> Positive numbers need not be 2-complemented. >> >> When decoding, integers < (2 raisedTo: (size * 8) - 1) are negative. >> >> HTH, >> >> Sven >> >> >> >> >> I was going to complain about expecting such niceties as a built in 2s-complement rather than program it myself (I am a bit rusty on such matters), but when I look what should I find? >> >> (-123 asTwosComplement: 16rFFFFFFFF) asByteArray. "=> #[255 255 255 133]" >> >> cheers -ben > That is nice indeed, I didn't that existed. Very handy. > > I don't like that there are no tests ;-) > > > >

Feb. 6, 2015

Re: [Pharo-dev] Switching to Pharo from Visualworks

by stepharo

Le 6/2/15 16:31, Sven Van Caekenberghe a Ã©crit : > Yes, but that is not really provided as a #catalog* method, is it ? > > There is #catalogDescription, but that is some lines of text. > > There should be something like #catalogLabel for a sjort one-line title style label. if configuration would be filled up we could take advantage of them. The flybyhelp when hovering over a package is displaying the description of project (when there is one) since two years. Stef > >> On 06 Feb 2015, at 16:26, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> there should be both: a name and a category >> >> Seaside - Web framework >> Zinc - HTTP server >> etc. >> >> Esteban >> >>> On 06 Feb 2015, at 16:16, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> Yes, we need to improve that. Names are nice, but they make it harder to explore the system. >>> >>>> On 06 Feb 2015, at 12:43, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>>> >>>> Markus Fritsche-4 wrote >>>>> +1 to that one. >>>> Yes, I also find it difficult - much more so when I was new to the >>>> community, but even still a bit now. Coral, Zinc, Seaside, Opal - may be >>>> catchy, but when I'm browsing the system, I just want to see where the darn >>>> WebClient is, not mine for minerals or go to the beach!! ;) j/k. But >>>> seriously, it's one thing to have "sexy" names at the top level - Pharo, >>>> Squeak, Ruby, Python; but inside the system, it definitely creates >>>> confusion. It's perhaps extra difficult for us because some of these >>>> projects have both an outside and inside identity. It's an interesting open >>>> problem... maybe some metadata at the MetaC/package level could help? Like >>>> some standard tags like #WebClient, #Compiler, etc to say logically what >>>> role a project fills... >>>> >>>> >>>> >>>> ----- >>>> Cheers, >>>> Sean >>>> -- >>>> View this message in context: http://forum.world.st/Switching-to-Pharo-from-Visualworks-tp4803811p4804142… >>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>>> >>> >> > >

Feb. 6, 2015

Re: [Pharo-dev] Howto create a new configuration?

by Nicolai Hess

2015-02-06 1:40 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)gmail.com>: > Well, then I cannot see packages that are not included in the version 2.7. > Can you mention some? I will try to make a new version. > I want to include the latest versions of Athens-Cairo: Athens-Cairo-NicolaiHess.82 and Athens-Text: Athens-Text-NicolaiHess.16 The other packages hasn't change since version 2.7 nicolai > > Juraj > > 5. 2. 2015 v 20:07, Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-02-05 23:06 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)gmail.com>: > >> I have downloaded the latest Pharo 4 and it looks like Esteban Lorenzano >> did the job. There is a new 2.7 version. >> > > No, the version 2.7 is not new, I have some changes that came after that > version. > > >> >> Cheers, >> Juraj >> >> 5. 2. 2015 v 18:28, Nicolai Hess <nicolaihess(a)web.de>: >> >> 2015-02-05 21:56 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)gmail.com>: >> >>> I am just guessing: try to click on âdevelopmentâ item on the left side. >>> >> >> >> -> "Information: Nothing to save" >> >> Already tried :) >> >> >>> >>> Cheers, >>> Juraj >>> >>> > 5. 2. 2015 v 17:13, Nicolai Hess <nicolaihess(a)web.de>: >>> > >>> > Hello, >>> > >>> > I fixed some issues for Athens and upload the changes to the >>> > repository. Now, I want to use Versionner to create a new >>> configuration. >>> > What I tried: >>> > >>> > Open a fresh image >>> > Open the Athens repository and load the new changesets >>> > -> There are some merge conflicts. Why? There shouldn't be >>> > any conflicts. How do you do this? >>> > >>> > After merging the changes I open Versionner. >>> > I thought I have to make a new Release but the button "Release >>> Version" is >>> > disabled. >>> > What did I miss? >>> > >>> > >>> > >>> > nicolai >>> >>> >> >> > >

Feb. 6, 2015

Re: [Pharo-dev] development workflow for GTools (GToolkitCore)

by stepharo

> Would it be possible/desirable to have a system such that: > * bug fixes for external packages can be still be directly applied and > tested in the Pharo-integrated branch > * the CI workflow generates an updated ConfigurationOf{external > package} that it pushes back to the external package repository? Yes this is the process I had in mind but this is not that simple because the configuration of the external package may also have changed and a merge should be done in the external package. > Its a great idea to separate out Configurations to devolve > responsibility for sub-packages, but it adds some friction to bug fixing. Yes I always thought about it. > It "seems" we will have a single branch combining both feature > development and bug-fixing, but it would be nicer to have two branches. > > --------------- > On another track, I wonder if it would be useful if a package which is > part of a Configuration is made dirty, the Configuration itself could > also be marked dirty? > > cheers -ben > > > > On Fri, Feb 6, 2015 at 4:36 AM, Nicolai Hess <nicolaihess(a)web.de > <mailto:nicolaihess@web.de>> wrote: > > 14850 <https://pharo.fogbugz.com/default.asp?14850> Integrate > GTools #development > "From this version onwards the development version should be > integrated." > > Is this a good idea? Does the #development version always include > *all* the latest > changes, because after Andrei opened > 14866 <https://pharo.fogbugz.com/default.asp?14866> Integrate > GTools (which got integrated in 40475) > I uploaded some changes for issue > 14608 <https://pharo.fogbugz.com/default.asp?14608> > ClassTest>>#testClassRespectsPolymorphismWithTrait failing due to > Spotter methods > I set the status to "Fix Review needed", > > but my changes are integrated in 40475 too! > > I am not satisfied with the way external packages are handled. > 1. if there is not one slice/changeset per issue, it is even less > likely someone will > review the changes. > 2. you don't know who works when on a issue. They are solved in a > bulk. > 3. a new configuration might not only includes bugfixes but new > features as well. > 4. often we have unbound globals / undeclared references or other > test failures. > > Can we use the build server for those external projects (like > GToolkitCore, Athens, TxText), > and that if a project makes a new configuration, it uses the same > issue validator for loading and testing that configuration? > > > nicolai > > >

Feb. 6, 2015

Re: [Pharo-dev] Switching to Pharo from Visualworks

by Andreas Wacknitz

Am 06.02.15 12:43, schrieb Sean P. DeNigris: > Markus Fritsche-4 wrote >> +1 to that one. > Yes, I also find it difficult - much more so when I was new to the > community, but even still a bit now. Coral, Zinc, Seaside, Opal - may be > catchy, but when I'm browsing the system, I just want to see where the darn > WebClient is, not mine for minerals or go to the beach!! ;) j/k. But +1 The names of these frameworks are nice as long as they are outside the image. Inside the image the focus should be on functionality (at least as long as the frameworks are unique). For somebody new to Pharo this is quite irritating. Andreas > seriously, it's one thing to have "sexy" names at the top level - Pharo, > Squeak, Ruby, Python; but inside the system, it definitely creates > confusion. It's perhaps extra difficult for us because some of these > projects have both an outside and inside identity. It's an interesting open > problem... maybe some metadata at the MetaC/package level could help? Like > some standard tags like #WebClient, #Compiler, etc to say logically what > role a project fills... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Switching-to-Pharo-from-Visualworks-tp4803811p4804142… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Feb. 6, 2015

Re: [Pharo-dev] SmallInteger asByteArray for negative numbers

by Sven Van Caekenberghe

> On 06 Feb 2015, at 18:03, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On Fri, Feb 6, 2015 at 10:48 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Alejandro, > > > On 06 Feb 2015, at 15:10, Alejandro Infante <alejandroinfante91(a)gmail.com> wrote: > > > > Hello, > > I have just found that calling asByteArray for any negative small integer returns the same result that the positive small integer. Is it supposed to be like that or is it a bug? > > > > 1 asByteArray = -1 asByteArray. "true" > > > > (1 to: 100000) allSatisfy: [ :int | int asByteArray = int negated asByteArray ] âtrue" > > > > Cheers, > > Alejandro > > (These kinds of questions should be asked on pharo-users(a)lists.pharo.org) > > You can only represent positive numbers as ByteArrays, because to represent negative numbers you have to decide how to do that. The most common solution is to use 2-complement. To do this you also need to decide on the number of bytes to use. > > Here is an example using 4 bytes: > > | integer size mask | > integer := -123. > size := 4. > mask := (2 raisedTo: size * 8) - 1. > (mask bitAnd: ((integer abs bitXor: mask) + 1)) > asByteArrayOfSize: 4. > > => #[255 255 255 133] > > => FF FF FF 85 > > The reverse is: > > | integer size mask | > integer := #[255 255 255 133] asInteger. > size := 4. > mask := (2 raisedTo: size * 8) - 1. > (mask bitAnd: ((integer abs bitXor: mask) + 1)) > negated > > This is for negative numbers. > > Positive numbers need not be 2-complemented. > > When decoding, integers < (2 raisedTo: (size * 8) - 1) are negative. > > HTH, > > Sven > > > > > I was going to complain about expecting such niceties as a built in 2s-complement rather than program it myself (I am a bit rusty on such matters), but when I look what should I find? > > (-123 asTwosComplement: 16rFFFFFFFF) asByteArray. "=> #[255 255 255 133]" > > cheers -ben That is nice indeed, I didn't that existed. Very handy. I don't like that there are no tests ;-)

Feb. 6, 2015