eitanblumin / crude-asp Goto Github PK

• Test mention of one column in another column.
• Test URL links that inject value from another column.

Will need to find a way to reconcile different Angular object names in the datatable versus the Modal dialog ("row" versus "selectedRow").
Need to check if we can rename "selectedRow" to "row" and if that doesn't cause conflicts.

Do we make it a centralized dashboard of sorts?
A landing page with a welcome message and navigation?
A fully customizable page with a selection of widgets and content boxes?
This thing alone opens up one hell of a can of worms.
We're getting into Wix-like territory here.
Very dangerous shit that could potentially suck me in as one heck of a project in and of itself.

Or... The default.asp page could simply be left to the user to do what they will with it by changing its code. hmmm...

New deal:
A few configuration settings would determine the home page behaviour:

• home page type (data view, data view charts, custom page, custom URL)
• data view id
• custom page id
• custom URL

Using recursive hierarchical navigation links poses several problems that will need to be dealt with:

• How would the recursive implementation of the levels work? Nested recordsets? Arrays? Json?
• How will we know which of the child-items is active?
• How will we know which parent-level item needs to be active (open)?
• How would we avoid excessive database round-trips?

The Edit/Add modal currently doesn't do anything special for read-only fields. need to add support.

Problematic input types:
rte, select

DataView Actions should be configurable on several levels:

• Top of page action buttons
  • Implement hierarchical links (?)
• Contextual links per row within the datatable under the Actions column (incl. Angular palceholders)

This may be useful:

https://datatables.net/reference/option/ajax.data

https://fontawesome.com/how-to-use/on-the-web/setup/upgrading-from-version-4

I'm not sure how soon I'll be able to get to implementing these features, but this is what I have planned:

• Data Views with DataTables - Fully functional datatables (sort, search, pagination), modals for editing/adding/deleting. Use Angular for async loading of data. Use ASP for dynamic fields presentation. Use toastr notifications for confirmation and error messages.
• Configurable Recursive Navigation - The navigation sidebar would be fully configurable, including hierarchical links. Each link would either point to one of the data views, or to a custom URL. If a link points to a dataview, it would automatically be visibly set as "active" when its dataview is opened. A navigation link could be activated by more than one dataview (in case there are dataviews that link to each other, and/or if there's a hierarchy between them).
• Data View Action Links - Each dataview can have, in addition to its data displayed, also a set of customizable "action buttons". Each such an action button can either be one of the following:
  • Regular HTTP link
  • Custom database T-SQL command
  • Parameterized database T-SQL command (will use a modal dialog to set parameter values before execution, and/or use pre-configured default values)
• Data Charts - Using the free javascript chart libraries (chart.js, morris.js, Flot, inline charts), I want to make it possible to present configurable chart data, instead of or in addition to the regular datatables. This is NOT going to be easy to implement, I fear the day when I'll reach this... But it's such a cool idea I just won't forgive myself for not doing it.

The AdminLTE 2.4.5 web template has a lot of very cool features. It'll be interesting to see how many of them I can implement dynamically, and how well it would eventually work.

Equivalent of the seek_* filters in form_template, but also the Filter part.

Would need to be implemented as advanced search using dynamic structured filters, plus implementation of pagination. This would also solve the big data problem causing buffer overflows #49.

Filter parameters should be saved in an AngularJS collection object (something like "filters"), which could be used similarly to the "row" object in angular. For example:
filter["Label"] - would return the search parameter value entered for the "Label" column.
This would allow using AngularJS placeholders in things like DataView description, action buttons, etc.

https://github.com/EitanBlumin/CRUDE-ASP/projects/2#card-11633828

After Action Links management is implemented in the admin section, we'll need to implement their usage in dataview.asp

Generic Framework:

• Actions and Action Parameters JavaScript object collections (i.e. "dt_Actions"), each action object would have action parameters collection same structures as "dt_Columns" collection.
• Action Parameters Modal
• Action Parameters Modal Rendering Function
• Action Parameters Modal Re-Fill Function
• Action Execution Wrapper Functions (for DataTable button: one for inline and one for toolbar)

Action Types:

• HTTP Link
• DB Procedure
• DB Ad-Hoc Command
• JavaScript Function
• HTTP REST API Request

Action Properties:

• Is Per Row
• Require Confirmation
• Open (HTTP Link) in New Window
• Send (Selected) DataTable Row(s) as Parameter (XML/JSON?)
• REST Method (GET / POST / PUT / PATCH / DELETE)

Declare values for additional AngularJS variables to be used as placeholders:

• row['...'] (already implemented row-level palceholders)
• {{this}} (current field value)
• dataview[id]
• dataview[title]
• dataview[...] (TBD)
• urlparam[...] (Get parameter values from querystring)
• user[...] (User properties, once authentication module is implemented)

for SQL
for Input field
for Output (optional)

Async paging or something, I dunno

When deleting an item using the Deletion modal, display in the modal body the item's fields (only those that are set to be displayed in the items list)

Allow changing the class of the datatable:

• table-hover
• table-bordered
• table-striped
• etc.

Sub-tasks:

• Add new field to portal.DataView table
• Add new field in portal.DataViewField for manipulation
• Implement usage of the new field

Seems to be somehow duplicated with a "ghost" of itself or something

Combobox-type fields need to be resolved in the items list. This could prove problematic due to the Angular implementation, so maybe a separate field needs to be added (i.e. "FieldName_resolved" or something).

This will also need to be done in the Deletion modal.

In dataview.asp Line 353, binding with angular to RTE field doesn't seem to do anything.

https://github.com/EitanBlumin/CRUDE-ASP/projects/2#card-11633828

The following "global" settings should be easily configurable:

• Site Name (to be used as browser tab title)
• Site Public URL (for use in e-mails and such)
• Color theme (use the themes provided by AdminLTE)
• Layout style (AdminLTE layout variations)
• Sticky Footer
• Footer Text
• Favicon
• Toggle Anonymous Registration
• Toggle User Profiles
• Database Connection String
• Toastr Notifications Style Options
• More (TBD)

These settings need to be database-independent. Probably saved in a json file or whatever. Like a web.config file of sorts.

Could be useful to implement them dynamically somehow.
Some sort of generic HTML template that displays data from a query?
The notification menu items themselves could be set up dynamically (glyph icon, badge color, "view all messages" URI...)

Site-wide search would search all data views titles and descriptions (this gives an idea: implement tags for dataviews?)

Question where to put the search box: Leave it at the side nav? Or move it to top nav?

Based on the AdminLTE advanced form controls in pages/forms/advanced.html

• Dropdown box with search
• Multi-selection box / tags box
• Date Picker
• Date Range Picker (for filtering date time columns) https://datatables.net/forums/discussion/33372/number-and-a-date-range-filter-for-datatable-serverside-script
• Time Picker
• Color Picker (new field type)

https://datatables.net/reference/option/ajax.data

Describe the bug
Trying to use undeclared "nOrdering" variable

To Reproduce
Add a new DataView using admin_dataviews.asp

http://l-lin.github.io/angular-datatables/archives/#!/angularWay

Same idea should be done for the Source, Modification, and Delete procedure

• Auto-Discover foreign keys and linked tables
  • PK to be used as Value field
  • First textual column to be used as Title field
  • If foreign key column is nullable, add "UNION ALL SELECT '-- None --',NULL" as linked table addition
• Unicode maxlength needs to be divided by 2

• Search
• Sortable columns
• Pagination
• Page size selection
• Client side state save
• Footer
• Information
• Default page size
• DML button styles: icon only, text and icon, text only, hyperlink, button