Hi Marc,
It would be so cool but no, it's not planned.
Like SDL and Morphic, Gtk is only used as a backend for windowing. This
means that only primitives related to windowing are currently implemented
(i.e GtkWindow related apis).
Working on widget binding with Gtk or Qt is something i would like
--- Begin Message ---
Hi Glenn,
does this mean, that in the future we can build GTK applications via
Bloc/Brick/Spec?
Best regards,
Marc
2017-06-08 14:46 GMT+02:00 Glenn Cavarlé :
> Hi all,
> As well described by Peter, Bloc is a low level graphics library which
> mainly manages multi-windowin
Hi all,
As well described by Peter, Bloc is a low level graphics library which
mainly manages multi-windowing (Morphic, SDL, Gtk soon), user interaction
(events) and drawing (using Sparta).
Brick is a widget framework on top of Bloc (button, inputField, ...) and
Spec is a "multi-backend" UI Build
On Tue, Jun 6, 2017 at 9:20 AM, Brad Selfridge
wrote:
> I'm confused. I see the latest news and documentation about Bloc. Is Brick
> now dead and Bloc the default? I thought Brick was a layer on top of Bloc
> and Spec was layer on top on Brick? What is the direction now?
>
> Brad Selfridge
>
>
Ca
--- Begin Message ---
What does 'Bloc Zeroconf Script' do?
What is the difference between the 4 different metacello lines here?
https://github.com/pharo-graphics/Brick
--- End Message ---
* Bloc - low level library (think basic shapes, rectangles, ...)
* Brick - widget library on top of Bloc akin to the widget part of Morphic
(buttons, checkboxes, ...)
* Spec - UI framework with adaptable backend; currently using Morphic as a
backend, however once Bloc/Brick matures, Bloc/Brick wi
I'm confused. I see the latest news and documentation about Bloc. Is Brick
now dead and Bloc the default? I thought Brick was a layer on top of Bloc
and Spec was layer on top on Brick? What is the direction now?
Brad Selfridge
-
Brad Selfridge
--
View this message in context:
http://forum
