(WISH) VisualBasic 6 GUI

robife

Member
Licensed User
Longtime User
Litle bit more LookLike VB6 And almost everything in one window.

What I mean with "one window" is
start with designer GUI, than with right click go to source code.
With changeable toolbar menu.(add/remove icons on toolbar) :sign0104:

visual.png
 

Vader

Well-Known Member
Licensed User
Longtime User
+1 to this.

I much prefer this way of doing things. VB did it, Delphi copied it, as did other groups.

When Microsoft had the opportunity to change it with the monumental move to .NET they just made it better. This tells me they must have a pretty good idea that it is the best way to do things.

Maybe you could release details on how the Activities are built and someone could help you out, much like you did with the B4A-Bridge? I'd happily sign a NDA.
 

mangojack

Expert
Licensed User
Longtime User
+1 as well .. the fact I to and fro between B4A , VB6 and 2010 that would be magnificent.
Cheers mj
 

pleskina

Member
Licensed User
Longtime User
It is nice to have such IDE (I am Delphi programmer otherwise), but I think most important reason to use present designer layout is to make it "portable" to any actual device. Embedding "virtual" designer into IDE makes sense on the other hand.
 

KMatle

Expert
Licensed User
Longtime User
Coming from VBA, for me it is difficult to use GUI objects like views, buttons, etc. Some things are the same, other's I don't understand so far.

Example (from my naive point of view as a beginner):

In VBA you can use and change all objects you've created in the designer GUI in a very intuitive way.

In B4A I often wonder why I can not change/retrieve an object's property like I do it in VBA or why it doesn't work or why it only works with THIS but not with THAT object.

Other things are sooooo easy, like "Just start b4a-bridge and connect. Click on Compile&Run..." ... WOW! .... THAT EASY?!
 

mc73

Well-Known Member
Licensed User
Longtime User
What I mean with "one window" is
start with designer GUI, than with right click go to source code.

I perfectly understand your points, still, this one is not something you would really want and here's why: In contrast with vb, layouts in b4a are not necessarily related to one specific module (activity). Since a layout can be used over and over again to different activities (though I have to admit this is not frequent), we cannot just click on a view and go to the corresponding event, since we don't really have a 1-1 relationship here. I know there can be some sort of chooser for this, but I find it will be more confusing than really simplifying things.
Anyway, having programmed with vb since its very start, took me some time to get really used to the new b4a environment, mainly due to how android really handles things and secondary due to how b4a handles things. Now, it looks pretty cool to me, but surely this is subjective :)
 
Top