Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- 3 participants
- 144636 messages
Re: [Pharo-dev] About ways to participate in community and general negativity
by Ben Coman
Tudor Girba wrote:
> Hi,
>
> Indeed, you are right about noting that the situation will look
> different in a couple of months from now. Please, let's discuss these
> problems again in 2 months.
My point was not to delay discussion, but just not let it get you down
and be tolerant...
* For those sending criticism, of the system being in flux as in progresses.
* For those receiving criticism, when its comes from those using the
bleeding edge because of their faith in Pharo
* For third parties looking on, be confident that it will come together
for the release.
> The classic tools are still around. Furthermore, in the Settings, you
> have a Glamorous Toolkit category which allows you to switch the
> Inspector and the Playground off.
How hard would it be to run some parts of GToolkit in parallel with
existing tools, rather than on/off? I'd rather it stare me in the face
without boxing me in - to help me adapt in my own time. I tend to forget
about things I need to change a setting for.
-ben
> Cheers,
> Doru
>
>
> On Sat, Oct 4, 2014 at 2:30 AM, Ben Coman <btc(a)openinworld.com
> <mailto:btc@openinworld.com>> wrote:
>
> Thierry Goubier wrote:
>
> Le 03/10/2014 21:48, stepharo a écrit :
>
>
> On 3/10/14 17:07, Thierry Goubier wrote:
>
> Hi Esteban,
>
> I'm not sure my answer will please you or stef, and
> maybe I shouldn't
> voice it, staying being a "customer" instead of
> contributing "the way
> you want it". Hard words, but yours are hard too.
>
> I'd say simply that Pharo is successfull, fairly
> successfull for
> someone like me. It allows me to engage in complex work,
> in what I do
> best and what affords me to be paid and have the freedom
> to use Pharo.
> Some of those things suppose that I maintain and extend
> fairly complex
> packages on top of Pharo, and deal with permanent, multiple
> overlapping interruptions (meeting, administrative work,
> travels,
> etc...).
>
>
> Same here :)
>
> Pharo is great, it allows me to build a significant
> activity on top of it.
>
> Some of the consequences of that success? I'm looking at
> things that
> works now, not in Pharo 5, 6, or 7. I'm a bit frightened
> by grandiose
> rewritting attempts which will be usable in a version or
> 2, at best,
> and leave an unsatisfying "now" situation. I'll
> carefully evaluate
> what new stuff is integrated. New stuff I look to see if
> they are
> usable (libcgit integration, TxText) and what I see is
> stuff that
> builds on unstable core libs extensions (NativeBoost,
> Athens)
>
> Why Athens would be unstable?
> or nativeBoost?
>
>
> NativeBoost is not unstable for me, but why libcgit is on a
> bleeding edge NativeBoost version then? Athens is stable for me,
> but I believe that TxText requires a bleeding edge Athens.
>
> on top of an already unstable version (4.0), and I'm
> really not
> impressed by the software development process.
>
>
> what should it be?
> You know Igor will not be paid in a month from now, JB
> should find a job
> and esteban has two years to prove that the consortium flies.
> So if we do not clean the event and windowing systems, rick
> and thales
> will be in trouble. So we are fighting against time.
>
>
> Thales is not an easy customer :) I know; apart from parser
> know-how, there is nothing that I can sell outside (projects,
> etc..) about Pharo. And if I'm not successfull, then its no more
> Pharo for me.
>
> The end result is, when I see a bug, I'm already at
> least two versions
> behind you guys...
>
>
> Why. I do not get why Pharo 3 would be unstable and that far
> from Pharo 20.
>
>
> I'm on Pharo 3. Some of the stuff I'm interested is on Pharo 4 +
> bleeding edge version of core Pharo subsystem... two versions
> off from 3 for me.
>
>
> Remember, this Pharo 4 is alpha status. I think we had similar
> discussions about this time last year with Pharo 3, and it shaped up
> really well for release.
>
>
>
> Libcgit is like that: its Pharo 4 + Bleeding edge native boost
> not yet in Pharo 4 + libcgit (and from ESUG, I get that it will
> require an entire refactoring of Monticello and a complete new
> on disk format). It's really shaping up like a long, long term
> target.
>
> so there's nothing worth reporting. There is some
> progress on the way
> things are being done (thanks Marcus for doing the
> deprecation API
> backporting on 3.0) and not much on others (and I speak of
> methodology, not of new features being added on).
>
> If you have the feeling that I don't contribute the way
> I should or
> the way you would like, step back and ask yourself if
> this is not my
> "unspoken" way of me saying that I don't find a way to
> contribute, or
> that contributing effectively is too costly.
>
> And look! This is not a matter of resources, but maybe a
> matter of
> slowing down a bit, so that the poor community members
> with limited
> resources like me that are not full time on Pharo 4.0
> development may
> catch up :) And please, no more rejection of feedback,
> even negative.
> It just gives me the feeling you are overstreched, and
> that Pharo has
> a problem setting its goals.
>
>
> Thierry,
> I do not have the impression that we go fast.
> You see we started Athens more than two years ago. It is a
> success for
> external tools like moose and Roassal but
> without TxText Athens will just be a nice package not change
> the face of
> Pharo and we will get there.
>
>
> I believe you're right about those; but I'd say that the way
> it's being done is a bit worrying. Why?
>
> Because for me, TxText is already more advanced than the current
> text editor: the ability to change the cursor, probably a better
> layout, etc... Should already been integrated, then, if its
> already better. But you still have the font bug that Alexandre
> complained about... how many months ago? So, as long as its not
> resolved, TxText can't be integrated (and additionally, I'm sure
> that there is aliasing issues on my machines: fonts in Roassal
> don't look as nice as in Morphic).
>
> And now, to make integration easier, we pile more stuff on top
> of the existing, bound to be removed, infrastructure: Glamour,
> Rubric, etc... And both Glamour and Spec don't make it easy to
> solve Morphic bugs.
>
> I value your ambition a lot :) But I also feel that it stresses
> the Rmod team, and it leaks over the community.
>
>
> What are the plans to integrate TxText? By which I mean, what will
> be the staging for refactoring existing tools on top of it? It seems
> the path of Opal where (I think) it was in one Release before it was
> fully enabled worked well.
>
> Now I know that GTools have been used in Moose for a long time, but
> its integration to Pharo REPLACING Workspace has been a cultural
> shock to those that haven't used it before (myself included, though
> I'm lookign forward to adapting). I think there'll be similar
> culture shock when Pharo 4 is released, from those that don't follow
> the bleeding edge. I'd strongly suggest that GTools operate for ONE
> release alongside existing tools, as an additional item in the first
> level World menu next to 'Workspace'.
>
> Indeed, even if Playground is quite stable through long use in
> Moose, it is new to Pharo, and marking its menu entry as
> 'Experimental' for now might provide some benefits.
>
> * This may provide a to stress test new evolving frameworks like
> TxText & Rubric - without affecting existing tools.
>
> * Now Playground has a wider community exposure, feedback from new
> users is likely to be less pressure and less negative if they still
> have access to old tools.
>
> * Feedback may result in changes.
>
> * Reduced culture shock. Builds confidence in a stable system not
> going "too fast" but just "fast enough" (very subjective I know).
>
> -ben
>
>
> Writing the chapter and maintaining Smacc is already a nice
> tribute to
> the community. Just continue that and we will be happy :)
>
>
> Thanks. John gave me plenty of fixes and I'm preparing a new
> version of SmaCC, and adding GUI tools (thinking of Guillaume
> needs and my needs as well).
>
> I certainly hope I'll be able to contribute on other things,
> still :)
>
> Thierry
>
>
>
>
>
>
>
>
> --
> www.tudorgirba.com <http://www.tudorgirba.com>
>
> "Every thing has its own flow"
Oct. 4, 2014
Re: [Pharo-dev] About ways to participate in community and general negativity
by Tudor Girba
Hi,
Indeed, you are right about noting that the situation will look different
in a couple of months from now. Please, let's discuss these problems again
in 2 months.
The classic tools are still around. Furthermore, in the Settings, you have
a Glamorous Toolkit category which allows you to switch the Inspector and
the Playground off.
Cheers,
Doru
On Sat, Oct 4, 2014 at 2:30 AM, Ben Coman <btc(a)openinworld.com> wrote:
> Thierry Goubier wrote:
>
>> Le 03/10/2014 21:48, stepharo a écrit :
>>
>>>
>>> On 3/10/14 17:07, Thierry Goubier wrote:
>>>
>>>> Hi Esteban,
>>>>
>>>> I'm not sure my answer will please you or stef, and maybe I shouldn't
>>>> voice it, staying being a "customer" instead of contributing "the way
>>>> you want it". Hard words, but yours are hard too.
>>>>
>>>> I'd say simply that Pharo is successfull, fairly successfull for
>>>> someone like me. It allows me to engage in complex work, in what I do
>>>> best and what affords me to be paid and have the freedom to use Pharo.
>>>> Some of those things suppose that I maintain and extend fairly complex
>>>> packages on top of Pharo, and deal with permanent, multiple
>>>> overlapping interruptions (meeting, administrative work, travels,
>>>> etc...).
>>>>
>>>
>>> Same here :)
>>>
>>>> Pharo is great, it allows me to build a significant activity on top of
>>>> it.
>>>>
>>>> Some of the consequences of that success? I'm looking at things that
>>>> works now, not in Pharo 5, 6, or 7. I'm a bit frightened by grandiose
>>>> rewritting attempts which will be usable in a version or 2, at best,
>>>> and leave an unsatisfying "now" situation. I'll carefully evaluate
>>>> what new stuff is integrated. New stuff I look to see if they are
>>>> usable (libcgit integration, TxText) and what I see is stuff that
>>>> builds on unstable core libs extensions (NativeBoost, Athens)
>>>>
>>> Why Athens would be unstable?
>>> or nativeBoost?
>>>
>>
>> NativeBoost is not unstable for me, but why libcgit is on a bleeding edge
>> NativeBoost version then? Athens is stable for me, but I believe that
>> TxText requires a bleeding edge Athens.
>>
>> on top of an already unstable version (4.0), and I'm really not
>>>> impressed by the software development process.
>>>>
>>>
>>> what should it be?
>>> You know Igor will not be paid in a month from now, JB should find a job
>>> and esteban has two years to prove that the consortium flies.
>>> So if we do not clean the event and windowing systems, rick and thales
>>> will be in trouble. So we are fighting against time.
>>>
>>
>> Thales is not an easy customer :) I know; apart from parser know-how,
>> there is nothing that I can sell outside (projects, etc..) about Pharo. And
>> if I'm not successfull, then its no more Pharo for me.
>>
>> The end result is, when I see a bug, I'm already at least two versions
>>>> behind you guys...
>>>>
>>>
>>> Why. I do not get why Pharo 3 would be unstable and that far from Pharo
>>> 20.
>>>
>>
>> I'm on Pharo 3. Some of the stuff I'm interested is on Pharo 4 + bleeding
>> edge version of core Pharo subsystem... two versions off from 3 for me.
>>
>
> Remember, this Pharo 4 is alpha status. I think we had similar
> discussions about this time last year with Pharo 3, and it shaped up really
> well for release.
>
>
>
>> Libcgit is like that: its Pharo 4 + Bleeding edge native boost not yet in
>> Pharo 4 + libcgit (and from ESUG, I get that it will require an entire
>> refactoring of Monticello and a complete new on disk format). It's really
>> shaping up like a long, long term target.
>>
>> so there's nothing worth reporting. There is some progress on the way
>>>> things are being done (thanks Marcus for doing the deprecation API
>>>> backporting on 3.0) and not much on others (and I speak of
>>>> methodology, not of new features being added on).
>>>>
>>>> If you have the feeling that I don't contribute the way I should or
>>>> the way you would like, step back and ask yourself if this is not my
>>>> "unspoken" way of me saying that I don't find a way to contribute, or
>>>> that contributing effectively is too costly.
>>>>
>>>> And look! This is not a matter of resources, but maybe a matter of
>>>> slowing down a bit, so that the poor community members with limited
>>>> resources like me that are not full time on Pharo 4.0 development may
>>>> catch up :) And please, no more rejection of feedback, even negative.
>>>> It just gives me the feeling you are overstreched, and that Pharo has
>>>> a problem setting its goals.
>>>>
>>>
>>> Thierry,
>>> I do not have the impression that we go fast.
>>> You see we started Athens more than two years ago. It is a success for
>>> external tools like moose and Roassal but
>>> without TxText Athens will just be a nice package not change the face of
>>> Pharo and we will get there.
>>>
>>
>> I believe you're right about those; but I'd say that the way it's being
>> done is a bit worrying. Why?
>>
>> Because for me, TxText is already more advanced than the current text
>> editor: the ability to change the cursor, probably a better layout, etc...
>> Should already been integrated, then, if its already better. But you still
>> have the font bug that Alexandre complained about... how many months ago?
>> So, as long as its not resolved, TxText can't be integrated (and
>> additionally, I'm sure that there is aliasing issues on my machines: fonts
>> in Roassal don't look as nice as in Morphic).
>>
>> And now, to make integration easier, we pile more stuff on top of the
>> existing, bound to be removed, infrastructure: Glamour, Rubric, etc... And
>> both Glamour and Spec don't make it easy to solve Morphic bugs.
>>
>> I value your ambition a lot :) But I also feel that it stresses the Rmod
>> team, and it leaks over the community.
>>
>>
> What are the plans to integrate TxText? By which I mean, what will be the
> staging for refactoring existing tools on top of it? It seems the path of
> Opal where (I think) it was in one Release before it was fully enabled
> worked well.
>
> Now I know that GTools have been used in Moose for a long time, but its
> integration to Pharo REPLACING Workspace has been a cultural shock to those
> that haven't used it before (myself included, though I'm lookign forward to
> adapting). I think there'll be similar culture shock when Pharo 4 is
> released, from those that don't follow the bleeding edge. I'd strongly
> suggest that GTools operate for ONE release alongside existing tools, as an
> additional item in the first level World menu next to 'Workspace'.
>
> Indeed, even if Playground is quite stable through long use in Moose, it
> is new to Pharo, and marking its menu entry as 'Experimental' for now might
> provide some benefits.
>
> * This may provide a to stress test new evolving frameworks like TxText &
> Rubric - without affecting existing tools.
>
> * Now Playground has a wider community exposure, feedback from new users
> is likely to be less pressure and less negative if they still have access
> to old tools.
>
> * Feedback may result in changes.
>
> * Reduced culture shock. Builds confidence in a stable system not going
> "too fast" but just "fast enough" (very subjective I know).
>
> -ben
>
>
> Writing the chapter and maintaining Smacc is already a nice tribute to
>>> the community. Just continue that and we will be happy :)
>>>
>>
>> Thanks. John gave me plenty of fixes and I'm preparing a new version of
>> SmaCC, and adding GUI tools (thinking of Guillaume needs and my needs as
>> well).
>>
>> I certainly hope I'll be able to contribute on other things, still :)
>>
>> Thierry
>>
>>
>>
>
>
>
--
www.tudorgirba.com
"Every thing has its own flow"
Oct. 4, 2014
Re: [Pharo-dev] About ways to participate in community and general negativity
by Ben Coman
Thierry Goubier wrote:
> Le 03/10/2014 21:48, stepharo a écrit :
>>
>> On 3/10/14 17:07, Thierry Goubier wrote:
>>> Hi Esteban,
>>>
>>> I'm not sure my answer will please you or stef, and maybe I shouldn't
>>> voice it, staying being a "customer" instead of contributing "the way
>>> you want it". Hard words, but yours are hard too.
>>>
>>> I'd say simply that Pharo is successfull, fairly successfull for
>>> someone like me. It allows me to engage in complex work, in what I do
>>> best and what affords me to be paid and have the freedom to use Pharo.
>>> Some of those things suppose that I maintain and extend fairly complex
>>> packages on top of Pharo, and deal with permanent, multiple
>>> overlapping interruptions (meeting, administrative work, travels,
>>> etc...).
>>
>> Same here :)
>>> Pharo is great, it allows me to build a significant activity on top
>>> of it.
>>>
>>> Some of the consequences of that success? I'm looking at things that
>>> works now, not in Pharo 5, 6, or 7. I'm a bit frightened by grandiose
>>> rewritting attempts which will be usable in a version or 2, at best,
>>> and leave an unsatisfying "now" situation. I'll carefully evaluate
>>> what new stuff is integrated. New stuff I look to see if they are
>>> usable (libcgit integration, TxText) and what I see is stuff that
>>> builds on unstable core libs extensions (NativeBoost, Athens)
>> Why Athens would be unstable?
>> or nativeBoost?
>
> NativeBoost is not unstable for me, but why libcgit is on a bleeding
> edge NativeBoost version then? Athens is stable for me, but I believe
> that TxText requires a bleeding edge Athens.
>
>>> on top of an already unstable version (4.0), and I'm really not
>>> impressed by the software development process.
>>
>> what should it be?
>> You know Igor will not be paid in a month from now, JB should find a job
>> and esteban has two years to prove that the consortium flies.
>> So if we do not clean the event and windowing systems, rick and thales
>> will be in trouble. So we are fighting against time.
>
> Thales is not an easy customer :) I know; apart from parser know-how,
> there is nothing that I can sell outside (projects, etc..) about Pharo.
> And if I'm not successfull, then its no more Pharo for me.
>
>>> The end result is, when I see a bug, I'm already at least two versions
>>> behind you guys...
>>
>> Why. I do not get why Pharo 3 would be unstable and that far from
>> Pharo 20.
>
> I'm on Pharo 3. Some of the stuff I'm interested is on Pharo 4 +
> bleeding edge version of core Pharo subsystem... two versions off from 3
> for me.
Remember, this Pharo 4 is alpha status. I think we had similar
discussions about this time last year with Pharo 3, and it shaped up
really well for release.
>
> Libcgit is like that: its Pharo 4 + Bleeding edge native boost not yet
> in Pharo 4 + libcgit (and from ESUG, I get that it will require an
> entire refactoring of Monticello and a complete new on disk format).
> It's really shaping up like a long, long term target.
>
>>> so there's nothing worth reporting. There is some progress on the way
>>> things are being done (thanks Marcus for doing the deprecation API
>>> backporting on 3.0) and not much on others (and I speak of
>>> methodology, not of new features being added on).
>>>
>>> If you have the feeling that I don't contribute the way I should or
>>> the way you would like, step back and ask yourself if this is not my
>>> "unspoken" way of me saying that I don't find a way to contribute, or
>>> that contributing effectively is too costly.
>>>
>>> And look! This is not a matter of resources, but maybe a matter of
>>> slowing down a bit, so that the poor community members with limited
>>> resources like me that are not full time on Pharo 4.0 development may
>>> catch up :) And please, no more rejection of feedback, even negative.
>>> It just gives me the feeling you are overstreched, and that Pharo has
>>> a problem setting its goals.
>>
>> Thierry,
>> I do not have the impression that we go fast.
>> You see we started Athens more than two years ago. It is a success for
>> external tools like moose and Roassal but
>> without TxText Athens will just be a nice package not change the face of
>> Pharo and we will get there.
>
> I believe you're right about those; but I'd say that the way it's being
> done is a bit worrying. Why?
>
> Because for me, TxText is already more advanced than the current text
> editor: the ability to change the cursor, probably a better layout,
> etc... Should already been integrated, then, if its already better. But
> you still have the font bug that Alexandre complained about... how many
> months ago? So, as long as its not resolved, TxText can't be integrated
> (and additionally, I'm sure that there is aliasing issues on my
> machines: fonts in Roassal don't look as nice as in Morphic).
>
> And now, to make integration easier, we pile more stuff on top of the
> existing, bound to be removed, infrastructure: Glamour, Rubric, etc...
> And both Glamour and Spec don't make it easy to solve Morphic bugs.
>
> I value your ambition a lot :) But I also feel that it stresses the Rmod
> team, and it leaks over the community.
>
What are the plans to integrate TxText? By which I mean, what will be
the staging for refactoring existing tools on top of it? It seems the
path of Opal where (I think) it was in one Release before it was fully
enabled worked well.
Now I know that GTools have been used in Moose for a long time, but its
integration to Pharo REPLACING Workspace has been a cultural shock to
those that haven't used it before (myself included, though I'm lookign
forward to adapting). I think there'll be similar culture shock when
Pharo 4 is released, from those that don't follow the bleeding edge.
I'd strongly suggest that GTools operate for ONE release alongside
existing tools, as an additional item in the first level World menu next
to 'Workspace'.
Indeed, even if Playground is quite stable through long use in Moose, it
is new to Pharo, and marking its menu entry as 'Experimental' for now
might provide some benefits.
* This may provide a to stress test new evolving frameworks like TxText
& Rubric - without affecting existing tools.
* Now Playground has a wider community exposure, feedback from new users
is likely to be less pressure and less negative if they still have
access to old tools.
* Feedback may result in changes.
* Reduced culture shock. Builds confidence in a stable system not going
"too fast" but just "fast enough" (very subjective I know).
-ben
>> Writing the chapter and maintaining Smacc is already a nice tribute to
>> the community. Just continue that and we will be happy :)
>
> Thanks. John gave me plenty of fixes and I'm preparing a new version of
> SmaCC, and adding GUI tools (thinking of Guillaume needs and my needs as
> well).
>
> I certainly hope I'll be able to contribute on other things, still :)
>
> Thierry
>
>
Oct. 4, 2014
New Cog VMs available
by Eliot Miranda
...at http://www.mirandabanda.org/files/Cog/VM/VM.r3095/.
CogVM binaries as per VMMaker.oscog-eem.890/r3095
Fix line-buffered input in sqFilePluginBasicPrims.c when buffer size > 1.
fread cannot be relied upon to answer lines.
Fix bug in Cogit>>lookup:for:methodAndErrorSelectorInto: which if cogging a
method found through an MNU would set the cog method's selector to the
original
selector that was not understood instead of #doesNotUnderstand:.
Fix the description of the blockonwarn flag (not blockonwarning).
Spur:
Fix one-way become for classes with and without copyHash, primarily by
fixing
allInstances. One-way become for classes causes duplicates in the class
table
(either that or an allInstances scan would be needed as part of the become
to
change instances referring to the deleted class index, which would be slow).
So allInstances must be able to cope with duplicates. Hence split it into a
fast path common case when the class in question is not duplicated, and a
slower
path when it is. Make both the marking phase of GC and allInstances check
for
and eliminate refereces to duplicate entries at wrong/obsolete class
indices.
Fix markAndShouldScan: to not scan the pun classes of non-objects on the
heap
such as implicit receiver caches and Sista counters.
Eliminate the classTableBitmap premature optimization. All the information
we
need is in the cassTable and the class's hashes therein.
Change pinObject: to answer 0 on failure and the (possibly moved) object on
success. Much easier than having to check and follow forwarding pointer.
The changes to platforms/Cross/plugins/FilePlugin/sqFilePluginBasicPrims.c
in r3092 in a Spur MT VM depend on this.
--
best,
Eliot
Oct. 4, 2014
Re: [Pharo-dev] playground size
by Ben Coman
Tudor Girba wrote:
> This is indeed a relevant use case, and we are already thinking about
> this issue for quite a while. The playground or even the workspace are
> not appropriate for things that need to live for a short time only.
>
> I would like to have an interface that comes, let's me enter my command
> and then vanishes. Similar to the spotlight interface. And once we will
> be on this, we will also make it a search interface... remember that
> Pharo4 is about tooling so now is the time to dream and do :).
>
> Doru
Why not use spotlight, allowing Cmd-d to work. Or would you want a bit
more space? Maybe if you need a second line you could use Alt-<Enter> ?
-ben
>
> On Fri, Oct 3, 2014 at 10:38 PM, stepharo <stepharo(a)free.fr
> <mailto:stepharo@free.fr>> wrote:
>
> Yes your use case make a lot of sense.
>
>> I am using GT in 3.0 and the inspector is indeed supercool.
>>
>> Now, I've the standard Workspace on Cmd-o Cmd-w and the Playground
>> on Cmd-g. Depending on the task, one or the other is better.
>>
>> I am using Workspaces as a kind of command prompt in Pharo to set
>> some state of the system, reinitializing etc. There is zero need
>> to inspect the result there nor have a large window. Also, the
>> ability to save/load such workspaces is very useful (as well as
>> making them unclosable). All of these abilities are lost with the
>> Playground and the size of the Playground there would be too large.
>>
>> There is a use case for both facilities.
>>
>> Phil
>>
>>
>> On Fri, Oct 3, 2014 at 5:07 PM, Sven Van Caekenberghe
>> <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote:
>>
>> I too feel that GT-Tools in general use up too much screen
>> real estate. It is as if they were designed for big screens
>> and/or small fonts. But I am concentrating on functionality
>> (views) first, the look can change later on I guess.
>>
>> On 03 Oct 2014, at 17:05, Christophe Demarey
>> <Christophe.Demarey(a)inria.fr
>> <mailto:Christophe.Demarey@inria.fr>> wrote:
>>
>> > Hi,
>> >
>> > First I need to say, I love the new GT tools. It really goes
>> a step further.
>> > I just wanted to say that I find the Playground window quite
>> big (at least 1/4 of the whole Pharo window).
>> > I understand that the size is bigger than a simple workspace
>> to be able to display panes after clicking play but if you
>> just need to evaluate ()do-it, print-it) some code, it is
>> over-sized.
>> > Would it be possible to have a default window size smaller
>> and resize automatically if you need to display an inspector pane?
>> >
>> > Regards,
>> > Christophe.
>>
>>
>>
>
>
>
>
> --
> www.tudorgirba.com <http://www.tudorgirba.com>
>
> "Every thing has its own flow"
Oct. 3, 2014
Re: [Pharo-dev] First additions to GT-Inspector
by Ben Coman
Tudor Girba wrote:
> Yes, I like "Raw". Thanks for the ping:).
>
> Anyone against "Raw"?
>
> Cheers,
> Doru
>
>
Raw is good.
Oct. 3, 2014
Re: [Pharo-dev] About ways to participate in community and general negativity
by Thierry Goubier
Le 03/10/2014 21:48, stepharo a écrit :
>
> On 3/10/14 17:07, Thierry Goubier wrote:
>> Hi Esteban,
>>
>> I'm not sure my answer will please you or stef, and maybe I shouldn't
>> voice it, staying being a "customer" instead of contributing "the way
>> you want it". Hard words, but yours are hard too.
>>
>> I'd say simply that Pharo is successfull, fairly successfull for
>> someone like me. It allows me to engage in complex work, in what I do
>> best and what affords me to be paid and have the freedom to use Pharo.
>> Some of those things suppose that I maintain and extend fairly complex
>> packages on top of Pharo, and deal with permanent, multiple
>> overlapping interruptions (meeting, administrative work, travels,
>> etc...).
>
> Same here :)
>> Pharo is great, it allows me to build a significant activity on top of it.
>>
>> Some of the consequences of that success? I'm looking at things that
>> works now, not in Pharo 5, 6, or 7. I'm a bit frightened by grandiose
>> rewritting attempts which will be usable in a version or 2, at best,
>> and leave an unsatisfying "now" situation. I'll carefully evaluate
>> what new stuff is integrated. New stuff I look to see if they are
>> usable (libcgit integration, TxText) and what I see is stuff that
>> builds on unstable core libs extensions (NativeBoost, Athens)
> Why Athens would be unstable?
> or nativeBoost?
NativeBoost is not unstable for me, but why libcgit is on a bleeding
edge NativeBoost version then? Athens is stable for me, but I believe
that TxText requires a bleeding edge Athens.
>> on top of an already unstable version (4.0), and I'm really not
>> impressed by the software development process.
>
> what should it be?
> You know Igor will not be paid in a month from now, JB should find a job
> and esteban has two years to prove that the consortium flies.
> So if we do not clean the event and windowing systems, rick and thales
> will be in trouble. So we are fighting against time.
Thales is not an easy customer :) I know; apart from parser know-how,
there is nothing that I can sell outside (projects, etc..) about Pharo.
And if I'm not successfull, then its no more Pharo for me.
>> The end result is, when I see a bug, I'm already at least two versions
>> behind you guys...
>
> Why. I do not get why Pharo 3 would be unstable and that far from Pharo 20.
I'm on Pharo 3. Some of the stuff I'm interested is on Pharo 4 +
bleeding edge version of core Pharo subsystem... two versions off from 3
for me.
Libcgit is like that: its Pharo 4 + Bleeding edge native boost not yet
in Pharo 4 + libcgit (and from ESUG, I get that it will require an
entire refactoring of Monticello and a complete new on disk format).
It's really shaping up like a long, long term target.
>> so there's nothing worth reporting. There is some progress on the way
>> things are being done (thanks Marcus for doing the deprecation API
>> backporting on 3.0) and not much on others (and I speak of
>> methodology, not of new features being added on).
>>
>> If you have the feeling that I don't contribute the way I should or
>> the way you would like, step back and ask yourself if this is not my
>> "unspoken" way of me saying that I don't find a way to contribute, or
>> that contributing effectively is too costly.
>>
>> And look! This is not a matter of resources, but maybe a matter of
>> slowing down a bit, so that the poor community members with limited
>> resources like me that are not full time on Pharo 4.0 development may
>> catch up :) And please, no more rejection of feedback, even negative.
>> It just gives me the feeling you are overstreched, and that Pharo has
>> a problem setting its goals.
>
> Thierry,
> I do not have the impression that we go fast.
> You see we started Athens more than two years ago. It is a success for
> external tools like moose and Roassal but
> without TxText Athens will just be a nice package not change the face of
> Pharo and we will get there.
I believe you're right about those; but I'd say that the way it's being
done is a bit worrying. Why?
Because for me, TxText is already more advanced than the current text
editor: the ability to change the cursor, probably a better layout,
etc... Should already been integrated, then, if its already better. But
you still have the font bug that Alexandre complained about... how many
months ago? So, as long as its not resolved, TxText can't be integrated
(and additionally, I'm sure that there is aliasing issues on my
machines: fonts in Roassal don't look as nice as in Morphic).
And now, to make integration easier, we pile more stuff on top of the
existing, bound to be removed, infrastructure: Glamour, Rubric, etc...
And both Glamour and Spec don't make it easy to solve Morphic bugs.
I value your ambition a lot :) But I also feel that it stresses the Rmod
team, and it leaks over the community.
> Writing the chapter and maintaining Smacc is already a nice tribute to
> the community. Just continue that and we will be happy :)
Thanks. John gave me plenty of fixes and I'm preparing a new version of
SmaCC, and adding GUI tools (thinking of Guillaume needs and my needs as
well).
I certainly hope I'll be able to contribute on other things, still :)
Thierry
Oct. 3, 2014
Failing FuelMetalevel tests
by Max Leske
FYI: the failing tests in FuelMetalevel are due to this bug: https://pharo.fogbugz.com/f/cases/14081/Removing-a-trait-usage-raises-an-ex… <https://pharo.fogbugz.com/f/cases/14081/Removing-a-trait-usage-raises-an-ex…>
Oct. 3, 2014
Re: [Pharo-dev] About ways to participate in community and general negativity
by phil@highoctane.be
On Fri, Oct 3, 2014 at 11:03 PM, Alain Rastoul <alf.mmm.cat(a)gmail.com>
wrote:
> Le 03/10/2014 22:10, stepharo a écrit :
>
> Hi Stef,
>
> I like your metaphor , and yes, I really hope to share my personal soup
> with Pharo community asap. A soup about databases, json, streaming/map
> reduce stuff I've been thinking (and still thinking) for a while now. All
> of that still in an alpha or infancy step now, but I'm working hard on that
> (big problem for me is time - I'm greedy on that, plus lot of stress at
> work).
> btw, I'm confident about Pharo technology, spur and 64 bits, and it is a
> great move forward :).
> May be I'll fail -it would not be the first time- but anyway, if I can
> contribute with Pharo (bugs, doc or whatever is accessible to me), I will.
> Just because I prefer Pharo over dotNet or Java
> :)
>
I've stopped doing Java and made a decision to do Pharo. It is a business
bet, we'll see how it unfolds. (Not going bad at the moment, it pays all of
the bills for a couple months).
Phil
>
> Regards,
>
> Alain
>
>
> Thanks alain.
>>
>> Here is my metaphor: I help myself and share my "soup of stones" with
>> people that want to improve our soup of stones.
>> At the end our soup may be great.
>>
>> Another way to present my metaphor is: "focus on what you need and
>> change the system (and send us fixes/enhancements) on what you need.
>> Because if you do not do it, then why a guy not needing it would need to
>> spend time."
>> ah to grow the market.... well Spur, 64 bits, better FFI, decent events,
>> automated build for VM and many many other things are already in the
>> pipeline and
>> (none of them is about research :) you can trust me on that
>>
>> Stef
>>
>>
>
>
>
Oct. 3, 2014
Re: [Pharo-dev] playground size
by phil@highoctane.be
Well, my Spotlight looks like this:
[image: Inline image 1]
You'll notice the $<expr> to execute commands.
Works well. Code is here:
http://www.smalltalkhub.com/#!/~philippeback/HOExtras/packages/Tools
Tools is an hefty package. Always interesting to dig in there. Looks like
there is SourceWebBrowser subclassing Workspace and a UserManager.
Never heard of those. It feels like an open world game. It is really nice
to be able to dig as deep as one wants in those areas.
Phil
On Fri, Oct 3, 2014 at 10:57 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
> This is indeed a relevant use case, and we are already thinking about this
> issue for quite a while. The playground or even the workspace are not
> appropriate for things that need to live for a short time only.
>
> I would like to have an interface that comes, let's me enter my command
> and then vanishes. Similar to the spotlight interface. And once we will be
> on this, we will also make it a search interface... remember that Pharo4 is
> about tooling so now is the time to dream and do :).
>
> Doru
>
> On Fri, Oct 3, 2014 at 10:38 PM, stepharo <stepharo(a)free.fr> wrote:
>
>> Yes your use case make a lot of sense.
>>
>> I am using GT in 3.0 and the inspector is indeed supercool.
>>
>> Now, I've the standard Workspace on Cmd-o Cmd-w and the Playground on
>> Cmd-g. Depending on the task, one or the other is better.
>>
>> I am using Workspaces as a kind of command prompt in Pharo to set some
>> state of the system, reinitializing etc. There is zero need to inspect the
>> result there nor have a large window. Also, the ability to save/load such
>> workspaces is very useful (as well as making them unclosable). All of these
>> abilities are lost with the Playground and the size of the Playground there
>> would be too large.
>>
>> There is a use case for both facilities.
>>
>> Phil
>>
>>
>> On Fri, Oct 3, 2014 at 5:07 PM, Sven Van Caekenberghe <sven(a)stfx.eu>
>> wrote:
>>
>>> I too feel that GT-Tools in general use up too much screen real estate.
>>> It is as if they were designed for big screens and/or small fonts. But I am
>>> concentrating on functionality (views) first, the look can change later on
>>> I guess.
>>>
>>> On 03 Oct 2014, at 17:05, Christophe Demarey <
>>> Christophe.Demarey(a)inria.fr> wrote:
>>>
>>> > Hi,
>>> >
>>> > First I need to say, I love the new GT tools. It really goes a step
>>> further.
>>> > I just wanted to say that I find the Playground window quite big (at
>>> least 1/4 of the whole Pharo window).
>>> > I understand that the size is bigger than a simple workspace to be
>>> able to display panes after clicking play but if you just need to evaluate
>>> ()do-it, print-it) some code, it is over-sized.
>>> > Would it be possible to have a default window size smaller and resize
>>> automatically if you need to display an inspector pane?
>>> >
>>> > Regards,
>>> > Christophe.
>>>
>>>
>>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
Oct. 3, 2014