+1 888 340 6572 Try free for 30 days
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-1690

core powerlanguage files should be on github

Go to the next issue (open or closed)
Go to the next open issue

If Multicharts had a public git repository for core scripts, then the community could help improve existing ones and even submit new ones. Updates to core scripts could be downloaded without a new release.

Everyone doing serious powerlanguage development should have all their work checked in to private git repositories for more convenient backup, history, etc. Multicharts should make it easier for people to do that by starting it themselves, creating documentation, allowing SrcEl directory to be configurable to a user controlled directory, etc.

Steps to reproduce this issue

see above

Comments (3)
user-offline.png  orad (orad)
Jan 17, 2015 - 00:39

I wanted to open a new issue on this but I noticed it is already suggested.
I also highly suggest moving all MC.NET techniques to a GitHub repository, including all C# and VB functions, indicators and studies. This allows people to contribute more code, add documentation, fix typos, etc. This would make the maintenance of these code a lot easier for MultiCharts and allow to update technique code much more frequently.
This is the path that many companies are going, for example Microsoft's GitHub repository is located at https://github.com/microsoft
I also think the priority of this item should be elevated.

user-offline.png  orad (orad)
Nov 13, 2015 - 19:08

MultiCharts has a github repository at https://github.com/multicharts
Please add core PL.NET source files that are shipped with MC.NET at ProgramData\TS Support\MultiCharts .NET64\StudyServer\Techniques\CS to a GitHub repository. Please allow contributors to improve code and document the studies. It's going to be good for MultiCharts and for the users.

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates