Re: [Pharo-users] What UI direction now (or in the near future)?
Thanks (to all). So, the best way (for now) is the old friend Morphic. Will be internal drawing methods in Morph switched to Athens drawing by default in future? pf
Subject: Re: [Pharo-users] What UI direction now (or in the near future)? From: Alain Plantec <alain.plantec@yahoo.com> Date: 25. února 2015 20:17:46 SEÄ To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
Hello Petr,
So far we have Morphic (Athens is the next underlying framework for 2D Drawing). Thanks to Nicolai, Athens is near to be fully integrated. We have Spec for widgets composition.
Regarding Bloc:
Sub-questions:
A) Is Bloc (complete Morphic rewrite, sigh) âone man showâ? What about future, support, long-term issues? Look at Marina CMS framework, even used for Pharo website, but not maintained nowâ¦
Iâve started Bloc with Stephane. So far Iâm the main developper, But, you are perfectly right. No future for Bloc if it stays like that. Weâve stopped adding because now, design decisions are to be made regarding the widgets layer. Currently, we are writing a documentation of the core. The next step is to make it available in the hope we will get feedbacks and also to bootstrap contributions from the community. It will take time. Be sure that I will stop Bloc if we stay only two or if someone else come and propose something better than Bloc. No problem, Iâve fun with Bloc.
Spec will stay, so we will also have to build new adapters to be able reuse tools.
B) Is Bloc prepared with Retina displays in mind (perfect smooth fonts and graphics, scaling, more detailed images for retina etc.)?
Bloc bring nothing on that point except that it is is based on Athens
C) Is current keyboard + UI component focus support perfect or pain inâ¦
I guess yes :)
Cheers Alain
Isnât a âbad timeâ for this decision (Pharo) now?
Thanks very much for any brief hint, Petr Fischer
Will be internal drawing methods in Morph switched to Athens drawing by default in future?
You can do the drawing in Athens. It is up to you. Using Athens will make your rendering faster and nicer (if you use the Cairo binding, which is the default binding). If I would be a beginner who want to understand what there is, I would simply give a try to Spec, bloc, and plain Morphic. In any case, your application logic should be independent from the UI. Because UI is frequently changing (have you though about exposing your UI on the web?) Cheers, Alexandre
Subject: Re: [Pharo-users] What UI direction now (or in the near future)? From: Alain Plantec <alain.plantec@yahoo.com> Date: 25. února 2015 20:17:46 SEÄ To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
Hello Petr,
So far we have Morphic (Athens is the next underlying framework for 2D Drawing). Thanks to Nicolai, Athens is near to be fully integrated. We have Spec for widgets composition.
Regarding Bloc:
Sub-questions:
A) Is Bloc (complete Morphic rewrite, sigh) âone man showâ? What about future, support, long-term issues? Look at Marina CMS framework, even used for Pharo website, but not maintained nowâ¦
Iâve started Bloc with Stephane. So far Iâm the main developper, But, you are perfectly right. No future for Bloc if it stays like that. Weâve stopped adding because now, design decisions are to be made regarding the widgets layer. Currently, we are writing a documentation of the core. The next step is to make it available in the hope we will get feedbacks and also to bootstrap contributions from the community. It will take time. Be sure that I will stop Bloc if we stay only two or if someone else come and propose something better than Bloc. No problem, Iâve fun with Bloc.
Spec will stay, so we will also have to build new adapters to be able reuse tools.
B) Is Bloc prepared with Retina displays in mind (perfect smooth fonts and graphics, scaling, more detailed images for retina etc.)?
Bloc bring nothing on that point except that it is is based on Athens
C) Is current keyboard + UI component focus support perfect or pain inâ¦
I guess yes :)
Cheers Alain
Isnât a âbad timeâ for this decision (Pharo) now?
Thanks very much for any brief hint, Petr Fischer
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Thanks (to all). So, the best way (for now) is the old friend Morphic.
Better way may be to stay at Spec level for all available components you need and for your special component write Morph which could be adapted back to Spec. After all Spec components still have Morphic under them, but you are not exposed to low level Morphic. Peter
On Feb 26, 2015, at 19:13, Peter Uhnák <i.uhnak@gmail.com> wrote:
Thanks (to all). So, the best way (for now) is the old friend Morphic. Better way may be to stay at Spec level for all available components you need and for your special component write Morph which could be adapted back to Spec. After all Spec components still have Morphic under them, but you are not exposed to low level Morphic.
I agree with Peter: build your UI with Spec, this will automatically use your old friend Morphic but make it much easier to construct a complete UI. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
participants (4)
-
Alexandre Bergel -
Johan Fabry -
Peter Uhnák -
Petr Fischer