Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
chordcalc - a stringed instrument chord calculator
-
The partial and multiple capo facility does not look simple from what I can tell. This code is pretty amazing but difficult to figure out. I was hoping that the original author would have thought about it since it would seem to be like modeling the fifth string of a banjo but provided for each individual string. In the physical world it is most like being able to move the nut to any spot on the fretboard on a per/string basis. The tuning remains the same, but open strings ring out at where the individual capos are placed. I am trying to understand your idea about it being like a filter.
-
Filter won't work. I am making an effort to add capos. Thought about the banjo as well and will incorporate it. I have to change the basic chord validating code to start its search at the "new" nut. Will add in banjo piece as well. atience please. Fiirst pain was add in a popup to read the fret number while in an action. Onwards!!!
-
I noticed that you have created a new dev-capo branch. Happy to test this whenever you want to put out a new version.
-
Will upload it when I get first working version. Got the capoes to draw, the logic to use\ them in the calculations, banjo style neck, etc. Give me a week. I have a day job, am studying mandolin and building guitars. (whew). Thanks for the push. Needed to do this, but just for me, not so much.
-
So...... shellista has sent 4 days of work into sock hyperspace. Created a temp file. moved everything in there. Messed around with git. moved everything back. Now gonzo. At least it did not remove my brain. Will get it back over the next week or so. Sorry. It was completely done and working.
-
Noooooo. I know the code will probably be better the second time around, but this sucks :-(
I would suggest doing the zip file archive thing next time before attempting the upload. http://omz-forums.appspot.com/pythonista/post/5306403304505344 The latest version even has dropbox upload support. This will come in handy when moving to a new device.
-
Did you do any commits in git, but then just accidentally clobbered it?
If so, everything is there still, hidden in the object store.
It would be possible to walk through all commits.
(Hmm... Thinking we need a git stash command for just this situation) -
@JonB - I just checked github and the last commits are from 9 day ago. This was to be his first attempt to commit to a different branch from the main branch. I was thinking that your new git repo manager app could be the solution to his original problem. He basically had already cloned his main branch into a dev_capo branch and had just completed changes to the code in the dev branch and wanted to commit those. This apparently did not go well from Shellista.
-
What I mean is, sometimes if you do a commit, but the accidentally copy other files and do another commit, it might seem as if your files were lost. Though in this case, I suspect what may have happened is he may have changed branches (checkout) after moving the files in... in shellista git this immediately does a checkout and overwrites what is there. I probably should add a check for uncommitted changes and issue a warning for operations that can clobber files.
By the way, a lot of the new development is happening within stash, (dev branch) instead of shellista. I do plan on porting a few improvements from gitview over to the stash git command, but probably won't keep shellista up to date.
-
I believe I panicked. I am mostly back, with a better implementation anyway. Using gitui really helps and now that I better understand git I don't have to go back to stacks of versioned punch cards in labelled boxes. ;-)
-
Punch cards had their benefits. It was a very satisfying way to write code. Made great fire starter and an endless supply of confetti.
Found a really good tutorial on git here
I think the tough part to get used to is that the code for all branches is suppose to live in the same local directory. That makes me nervous and I would want to zip up and stash a copy before I trust a script doing the push (upload).
-
Nervouseness agreed upon. Kaplooey again. Seems existing git tools for pythonista don't allow rollback to a previous commit. Especially if the base file has disappeared.
This is why my parents never bought a color TV. They were waiting for it to be perfected.
Zips and email for me from hereon out.
Trust everyone, but cut the cards.
-
If you do a push to github, your entire local history gets pushed as well, so you can use github to get back to any previous commit. then pull back into pythonista.
If you have deleted a file, but didn't rm from the repo, you will get an error. I'll have to think about fixing that. In the meantime, just recreate the missing files, or if you have no other changes pending, just checkout the current branch. then you can push.
I've been planning a "checkout sha" feature... But this is also a really good way to get lost. I think the way it would have to work would be to create a branch from that sha. Alternatively it would update the files on disk, but leave head pointing the same.
-
By the way, you can create a new branch by typing a new branchname in the branch box. Maybe that is not intuitive, I should add a button.
You should do that BEFORE making any changes....the current version seems to nuke any unstaged changes if you create a new branch... I need to fix that.. -
Actually, I forgot... Current gitview lets you paste a sha from the log into the branch field, and it will checkout a previous commit (but be sure to commit any outstanding unstaged commits or you will lose them forever)
-
FYI the latest version on github is a little safer, prompting you in most cases before clobbering uncommitted changes. Also, it handles missing files, offering to recreate them from the latest checkin. If you want to remove a file, remove it by pressing X on a file, then commit. You can then delete any untracked files safely.
The Log button now shows you every commit, sorted by date. If you drag the table entry to the left, it will show you an Open button, which checks out that revision into your current file system.
Then, you could stage a file and check in (to the active branch). Need to work on a proper merge system....
-
@polymerchm - Is everything OK? Did you lose it all again?
-
Chordcalc Version 2 is now up on Github. The capo enabled version is in the devel-capo branch. It is still a little buggy, and this thing does so many variants, that I can't test all the potential bad states without a little help. In addition, I've added 5-string banjo (with capo options) that handles the short 5th string and its reentrant tuning. I only included standard open G banjo tuning.
Had to delete the old branch and copy/paste all the new stuff. Included is a spinner class used to set the span (how many frets you can stretch to reach all the fretted strings).
Comments please. Some rest, then re-build the GUI to allow for iPhones (just got a 6). That one I might not release to github if I take the plunge and become a developer. We'll see. Got to check out the way xcode handles this beast.
-
Thanks for adding the capo feature. I did a simple test with my special tuning and the partial capo and was able to find the two fingered chords I have been playing. So it seems to work! I would like to post a screenshot but can't figure out how to do it in this interface.
-
you need to have it on some website and post a link. I have a website in the works, so I'll try. Don't think I can put on github and provide a link..Maybe on fo the gurus know.