KnownIssues

Known Issues

1. Probably deviated from accepted Enyo conventions
   1.1 Trying to build an architecture template that fits what I know
   1.2 Good and bad:
   1.2(a) Some decisions might be conflicting with Enyo/JavaScript practices
   1.2(b) Some ideas might prove useful in this context 1.3 If the user navigates to a link (e.g. forgot password), the URL displays
   1.4 http://localhost:8888/mvcAppDebug.html#/forgotPassword 1.5 Refreshing the browser takes the user back to the default page
   1.6 The displayed URL remains unchanged, and the user cannot navigate to the original link, until navigating somewhere else (e.g. login) to clear the URL
2. JavaScript
   2.1 Inconsistent use of callbacks, tried to standardize, probably needs some more cleanup
   2.2 Inconsistent callback objects: Tried to standardize on responses coming back from the server, but some of the NPM modules throw their own exception format
   2.3 Inconsistent code conventions: I used things I like form java, C++, JavaScript. Need to pick something consistent and clean it up
3. Would like to organize the Routes.js better. Right now the Enyo framework only seems to recognize a single Route controller. Maybe have the Route instantiate other Kinds or read a file and dynamically setupt he routes? This file is already a bit unweildy.
   3.1 Routes.js is unwieldy. Even a simple web site has many views. Need to find a way to organize routes by functionality.
4. Enyo 2 isn't 100% webOS friendly. Some things like the Gravatar widget and dynamic buttons built in the scrolling lists don't work.

Purpose

Project Background

Quick Start

Quick Start

Tutorial Walk Through

Add a Contact Page for Authorized users

Project Architecture

Application Architecture

Project Directory Structure

Directories and Package Layout

Architectural Decisions

Why is the project structured this way?

Implementation Decisions

Why are some things implemented this way?

Home

Home