On Sat, 17 Nov 2018 10:57:58 -0500, Paul wrote:

A neat thing about an IDE, is you can run a program you just
wrote, attach a debugger, and when you hit a breakpoint, the
text editor in the IDE "jumps" to the line of code where the
program is currently stopped.

This (very detailed) post is only for J.P. Gilliver whom I respect, so I
will explain, in detail, how IDEs are (vastly) _different_, in terms of
what a noob needs in monitor real-estate setup.
http://www.bild.me/bild.php?file=5901351androidstudio55.jpg

Bear in mind I'm a complete noob to this particular IDE, so the problem
*instantly* gets _different_ in that this isn't just punching buttons in
something relatively simple like, oh, say, "The GIMP", or "Photoshop", or
"ShotCut" (all of which pale in comparison to the complexity of this IDE).

Paul is correct (as alway, where, to help others who don't know how
freaking complex IDEs can be, here is a sample screenshot of the IDE that
I'm currently using.
http://www.bild.me/bild.php?file=9210567androidstudio05.jpg

The goal of this particular IDE, is to write Android apps on Windows:
http://www.bild.me/bild.php?file=5881250androidstudio73.jpg

Where the IDE is used to design & test Android apps on Windows computers:
http://www.bild.me/bild.php?file=5614359androidstudio42.jpg

It has many "panes", from coding panes, to error panes, to CAD panes, to
widget panes, to variable panes, to setting panes, to execution panes,
etc., all the while it interfaces to external devices and emulated devices.
http://www.bild.me/bild.php?file=7301488androidstudio29.jpg

It's very extensible, where you can add an entire new level of complexity,
such as adding the entire suite of Microsoft Visual Studio Android
emulators, as I did, which brings in yet another GUI into the equation:
http://www.bild.me/bild.php?file=9766951androidstudio33.jpg

When you're doing all that, even WITHOUT the video tutorials, your screen
is filled to the brim with necessary windows, which is shown here.
http://www.bild.me/bild.php?file=8515596androidstudio46.jpg

At the same time you're dealing with all that, you're _also_ dealing with
the Windows file system file explorer.
http://www.bild.me/bild.php?file=1054744androidstudio50.jpg

Where you're constantly creating & deleting & editing & moving files.
http://www.bild.me/bild.php?file=5602322androidstudio51.jpg

And all that assumes everything is already WORKING just dandy!
http://www.bild.me/bild.php?file=5790092androidstudio56.jpg

Which, almost always is not the case, at least for a noob like I am, so
you're constantly debugging something in Windows!
http://www.bild.me/bild.php?file=2597741androidstudio62.jpg

After all that, then add a start-and-stop video tutorial to _that_ mess,
and you see that the need for screen real estate is paramount!
http://www.bild.me/bild.php?file=7987464androidstudio74.jpg

To a noob, there is no freaking way they will get _anything_ done without
following a step-by-step tutorial. And, for a noob, the problem with almost
all (if not all) tutorials are numerous, where I can just summarize by
saying there are no good tutorials out there that I can find (yet) for this
particular IDE. (I'm not the only one looking where others have said the
same thing.)

Mostly the tutorials aren't so great because they're usually _old_ (like
they're on version 1 of the tools while the current tool is version 3), so
all the button presses are different.

Lots of the non-video tutorials don't show WHERE the icons are that they
hit, which is compounded by the fact that the icons are in different places
given the inevitable version mismatch (and setup mismatches).

For a noob, literally, you need more real estate than the typical 17-inch
monitor. If you have a HUGE monitor, then this question doesn't apply.

*But if you have only two small'ish monitors, the question applies.*

In summary, for J.P. Gilliver, an "IDE" is a complete environment (much
like, I guess, Microsoft Office is), where, for a noob, who is new to both
coding, and to emulation and to writing Android apps, the amount of "real
estate" you need on your monitor is *instantly* greater than doing simpler
things.

If you already have a *huge* monitor, the problem is vastly less.
If you have a *tiny* monitor, like I have, the problem compounds.
When you add a second 17" monitor, like I did, "things change".

Since I'm all about organization (if you have to resort to a search, you've
already lost the battle), all I'm asking is that people who have dealt with
these monitor changes for years to give me organizational advice.