I was reading the post about bugs, and started keying in things that were bothering me about DBPro and realized that they were not bugs as much as change requests. So I moved my thoughts over here. This will be reposted at DBDN.
------------------------------------------
I would most like to see object oriented code. I am finding it difficult to switch back to linear code. For instance having Events, Properties, And Procedures, with class reiteration. I picked up DarkBasicPro for it was a fast way to write test programs for clients. The problem is if all my foundation work is linear it makes it more difficult to take the process of the code and convert it to C++.
I would also like to see some custom GUI functions as native functions of the system. For example CreateWindow(PosX,PosY,Width,Height,Sizable) or CreateButton(PosX,PosY,Width,Height,Caption,EventHandler) this would simplify the creation of Gui's in general. (I know there have been a lot of attempts, privately and I applaud this, but it is not enough)
Option Explicit, would be nice so we have the choice of forcing variable declaration or not.
For the Editor, when I declare a type and then reference that type a context menu should drop down with the available type options. Saving me to have to look through my documentation for the 15th time.
The DarkBasicPro Manual is also in need of a LOT of work. It should be made in Microsoft Help Studio, hell it would be simplicity itself to convert the existing html into that format. This would allow true context sensitive help. This could also be leveraged in DBPro itself to give a help system to the programmers for writing there own help files. On top of that a professional manual writer should be hired, not written by programmers. In my 20 years in the industry I have not met a programmer who can write a good manual that does not read like a Chilton’s guide to auto-repair.
Lastly while I don’t think that dark basic pro should NOT be open source (Frankly I have been in this business to long to think Open Source works for programming languages) but the extensibility model should be extend to allow easier integration of further functionality. (By the way I applauded the new interface for DBpro it looks great! It was made available to the DBDN users, for those of you who have not seen it, get a DBDN membership, its well worth your money)
These are things in most modern programming languages, why are we taking a step backward, for simplicity sake? I would suggest that once you have learned OOP and event driven programming, that it is easier to use than linear code. I know I am having trouble shifting gears back.
Richard
Owner E-Engine Software©, part of the Cold Mountain Group© of companies
Game Programmer for 20 years.
"Aut viam inveniam aut faciam."
(I'll either find a way or make one.)