I found the cause - I created the #buttonBad accessing methods with code
(re)factoring (generate accessors), and in this case the accessors are made
in this fashion:
CustomerSatisfaction >> buttonBad: *anObject
*buttonBad := *anObject
*It's better to use
CustomerSatisfaction >> buttonBa
At this time I'd say that PharoJS would probably my first choice to check
out for such project in the future.
Given my Pharo n00bness however I have decided to stick with C# for this
project for now to avoid (too) long implementation times.
But I'll definitely dive into the options you tell me abou
Hi,
I just launched a new Pharo 7.0 - 32bit (stable) from the pharo launcher.
Got back an image from build: 160, commit: b84a1e1
First issue I noticed was a broken (?) component in the Wellcome
screen (red block with yelllow border and diagonals).
Then, after insalling Seaside and trying
I’m afraid the Gettext-Seaside integration is broken in current Seaside
versions.
Johan
> On 15 Jun 2019, at 00:18, BrunoBB wrote:
>
> Well,
>
> This method exist on GetText GemStone version.
>
> So i'm not quite sure what is going on. Maybe GS and Pharo version are not
> synchronized.
>
>
