Greg Weng [:snowmantw][:gweng][:λ] Assignee
	Description • 10 years ago

To minimize the risks while we're implementing the LockScreen as app, I would take the following steps in the first stage:

1. create an new app in dev-apps
2. create a '/build/build.js', which would copy the necessary files for LockScreen in System app.

The copying rules is only a temporary way, to keep these files in the app would not got conflicts or cause regressions compare to the plan to directly fork them from System app, in which case I need to spend lots of time to sync them everyday  and avoid problems among these tons of files.

I'll remove the copying rule incrementally, which means I would move these files from System to LockScreen one-by-one. In this way, the worst case is we can still have an as-an-app LockScreen for v2.1, and can greatly reduce the risks.

	Greg Weng [:snowmantw][:gweng][:λ] Assignee
	Comment 1 • 10 years ago

After consideration I think it's OK to put the new app in apps/ directory, so I would do this little change.

	Greg Weng [:snowmantw][:gweng][:λ] Assignee
	Comment 2 • 10 years ago

Since we changed the roadmap, this bug won't fix anymore. The new plan is to make LockScreen as an ordinary iframe first, and then become an app.