Thoughts

[TILogistic]

Thoughts

When we decided to develop in B4X, it was this post that guided us to use B4X in our mobile projects and others in B4J.

CustomFloatingMenuButton - B4A Library source code

The attached code shows how to create a Floating Menu Button, you can show the button by clicking on a button or a swipe gesture (right edge of the screen). This is a guide that hopefully will help you write libraries in B4A. B4A is a POWERFUL Android development tool (despite all its...

www.b4x.com

We know Java, Visual Studio, Visual Android, Xamarin, Angular, Ionic, React, Flutter and others very well.

But we wanted to have a single IDE to create and have control of all our components that we develop for future modifications or maintenance of our APPs and not have third-party components (GitHub) that we would depend on the creator of these components.

That is why we always try to create our own components (B4X) so as not to run the risk that a third party will stop maintaining the component (GitHub) that we could use.

It's just a personal thought.

 

[Erel]

That is why we always try to create our own components (B4X) so as not to run the risk that a third party will stop maintaining the component (GitHub) that we could use.

Note that all the new custom views that I release are released as b4xlibs. Not all developers are aware to the fact that the b4xlib file is a regular zip file and the source code is inside the zip.
You can create your own versions of these views based on this source code (this is not always the case with b4xlibs libraries by other developers).

 

[TILogistic]

Note that all the new custom views that I release are released as b4xlibs. Not all developers are aware to the fact that the b4xlib file is a regular zip file and the source code is inside the zip.
You can create your own versions of these views based on this source code (this is not always the case with b4xlibs libraries by other developers).

EREL:
I'm not referring to the b4xlibs libraries, we know they are B4X source code.

I mean this comment:

B4A is a POWERFUL Android development tool (despite all its limitations), and is usually overlooked by some users (especially noobs and LAZY "developers")
that's why they are always asking to "wrap" libraries they found around the interwebz (Erel should consider releasing a new version called B4G (Basic For GitHub))
since apparently some users have an infatuation with code posted there and do NOTHING but wrapping those libraries no matter how simple or silly might be,
that been said, some of those libraries could be EASILY done using nothing but Good 'ol B4A code (Fact: ALL my libraries posted are written in 100% B4A),
granted, some libraries would be too difficult if not impossible to write in B4A but there's where we draw the line, what you should do is look at the library
and ask yourselves: How could I do that in B4A? and then code away and TRY IT, don't sit there waiting for someone else to write it for you or posting silly "+1"
posts requesting a wrap, if that's all you do then you will NEVER learn.