What happened with the HostWindowProxy?
El mar., 5 may. 2020 a las 15:32, Esteban Maringolo ()
escribió:
> Is there a way to preserve the window state after saving the image on
> quit and restarting it again?
>
> If I save my image window maximized I would like it to be maximized
> when
Ahh. Apologies. I don't think I understand your point. Are you saying
Smalltalkers habitually make obscure/cool things with no documentation and
leave their coolness to make their case for adoption rather then helping
people adopt them with documentation & other help? Or something else?
I
> I've watched the youtube presentation and navigated through the impress
> presentation on your site and it too quickly introduces tons of concepts
> of
> what you can do but nothing about why anyone should want to do those
> things
> or how to put them together into something a user would use
Hi Craig,
>> ...Even better, a standalone application that could be hosted on
>> a plain static server, since all the code would run client-side.
>
> E.g., https://caffeine.js.org/3d
Yes, caffeine is impressive, but also something very different from a
standard single-page Web app showing
HighchartsSt, a highcharts js api wrapper for pharo smalltalk reached it's v11.0.0 version.
Changelog
Update Boardwalk to v5, RenoirSt to v7 and Seaside to v3.4
Fixed some warnings detected by Shellcheck on the bash scripts
Use GitHub actions instead of TravisCi
Use CodeCov instead of Coveralls
Is there a way to preserve the window state after saving the image on
quit and restarting it again?
If I save my image window maximized I would like it to be maximized
when starting again.
Having it otherwise can be annoying when moving from different screen
resolutions, because a 1920x1080
Willow-Mixpanel, integration between willow and mixpanel reached it's v4.0.0 version.
Changelog
Fixed #3. Use the new constant accessing facilities in Willow.
Updated Willow to v13
Use GitHub Actions instead of Travis CI
Use CodeCov instead of Coveralls
Regards,
The Buenos Aires Smalltalk team
--- Begin Message ---
Hi guys,
Is there something wrong with autocomplete in blocks in Pharo 8?
If I'm typing a variable in a block the autocomplete does not appear. In the
following statement I'm expecting a popup after typing "eac" :
'myString' do:[:eachChar | eac
TIA
Davide
--
Sent
By the way, while playing with this problem, I ran into a moderately
painful issue.
There is a reason that Smalltalk has both #printString (to get a
printable representation of an object) and #asString (to convert a
sequence to another kind of sequence with the same elements.) If I
*want*
Willow-JQueryUI, integration between willow and jquery ui reached it's v11.0.0 version.
Changelog
Updated Willow to v13 and Seaside to v3.4.x
Use GitHub actions instead of TravisCI
Use CodeCov instead of Coveralls
Regards,
The Buenos Aires Smalltalk team
Hi Erik,
> So it could be a way of creating standalone web applications. If that was
> the thought behind the question.
Exactly. Even better, a standalone application that could be hosted on
a plain static server, since all the code would run client-side.
> I did use this mechanism of creating
Hi Konrad,
Correct, the minimal image is running on SqueakJS VM. You can find info
here: https://squeak.js.org
Interesting question regarding deployment. In my current setup you do need
the server, but it is not unrealistic to have a setup in which at some point
the client is asked to create a
12 matches
Mail list logo
