Design, develop, and test the program following the Coding Standards provided on

Question

Design, develop, and test the program following the Coding Standards provided online in Canvas.
In addition to the Visual Basic Program itself, you must also submit your program algorithm's design in BOTH Pseudo-code and Flowchart formats. You can use Word or Notepad for your Pseudo-code, and you can use PowerPoint or Microsoft Paint to create your Flowcharts. Design, develop, and test the program following the Coding Standards provided online in Canvas.
In addition to the Visual Basic Program itself, you must also submit your program algorithm's design in BOTH Pseudo-code and Flowchart formats. You can use Word or Notepad for your Pseudo-code, and you can use PowerPoint or Microsoft Paint to create your Flowcharts. FIGURE 4.63 Possible outcome of Programming Project 5. 6. College Admissions The admissions offices of colleges often rely on a point system. A point system similar to the one in Fig. 4.64 on the next page is used by a large state uni versity. Write a program that allows an admissions officer to determine whether an applicant should be admitted. The numbers in brackets give the point count for each response. The GP A score entered into the text box at the top of the form should be from 2.0 to 4.0. The point value in the brackets to the right of the text box is 20 times the GPA and should appear automatically after the focus leaves the text box. A total of at most 40 points can be eaned for the responses below the line. The program should calculate the total score and then admit an applicant whose score is at least 100

Explanation / Answer

Getting code folded into Canvas core is not trivial. You should take a second right now and see if maybe your change would be better implemented as a separate service using the API or LTI. We have a high quality standard at Instructure and if you're not familiar with both Ruby and Rails then getting your code accepted may be difficult. We're happy to give suggestions on how to improve commits, but we're not going to teach you how to write Ruby code when you issue a pull request.

Every commit for Canvas is reviewed by at least one Instructure engineer (this is all true of Instructure-created code as well, btw). Every line is read and the reviewer is responsible for checking out the commit and testing it in their local environment. As such, commit messages need to provide enough information that the engineer knows what has changed and what should be tested.

The following checklist is worked through for every commit:

Other factors that should be considered:

Places to Start

If you're new to Canvas development, there are guides in this wiki for getting your dev environment set up (including getting specs running). Make sure you've given us a signed code contributor agreement, then start with something small. Get to know the commit process with something small like a bug fix or a UI tweak. If you're not sure where to start post a message on the mailing list.

Once you've got your feet under you then you can start working on larger projects. For anything more than a bug fix, it probably makes sense to coordinate through the mailing list, since it's possible someone else is working on the same thing.

Pull Requests

We like GitHub pull requests. If you report an issue, we’d love to see a pull request attached. Just keep in mind that because of the development standards mentioned above your commit is probably going to end up getting modified at least once before it’s accepted. Sometimes we’ll make the change ourselves, but often we’ll just let you know what needs to happen and help you fix it up yourself.

Enhancements and Extensions

Because Canvas Cloud runs as a multi-tenant environment, any changes to the codebase will affect all institutions at once. If you're looking to add major pieces of functionality to Canvas, you'll need to keep this in mind, since most likely only some institutions will want that functionality added.

To help with this we've built the notion of Plugins into Canvas. Plugins can be registered at runtime but only appear in the interface for enabled root accounts. There are some places in the code that have already been instrumented for plugins (such as web conferences and collaborations), but if you're looking to extend functionality somewhere else then the first step is going to be pluginifying that portion of the code, then building a plugin for your specific implementation.

The easiest way to get to know Canvas Plugins is lib/canvas/plugin.rb and lib/canvas/plugins/default_plugins.rb

Related Questions

Navigate

• Browse (All)
• Browse D
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.