morea-framework / plugin-intellij Goto Github PK

Create draft in discussions, then create on README in branch: issue-06

Do work in branch: issue-32

Create an initial poster using ppt for the presentation, needs to be submitted before 04/29

do work in branch named: issue-3

In the right click "new" option of the project view menu, the create new o/r/e/a options should be grouped together and in their own section with a separator that clearly illustrates that they are in their own group.

Waiting on approval from Intellij. https://plugins.jetbrains.com/plugin/21428-morea

do work in branch: issue-4

remove NewPageAction class, as actions are now separated into their own classes.

Relocate all Morea actions in a new section located at the bottom of the pop-up menu in its respective groups.

Do work in branch issue-23.

Implement function on file deletion to remove morea-id from respective module.md.

change plugin ID and other tags to match new build, do work in branch: issue-15

• Create New Morea Module ==> Morea Module
• Create Single New Outcome Page ==> Morea Outcome
• Create Single New Reading Page ==> Morea Reading
• Create Single New Experience Page ==> Morea Experience
• Create Single New Assessment Page ==> Morea Assessment

Do work in branch issue-21.

Do work in branch: issue-07

The Module Button Popup Window creates a dropdown menu that allows you to toggle off all unwanted files before you create the Morea Module

Do work in branch: issue-08

It is unintuitive what it is for.

Create methods in MoreaUtils and call method from there.

Do work in branch: issue-5

Implement snippets that allow users to utilize portions of code within the INCLUDES directory conveniently.

Do work in brach: issue-29

Change the logic of duplicate file checking to include module-id.

Create a developer guide that will help future developers to understand how to develop a plugin and include resources used during this project.

Upon creating a new Outcome/Reading/Experience/Assessment page, update the module.md file with the appropriate id and appropriate location.

Do work in branch issue-22.

Here are the things I've noticed:

Make new module label consistent with other labels

Which one of these labels does not look like any of the others?

So, first, rename your label to "Morea Module". Then it is consistent.

Second, below "Resource Bundle" (or whatever the last entry is):

• add a horizontal bar to indicate a new section (like the two horizontal bars already in there),
• Add the "Morea Module" action.

Make new page labels consistent with other labels.

Once again, your labels do not look at all like any of the others. You want to try to fit in, not stand out like a sore thumb.

Remember, the user has already selected "New...". They already have indicated that they want something new. You don't need to bang them over the head with it.

So, rename to "Morea Outcome", "Morea Reading", etc.

Second, below "Resource Bundle" (or whatever the last entry is):

• add a horizontal bar to indicate a new section (like the two horizontal bars already in there),
• Add the new Morea-related actions.

Update the module page when you add a new outcome, reading, etc.

When the user creates a new outcome, reading, etc, please update the module definition file with the appropriate ID in the appropriate place.

Display message when duplicate directory name occurs at creation of new module.

do work in branch: issue-18