yes, we forgot… I will send a note.
> On 06 May 2016, at 00:44, Ben Coman wrote:
>
> Thanks for the heads up. The past few releases had some notice when
> the changes file was being condensed.
> cheers -ben
>
> On Thu, May 5, 2016 at 9:56 PM, Bernardo Ezequiel Contreras
> wrote:
>> Ben,
>> Th
Hi,
I have updated
http://pharo.org/download
And they are of course on files.pharo.org:
http://files.pharo.org/sources/
Marcus
> On 05 May 2016, at 23:47, Alexandre Bergel wrote:
>
> Hi!
>
> It would be fantastic to have that file downloadable from the pharo.org
>
Hi,
Was with every release, we have created a new .sources file.
It is available at
http://files.pharo.org/sources/
The latest Pharo5 (50750) now uses this.
ZeroConf and the builds have been updated to include this file.
Please test and tell us if you see any problems.
(And
Hi,
Thanks!
And Pharo50.sources is also available via the ZeroConf scripts.
Cheers,
Doru
> On May 6, 2016, at 9:05 AM, Marcus Denker wrote:
>
> Hi,
>
> I have updated
> http://pharo.org/download
>
> And they are of course on files.pharo.org:
>
> http://files.pharo.org/sources
The Pharo Consortium is very happy to announce that feenk
has joined the Consortium as a Bronze Member.
About
- feenk: http://www.feenk.com
- Pharo Consortium: http://consortium.pharo.org
The goal of the Pharo Consortium is to allow companies and institutions to
support the ongoing development a
Hi,
the vmmaker image
http://files.pharo.org/vm/src/spur/vmmaker-image.zip
runs on top of Pharo 5 but with PharoV40.sources. The
wget -O- get.pharo.org/vm50
downloads PharoV50.sources and not PharoV40.sources. This means scripts
using the vmmaker-image need to be fixed to download Phar
Branch: refs/tags/50751
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: c65dec336c01105291a810b0a9f05d8392595682
https://github.com/pharo-project/pharo-core/commit/c65dec336c01105291a810b0a9f05d8392595682
Author: Jenkins Build Server
Date: 2016-05-06 (Fri, 06 May 2016
Hi,
An extra note to the announcement:
Due to the 2016 campaign for extending the reach of the consortium, the Pharo
Consortium receives from a generous external fund an extra amount corresponding
to one year fee for any new members or the difference for any upgrading members.
More details abo
Hi,
I thought that I already asked about this but apparently not...
Right now when I have an array like
observations := {
MElement -> {
#change -> #(name owner uuid).
#add -> #().
#remove -> #()
}.
MContainer -> {
#change -> #().
#add -> #(add:).
#remove -> #(remove:).
}.
}.
it gets formatted
Hi,
I use formatter all the time as I like to have uniform code. Because it's
not perfect I sometimes purposefully replace things like
{(#a -> #b).
(#c -> #d)}
with
Array with: #a -> #b with: #c -> #d
just so I have better control of the formatting...
However sometimes (especially for code in
2016-05-06 10:26 GMT+02:00 Peter Uhnák :
> Hi,
>
> I thought that I already asked about this but apparently not...
>
> Right now when I have an array like
>
> observations := {
> MElement -> {
> #change -> #(name owner uuid).
> #add -> #().
> #remove -> #()
> }.
>
> MContainer -> {
> #change -> #(
I have seen this too, and I hate it as well.
I would definitively prefer the minimal syntax: no parenthesis when not needed,
not extra $# when not needed.
> On 06 May 2016, at 10:26, Peter Uhnák wrote:
>
> Hi,
>
> I thought that I already asked about this but apparently not...
>
> Right now
>
> parent isArray ifTrue: [ ^ false ].
Wow this actually seems to work, thanks!
We could integrate it for Pharo 6.
As for the Literal Array, this appears to solve it
BlConfigurableFormatter>>visitLiteralNode: aLiteralNode
aLiteralNode value isLiteral
ifFalse: [ ^ self writeString: '' ].
aL
Hi,
is there some guide / help how to extend the GTDebugger?
I tried to take a look at SUnit/PParser but it looks quite complex…
certainly more complex than extending Inspector. :)
Thanks,
Peter
Listings can be floating (like figures) or not; I'd still recommend to
float the larger ones, especially if you want to refer to them from several
places, because for those, you need a number/caption and an entry in the
list of illustrations. Floating is more or less independent from the label
and
Hi Peter,
Yes, extending the debugger is more work than extending the inspector.
However it depends on what you want to do. Do you need to change the UI of
the debugger or just add new actions?
To create a new UI you need to subclass GTSUnitDebugger and
override debuggerStructureIn: and debuggerT
On 6 May 2016 at 10:56, Sven Van Caekenberghe wrote:
> I have seen this too, and I hate it as well.
>
> I would definitively prefer the minimal syntax: no parenthesis when not
> needed, not extra $# when not needed.
>
>> On 06 May 2016, at 10:26, Peter Uhnák wrote:
>> And second, perhaps less im
Who is in charge of the Jenkins installation for http://ci.inria.fr/dbxtalk.
I'm trying to modify certain projects and I'm getting the following error:
Error
JSONObject["scm"] is not a JSONObject.
I tried some hacks to make it work, but no luck.
Did this happen to somebody else? How to fix it?
19 matches
Mail list logo
