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.plan...@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
>> 
>> 
>> 
> 
> 
> 
> 

Reply via email to