First relevant :P

11 views
Skip to first unread message

dsirijus

unread,
Jan 24, 2011, 10:04:49 AM1/24/11
to MinimalComps
Just a small preamble. Components ROCK, couldn't do one project
without them for prototyping. WHERE'S THE DONATE BUTTON!? :D

Anyways, I have tons of feature requests that would still keep comps
minimal, don't even know where to start...
Cascading windows within same parent? Scrollbars on Text? Slightly
more advanced formatting on Label? A Nothing component, since we don't
have abstract or base class? Xpos and ypos on comps with Window parent
default to somewhere under the title bar?

I completely don't mind if you ignore these completely, comps still
rock. Couldn't believe my eyes when you put the Knob in (EXTREMELY
useful and not found in other libs/frameworks). Thanks for them.

Keith Peters

unread,
Jan 24, 2011, 10:18:21 AM1/24/11
to minimalcomps
Several of these features already exist.

1. Scrollbars on Text. Use TextArea.
2. A "Nothing Component". Use Component. It is the base class for all.
3. x/y pos on windows. Add children to the window's content property and it will appear at the 0,0 point of the window's content area, below the title.

Thanks. Oh, and there's donate buttons on my blog now at www.bit-101.com. I'll add one to the minimalcomps.com site.
--
---| Keith Peters

dsirijus

unread,
Jan 24, 2011, 10:58:10 AM1/24/11
to MinimalComps
There we go. If it weren't for the group, I would still be using HBox
as base class and adding to window instead to window.content. And I've
been using comps for quite some time now. Nice.

Will have to wait for paypal limit raise for donate though.

On Jan 24, 4:18 pm, Keith Peters <k...@bit-101.com> wrote:
> Several of these features already exist.
>
> 1. Scrollbars on Text. Use TextArea.
> 2. A "Nothing Component". Use Component. It is the base class for all.
> 3. x/y pos on windows. Add children to the window's content property and it
> will appear at the 0,0 point of the window's content area, below the title.
>
> Thanks. Oh, and there's donate buttons on my blog now atwww.bit-101.com.
> I'll add one to the minimalcomps.com site.
>

Keith Peters

unread,
Jan 24, 2011, 11:18:46 AM1/24/11
to minimalcomps
Yeah, I find not many people know about content on panel and window. I've considered overriding addChild to them to make it automatically add the child to the content. In retrospect, I would have done it that way originally. Doing it now, it could break things where people are actually intending to add things to the window/panel, though I think that's a pretty rare case. I could add another addRawChild method to accommodate that. But it would also throw off positioning for people who were adjusting the x/y values for the titlebar/border. Thoughts?

dsirijus

unread,
Jan 25, 2011, 9:51:45 AM1/25/11
to MinimalComps
Well, adding children to Window the way it is, was for me (and you say
many others) counter-intuitive. That should alone be sufficient to
make a change. AddRawChild could be interesting, but i'm not sure is
it worth it. Actually, come to think of it slightly harder, the way it
is ain't so bad.

Autoscroll on TextArea? (I could go on all day long this way. :D )

dsirijus

unread,
Jan 27, 2011, 11:24:29 AM1/27/11
to MinimalComps
Seen it on trunk. I, for one, think it's better this way. Thanks.
Reply all
Reply to author
Forward
0 new messages