This is the armaeditor (eclipse) I posted about.Notepad++ is a free (as in "free speech" and also as in "free beer") source code editor and Notepad replacement that supports several languages. This being the case, I am trying really hard to refrain myself from putting this project on hold and writing a SQF code validator in python or bash or whatever.ĭude, as I was reading this, I was thinking the same thing about the validator. This is the most effort an SQF script ever got I think, zero active users and already a whole rewrite :D Much shorter and more efficient (hopefully!) I read on the BIKI that normally SQF scripts should be about 200-300 lines long so I'm already in the process of rewriting the whole script based on functions this time. Having finished functional version 0.1 of my script I found the main piece at about 3000 lines long. I still use Notepad++ as the main editor BTW but I will check out the other editors you mentioned in this thread. It is still the best (in fact only) tool I can find to detect an open } so I still use it time to time to check script files, especially when I migrate a long script from another (a week old) branch to working tree. Its editor definitely sucks due to its inability to understand Arma 3 structures and it's visual inconsistency with Notepad++. As I keep working with more SQF files and as they get bigger in size I came to realize my initial opinion & love at first sight for squint is short lived. I just reached 250+ commits this week in my first script project. If you aren't using version control when you are coding, you are doing it wrong! Also pretty damn ugly to work with imo.īoth of the solutions I've posted integrate with SVN and Git right out of the box and to me that is a huge advantage. It throws a lot of false positives from what I've seen. Honestly squint is pretty rough around the edges. And my personal favorite eclipse plugin for sqf:
0 kommentar(er)
