Hi!
I am in the process to dabble around with the newly released thin client related serverblocks [1]. Some how I have trouble with the usage of alien class references and methods within the serverblocks. Given the code from the example: DevKitShell exportClassToServer: NeoCSVTestObject; onServerDo: [ System commitTransaction ]. Pharo won't execute that code neither commitTransaction or System are defined in the image.... What am I doing wrong? Thanks Sebastian [1] https://github.com/GsDevKit/gsDevKitHome/blob/dev/docs/articles/gsDevKitServerBlocks.md _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Hi again!
Okay, well,.... I have to define System as a Global,.... but also in the "right" workspace,... This now worked, but only in the "Pharo workspace" I was trying this in the roassal one... Sebastian On 2015-04-25 2:02 PM, Sebastian Heidbrink via Glass wrote: > Hi! > > I am in the process to dabble around with the newly released thin > client related serverblocks [1]. > > Some how I have trouble with the usage of alien class references and > methods within the serverblocks. > Given the code from the example: > > DevKitShell > exportClassToServer: NeoCSVTestObject; > onServerDo: [ System commitTransaction ]. > > Pharo won't execute that code neither commitTransaction or System are > defined in the image.... > > What am I doing wrong? > Thanks > Sebastian > > > [1] > https://github.com/GsDevKit/gsDevKitHome/blob/dev/docs/articles/gsDevKitServerBlocks.md > > _______________________________________________ > Glass mailing list > [hidden email] > http://lists.gemtalksystems.com/mailman/listinfo/glass _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Yes, there are a number of Caveats[1] to be observed when working with
server blocks .. perhaps I should have put the Caveats at the top of the doc? Dale [1] https://github.com/GsDevKit/gsDevKitHome/blob/dev/docs/articles/gsDevKitServerBlocks.md#caveats On 4/25/15 3:14 PM, Sebastian Heidbrink via Glass wrote: > Hi again! > > Okay, well,.... I have to define System as a Global,.... but also in > the "right" workspace,... > This now worked, but only in the "Pharo workspace" I was trying this > in the roassal one... > > Sebastian > > On 2015-04-25 2:02 PM, Sebastian Heidbrink via Glass wrote: >> Hi! >> >> I am in the process to dabble around with the newly released thin >> client related serverblocks [1]. >> >> Some how I have trouble with the usage of alien class references and >> methods within the serverblocks. >> Given the code from the example: >> >> DevKitShell >> exportClassToServer: NeoCSVTestObject; >> onServerDo: [ System commitTransaction ]. >> >> Pharo won't execute that code neither commitTransaction or System are >> defined in the image.... >> >> What am I doing wrong? >> Thanks >> Sebastian >> >> >> [1] >> https://github.com/GsDevKit/gsDevKitHome/blob/dev/docs/articles/gsDevKitServerBlocks.md >> >> _______________________________________________ >> Glass mailing list >> [hidden email] >> http://lists.gemtalksystems.com/mailman/listinfo/glass > > _______________________________________________ > Glass mailing list > [hidden email] > http://lists.gemtalksystems.com/mailman/listinfo/glass _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
In reply to this post by GLASS mailing list
On Sat, Apr 25, 2015 at 6:02 PM, Sebastian Heidbrink via Glass <[hidden email]> wrote: Hi! To minimize this compiler issues, wouldn't it be easier for you to load the package MockGemStone into Pharo? What am I doing wrong? _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Mariano,
That would help a bit in the short term, but in the longer term there are a couple of different approaches: 1. for the SHOUT highlighting in tODE, I already import the list of globals from the stone to Pharo, so I just need to create a special workspace that catches the notification compares the globals to the list ... a similar trick could be applied to resolving message selectors (at the cost of a round trip or two). 2. completely wire out the global/selector checking and let the compiler in GemStone resolve things 3. ??? Thanks for the thought tough:) Dale On 04/27/2015 06:14 AM, Mariano
Martinez Peck via Glass wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Free forum by Nabble | Edit this page |