But gwenael did a complete GTK binding for Squeak/pharo and he moved everything
to GNU.
Too bad. So we/you could gain from that.
Stef
On Jan 11, 2010, at 8:18 AM, Stéphane Ducasse wrote:
> Now for pharo people could ressurect the GTK port done by gwenael.
> Or pay for that.
>
> Stef
>
> On Jan
Given we're at the start of the year, I can still have wishes as well, then
let's add Gayvert's wxWidgets as well http://www.wxsqueak.org/
[]s
--
Cesar Rabak
Em 11/01/2010 05:18, Stéphane Ducasse < stephane.duca...@inria.fr > escreveu:
Now for pharo people could ressurect the GTK port done
Now for pharo people could ressurect the GTK port done by gwenael.
Or pay for that.
Stef
On Jan 11, 2010, at 2:40 AM, Stephen Taylor wrote:
> Schwab,Wilhelm K wrote:
>> Dolphin is better than that
>
> I've put my money where my mouth is with Dolphin - I think I've bought
> every product they'v
oject@lists.gforge.inria.fr
Sent: Sun, January 10, 2010 8:40:15 PM
Subject: Re: [Pharo-project] Pharo for Professional Development
Schwab,Wilhelm K wrote:
> Dolphin is better than that
I've put my money where my mouth is with Dolphin - I think I've bought
every product they've ever
-boun...@lists.gforge.inria.fr
[mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Stephen Taylor
Sent: Sunday, January 10, 2010 9:44 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Pharo for Professional Development
Schwab,Wilhelm K wrote:
> Steve,
>
> I&#
Schwab,Wilhelm K wrote:
> Steve,
>
> I'm confused: how is a D4 guy an idea space fan???
The key word is laziness - not the good sort of laziness that
programmers are supposed to have, along with hubris, etc, but the bad
sort you're supposed to shake yourself out of. I've bought the various
n
fr
Subject: Re: [Pharo-project] Pharo for Professional Development
Schwab,Wilhelm K wrote:
> Dolphin is better than that
I've put my money where my mouth is with Dolphin - I think I've bought every
product they've ever released, just to give them a hand - despite the fact th
Schwab,Wilhelm K wrote:
> Dolphin is better than that
I've put my money where my mouth is with Dolphin - I think I've bought
every product they've ever released, just to give them a hand - despite
the fact that I've still got a Dolphin version4 image on the go!
> The feature you are describing
other times.
Bill
-Original Message-
From: pharo-project-boun...@lists.gforge.inria.fr
[mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Stephen Taylor
Sent: Sunday, January 10, 2010 6:19 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Phar
Michael Rueger wrote:
> Henrik Johansen wrote:
>
>> This is just another reason why multiple native windows would be nice,
>> though, leaves the problem for someone else :)
>
> Interestingly enough a lot of the (complex) multiple native window
> applications have (gone back to) all in one windo
On Fri, Dec 18, 2009 at 1:39 PM, George Herolyants
wrote:
> 2009/12/18 Michael Rueger :
>> Henrik Johansen wrote:
>>
>> Interestingly enough a lot of the (complex) multiple native window
>> applications have (gone back to) all in one window UIs (Eclipse, all of
>> the Adobe products, ...).
>
> Yea
On 18 déc. 2009, at 12:29, Henrik Johansen wrote:
>
> On Dec 18, 2009, at 12:03 09PM, Simon Denier wrote:
>>
>>
>>
>> About the taskbar: I'm more and more convinced that the taskbar does not
>> work well for me, in particular does not scale. I would prefer something
>> like the Mac Os dock.
On 18 déc. 2009, at 13:23, Bart Gauquie wrote:
>
> The dev build really misses a process like the core build has with
> integrators. But we can not mimic this process in dev since it integrates
> external packages, whose developers are sometimes not concerned with Pharo. I
> volunteer for tha
nria.fr
Subject: Re: [Pharo-project] Pharo for Professional Development
On Fri, 18 Dec 2009, George Herolyants wrote:
> 2009/12/18 Michael Rueger :
>> Henrik Johansen wrote:
>>
>> Interestingly enough a lot of the (complex) multiple native window
>> applications
2009/12/18 Levente Uzonyi :
> Sure, start the vm with: -vm display=none. Then use RFB to connect to the
> image, we use several such images.
Yes. You're right. I completely forgot about the possibility to use
RFB. Yeah, in this case all the native dialogs won't fit at all. And
multiple windows in
Bart Gauquie wrote:
>
> Allow me to explain why I have such strong beliefs about this. On my
> firm, we are using some techniques to enable that. On one project they
> are releasing new functionality every two weeks. How they do that is as
> following. These 2 weeks releases are incremental ch
On Fri, 18 Dec 2009, George Herolyants wrote:
> 2009/12/18 Levente Uzonyi :
>> On Fri, 18 Dec 2009, George Herolyants wrote:
>>> And native basic dialogs may be helpful too, to not reinvent the wheel
>>> (aka FileBrowser :).
>>
>> At first sight this idea seems to be cool, but it's not. FileBrowse
On Dec 18, 2009, at 2:39 PM, Bart Gauquie wrote:
>
> Do you have negative experiences with writing tests?
No.
> I've been using it all my professional career; and I firmly believe it is the
> only way to develop software, a good test set really helps to move forward at
> a sustainable pace. C
Marcus,
We have the rule to do something, even if what we do it is not perfect.
>
I never suggested this. Only trying to improve the way we are working, so
that we can work more efficiently.
>
> The idea to request a test for everything does not work. And in addition,
> even tests do no guarant
2009/12/18 Levente Uzonyi :
> On Fri, 18 Dec 2009, George Herolyants wrote:
>> And native basic dialogs may be helpful too, to not reinvent the wheel
>> (aka FileBrowser :).
>
> At first sight this idea seems to be cool, but it's not. FileBrowser is
> not a "reinvented wheel", it's really useful in
On Fri, 18 Dec 2009, George Herolyants wrote:
> 2009/12/18 Michael Rueger :
>> Henrik Johansen wrote:
>>
>> Interestingly enough a lot of the (complex) multiple native window
>> applications have (gone back to) all in one window UIs (Eclipse, all of
>> the Adobe products, ...).
>
> Yeah! That's tr
On Dec 18, 2009, at 1:23 PM, Bart Gauquie wrote:
>
> Concerning the parts that are lacking tests. We have a rule to test
> everything.
We have the rule to do something, even if what we do it is not perfect.
The idea to request a test for everything does not work. And in addition, even
tests
On Dec 18, 2009, at 1:10 PM, Marcus Denker wrote:
>>
>> I think that in Pharo most of the tests are unit tests. Please correct if
>> I'm wrong, don't know it well enough yet. Each package is perfectly unit
>> tested.
>
> No, no package is perfectly unit-tested. Not even close. For some things
2009/12/18 Michael Rueger :
> Henrik Johansen wrote:
>
> Interestingly enough a lot of the (complex) multiple native window
> applications have (gone back to) all in one window UIs (Eclipse, all of
> the Adobe products, ...).
Yeah! That's true. And their look&feel may differ from the underlying
os
>
>
> The dev build really misses a process like the core build has with
> integrators. But we can not mimic this process in dev since it integrates
> external packages, whose developers are sometimes not concerned with Pharo.
> I volunteer for that.
>
>
That is true. However, since Pharo chooses e
On 18 déc. 2009, at 11:36, Bart Gauquie wrote:
>
>
> I think we should rename 1.1. It's not #alpha, it's #unstable.
>
>Marcus
> ___
>
>
> I think thats a bad idea. Pharo should also set a standard on stability.
> It's even in the mission
On Dec 18, 2009, at 1:05 PM, Bart Gauquie wrote:
> Hi Marcus,
>
> There is no release yet!
>
> How often are you planning to do a release? I suppose the next release is
> the reached milestones for 1.1?
>
Yes, this will be ready in a couple of months.
>
>
> I think that in Pharo most of
Hi Marcus,
There is no release yet!
>
How often are you planning to do a release? I suppose the next release is
the reached milestones for 1.1?
>
> > everything that worked before should still work perfectly. The new stuff
> being added are first buggy; seems normal to me. But if the new stuff
Henrik Johansen wrote:
> This is just another reason why multiple native windows would be nice,
> though, leaves the problem for someone else :)
Interestingly enough a lot of the (complex) multiple native window
applications have (gone back to) all in one window UIs (Eclipse, all of
the Adobe
On Dec 18, 2009, at 12:03 09PM, Simon Denier wrote:
>
>
>
> About the taskbar: I'm more and more convinced that the taskbar does not work
> well for me, in particular does not scale. I would prefer something like the
> Mac Os dock. On the other hand, Algernon is a great tool to navigate quick
Yep, IDE tools in Pharo are at least a few years behind what you can find in
other IDEs, at least in terms of usability. This is a known problem :) and
there already has been a stream of propositions, enhancements, and talks about
this (I myself did a presentation at ESUG 2009 about what I want
On Dec 18, 2009, at 11:21 AM, Bart Gauquie wrote:
> Hi,
>
> The point I'm trying to make is that even on an alpha release,
There is no release yet!
> everything that worked before should still work perfectly. The new stuff
> being added are first buggy; seems normal to me. But if the new stu
On Dec 18, 2009, at 11:36 AM, Bart Gauquie wrote:
>
>
> I think we should rename 1.1. It's not #alpha, it's #unstable.
>
>Marcus
> ___
>
>
> I think thats a bad idea. Pharo should also set a standard on stability.
> It's even in the miss
Thanks for pointing out, did not know that.
Kind Regards,
Bart
On Fri, Dec 18, 2009 at 11:30 AM, Adrian Lienhard wrote:
>
> On Dec 18, 2009, at 10:34 , Bart Gauquie wrote:
>
> > Just now, I've been looking into
> > http://code.google.com/p/pharo/issues/detail?id=1570 I've reported
> > last
> >
I think we should rename 1.1. It's not #alpha, it's #unstable.
>
>Marcus
> ___
>
>
I think thats a bad idea. Pharo should also set a standard on stability.
It's even in the mission statement: 'By providing a stable and small core
system, excelle
On Dec 18, 2009, at 10:34 , Bart Gauquie wrote:
> Just now, I've been looking into
> http://code.google.com/p/pharo/issues/detail?id=1570 I've reported
> last
> week.
Thanks for reporting. Please always send a short mail to the list when
you create an issue. See also
http://www.pharo-projec
Hi,
The point I'm trying to make is that even on an alpha release, everything
that worked before should still work perfectly. The new stuff being added
are first buggy; seems normal to me. But if the new stuff is breaking old,
working stuff, and we only notice it after a month; then it will take u
>
>
> I think we should rename 1.1. It's not #alpha, it's #unstable.
>
>
good idea.
Just as a feedback. I tried to use Pharo to implement some algorithms in
course I'm giving. This was instructive ... but I think I won't do it next
year (except if I implement a pseudo-language a la etoy tile to do
On Dec 18, 2009, at 10:34 AM, Bart Gauquie wrote:
> Hi Marcus,
>
> I can understand your reasoning. The point I was trying to make is that even
> for the 1.1 alpha release everything should be stable that was stable before.
> I really appreciate the effort everybody does in it; the new stuff b
Bart Gauquie wrote:
> Hi Marcus,
>
> I can understand your reasoning. The point I was trying to make is that
> even for the 1.1 alpha release everything should be stable that was
> stable before. I really appreciate the effort everybody does in it; the
> new stuff being added and all; but break
Hi Marcus,
I can understand your reasoning. The point I was trying to make is that even
for the 1.1 alpha release everything should be stable that was stable
before. I really appreciate the effort everybody does in it; the new stuff
being added and all; but breaking things that worked before is no
Hi Bart,
Thanks for the feedback. You make some good points.
If you want to help make Pharo better, please report bugs!
Stability is important for us. That is why we have a 1.0 that is
stabilizing, and a 1.1 alpha branch at the moment. We don't just
commit everything into one trunk... After
On Dec 18, 2009, at 9:41 AM, Bart Gauquie wrote:
> Dear all,
>
> I've been using Squeak before, now I'm using Pharo. Its still 'hobby' usage.
> However, on my firm, we have a lot of working groups in which we investigate
> new technologies. We mainly use Java / .Net.
> I've initiated a workin
Dear all,
I've been using Squeak before, now I'm using Pharo. Its still 'hobby' usage.
However, on my firm, we have a lot of working groups in which we investigate
new technologies. We mainly use Java / .Net.
I've initiated a working group around Smalltalk/Seaside. And chose Pharo as
a smalltalk p
44 matches
Mail list logo
