Hence graphics output necessarily lags input on Morphic. So these speed
differences have nothing to do with vm performance and everything to do with
GUI architecture.
Both Squeak and Pharo show the same delay for text selection latency. The
architecture difference is not likely
Hi Shaping,
> On May 18, 2020, at 6:52 PM, Shaping wrote:
>
>
> 1. Double-click text selection in both Squeak and Pharo shows a 75-100 ms
> latency (eye-balled, estimated) between end of double click (button up on
> second click) and time of highlighting of selected text. It could be as
1. Double-click text selection in both Squeak and Pharo shows a 75-100 ms
latency (eye-balled, estimated) between end of double click (button up on
second click) and time of highlighting of selected text. It could be as low as
60 ms, but I doubt it, and that’s still too long. I can’t track
Hi Shaping,
> On May 16, 2020, at 4:33 AM, Shaping wrote:
>
>
> Hi Eliot.
>
>
> Generally, comparing VisualWorks to either Squeak or Pharo or both, what are
> the most pressing speed problems?
>
> 1. Double-click text selection in both Squeak and Pharo shows a 75-100 ms
> latency
Hi all,
We wanted to announce that, as announced previously, Smalltalkhub is going read
only from tomorrow, 8h central Europe time.
This means the service could be down for a couple of hours until the sync of
data is done.
Keep tuned,
Guille and Christophe in behalf of the RMoD team
### Last week:
- Large Images Updating Baseline
- Pharo Sync Meeting
- LiveTyping in Pharo: Recovering the build, fixing some problems
- JIT Documentation / Test
- Benchmarks with the Lowcode variant
- Meeting with Esteban
- Activate setting to run build in Sista w/FullBlockClosures
-
https://github.com/svenvc/zinc/commit/7a4b4bda502092186d03b467dc6baf9d1a76baed
> On 13 May 2020, at 17:49, Sven Van Caekenberghe wrote:
>
> Yes, I know the pattern and yes it would make sense. I will study this a bit.
>
>> On 13 May 2020, at 17:21, Stéphane Ducasse wrote:
>>
>> Hi sven
>>
Short list today ;)
### Last week:
* [NewTools-Playground] polishing details and get it ready to test
internally (which now is the case :P)
* Documenting transmissions sub-framework.
* Spent a lot of time preparing integration of Spec2 0.6 into P9.
### This week (starting
