Window implementation outside of egui

Is your feature request related to a problem? Please describe.

I am currently writing an App which requires window management. The default egui::Window gets me to like 70% of where i want to be, but i need more features (buttons, different title bar etc.)

I thought yanking the current implementation would be a viable approach but that doesn't really work well. It seems to me that in cases like this i either need to write some mini framework on top of egui which is kind of inflexible and inefficient or fork the project.

Describe the solution you'd like

Moving the window to egui_extras or making required methods/fields public. The fields seem useful on their own. Would it be doable to implement, for instance, getters for most internal variables of say Area, WidgetText etc.?

Describe alternatives you've considered

Writing my completely own window implementation using egui and occasionally dropping down to epaint or forking egui.

Additional context

Egui is extremely powerful, but at some points there are certain barriers which make it hard to get additional functionality into existing widgets.
I love working with egui and would love to make these "low level" needs more accessible

Have a nice day ::)

Start by reviewing the existing egui::Window implementation and the public APIs of Area and WidgetText, then compare what can move to egui_extras without relying on internals. The issue needs a defined scope for extraction or public getters; done means that scope is agreed and the resulting API supports custom window functionality without a fork.