Le 25/12/14 15:46, Peter Uhnak a écrit :
This look really interesting! However is there any diagram showing how all the components (morphic, athens, spec, bloc, or even glamour and roassal) work together? At least to me it feels that there is some sort of overlapping. Is bloc replacing morphic?
Bloc is a core graphical frameworks. it rethinks - rendering - event handling - view composition Bloc is composed about a low-level: - morphs + event + views Then on top of it we will have Bloc-Widgets valueModel + (spec unsure but we want the same composibility/reuse) + bloc-core Bloc uses Athens. The goal is to replace Morphic (a framework) Glamour is on top. Roassal could reuse bloc-core. Stef
Peter ------------------------------------------------------------------------ From: stepharo <mailto:stepharo@free.fr> Sent: â12/â25/â2014 11:51 AM To: Pharo Development List <mailto:pharo-dev@lists.pharo.org> Subject: Re: [Pharo-dev] [Ann] a short Bloc demo
On some point, you will need to have some functional widgets. Exact and since there is no magic we will start to write them. We started to write a radio button and this led to a redesin of the core and now we should be ready to try again.
If you are not afraid about strange/bad/circumvoluted code have a look at the code of PluggableButtonMorph (not talking about tableLayout intrincaties). So we will not copy Morphic! It will take time and if people want to help they will be able to improve their future.
Stef
Can we start to build our own UI using Bloc?
Cheers, Alexandre
On Dec 25, 2014, at 11:33 AM, Alain Plantec <alain.plantec@yahoo.com> wrote:
On 25 Dec 2014, at 10:31, stepharo <stepharo@free.fr> wrote:
Le 25/12/14 03:04, Ben Coman a écrit :
Really nice to see your progress. Now do you have some sketches that show how it relates to the components of the existing Morphic? What is being disposed of, what reimplemented, what ported? yes, almost everything is new or rewritten and you are right, its time to write documentation. Now, there is one well identified issue. Athens is used to render everything except the Morphic world. This is cool but at the end of the rendering, the vm Form based display is used by wrappers : see in TBlAthensWrapper>>unprotectedFullDrawOn:
self surface displayOnMorphicCanvas: aCanvas at: self position ââ It slows down the rendering very much. what would be cool would be to have a native Athens/Cairo vm display to really benefit from Athens.
Cheers Alain
I'm writing class comments and soon a chapter. But it takes time because I have to also do a bit of reverse engineering. Now Bloc does not relate to Morphic :) Everything is rewritten from scratch and we will rewrite everything. We will try to reuse Spec. Now for default Morphic, rewritting all the morphs to use Athens is a huge tasks considered the current logic of certain morphic elements Since Bloc is fully athens-based, it may be better to only work on Bloc. Now the trick is that we can use the morphic elements.
This would really help to understand where contributions might be useful.
btw, with Build 40419, "ConfigurationOfBloc load" warns that it depends on BlEllipseShape which must be resolved before #drawOn: and #drawOnAthensCanvas: can be resolved. Yes this is normal, you should load bleedingEdge. "ConfigurationOfBlock loadDevelopment" works fine.
cheer -ben
Sven Van Caekenberghe wrote:
Yes, a nice X-Mas present !
On 24 Dec 2014, at 15:41, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Wow! Impressive!!!
Alexandre
On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec@yahoo.com> wrote:
Hello all,
Iâve just uploaded a small demo of Bloc. http://vimeo.com/115336678
Cheers Alain
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.