Re: [orca-list] Two questions about Linux termanology

[Christopher Chaltain <chaltain gmail com>]

I'll take a crack at this.


Flat comes from the fact that you're reviewing the screen or application 
interface and everything on it without any regard to the structure of 
the interface. You don't know what's a menu, title, parent, child and so 
on. You're just getting whatever's on the screen in  a flat 
structureless manner.


You're right about package. A package includes the application you want, 
all of the necessary dependencies and the default settings for the 
application. These are called packages and managed with a package 
manager, like APT. If you grab a tar file and need to make it yourself 
then it is frequently just called an application.




On 06/28/2018 07:53 PM, Christopher-Mark Gilland via orca-list wrote:
> Guys,
>
> I have two really quick questions about a few terms in the Linux realm of speaking.
>
> First of all, let's talk about the term I have in regards to Orca. I know what it means to use flat review to survey 
> the screen, but I'm curious. Where does the word "flat" come from? Why specifically do we use the term flat 
> review? I guess what I'm saying is, I don't understand the concept here in this context of where flat came from. Is it 
> actually an acronym?
>
> My second question is a little bit more complex, but not by much.
>
> When installing things under Linux regardless the process you take to do so, we often talk about installing a 
> package. We hardly ever say installing a program, or installing an application. When I think of a package, I 
> go back to in real life nontechnical terms. A package is generally something which contains multiple items to 
> make up the bigger picture, if you will.
>
> Most packages on Linux can't be installed alone. Some can, I know, but most cannot be. They require other 
> packages/libraries, or rather, dependencies, to function correctly.
>
> Is this why we call things packages in the Linux world? Is it mainly because the hierarchy of a full 
> installation usually consists of the main thing you want to install, but then along with it, you usually will 
> pull other things as well in the process in order to have full functionality? Therefore, you're not 
> technically installing just one thing. You're installing a package, as it's a full set of things. The main 
> application, but then also all the dependencies. Is this a valid way of looking at it? Before anyone comes to 
> me and says, who cares! It's what it is, just deal with it, please don't be rude! I think this is truly an 
> interesting question at hand. If you feel otherwise, just hit your delete key, but don't troll me for asking 
> a totally innocent question.
>
> Chris.
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
> Log bugs and feature requests at http://bugzilla.gnome.org

--
Christopher (CJ)
Chaltain at Gmail