Hello jPlayer Community,
I will be able to spend some time on jPlayer over the next week so hope to implement a few of the Pull Requests and some other features in that time. While I'm sure you all have a list of features that you desire, bear in mind that I want to get the 2.4.1 update official ASAP. I kinda dropped the ball on that one and it is now 4 months overdue.
We are making changes to our GitHub repo:
https://github.com/happyworm/jPlayerDevelopment will now be performed in the
dev branch. The release notes will record these items as [dev] and no longer assign a minor release number to each and every little thing I do.
Each major/minor release will have their own branch, such as
v2.3 and
v2.4, and these branches will have
bug fixes applied to them while they are the latest version. For example, v2.3 will not have any bug fixes applied to it, however, the v2.4 branch will have the bug fixes applied to it until v2.5 is released. So currently, v2.4 branch is 2.4.1, which is currently identical to the
master branch.
So... Over the next period of development, the changes will be occurring in the dev branch and when 2.5 is ready we will merge those developments into the master branch and update all the other bits and bobs that go with a minor release. ie., Tagging, incrementing versions in the JSON files and creating a version branch.
And, for example, if a bug fix is issued during this period, it would be applied to the v2.4 branch, then merges with the master and dev branches. That bug fix would be called jPlayer 2.4.2.
This may seem a little complicated, but the idea here is that we have a development area that is free to grow with loose checks, while the master and latest version branch contain important bug fixes for the latest official version.
References:
http://nvie.com/posts/a-successful-git-branching-model/https://www.atlassian.com/git/tutorialSummary of development areas being considered:
1) Adding
currentTime(t) command, to compliment the play(t) and pause(t) commands.
2) Adding extra format types, HLS/M3U8, M3U and maybe even PLS... But PLS has very limited support and even Apple don't advertise that it can work in their docs.
3) Time display types...
currentTime/duration versus
remainingTime. Envisage that clicking on currentTime GUI switches between currentTime and remainingTime... And probably have an option for enabling it and its initial state.
4) Look at the PRs on github and either merge, integrate or close them. And clean up the issues, since most are support requests and not issues.
Best regards,
Mark P.