New IDE

User projects written in or related to FreeBASIC.
Stueber
Posts: 46
Joined: Nov 22, 2009 16:20

Postby Stueber » Dec 30, 2009 12:54

oh, here's a new link http://users.freebasic-portal.de/stueber/Linux/ide_a11.tar.gz

By the way: The loading problem is solved.
Landeel
Posts: 710
Joined: Jan 25, 2007 10:32
Location: Brazil
Contact:

Postby Landeel » Dec 31, 2009 21:22

I'm getting :
./FB: symbol lookup error: ./FB: undefined symbol: _ZN7QTabBar12setExpandingEb
Stueber
Posts: 46
Joined: Nov 22, 2009 16:20

Postby Stueber » Jan 01, 2010 16:15

The IDE requires Qt 4.6.
Unfortunately, this version is not available yet from a few package repositories but it's merely a matter of time.
As a workaround, in this cases, it's possible to install the current SDK.

Important: This pre-compiled binary build (ide_a11.7z) is only suited for 64 bit architectures. A 32 bit build can be compiled from the sources being included.
Stueber
Posts: 46
Joined: Nov 22, 2009 16:20

New Version

Postby Stueber » Feb 15, 2010 19:58

Meanwhile I have extended the IDE significantly. Therefore, I’d like to show my new stage of work here. :-)

Switching to Scintilla as the main text edit control of the IDE
I have decided to switch to Scintilla, which is a very advanced text editing component. This change will permit several improvements and lots of new features in the next releases, as for example
  • calltips (a syntax-suggest function as known from VB)
  • auto-completion of code
  • folding of code structures (if-then-else statements, loops etc.)
  • live syntax-checking

A few new code editing features have already be implemented based on Scintilla:
  • zoom-in and zoom-out
  • indention
  • line numbers


New syntax highlighting
The IDE was given new syntax highlighting routines being able to deal with multi-line comments and preprocessor directives correctly. Moreover, the new highlighting function works much faster than the old implementation. Due to using Scintilla, personal settings concerning font sizes and font faces are possible.

Image


New GUI designer!
A new form designer (RAD) has been integrated in the IDE. At the moment it allows creating Windows-GUI applications but in future it will be able to export GTK-based GUIs also.
The embedded form designer creates XML files as a description of the forms. This approach can be compared to the FRM files known from VB. When compiling your application, the IDE exports temporary FB source code based on the information given in the XML file. The form designer is able to load existing XML GUI definitions. So you’re able to continue your work at the GUI after closing and restarting the IDE / your computer. ;-)
Within the designer, new controls are chosen out of a treeview (widget tree) and not by clicking buttons any more. Using another treeview you can manage the created controls (similar to the project explorer in VB). Furthermore, you can delete existing controls you don’t need any more.
Technical aspects: The GUI designer loads all the controls from control definition files (XML format) dynamically. Also the code (behavior of controls, methods) are stored in these XML files. The relationship between control properties (width, height, ...) and the preview in the design environment is implemented by scripting. Therefore, you can change the way a control looks and behaves in the IDE by editing the XML files.
The approach of XML-based control definitions allows easy adding and modifying of controls. It’s a bit like an open OCX system. ^^
Important notice: Currently only an pre-alpha preview version of the GUI designer is available for download. So please bear with me while I’m working on it. ;-)

Image

New project files
As a result of having restructured the file format of the project files used by the IDE, it’s not possible to open legacy project files any more. But the new project files allow a few improvements. Individual compile profiles (sets of fbc command line parameters for different purposes) are supported (e.g. „Debug“ and „Release“). They can be applied using a ComboBox in the IDE. Moreover, project files now contain relative paths, thereby allowing the user to move project folders without having to edit those files. ;-)
But still all the files belonging to one project have to be in the same directory. This will be changed in future releases.



New configuration dialog
The new configuration dialog doesn’t contain all the settings I’d like it to have, yet. But on the other hand it allows the user to configure the syntaxhighlighter. :-) In the next releases the config dialog will be extended of course.

Image

Many thanks in advance for your opinions!

Kind regards,
Stueber
dkl
Site Admin
Posts: 3210
Joined: Jul 28, 2005 14:45
Location: Germany

Postby dkl » Feb 15, 2010 21:52

It's nice to see you making progress. Scintilla is the best choice and RAD for FB is always eagerly awaited :p

Some thoughts:
I see no new or special concepts (compared to existing IDEs).
Please don't forget about possibilities of UI design: Which existing elements will never be used? What's missing?
Avoid making everything configurable.
I don't think including a webbrowser is a good idea: too heavy, everyone has one already.

