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

[ OT ] Je suis Charlie
by Sven Van Caekenberghe Jan. 8, 2015

Jan. 8, 2015

I am shocked by yesterday's events in Paris. http://en.wikipedia.org/wiki/Charlie_Hebdo_shooting Freedom of speech, including satire, is a fundamental right. I am sure that LibertÃ©, Ã©galitÃ©, fraternitÃ© will prevail. The way we work together in our little community, building and supporting free & open source software as a way to contribute to society, with diverse people from all over the world respecting each other, is one example of what humans can do. I am proud of that. Sven

4 3

FogBugsz issue assignment
by MartinW Jan. 8, 2015

Jan. 8, 2015

Whenever I reply to an issue or resolve an issue, everybody gets automatically removed from "assigned to this issue" and I am set as the only one the issue is assigned to. Is this intended? I just entered a new bug (https://pharo.fogbugz.com/f/cases/14679/Fix-layout-glitch-in-FileDialogWind…) then it is assigned to everybody. After i resolved it as "fix review needed" it gets automatically only assigned to me. But exactly now it should be assigned to everybody, so that someone can review it? Or do i misunderstand the mechanism? The same thing happens automatically, when i reply to an issue. Best regards, Martin. -- View this message in context: http://forum.world.st/FogBugsz-issue-assignment-tp4798024.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 2

Pharo CI down?
by Max Leske Jan. 8, 2015

Jan. 8, 2015

ci.inria.fr/pharo seems to be down...

2 2

Pharo{2,3} problems with seaside3.1
by David Carlos Manuelda Jan. 8, 2015

Jan. 8, 2015

Currently, there are issues with latest stable seaside and pharo, which have been talked before but seems not getting much attention, and some of them are important, so I want to do a little summary here. First of all, I have to say that I am new on smalltalk, pharo and seaside, and started by reading Pharo by example, Deep into Pharo and Seaside tutorial by Hasso Plattner Institut. Other issue, that is specially important because it confuses new users (like me) is that there are things which only works with pharo3 and not with pharo2, and other, that do work with pharo2 but not in pharo3, which is confusing, because the one click experience tarball comes with pharo2, so I try to enumerate them here: ** Halos, and code editing: - Pharo2: OK, working normally - Pharo3: DANGEROUS, partially not working, and when it works it makes you lose code, I explain: x There are times in which you simply get the error: MessageNotUnderstood: receiver of "generateWithSource" is nil and you can't edit code x When you don't get the above error, then you can edit code but when trying to save, I detected 2 possible bad behaviors: - Save appears to work, but when you actually browse the code you changed via browser in pharo, you see your whole method's code is replaced by self methodHasNoSourceCode, in this case you lost your original code - Save not working, and debugger is raised, telling you: Unknown variable (the method name you just edited), for example, in my case I edited via browser the initialize method, and I got Unknown variable initialize. ** Seaside Control Panel: - Pharo3: OK, no errors - Pharo2: Not working: x Menu entry is missing x If you invoke it manually or you just use the one that is raised when you open firstly the one click experience image: * Right click not showing anything (in pharo3 right click displays add adapter and that kind of options) * Selecting an adapter and clicking "Browse" give you: Not understood message WAServerAdapterToolbar>>owner * Start/Stop options also shows above message not understood error Summary: Again, I am not an expert, and some of these issues are not important enough, because seaside continues to work, but in my honest opinion, that incongruity of functionality between versions 2 and 3, do not make much sense, and make user to chose between comodity (seaside control panel) and functionality (halos). Any opinions to this? Thanks for taking your time to read :) David.

3 2

64-bit Pharo
by horrido Jan. 8, 2015

Jan. 8, 2015

I understand that Pharo is currently 32-bit. I was wondering whether this was a significant impediment to Smalltalk adoption, esp. in the enterprise. I'm always hearing developers wanting 64-bits in their applications. -- View this message in context: http://forum.world.st/64-bit-Pharo-tp4797744.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 2

Dark side of variables
by Roberto Minelli Jan. 8, 2015

Jan. 8, 2015

Hi guys, Can anyone please quickly explain to me the difference between (1) an instance variable defined on the class side and (2) a class variable defined on the instance side? Thanks a lot! Cheers, Roberto

4 5

Are there lazy quantifiers in Pharo's Regex implementation ?
by Paul DeBruicker Jan. 8, 2015

Jan. 8, 2015

I can see and use the "{1,3}" quantifiers but are there lazy quantifiers too? e.g. http://msdn.microsoft.com/en-us/library/3206d374(v=vs.110).aspx It seems like the "?" is parsed as a lookahead or as an optional element. Attempting to use it as a lazy quantifier gives an error.

1 0

Jan. 8, 2015

Hello, As some of you may know, Pharo is being enhanced with support for multiple bytecode sets. This will allow to run at the same time compiled methods with 2 different bytecode sets for experimentation and to add easily the new bytecode set described in this ESUG paper <http://esug.org/data/ESUG2014/IWST/Papers/iwst2014_A%20bytecode%20set%20for…> . The virtual machine knows which bytecode set the compiled method uses for its encoding based on the sign of its header. This means that on the contrary to right now, a compiled method *can* have a negative header. The issue is that typically operations such as #bitAnd: or #+ to access bits of the smallinteger does not work the same way on negative integers (2 complement's implementation of integers), resulting in incorrect values. I am fixing the problematic cases in Pharo. One case is in Fuel and I can't fix it myself. It's in: FLCompiledMethodCluster>>#serializeInstance: aCompiledMethodToSerialize with: anEncoder "some code" header := aCompiledMethod header. "some code" anEncoder *encodeUint32*: header "some code" This looks problematic because now header is not a uint anymore but a sint. In addition, #encodeUint32: uses #bitAnd: which may work differently on negative integers. What do you fuel experts think ? Is there anything to fix there ? Best, Clement

3 6

SmalltalkHub bugs & hangs :-(
by Noury Bouraqadi Jan. 7, 2015

Jan. 7, 2015

SmalltalkHub is slow, so donât click too fast :-( While Iâm grateful to developers of SmalltalkHub and previously SqueakSource, I believe as a small community, we cannot afford developing everything by ourselves. We donât have enough man-power. We can see the symptoms since SmalltalkHub is in beta stage since way too long... Itâs better to use some mainstream platform such as github. Weâll we have support for it in Pharo 4? It would be interesting also from the communication point of view to make the world a little bit more aware of Pharo. Noury

23 46

[ANN] WKHTML2PDF for Pharo
by Torsten Bergmann Jan. 7, 2015

Jan. 7, 2015

Need an easy way to convert HTML into PDF for printing? The project http://wkhtmltopdf.org can help you here. If you want to use it from Pharo just check out: http://smalltalkhub.com/#!/~TorstenBergmann/WKHTML2PDF This project allows you to easily use the library. First select the engine: HTML2PDFConverter useExecutable. or HTML2PDFConverter useLibrary. and then convert: HTML2PDFConverter convert: 'http://www.pharo.org' toFile: 'pharo.pdf' to get a printable version of the Pharo homepage. As ever docu is on the STHub project website. It uses NativeBoost to call the library and OSProcess to call the executable. Bye T.

4 4