FBIde - still alive
Yeah I know it's controversial, but how many times do you type out the same crap at the start of every program. If it put all the declarations in a specific place I'm sure it wouldn't be too hard to have a look over it every now and then.
That said it's no big deal to me, better to get the new version out b4 modules like this. It just came off the back of a thought that maybe QB was onto something with it's implicit stuff and we get too professional/pedantic sometimes.
That said it's no big deal to me, better to get the new version out b4 modules like this. It just came off the back of a thought that maybe QB was onto something with it's implicit stuff and we get too professional/pedantic sometimes.
-
- Posts: 605
- Joined: Feb 18, 2006 13:30
- Location: Alexandria / Egypt
- Contact:
I think wolfstar is referring to code snippets. I could see the usefullness in those. push say ctrl+alt+1 and it inserts
i was thinking of something like that for muddyide, but that's a ways off still.
Code: Select all
#include "fbgfx.bi
using fb
hi guys.
Just wanted to let everyone know that I have decided to port fbide project to QT toolkit. QT is more feature rich and better developed ( and better supported on linux machines ) than wx. Thus fbide is now migrating. This means some more delay to the release, but I hope it will be worth it :)
Just wanted to let everyone know that I have decided to port fbide project to QT toolkit. QT is more feature rich and better developed ( and better supported on linux machines ) than wx. Thus fbide is now migrating. This means some more delay to the release, but I hope it will be worth it :)
Hi guys.
I have reconsidered using QT after playing with it and evaluating it. It is a very nice ( and certainly a quality ) toolkit and in many ways superior to wxWidgets - however several aspects about it are a rather turn off. For example it's use of external and QT specific build tools makes it complicated to compile or use with most IDE's. It's not stricly standard c++, lacks some features I am fond of and complicated QScintilla appears to be a commercial product...
All in all I decided to keep wxWidgets.
Also I'd like to give out latest dev snapshot. There is a lot of on-going work. Major features in this one is "modification margins" on the side of the editor. It marks the line as ( yellow - edited lines, green - saved lines, non - untouched )
Although it still needs some work and ironing some bugs out. If you would give it a try and give me exact combination of actions that make it fail ( just edit, insert, copy, paste text ) please let me know.
THIS IS STILL A WIP AND IS NOT SUITED FOR ACTUAL USE. THIS IS ONLY MEANT AS A PREVIEW AND IS PRE-ALPHA STATE.
Use at your own risk
http://fbdevzone.com/downloads/fbide-de ... 3-2009.rar
Have fun
I have reconsidered using QT after playing with it and evaluating it. It is a very nice ( and certainly a quality ) toolkit and in many ways superior to wxWidgets - however several aspects about it are a rather turn off. For example it's use of external and QT specific build tools makes it complicated to compile or use with most IDE's. It's not stricly standard c++, lacks some features I am fond of and complicated QScintilla appears to be a commercial product...
All in all I decided to keep wxWidgets.
Also I'd like to give out latest dev snapshot. There is a lot of on-going work. Major features in this one is "modification margins" on the side of the editor. It marks the line as ( yellow - edited lines, green - saved lines, non - untouched )
Although it still needs some work and ironing some bugs out. If you would give it a try and give me exact combination of actions that make it fail ( just edit, insert, copy, paste text ) please let me know.
THIS IS STILL A WIP AND IS NOT SUITED FOR ACTUAL USE. THIS IS ONLY MEANT AS A PREVIEW AND IS PRE-ALPHA STATE.
Use at your own risk
http://fbdevzone.com/downloads/fbide-de ... 3-2009.rar
Have fun
But why has this editor been written in C++? Why has it not been written in FreeBASIC? Accessing WxWidgets from FreeBASIC is difficult (though the C binding to WxWidgets is actually being maintained by the people that maintain WxHaskell). But there is IUP, there is GTK+, there are choices. You're going to get GTK on Linux anyway (WxWidgets 'uses' the GTK widgets) so why not use GTK right away?VonGodric wrote:Hi guys.
....All in all I decided to keep wxWidgets....
I know debugging large(r) scale FreeBASIC programs is a bit difficult (using Insight helps but maybe not enough) but imagine the advantages of building an editor in FreeBASIC.
FreeBASIC programmers could help out in developing your editor. I'm sure that would make the development of your editor more of a community effort which I'd consider to be a positive thing.
Apart from that you are bound to find bugs in FreeBASIC while developing a large scale FreeBASIC application. It would aid the development of FreeBASIC if you'd write your editor in FreeBASIC.
The above is, of course, just a little food for thought.
-
- Posts: 2655
- Joined: Aug 28, 2008 10:54
- Location: new york
I really don't like the putrid pack boxes in GTK.
The original edit looked like instead of having collapsible blocks of code had color coordination. The color coordination makes it easier to sift through large files. And control-scroll makes the collapsible blocks more or less a shrug.
I really like the addition of the color blocks, and I always felt the FBIDE was an awesome no frills editor. A few frills will make it nicer...
Anyway, when I took the time to test it in comparison to FBEdit, I found FBIDE to be easier to work with, and my programs always compile when I hit F5. The lack of projects means nothing to me... I've never been a visual programmer and I never will be.
But the thing is both IDE's are well liked by those who are drawn to one or the other style of programming. So they're both doing something right.
I would probably advise against moving into doing things that FBEdit already does better, because people won't switch over, because people (like crackheads) are creatures of habit.
That and you already have a solid fan base of people who like typing... So I would say cater to your clientele and improve upon what FBIDE is already doing well instead of making it have the functionality of FBEDIT...
I like the original a lot, and I like the ideas you have about improving it.
BTW- I've written all my projects in FBIDE, most of which are upwards of 10 files large each around 10kb... Big projects, amateur programmer, FBIde... It can be done, if you're comfortable doing it and you're willing to organize your data yourself (which is better anyway...)
You said awhile back FBIDE was bassed on plugins?
How does this work?
rb
The original edit looked like instead of having collapsible blocks of code had color coordination. The color coordination makes it easier to sift through large files. And control-scroll makes the collapsible blocks more or less a shrug.
I really like the addition of the color blocks, and I always felt the FBIDE was an awesome no frills editor. A few frills will make it nicer...
Anyway, when I took the time to test it in comparison to FBEdit, I found FBIDE to be easier to work with, and my programs always compile when I hit F5. The lack of projects means nothing to me... I've never been a visual programmer and I never will be.
But the thing is both IDE's are well liked by those who are drawn to one or the other style of programming. So they're both doing something right.
I would probably advise against moving into doing things that FBEdit already does better, because people won't switch over, because people (like crackheads) are creatures of habit.
That and you already have a solid fan base of people who like typing... So I would say cater to your clientele and improve upon what FBIDE is already doing well instead of making it have the functionality of FBEDIT...
I like the original a lot, and I like the ideas you have about improving it.
BTW- I've written all my projects in FBIDE, most of which are upwards of 10 files large each around 10kb... Big projects, amateur programmer, FBIde... It can be done, if you're comfortable doing it and you're willing to organize your data yourself (which is better anyway...)
You said awhile back FBIDE was bassed on plugins?
How does this work?
rb
thanks guys for your responses:
AGS:
I started fbide project before FB even came out and then for a long time FB was not simply capable ( without great difficulty ) to handle large projects. That's when most of the previous FBIde was written.
Other than "historical" reasons are that I am fan of OOP and know wxWidgets pretty well by now. wx-c port is terribly out of date but thanks for the tip on WxHaskell - I will check it out. Secondly a project written in c++ is something that will look attractive enough on my CV or portfolio of projects I have worked on. So here you are - selfish reasons :D
However I do plan to have ( at least in part ) of the SDK available directly in FreeBASIC to allow people to write plugins. But that remains to be seen...
rolliebollocks:
Thanks. I think GTK looks pretty nice. However wx uses native APIs where possible. As for copying fbedit - to be completely honest I have never really used it so I don't know. I did have a look at it like a year or even more ago for about 10 minutes and then it crashed on me. Haven't touched it since.
I code fbide mainly for myself - in that I code it the way I like it and I add features I feel that I want to.
Plugins - yes current fbide "core" is written as an SDK - an api you can use to extend the IDE and add more functionality to it. check ide/plugins
For example the very freebasic editor window is provided by a plugin, art on the toolbars is provided by a plugin ( in config.ini there is an entry called "ui.plugin.theme=TangoTheme" change TangoTheme to ClassicTheme" :P )
So in theory I could add any kind of plugins like - rad tool, svn/cvs support, ftp, support for other languages, even games :D anything. without modifying the core of teh fbide at all.
AGS:
I started fbide project before FB even came out and then for a long time FB was not simply capable ( without great difficulty ) to handle large projects. That's when most of the previous FBIde was written.
Other than "historical" reasons are that I am fan of OOP and know wxWidgets pretty well by now. wx-c port is terribly out of date but thanks for the tip on WxHaskell - I will check it out. Secondly a project written in c++ is something that will look attractive enough on my CV or portfolio of projects I have worked on. So here you are - selfish reasons :D
However I do plan to have ( at least in part ) of the SDK available directly in FreeBASIC to allow people to write plugins. But that remains to be seen...
rolliebollocks:
Thanks. I think GTK looks pretty nice. However wx uses native APIs where possible. As for copying fbedit - to be completely honest I have never really used it so I don't know. I did have a look at it like a year or even more ago for about 10 minutes and then it crashed on me. Haven't touched it since.
I code fbide mainly for myself - in that I code it the way I like it and I add features I feel that I want to.
Plugins - yes current fbide "core" is written as an SDK - an api you can use to extend the IDE and add more functionality to it. check ide/plugins
For example the very freebasic editor window is provided by a plugin, art on the toolbars is provided by a plugin ( in config.ini there is an entry called "ui.plugin.theme=TangoTheme" change TangoTheme to ClassicTheme" :P )
So in theory I could add any kind of plugins like - rad tool, svn/cvs support, ftp, support for other languages, even games :D anything. without modifying the core of teh fbide at all.