loading Seaside 3.0.6.3 in Pharo 1.4

List overview All Threads
Download

newer

older

[Announce] S8 in the Concrete...

Calling component from radio...

Esteban Lorenzano

29 Jan 2012 29 Jan '12

9:23 p.m.

Hi,

I loaded last version of seaside into a pharo 1.4 image. Everything looks working fine, but there a couple of fixes:

KomLogger>>#attachTranscript self detachTheTranscript. ^(self streams detect: [:ea | ea isTranscriptStream] ifNone: [nil]) ifNil: [self addStream: TranscriptStream new]

"TranscriptStream" is not anymore on pharo and should be replaced with ThreadSafeTranscript

2) String>>#withBlanksTrimmed is deprecated, and now it should use #trimBoth

how can I proceed to apply this fixes into seaside (without breaking other platforms)?

cheers, Esteban

Show replies by date

Esteban Lorenzano

29 Jan 29 Jan

9:30 p.m.

El 29/01/2012, a las 5:23p.m., Esteban Lorenzano escribió:

...

String>>#withBlanksTrimmed is deprecated, and now it should use #trimBoth

I'm seeing this one, #trimBoth comes from grease... so I suppose seaside should use it, instead withBlanksTrimmed

best, Esteban

Lawrence Kellogg

9:47 p.m.

New subject: How do you programmatically set the root class??

Somehow, my system is not showing me the class that I want as my root class and the class does not show up in the configuration list. This used to work, now I don't know how my configuration got messed up.

Also, there is a class in there that says it can be root but should not be allowed. Is there some way to reinitialize the root list? I never added this class as an app.

Thanks,

Larry

Johan Brichau

10:02 p.m.

New subject: How do you programmatically set the root class??

Lawrence,

Maybe I'm referring to the obvious but: did you verify the implementation of the #canBeRoot class method in the involved classes?

Sorry if I did not catch your problem right.

Johan

On 29 Jan 2012, at 21:47, Lawrence Kellogg wrote:

...

Somehow, my system is not showing me the class that I want as my root class and the class does not show up in the configuration list. This used to work, now I don't know how my configuration got messed up.

Also, there is a class in there that says it can be root but should not be allowed. Is there some way to reinitialize the root list? I never added this class as an app.

Thanks,

Larry

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Lawrence Kellogg

10:09 p.m.

New subject: How do you programmatically set the root class??

On Jan 29, 2012, at 4:02 PM, Johan Brichau wrote:

...

Lawrence,

Maybe I'm referring to the obvious but: did you verify the implementation of the #canBeRoot class method in the involved classes?

Sorry if I did not catch your problem right.

Yes, this is the issue, but I guess I need a little help on the concept of canBeRoot. So, does canBeRoot indicate that the component can be accessed externally, as an entry can, or can a registered application be accessed externally and return canBeRoot>>false.

Larry

...

Johan

On 29 Jan 2012, at 21:47, Lawrence Kellogg wrote:

...
Somehow, my system is not showing me the class that I want as my root class and the class does not show up in the configuration list. This used to work, now I don't know how my configuration got messed up.

Also, there is a class in there that says it can be root but should not be allowed. Is there some way to reinitialize the root list? I never added this class as an app.

Thanks,

Larry

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Johan Brichau

10:30 p.m.

New subject: How do you programmatically set the root class??

Lawrence,

If #canBeRoot returns true, it just means that its class is made visible in the configuration tool.

Some more detail can be found in the seaside book: http://book.seaside.st/book/getting-started/cincom-smalltalk/component/regis...

Also, don't forget you can poke around in the image figure out what stuff means. This is how I usually start out. The comment in the WAComponent>>#canBeRoot (abstract) method explains what overriders are supposed to do. You can also check on that by looking for all senders of the message. That reveals that the sender are all in the configuration tool and tests.

cheers Johan

On 29 Jan 2012, at 22:09, Lawrence Kellogg wrote:

...

On Jan 29, 2012, at 4:02 PM, Johan Brichau wrote:

...
Lawrence,

Maybe I'm referring to the obvious but: did you verify the implementation of the #canBeRoot class method in the involved classes?

Sorry if I did not catch your problem right.

Yes, this is the issue, but I guess I need a little help on the concept of canBeRoot. So, does canBeRoot indicate that the component can be accessed externally, as an entry can, or can a registered application be accessed externally and return canBeRoot>>false.

Larry

...
Johan

On 29 Jan 2012, at 21:47, Lawrence Kellogg wrote:

...
Somehow, my system is not showing me the class that I want as my root class and the class does not show up in the configuration list. This used to work, now I don't know how my configuration got messed up.

