Should we tag issue 12144 for Pharo3? At the moment, this is only an isseu for
the debugger, but is is related to spec. We can expect more apps/developer
suffer from this in the future and I dont want to see, everyone invents its own
workaround.
I made to slices, with the first the textmodel
The debugger is very important and since we have a new one, the QA is essential.
So I vote for doing it right in 3.0
On 15 Feb 2014, at 11:02, Nicolai Hess nicolaih...@web.de wrote:
Should we tag issue 12144 for Pharo3? At the moment, this is only an isseu
for the debugger, but is is related
Ben Coman wrote:
Something very strange going on for me with Monticello in build
30763. The Packages I make changes in are not showing up starred at
the top, other packages are. When I select one of these other
packages and the Pharo30/main repository and click Changes, then it
reports No
the repository is here:
http://www.smalltalkhub.com/#!/~PharoExtras/XMLWriter/contributors
my username is pdebruic..
I'd like to add a #stable: method to the configuration
Thanks
Paul
So far I haven't been able to reproduce this. Maybe this is the result
of some network errors I had earlier.
cheers -ben
b...@openinworld.com wrote:
Ben
Coman wrote:
Something very strange going on for me with Monticello in build 30763.
The Packages I make changes in are not showing up
Well... I do no think so. There is a fair amount of work regarding memory
profiling. Dereferencing is probably only a small piece off.
Anyway, we will have time to refine the project description
Alexandre
Le 14-02-2014 à 18:17, Levente Uzonyi le...@elte.hu a écrit :
On Fri, 14 Feb 2014,
FYI writing any decent production quality tool takes way more than 1
hour. IME writing *two* reference finders, it takes a bunch of effort
to make them work correctly, reliably, quickly, and in a useful way.
On 2/15/14 6:31 , Alexandre Bergel wrote:
Well... I do no think so. There is a fair
Thanks Olivier i will try with it for sure.
Thanks ben! i will procrastinate with the game too :P...
Levente, i'm working in a Slang compiler at language side that generates
assembly that is run then with nativeboost. Then primitives could be
changed, compiled individually, and run at runtime.
Third attempt
SLICE-Issue-12144-TextModelgetSelection-NicolaiHess.3
please review, I really don't know what would be the correct way to
handle selection from
a) TextModel to View (PluggableTextMorph)
b) View to TextModel
I now use TextModel#setSelection: for changes that should be announced
On Sat, 15 Feb 2014, Andres Valloud wrote:
FYI writing any decent production quality tool takes way more than 1 hour.
IME writing *two* reference finders, it takes a bunch of effort to make them
work correctly, reliably, quickly, and in a useful way.
I would agree with you if the building
On Sat, 15 Feb 2014, Guido Chari wrote:
Thanks Olivier i will try with it for sure.
Thanks ben! i will procrastinate with the game too :P...
Levente, i'm working in a Slang compiler at language side that generates
assembly that is run then with nativeboost. Then primitives could be
changed,
Well, I tried today using that to release some memory used by Roassal.
Let's say all the instances of ROElement. So I executed the following code:
ROElement allInstances do: [:el | el becomeForward: nil ].
The next second the image crashed. Then I thought that was because the
visualization was
All that I said was it takes way more than 1 hour.
The useful part comes in when e.g. inboundPointers reveals stuff
that should also be gone. So now you need a full blown reference
finder, and getting one of those to work quickly and correctly is not
trivial. Also with some objects you
13 matches
Mail list logo
