On 13 Dec 2013, at 08:38, Sven Van Caekenberghe wrote:
>>
>> On 13 Dec 2013, at 05:32, Hernán Morales Durand
>> wrote:
>>
>>> If not, how do I know if a SLICE depends on other SLICEs?
>>>
>>> For example loading
>>> https://pharo.fogbugz.com/f/cases/edit/11282/Removal-DependentFields-refer
On 13 Dec 2013, at 08:19, Yuriy Tymchuk wrote:
> As far as I know all mcz(s) are self contained. But slices for me are still a
> big magic, so maybe there is something different.
Any mcz can have required packages, dependencies that need to be loaded with
it, outside its own contents.
A slic
On 12 Dec 2013, at 20:22, Frank Shearar wrote:
> On 12 December 2013 19:04, Eliot Miranda wrote:
>>
>>
>>
>> On Thu, Dec 12, 2013 at 7:03 AM, Marcus Denker
>> wrote:
>>>
>>>
>>> On 12 Dec 2013, at 15:44, Benjamin
>>> wrote:
>>>
I just discovered that in Pharo 3 you can do:
>>
As far as I know all mcz(s) are self contained. But slices for me are still a
big magic, so maybe there is something different.
Uko
On 13 Dec 2013, at 05:32, Hernán Morales Durand
wrote:
> If not, how do I know if a SLICE depends on other SLICEs?
>
> For example loading
> https://pharo.fog
If not, how do I know if a SLICE depends on other SLICEs?
For example loading
https://pharo.fogbugz.com/f/cases/edit/11282/Removal-DependentFields-references
using Monticello hangs the image and cannot interrupt with Alt+. Do I
need to load another SLICE before?
Cheers,
Hernán
On 12 December 2013 19:04, Eliot Miranda wrote:
>
>
>
> On Thu, Dec 12, 2013 at 7:03 AM, Marcus Denker
> wrote:
>>
>>
>> On 12 Dec 2013, at 15:44, Benjamin
>> wrote:
>>
>> > I just discovered that in Pharo 3 you can do:
>> >
>> > [ :bool |
>> > self logCr: bool.
>> > bool := false.
>
I'm now adding it for OpenDBX and glorp. We should create lint rules for it
;)
On Thu, Dec 12, 2013 at 10:57 AM, Stéphane Ducasse <
stephane.duca...@inria.fr> wrote:
> Yes :)
> In the output of the catalog itself
>
>
> https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/?
On Thu, Dec 12, 2013 at 7:03 AM, Marcus Denker wrote:
>
> On 12 Dec 2013, at 15:44, Benjamin
> wrote:
>
> > I just discovered that in Pharo 3 you can do:
> >
> > [ :bool |
> > self logCr: bool.
> > bool := false.
> > self logCr: bool.
> > ] value: true
> >
> > Is this a bu
On Thu, Dec 12, 2013 at 10:21 AM, Chris Cunningham
wrote:
> If it is a compatibility layer, then now that Pharo has it's own #package,
> shouldn't the Pharo version of Grease just not include it anymore? Once
> the various Smalltalks start to implement what it is claiming it wants, the
> compatib
If it is a compatibility layer, then now that Pharo has it's own #package,
shouldn't the Pharo version of Grease just not include it anymore? Once
the various Smalltalks start to implement what it is claiming it wants, the
compatibility layer for that dialect should change, I would think. So,
Sea
Doru wrote:
>This is clearly an issue of Grease. And it is not essential either as there
>are no senders to it.
There are senders in Seaside. They look not so difficult to change.
>So, I see no reason not to rename it in Grease.
It is a compatibility layer, so you wouldn't be able to know look
Stef wrote:
> Doru wrote:
>> We need to reconsider how we approach continuous integration for
>> pharo-based images.
>can you expand ?
The most important thing, from my POV, is to not break things silently when
cleaning up
the system. Having a system integration test that tells you you are no
Thanks for the pointers.
I'll look at Seaside/Moose/Mondrian and Roassal, because I need code I can load
and save in an image without destroying the very image I use to test (which
would happen if I load Pharo10 stuff in a 3.0 image ;) ).
Thierry
De : Pharo-de
Yes.
"AthensTutorial open"
meets DNU,
something related to spec.. I have no idea why it stopped working, but this
is related to changes in Spec.
On 12 December 2013 15:22, Stéphane Ducasse wrote:
>
>
>
--
Best regards,
Igor Stasenko.
And yes, we miss this data on Smalltalkhub. But I have some suggestions as
always :). Will reveal them next week.
Uko
On 12 Dec 2013, at 16:20, Yuriy Tymchuk wrote:
> Pharo10 on SmalltalkHub is humongous. You can definitely do a stress test
> with it :)
>
> Uko
>
> On 12 Dec 2013, at 15:43,
So if you want something big and with a lot of commits you can use Pharo* in
general. Pharo10 has the most versions and Pharo30Inbox is the largest one. If
you want some other projects then you heve to take a look at Seaside30,
Mondrian, Moose, Glamour or Roassal.
Uko
On 12 Dec 2013, at 16:20,
Pharo10 on SmalltalkHub is humongous. You can definitely do a stress test with
it :)
Uko
On 12 Dec 2013, at 15:43, GOUBIER Thierry wrote:
> I would need a large project, composed of one or more packages, with more
> than 150~200 classes, which triggers the slow read and writing times
> Sebas
On 12 Dec 2013, at 15:44, Benjamin wrote:
> I just discovered that in Pharo 3 you can do:
>
> [ :bool |
> self logCr: bool.
> bool := false.
> self logCr: bool.
> ] value: true
>
> Is this a bug or a feature ?
https://pharo.fogbugz.com/f/cases/12419/block-arguments-s
On 12 Dec 2013, at 15:53, Nicolas Petton wrote:
> Looks like a bug to me :)
>
Yes, the argument should not be writable…
> Nico
>
> Benjamin writes:
>
>> I just discovered that in Pharo 3 you can do:
>>
>> [ :bool |
>> self logCr: bool.
>> bool := false.
>> self logCr: bool
Looks like a bug to me :)
Nico
Benjamin writes:
> I just discovered that in Pharo 3 you can do:
>
> [ :bool |
> self logCr: bool.
> bool := false.
> self logCr: bool.
> ] value: true
>
> Is this a bug or a feature ?
>
> I am fighting with this every day in javascript, a
On 12 December 2013 14:44, Benjamin
wrote:
> I just discovered that in Pharo 3 you can do:
>
> [ :bool |
> self logCr: bool.
> bool := false.
> self logCr: bool.
> ] value: true
>
> Is this a bug or a feature ?
That's not a shadow, from what I can see? It is an
assign-to-a-block-argument, which I
I just discovered that in Pharo 3 you can do:
[ :bool |
self logCr: bool.
bool := false.
self logCr: bool.
] value: true
Is this a bug or a feature ?
I am fighting with this every day in javascript, and I do not know about to
feel about this :s
Ben
I would need a large project, composed of one or more packages, with more than
150~200 classes, which triggers the slow read and writing times Sebastian
experience. And, probably, to be complete, a long and complex commit history in
git (> 100 commits).
I'll keep in mind the idea of creating on
Are you interested in a package or a project? I can provide you information
based on size, etc…
Uko
On 12 Dec 2013, at 15:30, GOUBIER Thierry wrote:
> I gave up running gitfiletree on 1.4 :(
>
> It's possible to use gitfiletree from a 2.0 or a 3.0 image to browse your git
> repository, but t
I gave up running gitfiletree on 1.4 :(
It's possible to use gitfiletree from a 2.0 or a 3.0 image to browse your git
repository, but testing the writing will be an issue.
My best chance would be to find a large enough package I can use on 2.0 or 3.0
to test and profile. Does anybody has a larg
Doing this removes redundant code, still not a solution:
waitForConnectionFor: timeout ifTimedOut: timeoutBlock
"Wait up until the given deadline for a connection to be established.
Return true if it is established by the deadline, false if not."
^ self waitForConnectionUntil: (s
Max Leske wrote:
#setHaltOnce is implemented on Object. Evaluate this in a workspace:
self setHaltOnce.
-> same effect
Cheers,
Max
Yes :)
But each time I must::
* Search for the correct workspace among several open workspaces, as
well as lots of other windows for Finder, Browser, Deb
#setHaltOnce is implemented on Object. Evaluate this in a workspace:
self setHaltOnce.
-> same effect
Cheers,
Max
On 12.12.2013, at 13:06, b...@openinworld.com wrote:
> When I have a 'self haltOnce' breakpoint that I am activating often, going
> "World > System > Enable halt/inspect once" ea
I use it too, and I think they are a nice add that the tools should be more
aware (not just showing the flag icon in browser)
On Thu, Dec 12, 2013 at 1:05 PM, Marcus Denker wrote:
>
> On 12 Dec 2013, at 12:58, Torsten Bergmann wrote:
>
> > Did you check the number of senders of #flag: in a rece
When I have a 'self haltOnce' breakpoint that I am activating often,
going "World > System > Enable halt/inspect once" each time is
annoying. So using the Duplicate Halo on the menu item, I drag it onto
the background so that it acts like a button.
cheers -ben
On 12 Dec 2013, at 12:58, Torsten Bergmann wrote:
> Did you check the number of senders of #flag: in a recent Pharo image? You
> will be surprised that not all come from Squeak ;)
>
I use it, yes.
Marcus
Hi Marcus,
regarding 2) In Pharo 3.0 one can already open a file browser on the
memory file system:
|fs|
fs := FileSystem memory.
(fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Exported data' ].
FileList openOn: fs root
but it looks like it needs some love. One can create
Did you check the number of senders of #flag: in a recent Pharo image? You
will be surprised that not all come from Squeak ;)
By sharing I want to just show what is possible and others may find it valuable
for their own work in the given or in a customized form.
It is not a "best practice", more
so far icons are all packed together into an icon pack.
for example, Pharo3Icons and FamFamIcons.
all tools should register their icons there, as extensions of a theme.
then, a method:
MyClass clas>>#icon
^ Smalltalk ui icons iconNamed: #myIcon
can provide enough decoupling.
then... is i
Related to that:
For Pharo4 I want to experiment to have the following:
1) one Memory FileSystem per RPackage (just an ivar there).
2) File Browser support to show all these so one can put files in the package
filesystem
3) in Monticello, save all the files as part of the .zip (directory “resour
---
[Pharo Trick: #0008] - If appropriate use the memory file system
---
Works in: Pharo 2.0, 3.0, ...
---
>>
>
> I think the idea here is that maybe a class should have an icon. Independend
> of Nautilus.\
> (either just icon or toolIcon).
>
> Marcus
>
>
In a great environment you have icons and icon-sets defined by UX/UI designers.
If we couple too much to code we'll create a barrier fo
gee the big code package is airflowing which I have, quite conservatively,
running on #14438 images
I load filetree like this:
Gofer new
url: 'http://ss3.gemstone.com/ss/FileTree';
package: 'ConfigurationOfFileTree';
load.
((Smalltalk at: #ConfigurationOfFileTree) project vers
Then maybe Komitter should use this mechanism instead of registering to World.
But I am not sure if letting the possibilities to someone to override it
locally is bad or not
Ben
On 12 Dec 2013, at 11:50, Guillermo Polito wrote:
> Yes regarding the bindKeymapping:toAction:
>
> https://ci.inria
https://github.com/DamienCassou/pier-cl/blob/master/CheatSheet.pier.md
+caption>file://figures/image.png+
Ben
On 12 Dec 2013, at 11:50, Guillermo Polito wrote:
> Yes regarding the bindKeymapping:toAction:
>
> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild
Yes regarding the bindKeymapping:toAction:
https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/KeyMapping/KeyMapping.pier.html
- the bubbling explanation needs more love
- the global categories are not yet there
How do I add figures with the pier sintax?
guille
is the keymapping chapter up to date to that regards.
It would be good to explain better the bubble and the global binding.
If you have one hour it would be good.
Stef
On Dec 12, 2013, at 11:11 AM, Guillermo Polito
wrote:
> The world morph was initially intended to handle the global sy
On 12 Dec 2013, at 11:21, Nicolas Cellier
wrote:
> I don't much like this nice idea.
> Why? see all the (self flags: #toRemove) and such kind of annotations in
> Squeak.
>
self flag: #bob :-)
still two left in Pharo…
Marcus
I don't much like this nice idea.
Why? see all the (self flags: #toRemove) and such kind of annotations in
Squeak.
Then tend to last much longer than due.
A todo list should have a (short) expiration date.
Maybe a method with expired todo should be purely and simply erased ;)
2013/12/12 Serge Sti
not yet :D
On Thu, Dec 12, 2013 at 10:54 AM, Stéphane Ducasse <
stephane.duca...@inria.fr> wrote:
>
> On Dec 12, 2013, at 10:47 AM, Esteban Lorenzano
> wrote:
>
> Stef means "RPackageOrganizer", not PackageOrganizer :)
>
>
> ok I thought the old one was removed and the new renamed
>
>
> Esteba
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 01f4ef1faba4b076c0d655bb2db238bb8556f597
https://github.com/pharo-project/pharo-core/commit/01f4ef1faba4b076c0d655bb2db238bb8556f597
Author: Jenkins Build Server
Date: 2013-12-12 (Thu, 12 Dec 2013
Branch: refs/tags/30639
Home: https://github.com/pharo-project/pharo-core
Nice idea Torsten, this kind of tricks ;-)
Maybe we can save them online somewhere ?
gists.github.com ?
On Wed, Dec 11, 2013 at 12:16 PM, Torsten Bergmann wrote:
> Hi,
>
> the mailinglist, stackoverflow and other Pharo related medias are typically
> used
> in the "here is a question to problem"
The world morph was initially intended to handle the global system
shortcuts, taking advantage of the event bubbling. However, that posed the
fact that the global shortcuts have less priority than other shortcuts. The
bubbling will activate a global shortcut only if it they key event did not
activa
Ahh a little detail!
We are deprecating the usage of #on:do: for shortcuts so they are not
mistaken with exception handling, nor announcement registration :).
The right snippet would be
World
bindKeyCombination: $a shift command
toAction: [ Object browse ].
Actually, if you see t
BTW, no world binding has yet been initialized yet in Pharo 3.0 (but CMD+K)
Is it intentional?
see
http://stackoverflow.com/questions/17886061/switch-between-open-windows-in-pharo
2013/12/12 p...@highoctane.be
> Very sweet indeed.
>
> Phil
>
>
>
> On Thu, Dec 12, 2013 at 9:42 AM, Max Leske wro
Yes :)
In the output of the catalog itself
https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/?
There is probably a typo in the generator catalogkeyClassesAndExample =>
catalogKeyClassesAndExample
1. Aconcagua
Please define a class method named catalogDescription returnin
On Dec 12, 2013, at 10:47 AM, Esteban Lorenzano wrote:
> Stef means "RPackageOrganizer", not PackageOrganizer :)
ok I thought the old one was removed and the new renamed
>
> Esteban
>
>
> On Thu, Dec 12, 2013 at 8:37 AM, Roberto Minelli
> wrote:
> Thx Stef!
>
> I also found RPackage orga
TreeMorph
On Dec 12, 2013, at 10:27 AM, Benjamin
wrote:
> Of ?
>
> Ben
>
> On 12 Dec 2013, at 08:11, Stéphane Ducasse wrote:
>
>> In the midterm
>>
>> would it not be better to start a new implementation?
>>
>> Stef
>> On Dec 11, 2013, at 11:18 PM, Benjamin
>> wrote:
>>
>>> That’s the
This is clearly an issue of Grease. And it is not essential either as there
are no senders to it. So, I see no reason not to rename it in Grease.
Cheers,
Doru
On Thu, Dec 12, 2013 at 8:28 AM, Stéphane Ducasse wrote:
> +1
> I do not really get it because we mentioned that several times.
> Greas
is there a place where I can see the metadata methods I need to implement?
Esteban
On Thu, Dec 12, 2013 at 9:59 AM, Stéphane Ducasse wrote:
> Hi guys
>
> I really want to have an official catalog soon, so please add the missing
> metadata in your configurations.
> In addition I was discussing
Stef means "RPackageOrganizer", not PackageOrganizer :)
Esteban
On Thu, Dec 12, 2013 at 8:37 AM, Roberto Minelli wrote:
> Thx Stef!
>
> I also found RPackage organizer packages ;)
>
> Cheers,
> R
>
> On Dec 12, 2013, at 8:25 AM, Stéphane Ducasse
> wrote:
>
> >
> > On Dec 11, 2013, at 1:40 PM,
On Thu, Dec 12, 2013 at 8:19 AM, Stéphane Ducasse wrote:
> >>
> >
> > I think the idea here is that maybe a class should have an icon.
> Independend of Nautilus.\
> > (either just icon or toolIcon).
>
> Yes we got the idea :)
> Now we faced extensions management problems with pavel so we could no
On 12 Dec 2013, at 10:33, Dario Trussardi wrote:
>
> Ciao,
>
>> I will promote the latest vm (latest before spur) as stable tomorrow
>> morning.
>> So I suppose he can try that :)
>>
>> Pharo-VM-mac-latest.zip
>>
> I download it,
>
> but now what i need to do with it ?
>
>
---
[Pharo Trick: #0007] - Write UI prototype in a workspace
---
Works in: Pharo 2.0, 3.0, ...
Ciao,
> I will promote the latest vm (latest before spur) as stable tomorrow morning.
> So I suppose he can try that :)
>
> Pharo-VM-mac-latest.zip
>
I download it,
but now what i need to do with it ?
How i can update my Pharo 2.0 environment with it ?
Thanks
Of ?
Ben
On 12 Dec 2013, at 08:11, Stéphane Ducasse wrote:
> In the midterm
>
> would it not be better to start a new implementation?
>
> Stef
> On Dec 11, 2013, at 11:18 PM, Benjamin
> wrote:
>
>> That’s the default behaviour
>>
>> I was thinking today of introducing a special one which
---
[Pharo Trick: #0006] - Run code from a standalone button window
---
Works in: Pharo 2.0, 3.0, ...
-
Usually one can deal with morphs by doing the alt-shift-click on them, so
that we get the halos and do whatever.
Now, some morphs do not want to let you do this (like the Pharo image on
the desktop background) - or you just don't see them as they are leftovers
from experiments.
A shift click (on
Very sweet indeed.
Phil
On Thu, Dec 12, 2013 at 9:42 AM, Max Leske wrote:
> Nice! Didn’t know about that one.
>
>
> On 12.12.2013, at 09:35, Torsten Bergmann wrote:
>
> >
> ---
> > [Pharo Trick: #0004] - Run code
I want more :)
On Dec 12, 2013, at 9:42 AM, Max Leske wrote:
> Nice! Didn’t know about that one.
>
>
> On 12.12.2013, at 09:35, Torsten Bergmann wrote:
>
>> ---
>> [Pharo Trick: #0004] - Run code using a key comm
Hi guys
I really want to have an official catalog soon, so please add the missing
metadata in your configurations.
In addition I was discussing with robert pergl from Prague and he told me that
when he has a problem with a package he does not know to whom he should report
so
I would like to ad
Branch: refs/tags/30638
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 3f85b941eaab5b182b2139d9d3f889ad2f059cfa
https://github.com/pharo-project/pharo-core/commit/3f85b941eaab5b182b2139d9d3f889ad2f059cfa
Author: Jenkins Build Server
Date: 2013-12-12 (Thu, 12 Dec 2013
Nice! Didn’t know about that one.
On 12.12.2013, at 09:35, Torsten Bergmann wrote:
> ---
> [Pharo Trick: #0004] - Run code using a key command to speedup development
> ---
Hi,
I meant to say that projects that use pharo should rethink the tests and
rules they run in order to ensure that they do not break the Pharo
constraints.
For example, for Moose, we should have, like Stephan suggested, an
integration job that runs all tests in the image (at least). Ideally, it
---
[Pharo Trick: #0004] - Run code using a key command to speedup development
---
Works in: Pharo3.0 Latest update: #30637 but should work
On 12 Dec 2013, at 08:22, Marcus Denker wrote:
>
> On 12 Dec 2013, at 08:14, Tudor Girba wrote:
>
>> Hi,
>>
>>
>> On Thu, Dec 12, 2013 at 7:59 AM, Marcus Denker
>> wrote:
>>
>> On 12 Dec 2013, at 06:31, Tudor Girba wrote:
>>
>> > Hi Stephan,
>> >
>> > Thanks for pushing the #packages p
74 matches
Mail list logo
