I came to assembly from VB, so I love the Visual projects. However, I also love to streamline my code when building a release version. Is there a way to make a Visual project, and instead of building I want the assembly sources, which I can edit before I build it myself manually.
Also is there a way to turn off the spaces after commas?
Hi AeroAsm,
The visual library linked to Easy Code visual projects is just one compact library, so at the moment I'm afraid that I cannot do nothing about it, but I'll study the possiblity of dividing it in several parts.
About spaces after commas, just uncheck the option named Trim middle spaces and tabs in the Editor tab of Tools-->Options menu.
Regards,
Ramon
Thanks. So EasyCode has its own runtime library? I thought it just created asm files for you from the ecw files.
Yes, in fact it works like Visual Basic but in assembler. The visual library takes care of navigating through child controls while pressing the <Tab> key, the accelerators (<Alt+underlined char>), Font (name, size, bold, etc.), back and fore colors, the default and cancel buttons, etc.
Ramon
AeroASM,
I think Ramon is confused by what you are saying. EasyCode does not employ a runtime library in the sense that it adds a file that must be distributed with the executable. English can confuse some people. It will use DLLs in the same way as any other Windows executable.
Paul
I think you confused me more than Ramon. If it uses its own DLLs, then surely those DLLs must be distributed with the executable...
Hi AeroASM,
I think you deserve the best answer so you can come to the correct conclusion. So I have explained my thoughts to Ramon and I have asked him to give you an answer in that context. I am just a consultant in his project, he is the brain behind it all.
Take care,
Paul
Hi AeroASM,
When I created Easy Code I thought about a visual IDE, very closed to Visual Basic, being able to develop a Windows application quickly and easily. That makes some extra code necessary, taking care of the basic functions needed in any Windows application (navigation among child controls, shortcuts, fonts, colors, etc.). The Easy Code library takes care of all that and it can be linked statically or dynamically. When linked statically all code is inside the executable, so you do not need any other file than the .exe in order to run the application in any machine having a Windows O.S. On the other hand, only when linked dynamically, you need the ECObj100.dll file for the executable to work, which is very closed to a runtime library, but ONLY for visual projects linked dynamically.
At the same time, I also thought about the traditional mode and that is why Easy Code has the classic projects feature, where it works like any other IDE and you have to write all code for the application to work. No library nor extra code added in classic projects.
Regards,
Ramon
Thanks, that was a good explanation.
Personally, I think it would be better to miss out on some of the capabilities provided by VB and have no runtime library, but I appreciate that Easy Code is for people who don't really want to make a complete switch from Vb to ASM
That's it! Easy Code pretends to be a good classic IDE (I personally use it a lot in classic mode), but, at the same time, it offers an interesting visual way of assembly programmming which is really appreciated for many people. In visual mode, you can develop an application very quickly, saving you of having to write code even for hours and the only price you have to pay is a slight increase of the final executable file (just a few KB).
On the other hand, and as I said before, for those who prefer the traditional way of assembly programming, you have the classic mode, where I think Easy Code is a very good and complete IDE.
Ramon
Now, in Classic Mode, can the visual editor be used to make resource files? One of these days I hope to be abble to switch from Visual to Classic.
Thats what I was trying to say, but I forgot to say it. I would like the Visual capabilities, but without the larger exe, even if it means less functionality.
Hi Robert,
Yes, the Resource editor is available in classic projects so that you can make resources for your application. Have a look at (The Resource Editor topic, written by Paul E. Brennick, in the Easy Code help file.
Ramon
Hi AeroAsm,
I did my best trying to write the EasyCode library as short as possible, but take into account that all visual capabilities have to be managed, and that means code! Otherwise, with no capabilities, the visual mode would have no sense. Anything you want to do, create the child controls and their brushesand fonts, or managing the <Tab> key to navigate through them, needs the corresponding code to be written anywhere. There is no other way (as far as I know).
Ramon
How about embedding the code in the ASM file?
Well, in fact that's what you do (more or less) when linking the library statically (the default option).
Ramon
Hey Ramon,
I also like the development environment. Not so much the VB interface but thats just personal preference. I thought I would point out from an earlier post of yours:
Quote
or managing the <Tab> key to navigate through them
You dont have to do this manually if you dont want to. In the main window message pump add a call to IsDialogMessage and this will do it for you which will reduce your "run-time" file size.
IsDialogMessage:
Quote
Although the IsDialogMessage function is intended for modeless dialog boxes, you can use it with any window that contains controls, enabling the windows to provide the same keyboard selection as is used in a dialog box.
Hi Maelstrom,
Yes, you are right but there are some problems using that API call. For example, you never get access to some keys (<Tab>, <Esc>, <Return>).
Ramon