Also, there is a class in there that says it can be root but should not be allowed. Is there some way to reinitialize the root list? I never added this class as an app.

Thanks,

Larry

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Dale Henrichs

10:06 p.m.

Esteban,

If it were me, I'd isolate the specific changes in two new packages:

KomHttpServerPortability.common KomHttpServerPortability.pharo14

existing implementation in the common branch and the Pharo1.4 changes in the pharo14 branch.

I've attached a new version of the configuration that creates a new baseline and version with the necessary changes ...

As other posters have mentioned #trimBoth could be used, but currently Kom does not depend upon Grease, so I would be curious whether other users of Kom would all of a sudden want Grease included in the image ... I'm not the Kom maintainer so I would choose to create the Portability package with the two branches as the the least impactful change ...

TranscriptStream is currently not managed with Grease and it could be, but then Grease doesn't have any Pharo1.4 specific packages either (yet....)...

My $0.02..

Dale

Philippe Marschall

30 Jan 30 Jan

5:46 p.m.

2012/1/29 Dale Henrichs dhenrich@vmware.com:

...

Esteban,

If it were me, I'd isolate the specific changes in two new packages:

KomHttpServerPortability.common KomHttpServerPortability.pharo14

existing implementation in the common branch and the Pharo1.4 changes in the pharo14 branch.

I've attached a new version of the configuration that creates a new baseline and version with the necessary changes ...

As other posters have mentioned #trimBoth could be used, but currently Kom does not depend upon Grease, so I would be curious whether other users of Kom would all of a sudden want Grease included in the image ... I'm not the Kom maintainer so I would choose to create the Portability package with the two branches as the the least impactful change ...

TranscriptStream is currently not managed with Grease and it could be, but then Grease doesn't have any Pharo1.4 specific packages either (yet....)...

AFAIK KomLight doesn't have these issues. KomLight is a much smaller code base with no dependencies (KomServices, DynamicBindings) and should work just fine. In Pharo 1.4 switching to Zinc is attractive because you already have most of the parts in the image. IMHO it would therefore be best to replace Kom with KomLight.

Cheers Philippe

patmaddox

1 Mar 1 Mar

9:56 p.m.

Philippe, where can I get KomLight?

-- View this message in context: http://forum.world.st/loading-Seaside-3-0-6-3-in-Pharo-1-4-tp4339150p4436379... Sent from the Seaside General mailing list archive at Nabble.com.

Philippe Marschall

9:59 p.m.

2012/3/1 patmaddox patmaddox@me.com:

...

Philippe, where can I get KomLight?

http://www.squeaksource.com/KomHttpServer.html

Cheers Philippe

patmaddox

9:38 p.m.

Dale, how can I install this? I've added your .mcz file to my package cache and run

ConfigurationOfKomHttpServer project load: '1.0.10'.

and I get

'Could not resolve: KomHttpServerPortability [KomHttpServerPortability.pharo14-xxx.1] in /Users/padillac/code/Pharo-1.4/package-cache http://www.squeaksource.com/KomHttpServer'

Googling for KomHttpServerPortability only points me to this thread...

-- View this message in context: http://forum.world.st/loading-Seaside-3-0-6-3-in-Pharo-1-4-tp4339150p4436315... Sent from the Seaside General mailing list archive at Nabble.com.

Dale Henrichs

10:01 p.m.

Pat,

I didn't take any direct action on that thread, I think I was advising someone else on what to do ... when I look at the configurations for Kom I don't see a 1.0.10, so I'm not sure where you got your configuration from ...

Dale

patmaddox

10:05 p.m.

It's in the ConfigurationOfKomHttpServer-dkh.26.mcz you posted! ConfigurationOfKomHttpServer>>version1010:

...

I didn't take any direct action on that thread, I think I was advising someone else on what to do ... when I look at the configurations for Kom I don't see a 1.0.10, so I'm not sure where you got your configuration from ..

-- View this message in context: http://forum.world.st/loading-Seaside-3-0-6-3-in-Pharo-1-4-tp4339150p4436402... Sent from the Seaside General mailing list archive at Nabble.com.

Dale Henrichs

10:12 p.m.

Ah,

Sorry, that was just an edit for the configuration as example for Esteban ... I assumed that he or someone else would make the final decision and repackage things ...

Esteban, did you resolve your Kom issue?

Dale

4476

Age (days ago)

4508

Last active (days ago)

seaside@lists.squeakfoundation.org

13 comments

6 participants

tags (0)

participants (6)

Dale Henrichs
Esteban Lorenzano
Johan Brichau
Lawrence Kellogg
patmaddox
Philippe Marschall