Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure "Examples" project exists on session start #295

Closed
PropGit opened this issue Oct 13, 2015 · 3 comments
Closed

Ensure "Examples" project exists on session start #295

PropGit opened this issue Oct 13, 2015 · 3 comments
Assignees
Milestone

Comments

@PropGit
Copy link
Contributor

PropGit commented Oct 13, 2015

[This issue spawns from issue #133]

App must perform the following:

  • Upon every session start (after the "New Version" notice, if any) check for the existence of a project named "Examples"
    • Exists? Done!
    • Doesn't exist?
      • Create a project called "Examples"
      • Fill the new Examples project with BASIC Stamp Source Code Examples
      • Prompt user with the message "Explore the 'Examples' project to view source code examples."
        • The prompt should have an Ok button that the user can click to hide the prompt
@urbantumbleweed
Copy link
Contributor

It is great that we added this issue to the project and I saw it was added to sprint 12. As it stands we are not able to get to it this sprint. I will mark it as deferred and then we can talk about it during the demo meeting.

@PropGit
Copy link
Contributor Author

PropGit commented Oct 26, 2015

@urbantumbleweed - I updated the examples files in the link in the first post. The archive is now dated 2015-10-26.

@phated
Copy link
Contributor

phated commented Oct 30, 2015

It seems the discussion during sprint planning wasn't captured here. We had decided that the default project would be the "Examples" project instead of "new project", so it doesn't seem necessary to have yet another popup dialog.

Also, we are restoring any example file that doesn't exist (deleted or newly added in a future release) instead of trying to determine if an example directory existed at the start (which wouldn't handle added files).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants