Stephan Eggermont wrote
> This is open source. You can commit in the repo.
One point of confusion is probably that there is no indication (like we used
to have in sqs) in StHub's web interface whether repos are publicly writable
or not
-
Cheers,
Sean
--
View this message in context:
http:/
As I have discovered recently I quite regularly have large images (500+
MB); the reason seems to be combination of memory leaks, Roassal (maybe
Athens), GUI, and a LOT of saving while having all those things opened. But
Image cleanup tends to shrink it back to tens of megabytes.
Personally I don't
On 13/05/15 15:38, Julien Delplanque wrote:
So, I throw the fork on github and provide a compatibility package on
smalltalkhub?
Yes. Forking is ok if it is difficult to maintain compatibility,
and that is definitely not the case here. Paul has made improvements
to the code a few months back, so
If it is just the Url class, then I can't imagine the difference between the
old Url class and the new ZnUrl to be very large. An abstraction layer is
probably not needed, both should understand #asUrl and should have quite a lot
of common methods. The HTTP client is another story ;-)
On a more
Nice!
On Wed, May 13, 2015 at 8:51 AM, Sean P. DeNigris
wrote:
> laura wrote
> > Also the discussion brought up very interesting msg collaborations
> > snippets
> > and system features for future reference!
>
> I compiled them at
> https://github.com/pharo-project/pharo-core/wiki/Memory-Hogs
>
>
EstebanLM wrote
> It is not a demand. Just a suggestion. You can do whatever you want and
> nobody can impose you how to handle your code :)
+1. And to clarify, the suggestion is not that /you/ implement code for
Squeak, Pharo, and Gemstone, but that you abstract a Url layer so that other
interes
Igor Stasenko wrote
> Symbol + ??? => Selector
>
> give me a strong reason.
>
> i like the idea of shrinking a Symbol's protocol and putting it into
> lean and clean place - Symbol.
While fixing Issue 15523: "Code Cruft Rule Only Matches One-Liners", I
really wanted:
Selector
UnarySele
Well, I don't think I'm going to create/keep the compatibility, the
purpose of the fork is to make it fully compatible with Pharo and I
don't want to be responsible of the compatibility with others smalltalk.
I also think that it's going to be harder and harder to keep
compatibility between Ph
> On 13 May 2015, at 15:38, Julien Delplanque wrote:
>
> So, I throw the fork on github and provide a compatibility package on
> smalltalkhub?
It is not a demand. Just a suggestion. You can do whatever you want and nobody
can impose you how to handle your code :)
Esteban
>
> I wanted to i
So, I throw the fork on github and provide a compatibility package on
smalltalkhub?
I wanted to improve the lib, but I don't own it and there is no "pull
request" system on smalltalk hub.
I don't want to bother the owner of the repository with changes I want
to do. He probably has others thing
Julien Delplanque writes:
>> A list of nicely-formatted events would already be great. Something
>> along the lines of
>> http://getandroidstuff.com/wp-content/uploads/2013/01/Chronus-CM-10-Clock-Caledner-widget.jpg
> I already did this kind of stuff (attachments) but I'm not a designer so
> it
On 13/05/15 13:44, Esteban Lorenzano wrote:
honestly, the more and more the time passes the less and less we are
compatible… and this will increase will time.
if you want to keep compatibility you will have to provide compatibility
abstractions and packages (in the same way Seaside uses Grease,
laura wrote
> Also the discussion brought up very interesting msg collaborations
> snippets
> and system features for future reference!
I compiled them at
https://github.com/pharo-project/pharo-core/wiki/Memory-Hogs
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Imag
> On 13 May 2015, at 13:21, Sean P. DeNigris wrote:
>
> Julien Delplanque wrote
>> I took a little time to enhance the ICal library and to make it work
>> with Pharo 4!
>
> Thanks!
>
>
> Julien Delplanque wrote
>> I forked the one on smalltalkhub... I wanted to make it work on pharo 4...
>>
Julien Delplanque wrote
> I took a little time to enhance the ICal library and to make it work
> with Pharo 4!
Thanks!
Julien Delplanque wrote
> I forked the one on smalltalkhub... I wanted to make it work on pharo 4...
> Url class that were deprecated in Pharo 3 and even removed on Pharo 4!
I
Hello again,
Just for the record, the EventRecorder source code allowed me to solve my
problem.
It is apparently not possible to move the main HandMorph but you can create
a new secondary one and move it wherever you want !
Thanks again,
Matthieu
2015-05-12 17:59 GMT+02:00 Matthieu Lacaton :
>
Hi Julien,
Julien Delplanque writes:
> Hi everyone,
>
> I took a little time to enhance the ICal library and to make it work
> with Pharo 4!
>
> So I forked the one on smalltalkhub
> (http://smalltalkhub.com/#!/~pdebruic/iCal) and put all the modified
> code on github https://github.com/julie
17 matches
Mail list logo
