diraven

Hello. I work on a script that uses https://community.bistudio.com/wiki/PreProcessor_Commands (namely Macros) a lot. So EQUAL(_oldItem,"some_otherItem") is rather frequent situation. And I did not find any way to make these acceptable by the linter/syntax checker. Any advice? Thanks.

Well I want my checker at least make sure user did not type if (***) {asdf} (without "then" keyword). I.e. check at least some basical errors. If there is no real situation where you would write ((( for "_i" ) from 10 ) to 12 ) do { player sideChat str _i } - I'm not sure if I should disable the "if-then-else" correctness checks just to allow statements like above one. Turning it off basically would mean just turning off the spellchecker. With the same profit you would just ignore it's warnings.

The language is ok, but to be honest I didn't really get what the problem is. I understand that lexer/parser gives wrong output while lexing the code? And you have just given few examples showing the code that works in-game (i.e. Arma compiler takes it and processes it) while my lexer/parser says it wrong, right? ---------- Post added at 01:23 PM ---------- Previous post was at 12:25 PM ---------- I guess first problem - my parser does not know what is >>. I'll fix that. Second, is there any real task that would need inputs like: 123 = qwe / player or ((( for "_i" ) from 10 ) to 12 ) do { player sideChat str _i } ? I understand that they may be valid in terms of semantics, but is there any real need to write ((( for "_i" ) from 10 ) to 12 ) do { player sideChat str _i } instead of justfor "_i" from 10 to 12 do { player sideChat str _i }? Just to add this specific case I'll need either disable if-then-else checks, that may be resould in having code with incorrect statements rendered as valid, or add high level parser rules to make sure this is handled. Just need to know if this is worth of time spent.

Sorry for no updates - I've got a huge project to work with and still trying to write my own small game. =) No updates has one important advantage - there are no new bugs. xD Since someone downloaded this thing and may be even using it - I'll take time to add some new features, but not right now.

Yes, of course. Here is the main window. Looks pretty much like any other NB IDE'ish thing. =)

Well since no other ideas written - I'll take it. Thanks.

Ok, there are actually few ways of extending the IDE right now: 1. Keep trying to implement code folding/autoformatting - looks like a dead end for me rignt now. I'll keep searching for info and trying, but for now no progress made. 2. Work on the contextual code completion and extended contextual error reporting (like Squint does) - a whole bunch of work, actually. Not the matter of few days. 3. Incorporate few useful 3rd-party tools (optimizers, checkers etc.) into the IDE to make it more like an IDE - that is simpler task. 4. Add more filetypes support. SQS, EXT, SQM. Any ideas? What would you like to be done first?

There are few options to make reinstalling go away, but neither of them is easy, so that's not the matter of the nearest future. Anyways all the config files are untouched unless you explicitly set them to be deleted during the uninstall.

0.1.3 released. [FIX] "waitUntil {true;" case will be reported as an error, Skufer will try to guess the location of the braces mismatch error, but this location may not be 100% precise. [FIX] "waitUntil {true};" now will not be reported as an error. ---------- Post added at 12:25 PM ---------- Previous post was at 12:19 PM ---------- Still trying to sort out the code folding and autoformatting. Netbeans lacks user-friendly documentation. =)

Both issues are fixed in the next version. It will let you know there is braces mismatch, but for now not able to tell you where the problem is, it will just highlight the first line of the script and tell "(location unknown)". Not really great, but better then nothing. UPD: It will try to guess the mismatched brace position, but location may not be 100% precise.

Yes, it probably does not like single-line statements inside curly braces (arma allows them to be without semicolon while my parser goes mad when sees that). Will fix, thanks.

v. 0.1.2 was released. [NEW] Introduced code templates (Tools->Options->Editor->Code Templates) (will add more templates later). [NEW] You can now delete project along with the real folder on the disc (not only project from Skufer). [NEW] You can now create new project by importing PBO file contents. Just go into the File->New Project->Projects with Existing Sources and follow the wizard. [NEW] You can now build PBO right from inside the IDE by right clicking the project node and selecting "Build PBO" option. In the dialog you may select folder or *.pbo file, or even put filename yourself, just not forget to put the *.pbo extension. To see the output of the process, press ctrl+4 or use Window->Output->Output menu. [CHANGE] Moved "Empty Sqf" template into the "ArmA" group.

Just curious, why do windows EXE's (MakePbo.exe, for instance) send all the output with the help from the dry run (did not yet check the rest) via ErrorStream instead of regular Input(Output)Stream?

Found a pretty much ugly bug with the deployment version. Building fixed version now, will upload in a few minutes.

0.1.0 is out: - [NEW] Added simple code completion (thanks PvPscene for the database). Aside from the completion itself and internal docs about the command - you can always click the button at the top of the command description window to get to the corresponding wiki page and view full info with examples there. - [NEW] Added an ability to create arma mission projects.