It's important to get a Chromebook with an Intel CPU. The ARM-based
Chromebooks cannot run Crostini, so they do not have the option of running
Linux containers -- so, no Pharo on ARM Chromebooks!
Also, it's important to get a later model, in order to get a Linux kernel
that supports containers on
No, it's not quite the same... I've installed CloudReady on old
(non-Chromebook) systems myself, so I'm a little bit familiar with it and
what it can do.
However, I've never tried to run 'Crostini' in CloudReady, so I don't know
if that works, or (if it does), how well it parallels the implementa
Hi Vitor,
Willow is built on top of Seaside and it aims to ease the creation of
interactive AJAX-based web applications. So if you're planning to do a lot
of partial page rendering via AJAX updates it's worth a try.
We're using it for several applications and the only full page refresh is
done on
Thanks to Ivo Roefs and Dave Mason !
Noury
Thanks to Ivo Roefs and Dave Mason :-)
Noury
Hello,
What's is the difference? Why should I use one or another?
Regards,
Vitor
Dear Gabriel,
thanks for the answer, it helps tremendously.
Best wishes,
Tomaž
Well, one thing that might disappoint you in Pharo is UI libraries.
You'd assume that system that has UI as integral part and relies on it would
have excellent UI framework, but sadly that's not the case.
Old framework - Morphic - is outdated; it's buggy, poorly documented, and
its code is convolut
Hi Tomaz,
First check that your selection component is not created in every render
cycle, so it can hold its state between calls. Usually components holding
state must be kept in instance variables in the containing component,
initialized once and rendered many times.
Second, the selection state
Hello
Does any of you already used the youtube REST API?
S.
Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org
03 59 35 87 52
Assistant: Aurore Dalle
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley,
P
Hi, I have tested with CloudReady (another variation of Chromium OS)
but I couldn't reproduce the error. Maybe there is a problem with the
latest version of Chrome OS (that of course is not the same).
On Mon, Jun 8, 2020 at 8:25 AM Stéphane Ducasse
wrote:
>
> I think that we will have to buy one
Thanks Olivier
You do not experiment UI glitches so this means that it probably depend on the
OS version.
S
> On 8 Jun 2020, at 09:22, olivier auverlot wrote:
>
> Hi,
>
> The leaders of the Chromebooks are Asus, Acer and HP. I recommend you to
> choose a recent model with a powerfull x86
Hi,
when using selection components in Willow (like single and multiple
selection lists), should #currentSelection and #currentSelectionIfNone:
be called only within their own affordances? If I use these messages
from onTrigger evaluate: of other components (e. g. buttons), then I
don't get a
13 matches
Mail list logo
