-
Notifications
You must be signed in to change notification settings - Fork 2
ajax
Look at the parents first, I probably won't get around to fleshing out the docs here. The JavaScript files themselves will (hopefully) describe by name and the REST API, what is going on.
- AJAXAdminDeleteUser.js
- AJAXAdminUserUpdate.js
- AJAXArchiveMessageThread.js
- AJAXArchiveSystemMessage.js
- AJAXArchiveTermsAndConditions.js
- AJAXDeleteBetaInvite.js
- AJAXDeleteSystemMessage.js
- AJAXEmailExists.js
- AJAXLogin.js
- AJAXLogout.js
- AJAXSendBetaInvite.js
- AJAXSendMessage.js
- AJAXSendSystemMessage.js
- AJAXSendTermsAndConditions.js
- AJAXUpdateBetaStatus.js
- AJAXUpdateMessageThread.js
- AJAXUserDetails.js
- AJAXUsernameExists.js
- AJAXUserSignup.js
- AJAXUserUpdate.js
- JSONPCheckAdmin.js
- JSONPCheckAuth.js
- JSONPCheckDB.js
- JSONPGetBetaStatus.js
- JSONPGetMessageThreads.js
- JSONPGetSessionTimeout.js
- JSONPGetSystemMessages.js
- JSONPGetUserList.js
- JSONPResendVerificationEmail.js
- JSONPResetPassword.js
- JSONPGetTermsAndConditions.js
#../
\enyo-mvc-web-app
|
+---index html
+---mvcApp html
+---mvcAppDebug html
+---package json
+---node-server js
+---mvcApp html
+---assets
+---enyo
+---lib
+---node_modules
+---public
+---scripts
|
\---source
|
+---apps
+---controllers
| |
| +---auth
| \---public
|
+---css
+---ext
+---models
| |
| +---ajax
| \---socket
|
\---views
|
+---auth
| |
| \---body
|
\---public
|
\---body
Add a Contact Page for Authorized users
Why is the project structured this way?
Why are some things implemented this way?