Add element columns to sort table

[lukasturcani]

Note

I have a question:

Should the element be automatically wrapped in an Element.el?

For example, this code

            , Widget.elementColumn
                { title = ""
                , value = \task ->
                        Widget.switch
                            (Material.switch Material.darkPalette)
                            { description = "active"
                            , onPress = Just <| ToggleActive task.index
                            , active = task.active
                            }

                , width = Element.fill
                }

leads to

I have to do

            , Widget.elementColumn
                { title = ""
                , value = \task ->
                    Element.el
                        []
                        (Widget.switch
                            (Material.switch Material.darkPalette)
                            { description = "active"
                            , onPress = Just <| ToggleActive task.index
                            , active = task.active
                            }
                        )
                , width = Element.fill
                }

to make it look right

I could edit the PR so that Element.el is used automatically, and the user does not have to write it, but I'm wondering if this can cause issues in other cases?

Description

• I extended the sortTable to allow the embedding of arbitrary Element into columns.
• MadeColumn and ColumnType types polymorphic on a msg type variable. This allows them to hold data of type Element msg
• Updated type definitions to use Column a msg and ColumnType a msg
• Added a new constructor for ColumnType, ElementType, which is used to construct columns which hold Element msg data
• Added a constructor function elementColumn for Column instances, which have values of type Element msg
• Updated the definition of sortTable to handle ElementColumn data. ElementColumn data is not sortable.
• Refactored the view in sortTable. See https://github.com/Orasund/elm-ui-widgets/pull/85/files#r771978681
• Updated doc of sortTable to include example of elementColumn use

Pull request solving issue #84.

Please only open Pull Requests for existing issues.

Checklist for new Widget

• [x] Checked out the Material design specification of the widget
• [x] Added constructors, Widgets Type and Style Type in src/Internal/[Your Widget].elm
• [ ] Added styles in src/Internal/Material/[Your Widget].elm
• [ ] In src/Widget.Material.elm:
  • [ ] Linked each style to its representative in src/Internal/Material/[Your Widget].elm
  • [ ] Added Documentation
• [x] In src/Widget.elm:
  • [x] Added a copy of the Widget Type
  • [ ] Added a copy of the Style Type
  • [x] Linked each constructor to its representative in src/Internal/[You Widget].elm
  • [x] Replaced the Widget Type in the type signiture of each constructor with its definition
  • [x] Added Documentation with a small example
  • [x] run elm-verify-examples && elm-test to test the example

Optional:

• [x] Added a Page in explorer/src/Page/[Your Widget].elm and added it to explorer/src/Main.elm

[Orasund]

Currently, this would be a major change. I'd like it to instead be a minor one, so please instead of changing the type signature of a function, create a V2 version. So SortTableV2, ColumnV2, sortTableV2, floatColumnV2, intColumnV2, stringColumnV2 and unsortableColumnV2.

Regarding the wrapped El. Yes, you will have to wrap it in an Element.

[lukasturcani]

Ok updated:

Description

• Added new module Internal.SortTableV2
• sortTableV2 also uses the style, SortTableStyle from Internal.SortTable
• Functions in Internal.SortTableV2 are copies of functions from Internal.SortTable but with type signatures modified to be polymorphic on the msg type. The sortTableV2 function is slightly modified to work with the CustomColumn.
• Added Page.SortTableV2 and updated explorer/src/Main.elm to use it
• Added an png of the new sort table in docs/assets/sortTableV2.png
• Custom elements provided by the user in CustomColumn are automatically placed into an Element.el to prevent scaling issues by default

[lukasturcani]

Also updated docs.json