0 Members and 1 Guest are viewing this topic.
...If nTxt is not developped anymore, maybe I or someone else could modify it to allow these features (I didn't see any license, but the sources are given...) Just asking...
Thanks in advance to consider these feature requests... hoping this program is still in development...
Quote from: DJ Ounless you mean making nTxt so that it lets people write Python code inside it instead of just plain text files, which would definitively be very great. That's exactly what I meant. Sorry for being unclear.In fact, it already works. Just type your Python code in nTxt, save it as "anything.py.tns" and MicroPython will launch it.My feature requests were only to simplify some routines many times repeated when testing a new program...With the actual version of nTxt, if you want to modify a previously saved "anything.py.tns", you have to :- launch nTxt- ask to open an existing document- close the current (empty) one- search for your document in tree hierarchy and finally open itThen you add the ":" that you forgot, save and close for testing it again.And you have to do it again if you want to change anything. It can get very annoying, especially for students leaning the language and making many syntax errors.It would be a real big plus if this could be simplified.If nTxt is not developped anymore, maybe I or someone else could modify it to allow these features (I didn't see any license, but the sources are given...) Just asking...
unless you mean making nTxt so that it lets people write Python code inside it instead of just plain text files, which would definitively be very great.
Also, one of my students noticed that there is no key combination for the % character in nTxt. As it symbolizes "modulo" in Python, it is clearly needed, so it should be added to the priority list.
Also, could someone host it on a github repo (preferably lkj ?) and could add several contributors so that it'd be easier for anyone to help out
Nice, thanks.I merged the pull request and removed some of the things with a comment "unused ?". Some others of them aren't really unused, though.
Hi matteob92. I actually haven't worked on nTxt during this year, for multiple reasons. Firstly, studying at university left me with almost no time for programming. Secondly, I didn't know what to do next with nTxt: all the features I had suggested back then are almost useless without unicode support, and implementing that would require too much work. Also, pdfs or the built-in documents are better suited for most usage cases of those things.If you want something added, you cann suggest it and maybe I'll do it, or implement it yourself, the code is on github