Hello all, Is there a Status Bar component I can e...
# compose-desktop
k
Hello all, Is there a Status Bar component I can easily add to my CfD program, similar to the way MenuBar works? Or do I need to just create a custom area with text and icon objects etc? Thanks!
k
What is special about it that you need a separate component?
k
Hello Kirill, Thanks for your reply. No, nothing special. I just wondered if there was a preconfigured item I could add at the bottom of the screen, like e.g:
Copy code
Surface(){
  MenuBar(){
    Menu(){
      Item()
      Item()
    }
  }
  StatusBar(){
    Left(){
      Item()
      Item()
    }
    Right(){
      Item()
    }
  }
}
Otherwise I can soon build another Surface or Box and fill it with text objects, etc. Unless there's a better suggestion you could give me to build it with? I'm still learning! πŸ˜€πŸ‘ Thanks! Cheers.
Actually I think it was TornadoFX when I tried it briefly, that had the status bar item you could add to the GUI. So glad that @darkmoon_uk pointed me to Compose!!! πŸ˜ŽπŸ›€οΈ
d
There aren't very many specialized components currently; I made my own statusbar
which is nothing more than a Box with items positioned in it
k
Ok! Goodoh, thanks. That's the info I need. Won't be hard, just wondered! πŸ˜ŽπŸ‘
d
there isn't even a ComboBox component πŸ™‚ but fortunately it's easy to make wheels here
k
Ok! I haven't even got that far yet! Wow. More learning.
I would've thought there'd be pretty much the "standard" GUI objects!
d
Hopefully there will be (or is, but I don't know about it yet) a third party library to add a bunch of more specialized components
k
Yes, would be nice, but it's awesome what we already have, eh!
d
Actually let me check if Aurora forces you to use one of its themes
πŸ‘ 1
@Kirill Grouchnikov can Aurora be used only for the components? Using MaterialTheme instead of an Aurora theme.
all of the screenshots in the docs use an aurora theme but I'm not sure if that means it's required or just showcasing them
k
Ok.
k
Aurora is completely separate from Material. Material is a design system with its own components. Aurora is a design system with its own components.
πŸ‘ 1
And this part is to make sure that there is no dependency on anything in Aurora on anything from Material. Very much intentionally.
d
So, they are mutually incompatible? As in you can mix'n'match in the same project, but not use one design on the others' components.
My grasp on Compose is still kinda tenuous
k
There might be a way to mix the two together side by side, but certainly not to apply styling from one on components in another. Very much by design. I see Material as its own, separate, opinionated design system built on top of Compose. The fact that it happens to ship with Compose is just a convinience.
πŸ‘ 1
d
Thanks, that makes sense.
Text
is part of
material-desktop
, and Aurora would have its own
Text
component
k
In Aurora I approach things differently. In Material, the
Button
is a shell with slots for `Icon`s, `Text`s and pretty much anything else (I guess you can put a button inside a button inside a checkbox, etc). In Aurora it is a more traditional approach where you can provide icons, texts, etc that are "relevant" to the specific components, but not as child composables. So there's
AuroraLabel
,
AuroraButton
,
AuroraTextField
etc. But not directly available to app code. All these composables are internal, and you work with content models, presentation models and projections that abstract away specific composables. See https://github.com/kirill-grouchnikov/aurora/blob/icicle/docs/component/Intro.md for more.
πŸ‘ 1
d
interesting. not my cup of tea, but it's clearly popular and well-thought out
k
Yes, very interesting and awesome appearance. Lots of options, etc. I'll prob stick to the basic stuff, too, till I get my head around it!