Skip to content

Instantly share code, notes, and snippets.

@leekelleher

leekelleher/ucomponents-data-list.md

Last active May 18, 2019 08:32
Show Gist options
  • Save leekelleher/6183524 to your computer and use it in GitHub Desktop.
Save leekelleher/6183524 to your computer and use it in GitHub Desktop.
Download ZIP
uComponents - potential data-type... Data List
Raw
ucomponents-data-list.md

uComponents - Data List

The idea is to have a provider-based property-editor for various data list types. To have a separation between the UI (editor control) and the data-source. e.g. a DropDownList shouldn't care where the data comes from, only that it's available and consistent.

Data List (types of)

  • DropDownList
  • CheckBoxList
  • AutoComplete
  • Templatable List

I/O

  • Inputs => Config / Options
  • Outputs => XML, CSV, JSON

Data Sources (bound to list)

  • Key / Name / Text / Label
  • Value

Providers

  • XPath
    • Content
    • Media
    • Members
  • Examine
    • Content
    • Media
    • Members
  • SQL
    • T-SQL
    • MySQL
    • SQL-CE
  • XML
    • Local FileSystem
    • Remote URL
  • JSON
    • Local FileSystem
    • Remote URL
  • Macro
    • Could return anything?!
@kgiszewski
Copy link

As a companion to xPath, what about having a Linq expression that can be passed?

i.e. Model.Ancestor(1).Descendants("SomeDocType")

@leekelleher
Copy link
Author

@kgiszewski 👍 Totally... a C# provider. (or even make use of a Macro, which could be Razor, etc)

@bewildergeist
Copy link

If anyone stumbles across this gist, the data type now exsists as nuPickers :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment