[haiku-development] Re: Utilities Folder (was: hrev44091 - build/jam)
- From: pulkomandy <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 2 May 2012 21:54:27 +0200
On Wed, May 02, 2012 at 09:50:18PM +0200, Truls Becken wrote:
> On 2012-05-02, pulkomandy wrote:
>
> > So, to make Terminal an application in this sense, we would need to add
> > some kind of document to work with.
> > [..snip..]
> > my typical setup would be a gvim window + a terminal in the right dir
>
> There you are - every folder on your system is a terminal "document" ;)
>
> -Truls
>
Not really. A document for me implies :
* Window size & position
* File contents
* Any other app setting
Folder are Tracker documents (in spatial mode at least). They define all
of this for Tracker. They don't define the window size&position for
Terminal, nor the command history, nor the color settings and other
bashrc customizations (sometime a project needs some dir in the path or
other env vars), ...
This is one example of my activity as a developer. As an electronics
engineer a project would consist of :
* Schematics and PCB I'm working on
* Documentation for the various chips I'm using
* Firmware sourcecode I'm writing
* Likely a calculator with hexadecimal/binary mode, and resistor color code
* And layout of all these windows around my screen & my workspaces
I'm sure any activity can be defined in terms of such a
project/document. redacting a research paper would need the paper you
are working on + a set of references, drawing a picture could consist of
only a wonderbrush window, or could have showimage with a set of
references opened as well, composing music could need an instrument bank
and a score editor (and throw Cortex in the mix, while we're at it).
I took my own uses as an example (and they aren't the most classical
ones), but I think any workflow with any tools can be made in a similar way.
--
Adrien.
Other related posts: