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.
Editor, set interest points (sorry, it's not correct terminology )
-
@omz, I think a great addition to the editor would be a 'set point' function. Sorry I can't remember the right term. But my meaning is if you click a line number in the gutter of the editor. It toggles with a dot or something. But then with up and down arrows same as you have in search, you iterate through the points. It would be great if these controls to iterate through these points were visible without having to enter a mode like you do in search. Or, if you think it's too much, maybe it could be a user configurable item.
I know this is not new to code editors, that's why I thought of it. But in this environment would be so handy to be able to quickly note sections of code you are working on by just clicking the line number , then navigate to each one by just using up and down arrows in the menu bar. If you had a long press in the line gutter, would be nice to have a popup menu 'clear all' -
I still want the zoom slider that collapses indent levels.
-
@Webmaster4o, I know what you mean. But I am sure he has many things to do. My feeling is code folding is fairly tricky. I am not sure how much effort to make 'set points', but I think a lot less effort than code folding. But I think you would be surprised how useful the 'set points' feature would be. So many times I just want to bounce around in a few places in my code, this would be perfect for that.
-
I actually like the current implementation better than these two suggestions. Click once the filename in the title bar and you get a popdown menu of all the functions and methods in your script. Click on a function or method in that menu to see its implementation. If your function or method scrolls off the bottom of an iPad screen then it is too long. Refactoring it to fit on one screen will decrease your debugging time and increase your ability to reason about, test, and reuse your code.
Breakpoint markers are good for debuggers (pdb) and big screens but I would hate to lose one character per line to reserve space for them on the small screens of iOS devices.
-
phuket, it would not be hard to add such a feature yourself, from the action menu. for the bookmark "set" function, you could either store a dict that has filename/linenumber/ and text of current line, or else you could insert specially formatted comments in your code. for the bookmark jump feature, you would show a popover with all of the bookmarks in the current document (or, if you opt for the global dict approach, all bookmarks in all files), maybe with a few lines of context.
-
@ccc , is a different concept. You also do not need to lose a character for a marker. Example the line number could invert color or go bold for example. I agree that the menu is good for navigating, but when you are just focused on one or 2 methods, this idea is great :) it's hard for me to disagree with you, but on this subject I can :)
