On Tue, May 12, 2015 at 3:22 AM, marcel.taeumel <Marcel.Taeumel at hpi.de> wrote:
> Hey, I do account for all of those. It might only be a slip because the
> documentation is poor. :P
>
> As for Message Names, it should be built with ToolBuilder to also work in
> MVC. So that rules out (!) all Morph-specific features. What lies in the
> Tools package, must not assume Morph API.

Well, I really don't understand that logic.  There is already very
little that can be done in a MVC project today compared to a Morphic
project, and I find it hard to believe MVC cannot have a field which
does something when Return is pressed anyway.  And if its true why not
improve MVC than restrict Morphic-based UI's?

I also think it is good to really ask what is the benefit of having
multiple... errr, "two" UI frameworks which do exactly the same thing?
 Isn't it their _differences_ which would appeal us to choose one over
another?  Sometimes I think we get too hung up on the idea of
"uniformity" -- not only is it never achieved, I'm begining to feel
dubious about it as a goal in the first place.  Seriously, I'd be
suprised if anyone could articulate a compelling reason in one or two
sentences..

> Yes, there might be a need for MorphicTools as a specialization for tools
> that want to benefit from Morphic-only features. :P
>
> As for now, you can trigger the search with CMD+S. That's only one (half)
> keystroke more. ;)

It's not about the required effort, its about the non-standard
behavior for a search field.  When you use Google, do you actually
click the magnifying glass or press Return?  Be honest.  What would a
new user think if Return didn't work?

> As for the future, yes, we can just implement a flag in
> PluggableInputFieldSpec to support multi-line input fields if desired.
> However, I consider the "eye jump" that occurs with multi-line fields on
> overflow quite distracting for input fields. :-) --- We have code-freeze. So
> if I should add that now, make a vote.

We are in feature freeze, not a code freeze.  This seems like a
unnecessary usability bug for new users.

Say, you never said what function CR's serve in that input field.  Do
they serve a use-case?