wxFBE is an FreeBASIC editor for both Windows and Linux. It is completely written in FreeBASIC and uses wx-c as a GUI.
Features:
FreeBASIC syntax highlighting
cross-platform
visual designer (emitting XML, wx-c, fltk-c, ...)
plugin system
multi compiler support
autoformat code while typing it
block comment and uncomment
indentation guides
multilingual
customisable
compiles and runs code from within the editor
tabbed
...
Screenshot on Win7 (click to enhance):
Here a early video of the usage on Ubuntu 12.04 VM: Video
This video shows the designer using wx-c emitter on Windows 7: Video
This video shows the designer using fltk emitter on Windows 7: Video
if you add a cool dark-background theme, add super-hardcore processing of entire project, and support modules i will use it :)
no need fr immediate window or anything other than build options, good colors and good ctrl+space help
if i press f2 (or some other key) i ___must___ go to that variable declaration or function.. it doesnt always work properly in fbedit :)
You will find a download link to a test release in the first post.
@Gonzo:
- There're no themes and you can't change the background color so far but change some other colors
- "super-hardcore processing of entire project" !? (as for projects, they doesn't exist so far)
- "support modules" - any special support?
- ctrl-space: auto complete is planned but will take some time so it isn't implemented now
- F2: not implemented, this will have to wait, until I got a function browser. Both functions will come together as one update
In the image file paths and file BAS need to make support for Unicode. Otherwise, no one other than English and German speak users will not be able to use the editor.
This is a general wx-c problem. I can omit it for windows but not for linux, so I didn't. Even the german language file don't uses german letters (ÄÖÜäöüß) to not run into this.
My plans are to fork wx-c on longterm, so I can fix it in future. For now, sorry, there's nothing I can make.
@Vanya: I guess I fixed the Unicode problem for Windows so far. On Linux it's still a problem, but dkl just fixed a WStr() releated bug in the runtime lib for Linux, so I can test if this will solve the problem with Linux as well.
@Vanya: I guess I fixed the Unicode problem for Windows so far. On Linux it's still a problem, but dkl just fixed a WStr() releated bug in the runtime lib for Linux, so I can test if this will solve the problem with Linux as well.
Thank you, but the same problems.
I think for the images to the toolbar should use relative paths, or this is not possible with the library WX?
I could use relative paths but this would destroy the drag&drop feature where you drop a file on the wxFBE.exe and it opens the file. In this cases it will try to load all images and language files from the path of the code file instead of the exe when using relative paths.
How do you use FBEdit then? I copied a translation from Google (дедушка) and used it as folder name. FBEdit couldn't load files from this folder at all and even my try to compile this file directly in my cmd the fbc gave me an error 23: File not found.
Same for FBIDE which can't do anything with a file in a folder like this.
MOD wrote:I could use relative paths but this would destroy the drag&drop feature where you drop a file on the wxFBE.exe and it opens the file. In this cases it will try to load all images and language files from the path of the code file instead of the exe when using relative paths.
How do you use FBEdit then? I copied a translation from Google (дедушка) and used it as folder name. FBEdit couldn't load files from this folder at all and even my try to compile this file directly in my cmd the fbc gave me an error 23: File not found.
Same for FBIDE which can't do anything with a file in a folder like this.
