Collapsible functions in IDE

[TempodiBasic]

Just in case you guys didn't found it yet, here's my Notepad++ config for QB64.

Hi RhoSigma
I had tryed and used your config for QB64  and until there was no _OPTION EXPLICIT and _OPTION EXPLICIT ARRAY commands IMHO it is a very interesting way to write QB64 code into Notepad++.
But these 2 parser commands are not makable into another Editor like Notepad++ or VScode or Intellij++ or anyothers Eclipse/NetBeans/etc.
Further developing of QB64IDE had added interpreter of QB64 and a debug tool very close to the original of QB45... so writing code into Notepad++ with customized color for keywords and for the other parts of code (variables, comments, numbers, strings)
but lacking of those other features can be a choice for all those people that has used to write code without those tools. Instead all those need/like of _option explicit or of  debugger or of interpreter for a runtime  execution, the adventure stops here.

[RhoSigma]

Just in case you guys didn't found it yet, here's my Notepad++ config for QB64.

Hi RhoSigma
I had tryed and used your config for QB64  and until there was no _OPTION EXPLICIT and _OPTION EXPLICIT ARRAY commands IMHO it is a very interesting way to write QB64 code into Notepad++.
But these 2 parser commands are not makable into another Editor like Notepad++ or VScode or Intellij++ or anyothers Eclipse/NetBeans/etc.
Further developing of QB64IDE had added interpreter of QB64 and a debug tool very close to the original of QB45... so writing code into Notepad++ with customized color for keywords and for the other parts of code (variables, comments, numbers, strings)
but lacking of those other features can be a choice for all those people that has used to write code without those tools. Instead all those need/like of _option explicit or of  debugger or of interpreter for a runtime  execution, the adventure stops here.

Hi TempodiBasic,
exactly for that reason you can always open your code in the IDE right from Notepad++ its "Run" menu. It's right that N++ can't do the _Explicit checks nor debugging nor automatic code formatting.

I never considered N++ as a replacement of the IDE, but as convenience addition. E.g. I personally write my code in N++ just as it comes, when working with libraries I can enjoy the comfort of having it open in different tabs and I can use all the cool editing facilities. When I wrote enough lines of code and get the impression that it becomes cluttery and I lose the overview, then I press Ctrl-S to save then Ctrl-F7 to load it into the IDE, which will nicely format the code and also warns me for _Explicit errors. Now I press Ctrl-S in the IDE to save the just formatted code and then quit the IDE. Now N++ immediatly recognize the change and update the code and I go on coding in N++ until I next time lose the overview.

In short, see the IDE and N++ as companions, not as competitors.

[TempodiBasic]

I don't see code folding as an unreasonable request but I'm also not going to be the one having to code such a thing. It could be quite difficult to do. But I don't think it would necessarily be more resource intensive, since code is hidden from display. I could be wrong, though. And if I am, I'm sure someone will be quick to let me know.

I agree that the collapsable  block of code  is a fine feature that can be useful, moreover it requests only a modding to the part of code that manage the output of the text in the editor window, in the case the QB64IDE has one routine to do this.
But  I think that it is important to say that QB64 IDE has some navigation tools:
1. via Search menu you can use the Go To line  (Ctrl+G) command
2. a Quick Navigation option that let you follow the flow of the code and go back using the little arrow to left appaering on the editor screen of the IDE
3. a Bookmark tool in which you can set some bookmark points by Alt+left arrow (How many you can set I dunno)) and navigate through these by Alt+up arrow and Alt+down arrow.

[TempodiBasic]

@RhoSigma

In short, see the IDE and N++ as companions, not as competitors.

This is a very interesting point of view and subsequential a very interesting way to work for writing QB64 code.
Thanks for sharing this,

[mnrvovrfc]

I never considered N++ as a replacement of the IDE, but as convenience addition. E.g. I personally write my code in N++ just as it comes, when working with libraries I can enjoy the comfort of having it open in different tabs and I can use all the cool editing facilities. When I wrote enough lines of code and get the impression that it becomes cluttery and I lose the overview, then I press Ctrl-S to save then Ctrl-F7 to load it into the IDE, which will nicely format the code and also warns me for _Explicit errors. Now I press Ctrl-S in the IDE to save the just formatted code and then quit the IDE. Now N++ immediatly recognize the change and update the code and I go on coding in N++ until I next time lose the overview.

It sure beats having to fire up the QB64PE program from the terminal, only to check which variable is incorrectly assumed as single precision...

[aurel]

My code editor for qb64 have left-side panel where SUB-s and FUNC are listed

[mnrvovrfc]

From armchair distance, code-folding might not be difficult to do after all. Store each BASIC file line(*) as a numerical array, for which ones to display. The "folded" lines are then excluded from this array. (shrugs)

(*) A "line" is at the mercy of the newline character at the end. More tricky would be to account for the underscore that allows continuation of a very long "IF... THEN" statement or something else.

But then this could add to the IDE's memory requirements. Also the auto-complete. I've seen it in Openoffice/Libreoffice: when the user starts submitting words into a list, because he/she is annoyed with the spell-checker or whatever, that list could become large very soon. Binary search is wonderful but the overhead could begin to build up when the list has to be referred to multiple times in a single code line the programmer is typing into. Another thing is how to show the auto-complete: just type the rest of the text out, or show it in a nice-looking temporary pop-up?

Another possibility is "split" view, like QuickBASIC supported, limit to one large source code file viewed in two different places. Maybe expand that to show that source code in one pane, and an include file in the other pane.

[bobalooie]

Just in case you guys didn't found it yet, here's my Notepad++ config for QB64.

Well, this is a pretty slick adaptation, thanks for sharing!

[mnrvovrfc]

Before long, if this project could find another maintainer, the QB64 IDE could be offered in more than one mode. I don't like many gimmicks it gained since the last SDL edition. Therefore, offer a "Spartan" or "stripped-down" level of the IDE, and also have a version like what it has become today. The lesser edition could be fixed only if it contains a serious bug or security issue long not discovered.

There are users trying to run the IDE on Windows7 with single-core CPU and limited memory. They might appreciate the ability to disable code-folding, include-file auto-display or anything that enhances the experience. Yeah sure, they are also trying to get millions of frames per second, trying to "let the music play" without starting and stopping and glitches, and are anxious to get that "in-house" download manager going...

(This forum should support a "spoiler" posting trick...)
The reaction would be interesting from the "official" version guys: what is highest priority for new functionality, the IDE or for user programs?

[bplus]

I say to brook, stick with the On / Off switches for the bells and whistles on IDE, that way everyone can have their cake and diet too!