(biased opinion: I don't like IDEs much, especially the all-in-one monsters)
Stueber
Posts: 46
Joined: Nov 22, 2009 16:20

Postby Stueber » Feb 16, 2010 0:41

I forgot the download link: here
aurelVZAB
Posts: 309
Joined: Jul 02, 2008 14:55
Location: Croatia
Contact:

Postby aurelVZAB » Feb 17, 2010 7:37

WOW 10MB 7z package, why is so big?
marcov
Posts: 2843
Joined: Jun 16, 2005 9:45
Location: Eindhoven, NL
Contact:

Postby marcov » Feb 17, 2010 9:37

aurelVZAB wrote:WOW 10MB 7z package, why is so big?


It is really time to throw away that 100MB HD now. If you get a modern one, it will be like a Terabyte, and the IDE will fit on it 100000 times.
marcov
Posts: 2843
Joined: Jun 16, 2005 9:45
Location: Eindhoven, NL
Contact:

Re: New Version

Postby marcov » Feb 17, 2010 9:39

Stueber wrote:

New GUI designer!
A new form designer (RAD) has been integrated in the IDE. At the moment it allows creating Windows-GUI applications but in future it will be able to export GTK-based GUIs also.
The embedded form designer creates XML files as a description of the forms. This approach can be compared to the FRM files known from VB. When compiling your application, the IDE exports temporary FB source code based on the information given in the XML file.


Ever considered not creating source code to instantiate a form, but stream the form as objects properties to a resource file? And then stream the object back into mem on instantiation.

The principle can be tighter(*) (only one load routine for all forms), and can be (minorly) postedited for internationalization purposes. (e.g. make a caption slightly longer, since in many languages phrases are longer than in English)

(*) smaller for large apps (streamed objects are more compact than instantiation code), usually larger for small apps (since RTTI pulls in objects that might not be streamed, unless all GUI widgets are in a dll/so)
Stueber
Posts: 46
Joined: Nov 22, 2009 16:20

Postby Stueber » Feb 17, 2010 10:05

WOW 10MB 7z package, why is so big?

Because QtWebkit. I use QtWebkit for reading the german reference.

@marcov: I answer you later, first I have to translate your post. (My englisch skills are weak) :)
marcov
Posts: 2843
Joined: Jun 16, 2005 9:45
Location: Eindhoven, NL
Contact:

Postby marcov » Feb 17, 2010 14:33

Stueber wrote:
WOW 10MB 7z package, why is so big?

Because QtWebkit. I use QtWebkit for reading the german reference.

@marcov: I answer you later, first I have to translate your post. (My englisch skills are weak) :)


If you are German (guestimate on your name), you can mail me directly at marco at freepascal dot org. My German skills are not that great, but maybe better than your English.
Stueber
Posts: 46
Joined: Nov 22, 2009 16:20

Postby Stueber » Feb 20, 2010 18:44

If I understood you right, you say that loading at runtime is better than converting the XML to basic sourcecode.
Both have a lot of pros and cons.
Translating the UI of a programm is easier when the XML file is loaded at runtime but converting to basic code is more dynamic and easier to implement for me.
All in all I think converting to code is better but if you know more reasons for loading at runtime I could implement both and give the user the choice.
marcov
Posts: 2843
Joined: Jun 16, 2005 9:45
Location: Eindhoven, NL
Contact:

Postby marcov » Feb 20, 2010 23:34

Stueber wrote:If I understood you right, you say that loading at runtime is better than converting the XML to basic sourcecode.


No, I asked if you considered it, and named some of the pros.

Both have a lot of pros and cons.
Translating the UI of a programm is easier when the XML file is loaded at runtime but converting to basic code is more dynamic and easier to implement for me.


Both correct. The latter is nearly always true, the better, more fundamental approaches need more work, and often backend changes (e.g. in this case higher percentage OS dependant due the need to support resources multiplatfomr)

All in all I think converting to code is better but if you know more reasons for loading at runtime I could implement both and give the user the choice.


I named the major ones already. (postediting, tighter code). The ability to postedit is btw also a disadvantages (since it is easier to do malicious edits, e.g. removing copyright notices, or making them invisible)

Runtime loading (but not in resources) is of course also important to store form layouts in databases or client server apps. This is mostly useful if the used components in the forms databind automatically, this way fields can be added by db-admins, and client apps need to be updated less often.

The only advantage of codegeneration is that form instantiation can be debugged a bit easier. Stepping through the generic loading code is possible, but a bit more involved. But usually this is fairly uninteresting, except for a developer who can always make an unittest in code, or reduce the impact by choosing breakpoints smartly.

I don't think that XML is good for runtime instantiation though. Better some more tight format. (validating XML parsers are quite bulky or external dependancies, and the forms will be bulkier, while there is not that much benefit compared to a simpler format)
cha0s
Site Admin
Posts: 5317
Joined: May 27, 2005 6:42
Location: Illinois
Contact:

Postby cha0s » Feb 21, 2010 16:13

Hey, nice lookin' app you got going here! Qt ftw. I wish we could use Qt with FB but I think that will never happen (the moc, for one)
Stueber
Posts: 46
Joined: Nov 22, 2009 16:20

Postby Stueber » Feb 21, 2010 16:29

This weekend I wrote a wrapper for a few basic QT classes for FB, if you are interessted you can post here or write to me in IRC.

Return to “Projects”

Who is online

Users browsing this forum: No registered users and 3 guests