Vision Elements

[Sparky983]

Vision Elements is a seperate project that aims to solve more specific and opinionated issues such as:

• State management - #203
• Pagination
• Filling - probably should be directly integrated into the main API. maybe an add an interface to enforce a consistent API between the two projects
• Borders - should also probably be directly integrated into the main API #162

This should only require a few changes:

• [ ] Removal of fill and borders - no major change because both are marked with @ApiStatus.Experimental
• [ ] GuiLike (or similar) interface?

[Sparky983]

Some of these features would be too disjointed unless integrated directly into the library.

[Sparky983]

Could this be repurposed to contain only reusable Gui components? e.g. pagination (can't think of anything else)

[Sparky983]

The required changes are affected by this change in scope.

This should only require a few changes:

• [ ] Removal of fill and borders - no major change because both are marked with @ApiStatus.Experimental

Probably don't need to go.

• [ ] GuiLike (or similar) interface?

Depends on if the components have their own APIs?

For example, with pagination, would we have an API like (ignore pagination part of this API, the main thing I'm trying to get across is whether to have GuiLike or simply return a Gui)

public final class PaginatedGui {
    private PaginatedGui() {}

    public static Gui.Chest create(...);
}

public final class PaginatedGui implements GuiLike {
    public static PaginatedGui create(...);

    public void setPage(int page);
}

[Sparky983]

If we were to choose GuiLike (and presumably ButtonLike), we could do so without changing the type in the new slot methods without breaking the binary or source interfaces (since they aren't stable as of pre 1.1).