StartupPreferences bug

There was a change on the storeOn: method of StartupAction that is breaking things. Before it said: " aStream >> code printString" and now it has "code storeOn: aStream". I'm almost sure that the previous one is the correct one. We didn't one to print the object on the file, only the text for later running it or am i wrong?

Cheers,

Guido.

Mariano!

Yes, i'm seeing the same on last 2.0. I've made a little add-on for writing startup rules modular on the image and then a builder that generate startup files from those methods and i had to rollback to previous versions of the method i said for being able to store the rules on files.

Cheers,

Guido.

2012/9/20 Mariano Martinez Peck <[hidden email]>

Hi Guido. Is this still a problem?

On Wed, Aug 22, 2012 at 4:40 PM, Guido Chari <[hidden email]> wrote:

There was a change on the storeOn: method of StartupAction that is breaking things. Before it said: " aStream >> code printString" and now it has "code storeOn: aStream". I'm almost sure that the previous one is the correct one. We didn't one to print the object on the file, only the text for later running it or am i wrong?

Cheers,

Guido.

--
Mariano
http://marianopeck.wordpress.com

I'm looking forward to integrate this :)

On Thu, Sep 20, 2012 at 4:42 PM, Guido Chari <[hidden email]> wrote:

Mariano!

Yes, i'm seeing the same on last 2.0. I've made a little add-on for writing startup rules modular on the image and then a builder that generate startup files from those methods and i had to rollback to previous versions of the method i said for being able to store the rules on files.

Cheers,

Guido.

2012/9/20 Mariano Martinez Peck <[hidden email]>

Hi Guido. Is this still a problem?

On Wed, Aug 22, 2012 at 4:40 PM, Guido Chari <[hidden email]> wrote:

There was a change on the storeOn: method of StartupAction that is breaking things. Before it said: " aStream >> code printString" and now it has "code storeOn: aStream". I'm almost sure that the previous one is the correct one. We didn't one to print the object on the file, only the text for later running it or am i wrong?

Cheers,

Guido.

--
Mariano
http://marianopeck.wordpress.com

http://code.google.com/p/pharo/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty&groupby=&sort=&id=6728

On Mon, Sep 24, 2012 at 10:37 AM, Guillermo Polito <[hidden email]> wrote:

I'm looking forward to integrate this :)

On Thu, Sep 20, 2012 at 4:42 PM, Guido Chari <[hidden email]> wrote:

Mariano!

Yes, i'm seeing the same on last 2.0. I've made a little add-on for writing startup rules modular on the image and then a builder that generate startup files from those methods and i had to rollback to previous versions of the method i said for being able to store the rules on files.

Cheers,

Guido.

2012/9/20 Mariano Martinez Peck <[hidden email]>

Hi Guido. Is this still a problem?

On Wed, Aug 22, 2012 at 4:40 PM, Guido Chari <[hidden email]> wrote:

There was a change on the storeOn: method of StartupAction that is breaking things. Before it said: " aStream >> code printString" and now it has "code storeOn: aStream". I'm almost sure that the previous one is the correct one. We didn't one to print the object on the file, only the text for later running it or am i wrong?

Cheers,

Guido.

--
Mariano
http://marianopeck.wordpress.com