25 Apr
2015
25 Apr
'15
8:05 p.m.
On Sat, Apr 25, 2015 at 7:12 PM, Stephan Eggermont <stephan(a)stack.nl> wrote:
Verstuurd vanaf mijn iPhone
Having more stuff under Spec than Morphic would help with the interface.
There is a lot of mess, but there is also continued effort to clean it up
and make it work as it should.
But in principle nothing should really be stopping you (imho) from writing
GlamourAdapter between Spec and Glamour just like it is done for Morphic.
Unless you are doing something really specific and want very tight control
over things (e.g. Spotter) Spec should be the go-to choice.
1. A explicit menu with submenus on top of the browser windows (not hidden
Op 25 apr. 2015 om 18:10 heeft Offray Vladimir
Luna Cárdenas <
offray(a)riseup.net> het volgende geschreven:
Hi Stephan,
Thanks. The main issue for me with morphic is there is little
information right
now, except may be for [1] and the upcoming information
from the Kilion chapter/document. I will take a look to Spec, which seems
to have the most updated/complete documentation now and get a feeling of it
and come back with findings/inquiries.
That won't really help you. Spec is mapped to Morphic. behind the dots like now).
2. Better icons and a tool bar.
Spec has support for this
also look at
ApplicationWithToolbar new openWithSpec
3. A contextual menu in each node of the tree for
actions on that node.
This can be also done
look at TreeModel, and ListModel; both have class-side examples.
Peter
