I agree, for chat and IM applications the top pane shouldn't be editable. However the Label isn't a good alternative to read-only TextArea. Label doesn't support multi line texts and text select/copy operations.
BTW Home and End keyboard buttons don't work in TextArea too. On Sun, Feb 14, 2010 at 11:33 PM, Greg Brown <[email protected]> wrote: > Right. Also, the text in the top pane is generally not editable. For > example, in iChat it is presented as a vertical list of read-only labels. > This could be accomplished in Pivot using a vertical BoxPane. > On Feb 14, 2010, at 4:18 PM, Todd Volkert wrote: > > FWIW, every chat application I've used (YIM, Pidgin, Epiphany, AIM) has been > some variation on this theme: two panes divided vertically by a splitter. > The text area in the lower region is for typing your outgoing messages, and > the text area in the upper region is to show the conversation. Both text > areas use top alignment, but the conversation window automatically scrolls > to bottom when new text appears. This behavior is supported in Pivot. > > I haven't thought through all possible use cases to decide if bottom > alignment in text area would ever make sense -- I'm just saying that from my > observations, IM clients are not a typical use case of bottom alignment. > > -T > > On Sun, Feb 14, 2010 at 4:09 PM, Rostislav Krasny <[email protected]> > wrote: >> >> >> Why vertical alignment in TextArea is less likely to be implemented? >> >> Is it harder to be implemented than the horizontal one or some other >> >> reason? >> > >> > There is not as much of a use case for vertical alignment in TextArea. >> > Think about a typical word processor - it supports horizontal alignment, >> > but >> > not vertical, because text is laid out from right to left and is expected >> > to >> > scroll vertically. >> >> I can't agree with this statement. Almost all chat and IM (Instant >> Messaging) applications use vertical text alignment. This is always >> naturally enough to find a new text near the text input it was typed >> in and not somewhere else. > > >
