search

intendednull / dm-toolkit

Native management tool for tabletop rpgs
0 stars 0 forks source link

Widget Discussion: View #10

Open intendednull opened 4 years ago

intendednull commented 4 years ago

The base container object. It manages child widget layout and scope.

As we discover what functionality we need this object to fill, we can edit this as needed.

Actions

intendednull commented 4 years ago

We also need to figure out the default layout behavior. We could use the provided layouts, or build our own.

If we want to support drag and drop, it would make sense to using floating point as the default, with a custom layout manager.

CLyonsDev commented 4 years ago

A property every widget should probably have is a visibleToPlayers boolean. That way when creating a layout, one can choose to allow any widget to be hidden/shown to clients.

intendednull commented 4 years ago

I'm thinking we do some sort of trait for this? Have a global user permission that's used to determine whether the widget is visible.

Should it be invisible or just not added to the layout at all? Both options could potentially cause odd layout behavior, though I think invisible is the least problematic.