stenpetrov / wham Goto Github PK

https://github.com/Azure/azure-content/blob/master/articles/app-service-web/web-sites-dotnet-deploy-aspnet-mvc-app-membership-oauth-sql-database.md

App name must be set at the least

See
https://github.com/Rick-Anderson/SecureData

Completely missing

Add at least one option to import a SQL schema from a format that's easy to export to in SQL

Click a button on the top and the page gets loaded with a bunch of pre-made tables and fields that demonstrate what can be done. Then the user can customize or just click "Submit" and get a zip.

This would be the fastest way to demo to anyone and explain what the project is meant to do

Table items allow for Heading, which is a composite field calculated runtime by concatenating the values of fields in a table, such as Heading="{Street}, {City}, {State} {Zip}" for an imaginary Address table.
Not all fields may be known when adding the table

Should change isAuth visibility for relevant types - else no field can be isAuth

The workflow should be:
View mode --buttonEdit--> Edit Mode
Edit Mode --buttonSave--> ViewModel.Save()
Edit Mode --buttonCancel--> ViewModel.Load(ViewModel.Model)

CollectionPage should have
[+] button in the toolbar which will show a new page in edit mode
Swipe list actions to edit and delete

These will be used to construct what shows up in a list of items made up of that table’s objects. For example a list of customers may have Heading = “{FirstName} {LastName}” and Details = “{HomeAddress}”, so that a list of customers looks like

John Doe
123 str, WA
Jane Doe
345 str, WA

The json now contains:
"isVisible": "on"
"isCollection": "on"

Hint will be used as a placeholder in empty textboxes, used for text and number entries.
Label will be used next to a UI control for any field type, including Ref.

So for a field
{ Name=”FirstName”, Hint=”your first name”, Label=””, Type=”string”, UIType=”TextBox” }
and if Label is used:
{ Name=”FirstName”, Hint=””, Label=”First Name:”, Type=”string”, UIType=”TextBox” }