On 02.01.2014, at 14:07, Marcus Denker <[email protected]> wrote:
> > On 02 Jan 2014, at 11:49, Volkert Barr <[email protected]> wrote: > >> >> On 01.01.2014, at 19:26, Stéphane Ducasse <[email protected]> wrote: >> >>>> I understand that community support is needed, and yes i am willing to >>>> help. As a first step i can offer my help to test pharo features, help to >>>> write test cases, write some example code snippets, open bug reports. But >>>> i am not sure what Pharo features or libraries i should put my focus on. >>>> Any suggestions where to dig in? >>> >>> Excellent! >>> Thanks. I suggest that you focus on what you like or what you want to learn >>> and do it step by step. >>> Stef >>> >> I would like to understand ui and graphics programming in Pharo. I have >> found different ui related libraries, but not really understand how >> they all relate to each other, what their purposes and what will be "part >> of" future Pharo Versions and what not. >> > This is not that easy. For example, some of these things are not libraries > but just “SystemCategories full of random stuff”. > >> Spec > > Specifying UIs, layer on top of Morphic (but the goal is to be in depended) > >> Glamour > > From Moose > >> UIManager > Random package, not nice. Needs love. > >> Polymorph > Partly new widgets, partly a builder (programmatically) for UIs, partly lots > of overrides for morhic > > —> needs to be moved to Morphic base, Morphic Widgets, overrides need to be > move to the other packages > We need to see if the builder parts are needed considering Spec. > >> FreeType > Fonts > >> Keymapping > Keyboard shorcut support > >> Multilingual > > Lots of random stuff for I18N support. > >> Morphic > > a big mess... > >> Graphics > > Random classes related to Graphics. The Canvas is strangely in Morphic, > though. > needs cleanup and thought. What is basic Graphics? What is Morhic? What is > backward > compatibility? What can be removed? > >> Balloon > Old 2D stuff, incomplete. There is a backend for Athens that uses it, which > is handy for > debugging. In the long run —> remove > >> Athens > New 2D Vector API, with backend for Cairo (and Ballon for debugging) right > now. > This is the future. > >> NBOpenGL > > OpenGL bindings. We want in the long run to render Athens directly with this… > (very long run). :-) Thank you Marcus for your clarification. I first try to dig into Spec, Polymorph and Morphic. BW, Volkert
