Indeed we spent some time in Edinburgh looking at it :-) that was too long ago
:-(
The problem i see with the original debugger inherited from Squeak, in the
Pharo context, is that it is very sensitive to a lot of the core code in the
image. What this means is that the accelerated changes in Ph
Hi Stef, I have skimmed the proposal in the included class comment. It is
beyond my knowledge really to comment specifically. Looks great! :-)
I picked up on the reference to 64k classes limit. Whilst at the moment I can't
imagine a Pharo system needing that many classes, the VW system I am work
r 7, 2012, at 2:33 PM, Michael Roberts wrote:
>
> > Hi, i tested the fix in 1.4 and it seemed to work fine.
> >
> > http://code.google.com/p/pharo/issues/detail?id=5445
> >
> >
> > thanks,
> > Mike
> >
>
>
>
Hi, i tested the fix in 1.4 and it seemed to work fine.
http://code.google.com/p/pharo/issues/detail?id=5445
thanks,
Mike
sp module or C library? What about collections?
>
>
> Thanks for your help. It really did help.
> Gerry
>
>
>
> -Original Message-
>> From: "Michael Roberts"
>> To: Pharo-project@lists.gforge.inria.fr
>> Date: 01/05/12 02:18
>&
I like the idea. I wonder how you resolve dependencies & failures.
Cheers,
Mike
On 7 Jan 2012, at 11:39, Stéphane Ducasse wrote:
> Hi guys
>
> What is the process we want?
> What I would like is
>
>MetaRepoForPharo13Inbox were everybody can write
>and a jenkins process that loads
On 5 Jan 2012, at 05:50, "Gerry Weaver" wrote:
> Hi,
>
> Perhaps I should just take a shot at explaining what I'm having trouble
> understanding.
>
>
> My current take on the environment is that an image is basically a container
> that holds everything in the application.
Indeed.
> In d
Ok I see. Have you measured the collisions on a very big graph? What stats do
you get?
Cheers Mike
On 13 Dec 2011, at 08:37, Mariano Martinez Peck wrote:
>
>
> On Tue, Dec 13, 2011 at 8:43 AM, Michael Roberts wrote:
> Hi Mariano, when I read this thread I was a bit confused tha
Hi Mariano, when I read this thread I was a bit confused that you wanted an
IdentitySet that used #hash. From that statement it sounded like you just
wanted a Set. This would allow any object to define its own hash and
importantly what equality means with #=. So if you want to delegate that to
the
I wonder if it would be possible for you to come up with a separate
format, whose purpose was only ever for this purpose. It would not
need to be efficient in any respect, just something you could write
out to file (say) during the process. It would be a shame to rely on
the whole graph needing to
I find the thread a bit confused in the sense
Dictionary *new* at: x ifAbsentPut: y
does not make sense (is academic), because the new dictionary will
never have x as a key. So why profile it and use that as reasoning?...
whereas
myDict at:x ifAbsentPut: y
is more interesting.
In my experienc
7 PM, Stéphane Ducasse
wrote:
> Hi guys
>
> I'm a bit busy (too much to follow carefully).
> Just tell me what I should integrate and I will do it fast.
>
> Stef
>
> On Sep 8, 2011, at 2:37 PM, Michael Roberts wrote:
>
>> So I found the bug with the first assignm
So I found the bug with the first assignment. It is caused by a difference
between squeak and Pharo in SortedCollection. (on my phone so will be brief)
In Pharo the debugger map collection gets sorted and asked for an index for a
given pc. It is supposed to answer 1 because there is no match and
if you could select different rendering of that area that would be
nice (e.g on context menu). i would add an option to display it in a
table widget. it could allow simple filtering & sorting etc, assuming
we had such a widget (essential really) . that would allow compact but
powerful slicing of th
is #abstractSourceMap
>> >> There is a first step to obtain
>> >> CompiledMethod>>rawSourceRangesAndMethodDo:
>> >> This is the most important part.
>> >> The rest is again a mapping from concretePC (instruction byte offset)
>> >>
this is brilliant!...
one tiny thing i noticed on page 22/24 if you print the method source,
the editor highlight only covers the first line of the multi-line
output. Perhaps it only ever expects single line highlights.
cheers,
Mike
On Tue, Sep 6, 2011 at 9:27 PM, laurent laffont
wrote:
> Funny
nice idea. Marcus mentioned this last night. One thing I would say,
potentially 1.4 list below is quite a bit of work (i don't know)? so can we
time box it? And then push on the bug fixes.
cheers
Mike
On Fri, Aug 26, 2011 at 5:38 PM, Stéphane Ducasse wrote:
> Hi guys
>
> I was thinking about o
ok i'll take a look and try add some test cases to the analyser
Mike
On Fri, Aug 26, 2011 at 5:16 PM, Stéphane Ducasse wrote:
> While working on a chapter on blocks I got the following problems
>
>
>
> foo
>
>| a|
>a := 0.
>^ {[a :=2] .[a]}
>
>
> | res |
> res := ZnC
ers,
Mike
On Fri, Aug 26, 2011 at 9:00 AM, Michael Roberts wrote:
> I will try it in my image, thanks!
>
> I got a little further with Andres. The thing about the loop example is
> that the block is copying values outside its scope. You get get extra
> bytecodes at the start of the me
gt; an iterator and a sort of visitor on byteCode instructions.
> >>>> So this is not really interesting.
> >>>>
> >>>> The more interesting part is #abstractSourceMap
> >>>> There is a first step to obtain
> CompiledMethod>>rawSourceRan
http://code.google.com/p/pharo/wiki/DebuggerInternals
t; would be amazed to see it much different.
> > It's now late, and my spare time is off, but you have clues to get
> > more insights. I wish you good debugging, and come back to me if it
> > ever goes in deeper complications.
> >
> > Cheers
> >
> > Nicolas
>
>
> Ok I'm curious to know then.
Here is a little trace from this example method:
toDoOutsideTemp
| temp collection |
collection := OrderedCollection new.
1 to: 5 do: [ :index |
temp := index.
collection add: [ temp ] ]
Trace is start,stop position of the highlight for each 'step over'.
Whilst
Nicolas thanks! super you have even a few minutes.
Even though Squeak has the problem, it is subtly different. I will
post my little scaffolding class maybe the end of this week which just
helps to slowly step a debugger through. And do this in different
images.
What would be great, on a wiki pa
In inbox:
Name: Tools-MikeRoberts.658
Issue: 4697
-Fix to OrderedCollectionInspector that fails #fieldList on
OrderedCollections that are not fully formed.
I did a little fix for this bug, that prevents the debugger stepping
into OrderedCollection new. I mention this to folks working on t
I think for the debugger, we all live with the bugs. I mean, we (I)
unfortunately made the situation worse with the introduction of the
closures around 1.0/1.1 and it has never been fixed. It is hard to fix
too, this stuff is not simple. I contacted a few people quietly maybe
a year ago to see if
folks, following recent problems with SqueakSource we (Stef and
myself) are moving Pharo 1.4 repository to ss3 running at GemStone.
http://ss3.gemstone.com/ss
We are in the middle of the migration, and will let you know when it
is finished.
cheers,
Mike
gt;- removing reference to SourcedMethodReference and friends (veronica
> should add a better instance creation method on methodDefinition
>because I did most of the work and realized after that I was using the
> wrong api.
>- and we have a long time of open issue on the tracker
>
>
Hi, just wondering if there were any pharoers at Camp Smalltalk this
weekend? If so any tasks lined up?
cheers,
Mike
is MyClass a domain class or a (unit) test class?
thanks,
Mike
On Sun, Jul 17, 2011 at 10:45 PM, Sean P. DeNigris
wrote:
> I keep coming up against this situation over and over in testing.
>
> MyClass>>doSomethingWorthTesting
> ...
> now := DateAndTime now.
> ...
>
> I want to control D
Ok. And is the idea to build a new core debugger in this effort? I wanted to
check we would only build 1 debugger model; and to know where it is. (I only
see one in glamourst source).
Thanks
Mike
On 6 Apr 2011, at 07:01, Stéphane Ducasse wrote:
> It is not.
> The idea is to have a default br
Hi, how does it relate to glamourost?
thanks,
Mike
On Tue, Apr 5, 2011 at 7:57 PM, Stéphane Ducasse
wrote:
>
> On Apr 5, 2011, at 5:31 PM, Alexandre Bergel wrote:
>
>> Hi Guys,
>>
>> Maybe I missed part of the discussion, but what is Nautilus?
>
> A new browser :)
> Supporting
> - groups
n Sun, Mar 20, 2011 at 11:03 PM, Marcus Denker wrote:
>
> On Mar 20, 2011, at 11:44 PM, Michael Roberts wrote:
>
>> Hi, a meta question...
>>
>> when i made changes to SystemVersion I put a comment in that method
>> thinking it would not make sense to use it.
>
Hi, a meta question...
when i made changes to SystemVersion I put a comment in that method
thinking it would not make sense to use it. You have published a use
for it ;-)
is there a reason you did not want to do
SystemVersion current suffix: '1a'
that was the main reason i made the changes so i
ok cool. Yes, Torsten is right that i want to load this into Core. Not
just for deployment though, but i like working with smaller images.
It is also a way of exercising the core image and trying to improve
that code base, testing it etc.
What i was really after which Dale answered was more detail
n
>
>
> Le 14/02/2011 22:52, Sven Van Caekenberghe a écrit :
>>
>> Micheal,
>>
>> On 14 Feb 2011, at 22:40, Michael Roberts wrote:
>>
>>> Hi, there is a recent (I don't know how old) feature where text areas
>>> now highlight the sel
Hi, there is a recent (I don't know how old) feature where text areas
now highlight the selected text in all parts of the same text pane.
Does this feature have a name and a setting to control it?
thanks,
Mike
Hi, i want to load Seaside into Pharo 1.2 core. I have followed
various threads talking about doing this with metacello, but beyond
the simple tutorial i have worked through I am lost. I don't want to
have to specify each package by hand.
I can do this...
Gofer new
squeaksource: 'Metacel
yes as Adrian pointed out debugger highlighting is broken in Pharo.
Has been since the very beginning. what we need ideally is a set of
test cases describing the desired behaviour. i struggled to simulate
this, i am not sure what a good test harness is for the debugger.
ideally the highlighting can
I suspect one reason there is so much inclusion of the content of the
existing thread is all the folks using Gmail, which generally hides
quoted text very well. I wasn't going to post, but then i didn't see
it mentioned. It's the reason I get lazy with quoting
cheers,
Mike
I think the idea was that the deprecation scheme was fairly simple,
and slightly better than just the original deprecated: . What you
describe looks a bit over the top to me. just my 2p...
cheers,
Mike
2010/10/24 Levente Uzonyi :
> On Sat, 23 Oct 2010, Mariano Martinez Peck wrote:
>
>> On Sat, O
regarding streaming frameworks, has anyone looked at
http://code.google.com/p/xtreams/ ? the podcasts on it sounded
interesting.
cheers,
Mike
On Tue, Oct 5, 2010 at 5:02 PM, Stéphane Ducasse
wrote:
> Noury,
>
> One of the other aspects that I find important is elementary efficie
surely the test runner should run with deprecations turned off? It is
not a bug. I explicitly wrote the test, to test it actually worked.
When i was running all the system tests by hand in 1.0, you could not
run them without turning deprecations off. it was the first thing i
did when i scripted it.
Depends what level
At a high level you could use OSProcess to invoke the correct Python
command line and do it in a different process. Or you could use some
socket protocol if you have a python interpreter already running
waiting for commands. or a mixture of the two...
At a lower level you co
> Issue 2553: SystemVersion lost its state in 1.2
thanks Marcus. I have added 3013 to deprecate #version:.
cheers
Mike
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-pr
why that wouldn't work.
Cheers mike
On 13 Sep 2010, at 00:26, Michael Roberts wrote:
When I looked through the code I imagined one could implement the
nesting by just maintaining a stack on the progress initiator sort
of like
...
On 11 Sep 2010, at 16:45, Eliot Miranda
wrote:
When I looked through the code I imagined one could implement the
nesting by just maintaining a stack on the progress initiator sort of
like
...
On 11 Sep 2010, at 16:45, Eliot Miranda wrote:
Hi Ralph,
On Sat, Sep 11, 2010 at 1:05 AM, Ralph Boland
wrote:
> Hi, i don't know why thing
Hi, i don't know why things are done the way they are...
Is your question how the exception mechanism works, or why it is
needed to be done with an exception? as opposed to say doing it some
other way?
The direct answer to your question is that given it is implemented in
terms of exceptions, the s
>>
> Cool, I appreciate you getting the ball rolling - I am trying to push it
> further! (and I don't know too much about sockets)
no worries. I have found this guide really useful: http://beej.us/guide/bgnet/
Even if you don't read C, there are lots of comments throughout.
cheers
Mike
__
Hi,
it just so happens I wrote that section on the colab wiki 1) primarily
to play around with the wiki engine 2) I was debugging Magma socket
issues and I could not find decent cookbook / snippets to illustrate
some simple examples and how to test it outside of Pharo itself. I
just thought as an
I just put the status back to fixed and changed the milestone.
http://code.google.com/p/pharo/issues/detail?id=1068
not sure what the process is for fixes spanning multiple versions. can
do it separately in the future?
Mike
___
Pharo-project mailing l
Merged against 1.1. Please integrate for the one-click release.
Name: HostMenus-MikeRoberts.56
Author: MikeRoberts
Time: 4 August 2010, 3:19:49 pm
UUID: 142b944e-e012-46ac-bc82-52889e20b4e7
Ancestors: HostMenus-MarcusDenker.54
-Relax lookup for OS X Quit menu item otherwise it breaks really
easil
=Platform integration=
-multiple host windows
-deeper platform look 'n feel
=Documentation=
cheers
Mike
On Mon, Aug 2, 2010 at 8:50 PM, Stéphane Ducasse
wrote:
> Hi guys
>
> with the experience around the XMLRPC project, ESUG wants to change strategy
> to help growing business at the techn
clearly not the case and I do not like that.
>
> Stef
>
> On Aug 2, 2010, at 10:03 PM, Stéphane Ducasse wrote:
>
>> this is strange because I thought that we get the complete history chain in
>> the Pharo folder since we always
>> merge and republish.
>>
&g
shouldn't that be added as a package to the general images? otherwise
this will always be a potential error when pushing fixes?
cheers,
Mike
2010/8/2 laurent laffont :
> On Mon, Aug 2, 2010 at 2:43 PM, Michael Roberts wrote:
>>
>> Hi,
>> i am trying to publish a fix
Hi,
i am trying to publish a fix, but I get MC error can't find
HostMenus-LaurentLaffont.53. It is the ancestor of
HostMenus-MarcusDenker.54 but does not seem to be in the /Pharo
package. Where did it go?
thanks,
Mike
___
Pharo-project mailing list
Pha
iliar but i have had a poke around. I prefer Pharo anyway. it is
less verbose. I will see if i can change it and get it to work.
thanks,
Mike
On Sat, Jul 31, 2010 at 1:04 PM, Michael Roberts wrote:
>>
>> Michael, it is working for me. Not only in the OneClick but also with the
>
sounds tricky. at the very least add a checker to a menu somewhere so
we can start to use it. You wouldn't need to that deeply integrate it
in the first instance...
do you need to match the existing semantics exactly? I don't think
it's good that we can get into these situations. Perhaps we should
>
> Michael, it is working for me. Not only in the OneClick but also with the
> image and the Squeak 4.2.5beta1U
> what is exactly what it is NOT working for you?
like I said literally the host menu quit menu item does not do
anything. exactly the symptom described in the original issue. this is
w
> - SystemVersion current majorMinorVersion prints:
>
> PharoCore 1.0: 'PharoCore1.0'
>
> PharoCore 1.1: 'Pharo1.1'
>
the version object has been downgraded again. the version string
needs to be nil and it keeps on getting broken. I will deprecate the
mechanism once i recheck the package issues.
I gave the latest release a spin and it seams quit doesn't work (again).
old reference ->
http://code.google.com/p/pharo/issues/detail?id=1068
can someone confirm? if so do we want a new issue or reopen the old one?
Also the host menu is not consistent with the world menu. for example
the tools
>> 2) e.g you move somethings to *Tools and some things to *Tools-Explorer
>> is that not going to create the same problem that happened to System,
>> with both parent and child packages defined in the same image?
>
> There's only one MC package named Tools and this package is not
> splitted. But w
Hi,
1) do MC packages already exist for all re-categorization?
2) e.g you move somethings to *Tools and some things to *Tools-Explorer
is that not going to create the same problem that happened to System,
with both parent and child packages defined in the same image?
thanks,
Mike
__
ldren?
thanks,
Mike
On Sun, Jul 4, 2010 at 3:01 PM, Stéphane Ducasse
wrote:
> there is probably a problem since we worked with pavel on reorganization at
> the package level.
>
> Stef
>
> On Jul 4, 2010, at 3:53 PM, Michael Roberts wrote:
>
>> I am about to post a deprecati
I am about to post a deprecation of SystemVersion>>version: to 1.2 but
once i have made my changes i see something odd in MC browser:
dirty packages
* System (System-StephaneDucasse.6)
* System-Support (System-Support-StephaneDucasse.317)
Stef, have you started to publish System as a whole? did y
ses too?that
would not make a lot of sense to me.
So what do you think?
mike
Stef
On Jun 17, 2010, at 6:42 PM, Michael Roberts wrote:
I'm missing something. Why do we need to adopt the (copy of)
methods and not just adopt the package as lukas said? I thought
we wanted core to
PM, Michael Roberts wrote:
I'm missing something. Why do we need to adopt the (copy of)
methods and not just adopt the package as lukas said? I thought we
wanted core to get smaller over time and better modularised anyway?
We would just need to track a stable version rather than
mainta
I'm missing something. Why do we need to adopt the (copy of) methods
and not just adopt the package as lukas said? I thought we wanted core
to get smaller over time and better modularised anyway? We would just
need to track a stable version rather than maintaining our own branch.
Surely it
Hi
You asked this question before I think on the users list.
Someone would have to write a parser for the specific formats
returned. In this case i think they are a ms specific text format. The
more common auto config files are JavaScript and require a parser or
mini execution environment t
, 2010 at 2:23 PM, Stéphane Ducasse
wrote:
> do you have a pointer?
>
> Stef
> On Jun 13, 2010, at 3:17 PM, Michael Roberts wrote:
>
>> Hi,
>>
>> SystemVersion current is missing all the state (i put some effort into
>> making that). I'm not sure wh
Hi,
SystemVersion current is missing all the state (i put some effort into
making that). I'm not sure when it got lost but should really be
fixed.
thanks,
Mike
On Sat, Jun 12, 2010 at 1:37 PM, Marcus Denker wrote:
>
>
> https://gforge.inria.fr/frs/download.php/27158/PharoCore-1.2-12003
With a few sprints coming and such enthusiasm for our tools this is an
opportune thread to remind folks the debugger itself needs some
serious work on it. I would suggest doing this first before adding
features to it. Any volunteers?
1) pressing send does not always change the highlighted c
timeouts. The timeout block
>>> can simply raise an exception or assert false, and there is no need to
>>> disable timeouts where they do not belong.
>>>
>>> Bill
>>>
>>>
>>> From: pharo-project-boun...@lists.gfo
yes think it's a good idea. I'm not sure the granularity that's
required though.
mike
On Saturday, May 29, 2010, stephane ducasse wrote:
> Hi guys
>
> in Squeak andreas introduced the idea of test time out
> Do you think that this is interesting?
>
> Stef
>
> SUnit
> -
> All test cases now h
I am surprised too. would it not be safer to just apply the same
reversion of the code so that 1.1 is the same as 1.0? Then when
someone has the time to do a full review, a "new" network can be
applied to the start of a dev cycle, with some form of integration
tests.
cheers,
Mike
On Tue, May 18,
way back then there was a thread about not calling Pharo what we
should not call it but we have as a group consistently failed to
do this. i would suggest that if people can't drop using *it*, then we
have to give up. it is very difficult doing such brand management in
an online group. we shou
what are the exact problems with the network? lukas' email said that
the resolver behaviour had changed positively, not that there was an
issue. or did i miss read?
thanks,
Mike
On Mon, May 17, 2010 at 9:21 AM, Stéphane Ducasse
wrote:
> So what do you suggest
> beta for two three weeks
>
I don't know whether Miguel
> updated his Metacello config for Magma; I have not yet had time to get
> into Metacello or I would have done it.
>
> So how did you install this?
>
>
> On Fri, May 14, 2010 at 9:43 AM, Michael Roberts wrote:
>> Hi just trying to run th
You might disagree but it's what we decided. We should keep different
version tags so that we can use different update streams (sections
within) in the future.
Cheers mike
On Friday, May 14, 2010, Stéphane Ducasse wrote:
> I do not have strong feeling about that ;)
> Just busy :)
>
> On May 14,
Hi just trying to run the tests via the standard magma test
expression. So it is looking to see if Display exists. That's the
point on my mac I recognize that it annoyingly changes my screen
resolution :-)
anyway it is missing your ma extension to query the namespace.
Cheers
mike
On Friday, May
t; On May 13, 2010, at 7:53 PM, Michael Roberts wrote:
>
>> I have tried to load Magma in Pharo1.1 but have not yet succeeded. I
>> don't have a lot of time i'm afraid. the existing Metacello config
>> doesn't load the right packages, nor the list on the wi
I have tried to load Magma in Pharo1.1 but have not yet succeeded. I
don't have a lot of time i'm afraid. the existing Metacello config
doesn't load the right packages, nor the list on the wiki page (using
installer) it seems. I am missing an implementation of a method
maAt:ifPresent:ifAbsent: on S
On Sun, May 9, 2010 at 9:06 AM, Lukas Renggli wrote:
>> We should run the Magma test suite.
>
> Could you do that?
Yes, i'm just asking Chris what the latest packages are. My emails on
the subject don't seem to match the repository any more.
>
>> It was not just related to those NetNameResolver
We should run the Magma test suite.
It was not just related to those NetNameResolver methods IIRC. The API
changed very slightly. Also, the lazy initialization of useOldNetwork
made it really difficult to see what was going on.
I'll have a dig around.
cheers,
Mike
On Sat, May 8, 2010 at 4:54 P
I agree with Lukas, although I have already expressed these sentiments
in previous threads when I raised my own design concern. For me the
point is that the standard old class comment / method comments is not
expressive enough to be integrated into such a help system. There is a
desire to annotate
it's much more important to enable documentation to be easily written.
Thanks for putting it in
mike
On Saturday, May 1, 2010, Stéphane Ducasse wrote:
>>
>> Hi,
>>
>> The help core package and the according tests package are ready for
>> integration in the pharo inbox. After talking today with
starting point to look for documentation, at
> http://docs.pharo-project.org
> Cheers,
> Laurent Laffont
>
>
> On Wed, Apr 21, 2010 at 10:46 PM, Michael Roberts wrote:
>>
>> Laurent, i think this is a tension that a number of us feel. should we
>> put documentat
Laurent, i think this is a tension that a number of us feel. should we
put documentation in the colab book, or in the system? For me the two
are distinct. The book, ultimately, should read as a book. That is
there is a logical flow from start to finish and the content is
consistent, from start to
thisContext reifies the activation contexts (if that is the exact way
to describe it?). I don't believe you have it in VA. So you can just
walk it. If you look for some of the fatal error handling logic you
can see how the debug log is written out on crash containing the
stack. Cheers mike
On Wedn
Ducasse
wrote:
> Cool I will do that too.
> Can you create a book entry with that because this is cool :)
>
> Stef
>
> On Apr 21, 2010, at 8:40 AM, laurent laffont wrote:
>
>>
>>
>> On Tue, Apr 20, 2010 at 11:21 PM, Michael Roberts wrote:
>> i'm
i'm not sure what either of you mean. I want there to be no UI choice
and the system just looks higher up in the file system hierarchy.
certainly environment variables or a .pharorc style file would solve this.
thanks,
Mike
On Tue, Apr 20, 2010 at 6:33 PM, Chris Muller wrote:
> Whether the user
Regarding sharing a package cache, I made a change a while ago that
searches up the directory tree to see if there is one higher up. You
then don't have to change the fresh image. What do you think?
Cheers
mike
On Tuesday, April 20, 2010, Stéphane Ducasse wrote:
>
> On Apr 20, 2010, at 1:00 AM,
there is a directory package-cache in the same level that the image
lives. are you doing this in the 1-click image or a normal image?
assuming you can easily see the directory you can just delete it. I'm
sorry i'm not more specific about the error. I'm hoping someone else
chips in with a better des
Hi, I think this is a common error caused by corrupt mcz files. Can
you clear your cache and try again?
thanks,
Mike
On Mon, Apr 19, 2010 at 6:47 PM, Sean P. DeNigris wrote:
>
> http://code.google.com/p/pharo/issues/detail?id=2327 :
> Pharo image: core
> Pharo core version: PharoCore1.1ALPHA #11
On Monday, April 19, 2010, Adrian Lienhard wrote:
> On Apr 19, 2010, at 09:10 , Stéphane Ducasse wrote:
>
>> On Apr 19, 2010, at 1:56 AM, Stephen Taylor wrote:
>>
>>> Henrik Johansen wrote:
>>>
Gotta love reddit...
>>> [...]
- "I don't know what Smalltalk is, and the site doesn't tell me
On Sunday, April 18, 2010, Tudor Girba wrote:
> Fixed.
>
> Doru
thanks!
Mike
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
cheers Lukas, can you check how it has rendered, i am not sure the
copy/paste has quite worked?
Mike
On Sun, Apr 18, 2010 at 10:57 AM, Lukas Renggli wrote:
>> yes i was going to copy it into the new help section. Can someone with
>> access to book.seaside.st send me the original markup? or tell
yes i was going to copy it into the new help section. Can someone with
access to book.seaside.st send me the original markup? or tell me how
I can view the pier source. I have added a link for now.
I also created a sandbox for trying things out.
thanks,
Mike
2010/4/18 laurent laffont :
> OK than
On Sun, Apr 18, 2010 at 8:21 AM, Stéphane Ducasse
wrote:
> we should release 1.1 much faster :)
> like that people will be able to get all the fixes
yes ;)
for tagging fixes for 1.0 maintenance, should we use a milestone 1.0.1
in the tracker? - is this code candidate for 1.0.1?
cheers,
Mi
Stef, Doru i have got confused as well with where pages get added. It
makes sense once you understand what Pier is doing, but i have put too
many pages in the wrong place.
Anyway i have created a help chapter, with some tips. Please feel
free to correct or add more.
cheers,
Mike
___
1 - 100 of 360 matches
Mail list logo