Poll: who has tried a740g InForm setup for QB64pe

[Magdha]

The poll is only for those who tried a740g's setup. 

If you did try it and succeeded but don't remember how, sounds to me like a modification through muddling your way along. Seems to me you'd remember a straight out of the box success.

Just for the record, I think it was straight-out-the-box.  Honestly can't remember.  So that would make it 4/1/0 at time of posting.
Magdha, resident at the QB64 Home for the Bewildered.

[TempodiBasic]

Hi guys and gals of QB64pe & InformPE fans

I have never had an issue in the installation and execution of InformPE.exe.
Run it, build app, compile app, run app. No issue.

But also I must say that I have never got UIeditor.exe there, in my Lubuntu/Kubuntu land! 
And there I got some issues with compatibility with Windowing system (both KDE and its plasma, both OpenBox both LXqt) and with built applications. But this is another tale.
Also QB64pe has an issue of viewport in these windowing systems (take a look at my tool tool for testing SCREEN viewport) while it doesn't exist for other Linux Users in other Distros. But also this is another different tale.

So coming back to the main poll:
Does InformPE work for you? YYYYEEEEESSSSSS

I hope to see as soon as a thread with the Best Practice for sharing Source code of applications made using InformPE .
In another thread, some of us (InformPE users) have discussed about our different ways to do this and how using different ways to include libraries can bring to issues for who download the files. So we need a canonical way to do this.
PLEASE WRITE THE TEN COMMANDMENTS : it is simpler  communicating and sharing works while we using shared rules.

with empathy
Lucky TempodiBasic

[Magdha]

I hope to see as soon as a thread with the Best Practice for sharing Source code of applications made using InformPE .

Sanity check required:
Am I correct in believing that / is ALWAYS used as a directory marker in all PE .bas files?  \ will work with Windows OS (and is still required in Windows Shell commands).
But the Inform Include statements will ALWAYS be:
'$INCLUDE:'InForm/InForm.bi'
'$INCLUDE:'InForm/xp.uitheme'
& At End
'$INCLUDE:'InForm/InForm.ui'

The Project Directory will have the InForm folder in it.

Some of my recent InForm work used \ instead of /, I think.  A mistake for universality.

[SMcNeill]

When it comes to many of the QB64PE commands, from what I remember, the slash really doesn't matter.   QB64PE will look at your OS and then do the appropriate substitution for you whit regard of slashing.   It won't work with SHELL statements, but many of the built in functions like $INCLUDE will swap from / to \ as needed for yout OS.

Or at least... I *think* it used to.   I honestly haven't did anything multiplatform for ages.   Try this -- it works for me:

HW.bas :

Code: (Select All)

'$Include:'.\HW count.bas'

'$Include:'./HW count.bas'

HW Count.bas

Code: (Select All)

count = count + 1

Print "Hello World"; count

The first includes the second, and once compiled you can see that *BOTH* includes are added to the file. The direction of the slash really doesn't change anything with regards to finding the file specified.

[TempodiBasic]

I have an experience of selfmanagment of \ and / by QB64pe IDE,
moreover I can affirm that in the same path mixing \ and / (BAD PRACTICE) doesn't affect the result. 
So if the path is right, the file was included.  

Talking about the path I have an experience of different ways to manage it by Informpe (UIeditor) and QB64pe IDE.
So the included files' path sometimes is wrong when you compile from within QB64pe, and correcting handly the path it works.
This is true for my Kubuntuland, and in a next future time I'll test this also in Windows11.

So if in Windows11 you have not installed Inform in the QB64pe folder, but outside of this, you'll get an error File Not found for the standard InformPE included files, also if in the folder of the application to be compiled (for example my NewPongClone) there are all standard InformPE files.

[Magdha]

@SMcNeill Thanks Steve.  On my system it doesn't seem to matter which is used.

[bplus]

Yeah from what I remember Windows doesn't care which slash you use.

AI agrees generally:

Code: (Select All)

Windows generally does not care which slash you use for file paths, as it accepts both backslashes (\) and forward slashes (/) in most applications, APIs, and PowerShell. While the native Windows separator is the backslash, the system frequently converts forward slashes to backslashes automatically.
Reddit
Reddit
+3
Key Details on Slash Usage in Windows:
Compatibility: Most Windows APIs, PowerShell, and File Explorer treat forward slashes (/) as valid directory separators, even though the standard is backslash (\).
Context Differences: While C:/Users/Files often works, some legacy command-line tools or specific software might strictly require the backslash (\).
Programming (Python/Node): Using forward slashes in programming is often preferred for cross-platform compatibility (working on both Windows and Linux), as languages like Python automatically handle the conversion.
Historical Context: The backslash was originally chosen for DOS to avoid conflict with command-line switches (e.g., /p).
Stack Overflow
Stack Overflow
+7
Best Practice: Use backslashes (\) for native Windows commands, but feel free to use forward slashes (/) in web browsers, coding, and most modern applications.

---

So 6 votes in, nobody will confess to being unsuccessful. NOT surprising bLOL

[SMcNeill]

@SMcNeill Thanks Steve.  On my system it doesn't seem to matter which is used.

Note that it may matter if you use SHELL or other system type calls that aren't handled internally by QB64PE.  Same with DECLARE LIBRARY calls and such.  If you're using things outside of vanilla QB64, then you may have issues with / vs \, but in QB64 it usually doesn't matter.

[ahenry3068]

@SMcNeill Thanks Steve.  On my system it doesn't seem to matter which is used.

Note that it may matter if you use SHELL or other system type calls that aren't handled internally by QB64PE.  Same with DECLARE LIBRARY calls and such.  If you're using things outside of vanilla QB64, then you may have issues with / vs \, but in QB64 it usually doesn't matter.

   It's a bit of a pita but for stuff like that I use

Code: (Select All)

DIM SHARED SLASH$



$IF WINDOWS THEN

      SLASH$ = "\"

$ELSE

      SLASH$ = "/"

$END IF

   Then I make sure I build my Command strings for shell or file paths with the SLASH$ variable !