- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Migration morph objects from 1.1 to 1.2

by Marcus Denker

On Mar 29, 2011, at 10:26 PM, Denis Kudriashov wrote: > > But I really want ask where I can read about morphic changes between 1.1 and 1.2 pharo. http://code.google.com/p/pharo/issues/list?can=1&q=Milestone%3D1.2 too much to be useful, I fear. We need to a) automatize releases so we can release more often b) automaize change reporting of releases. Marucs -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 29, 2011

Re: [Pharo-project] Migration morph objects from 1.1 to 1.2

by Marcus Denker

On Mar 29, 2011, at 10:30 PM, Denis Kudriashov wrote: > Thanks for reply. > > I should search mails first. > We should have added that fix to 1.2, not just 1.3.... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 29, 2011

Re: [Pharo-project] Migration morph objects from 1.1 to 1.2

by Denis Kudriashov

Thanks for reply. I should search mails first. 2011/3/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi denis > > Check the archive of the list since we already explained it at least two > times :) > Let us know if you have questions after. > Basically turning the last dictionary into a SharedPool. > We should finish to clean the sharedPool now. > > > Stef > > On Mar 29, 2011, at 10:12 PM, Denis Kudriashov wrote: > > > Ok, I load my morph. > > > > I just implement "TextConstants class>>at: aSymbol" with: "^classPool at: > aSymbol". > > Now all work good. But I want to now what really changed in TextConstants > stuff? > > > > > > 2011/3/29 Denis Kudriashov <dionisiydk(a)gmail.com> > > Hello > > > > I have many morphs saved in files by smartReferenceStream. I doing it in > pharo1.1 image. > > Now I want to load this objects to pharo1.2. > > When I doing this I have exception about absent TextConstants stuff. My > saved Morph containes textMorph. > > I know pharo1.2 has textMorph refactored and TextConstants was removed. > > > > How old object can be migrated to new stuff? Is some rules exists? > > For example, when I import morph from file (created in pharo1.1) I see in > debugger "TextConstants class at: index" where "index=#DefaultTabsArray" > > > > Best regards, > > Denis > > > > > > >

March 29, 2011

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image

by Igor Stasenko

On 29 March 2011 22:18, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Pharo 1.2.1 looks good so far, except for the GLMOrangeUITheme that is >> still in a circular dependency. >> >> Lukas > > Can you open a ticket? > I want to clean all the themes soon in 1.3 > > i wonder how it is happen that this bug not eliminated before switching to 1.3 line? i remember that we fixed it few updates later. > Stef > > -- Best regards, Igor Stasenko AKA sig.

March 29, 2011

[Pharo-project] Issue 3911 in pharo: Change updater to allow updating a release image

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3911 by marcus.d...(a)gmail.com: Change updater to allow updating a release image http://code.google.com/p/pharo/issues/detail?id=3911 right now (1.2 and 1.3), the update logic checks for some character in the version number to allow updating and image. Now the fact is that people only look at released images. Leading to lots of suggestions of fixes directly after a release, but no way to update that release. Allowing the update process to update release images will remove a *significant* amount of work from the release manager who now needs to do a complete release cycle even for point releases (1.2.1a followed by 1.2.1 folowed by 1.2.2a followed by 1.2.2... with lots of manual intervention).

March 29, 2011

Re: [Pharo-project] Migration morph objects from 1.1 to 1.2

by Denis Kudriashov

2011/3/30 Marcus Denker <marcus.denker(a)inria.fr> > > No, I don't think so... keeping the system compatibel at that level is > *really* difficult... simple refactoring can be done > (e.g. etoys did that for years), but complex changes in the image will be > nearly impossible if you require serializability compatibility > at that level. (especially when using image segment style low-level > serialization). > > Being compatible on that level was religion for Squeak (and it's even > today). I personally don't think that what we have is > valuable enough to define compatibility on that level to be more impotant > than being able to evolve the system. > > The system as it is now is just not good enough to have any form of future > with it, so trading "improve it" vs. "be backward compatible > on a binary level" is selection between having the past and having a > future... > > I agree with you absolutelly. And I solve my problem :) With smalltalk compatibility is not problem to my mind. Just open debugger and you can do everything :) But I really want ask where I can read about morphic changes between 1.1 and 1.2 pharo. With this my migration should be easy

March 29, 2011

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image

by Marcus Denker

On Mar 29, 2011, at 10:18 PM, StÃ©phane Ducasse wrote: >> Pharo 1.2.1 looks good so far, except for the GLMOrangeUITheme that is >> still in a circular dependency. >> >> Lukas > > Can you open a ticket? We can do a 1.2.2... and add the TextContstants at:put: fix, too. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 29, 2011

Re: [Pharo-project] Migration morph objects from 1.1 to 1.2

by StÃ©phane Ducasse

Hi denis Check the archive of the list since we already explained it at least two times :) Let us know if you have questions after. Basically turning the last dictionary into a SharedPool. We should finish to clean the sharedPool now. Stef On Mar 29, 2011, at 10:12 PM, Denis Kudriashov wrote: > Ok, I load my morph. > > I just implement "TextConstants class>>at: aSymbol" with: "^classPool at: aSymbol". > Now all work good. But I want to now what really changed in TextConstants stuff? > > > 2011/3/29 Denis Kudriashov <dionisiydk(a)gmail.com> > Hello > > I have many morphs saved in files by smartReferenceStream. I doing it in pharo1.1 image. > Now I want to load this objects to pharo1.2. > When I doing this I have exception about absent TextConstants stuff. My saved Morph containes textMorph. > I know pharo1.2 has textMorph refactored and TextConstants was removed. > > How old object can be migrated to new stuff? Is some rules exists? > For example, when I import morph from file (created in pharo1.1) I see in debugger "TextConstants class at: index" where "index=#DefaultTabsArray" > > Best regards, > Denis > >

March 29, 2011

[Pharo-project] Issue 3910 in pharo: -0.01s2 printString is loosing its sign

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com CC: nicolas....(a)gmail.com New issue 3910 by stephane...(a)gmail.com: -0.01s2 printString is loosing its sign http://code.google.com/p/pharo/issues/detail?id=3910 -0.01s2 printString loosing its sign

March 29, 2011

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image

by StÃ©phane Ducasse

> Pharo 1.2.1 looks good so far, except for the GLMOrangeUITheme that is > still in a circular dependency. > > Lukas Can you open a ticket? I want to clean all the themes soon in 1.3 Stef

March 29, 2011