2015-01-25 18:52 GMT+01:00 Sebastian Heidbrink <sheidev@yahoo.de>:
Okay, .... I am new to the UI implementations and options in the Pharo world and I am really confused.
So, am I right to say. - Polymorph is no more really the way to go? - Spec is the official way to go right now?
- Roassal2 is the way to go for visualizations?
- Athens is well, I can't even say.... hmm interesting when it comes to SVG?
athens is a api for doing 2d rendering (shapes, fill, strokes, ..). Roassal2 is built with athens. DrGeo (https://launchpad.net/drgeo) was ported to use athens.
- Glamour has to be seen in conjunction with Moose? I had a look into GTSpotter and I have the feeling this took a long long time for implementation. - No e.g. Google material like UI possible since there are no frameworks available to do animation stuff.... didn't Squeak and E-Toys do that? Is there nothing left in Pharo? - Lumiere or Roassal3D when it come to sprites?
Are all of these framework compatible to each other? How much maintenance and repair effort may I expect when I combine e.g. Spec with Morphic and Roassal2?
VASmalltalk has a very strong separation of UI-View and UI-Control layers. Which Pharo framework could allow me t replace the look and feel of my application without loosing my event handling/ control layers?
The look: there are different themes. And you can even use different themes per application (I think). The feel: I think pharos theming is only for the look, maybe keymappings are theme dependent.
This is Smalltalk and this is objects, and I am bound so much to a windowing representation? There is nothing I could do like with HTML5 and css? Put some pictures in the world and just add event handlers to them?
This is, for sure, much more easier in squeak/pharo than with HTML5 and css. You can attach an eventhandler to any morph (ImageMorph for example). And you are not "bound to windowing representation". This is exactly what morphs are for: build, use and combine visible and active elements directly on the screen. (The problem is now, this is not what people expect. They expect an "application" with buttons and list and textfields. And this is why you need frameworks like polymorph, spec or glamour, in order to use commonly known widgets).
So I might go with Spec and Morphic then? Glamour is more Moose? Or is there a direction to deprecate one of them?
Thanks for all you into so far. I'll carefully read all the so far provided resources.
Sebastian
On 2015-01-25 6:04 AM, Stephan Eggermont wrote:
That Maya Node Editor looks like a PasteUpMorph with Connectors to me. You'd might want to wrap them (Morphic) in a in a standard window with menu bar and toolbar from either Spec or Glamour for now.
And then follow Bloc developments to move there.
Stephan