Hello, I am thinking of a** tabular data-grid field** plus upload feature. For sure, there are 1000 ways, techniques and interpretations ;-) Let me explain the simplest form...
Comparable to the basic K2 CSV field. It offers a file upload, parses the content and build a HTML table/grid. Not sure how this one stores the values. Maybe it would be ideal to keep the data in a sort of Array or multi-value list. And adding output-style in field template. So, better not storing a complete HTML structure.
Some thoughts about techniques:
**A.) **Cobalt Uploads field. Store CSV or create JSON file? Output template loads file? Parsing CSV/JSON and build table/grid
B.) Cobalt import feature - Utilize upload and CSV parser in new Cobalt field?!
C.) New field with new jQuery upload. Storing and parsing script (see K2 method)
D.) General pros and cons about server- and client-side techniques?
Requirement:
Easy for none-techies, DAU's ;-)
Any thoughts are welcome. Thanks in advance.
Related Links:
- jQueryCSVtoTable
jQuery CSV to Table reads in CSV or TSV data (both can be saved from Excel) and generates an HTML table
Parse CSV (Comma Separated Values) to Javascript arrays or dictionaries.
PS: Optional "cherry on the cake":
Data is searchable and maybe filterable?!
Question
Announcement
Conversation
Idea
Praise
Problem
Open
Hello, I am thinking of a** tabular data-grid field** plus upload feature. For sure, there are 1000 ways, techniques and interpretations ;-) Let me explain the simplest form...
Comparable to the basic K2 CSV field. It offers a file upload, parses the content and build a HTML table/grid. Not sure how this one stores the values. Maybe it would be ideal to keep the data in a sort of Array or multi-value list. And adding output-style in field template. So, better not storing a complete HTML structure.
Some thoughts about techniques:
**A.) **Cobalt Uploads field. Store CSV or create JSON file? Output template loads file? Parsing CSV/JSON and build table/grid
B.) Cobalt import feature - Utilize upload and CSV parser in new Cobalt field?!
C.) New field with new jQuery upload. Storing and parsing script (see K2 method)
D.) General pros and cons about server- and client-side techniques?
Requirement:
Easy for none-techies, DAU's ;-)
Any thoughts are welcome. Thanks in advance.
Related Links: - jQueryCSVtoTable
jQuery CSV to Table reads in CSV or TSV data (both can be saved from Excel) and generates an HTML table
Parse CSV (Comma Separated Values) to Javascript arrays or dictionaries.
PS: Optional "cherry on the cake":
Data is searchable and maybe filterable?!