Mikelgiles Active Member Licensed User Longtime User Sep 14, 2019 #1 Can anyone voice opinions on the pros & cons of setting up nodes in the source code instead of doing it in the designer?
Can anyone voice opinions on the pros & cons of setting up nodes in the source code instead of doing it in the designer?
EnriqueGonzalez Expert Licensed User Longtime User Sep 14, 2019 #2 Apart from the extra work for the code ones. There shouldn't be any difference. There are some views called customviews, those are better with the designer not because something fancy but because ide request to do so. Upvote 0
Apart from the extra work for the code ones. There shouldn't be any difference. There are some views called customviews, those are better with the designer not because something fancy but because ide request to do so.
Daestrum Expert Licensed User Longtime User Sep 14, 2019 #3 The biggest advantage of using the designer would be the ability (now) to copy them to other platforms eg, Android. For quick test apps I tend to use code to create the layouts. Upvote 0
The biggest advantage of using the designer would be the ability (now) to copy them to other platforms eg, Android. For quick test apps I tend to use code to create the layouts.
Erel B4X founder Staff member Licensed User Longtime User Sep 15, 2019 #4 In B4J and B4i it is especially important to use the designer as the designer script and anchors are reapplied when the parent is resized. If you create the layout programmatically then you must also handle the various resize events and take care of resizing the layouts. Upvote 0
In B4J and B4i it is especially important to use the designer as the designer script and anchors are reapplied when the parent is resized. If you create the layout programmatically then you must also handle the various resize events and take care of resizing the layouts.
xulihang Well-Known Member Licensed User Longtime User Sep 15, 2019 #5 I use ABPlugin to add extra functionalities to my app. But as the plugin is compiled to libraries, I cannot load layout files, so I have to code the UI, which is a bit inconvenient. I have to deal with all kinds of anchors and size settings. Upvote 0
I use ABPlugin to add extra functionalities to my app. But as the plugin is compiled to libraries, I cannot load layout files, so I have to code the UI, which is a bit inconvenient. I have to deal with all kinds of anchors and size settings.
KMatle Expert Licensed User Longtime User Sep 15, 2019 #6 In B4a I like to add views by code which is good for me (first to learn how it works, now more "I'm used to it"). In B4J I only use the designer. Don't ask me, why B4x has developed enourous since I started so the designer is now a "pro tool" which I strongly recommend. Upvote 0
In B4a I like to add views by code which is good for me (first to learn how it works, now more "I'm used to it"). In B4J I only use the designer. Don't ask me, why B4x has developed enourous since I started so the designer is now a "pro tool" which I strongly recommend.
MarkusR Well-Known Member Licensed User Longtime User Sep 16, 2019 #7 if there are hundreds of ui elements it is easier by code, or if you have a dynamic view. else i prefer to see the layout in the designer. Upvote 0
if there are hundreds of ui elements it is easier by code, or if you have a dynamic view. else i prefer to see the layout in the designer.