From: Ken Smith on
In article <871wkosial.fsf(a)nonospaz.fatphil.org>,
Phil Carmody <thefatphil_demunged(a)yahoo.co.uk> wrote:
>kensmith(a)green.rahul.net (Ken Smith) writes:
[....]
>> It may have been better if a new term was invented. All the existing
>> terms had meanings:
>>
>> "another screen" is bad because many Linux systems have more than one
>> screen
>>
>> "another virtual screen" is bad because many Linux systems have a non
>> graphics virtual screen along with the graphics one. You can configure
>> for only one "desk top" and still have "another virtual screen". Also
>> the "virtual screen" may be larger than the physical hardware screen.
>>
>> "another window" won't do because the term window is used for a part of
>> what is on the screen.
>
>'Workspace' is used by some window managers. I've also
>seen 'pane'.

"workspace" may be a good one.

"Pane" is also used as a subsection within a window so it could also be
confusing.

> I hear 'desktop' far more often though, and
>have done for well over a decade.

It was in use as a term before the creation of "Windows". Borland didn't
invent the term for their IDE.

--
--
kensmith(a)rahul.net forging knowledge

From: jasen on
On 2007-02-17, MassiveProng <MassiveProng(a)thebarattheendoftheuniverse.org> wrote:
> On Fri, 16 Feb 07 12:25:03 GMT, jmfbahciv(a)aol.com Gave us:
>
>>> Right now I also have LTSpice running on another
>>>desktop. I'm typing this while if figures.
>>
>>My point is that you should not have to have another computer _system_
>>to do any other task.
>
>
> He said on another desktop. If you had any modern brains, you would
> know that that IS the SAME computer, that has multiple "desktops". A
> feature of Linux GUIs.
>
> Th glaring error I see is that LTSpice doesn't take long enough to
> run that it needs to do it in the background on another desktop.

that depends on the simulation.

once you've got 30 or 100 or active components on the schematic it can slow down
considerably

When I was playing with simulated MOSFETS and ideal gates to construct a
D type flipflops from basic components I was starting to see slowdowns.

if you're just doing the 555 + LED thing then yeah there's nothing to wait
for.

Bye.
Jasen
From: jasen on
On 2007-02-16, jmfbahciv(a)aol.com <jmfbahciv(a)aol.com> wrote:
> In article <er45sh$pkf$2(a)jasen.is-a-geek.org>,
> jasen <jasen(a)free.net.nz> wrote:
>>On 2007-02-12, Ken Smith <kensmith(a)green.rahul.net> wrote:
>>>>> You had to load the CX register to do a LOOP.
>>>>
>>>>What's LOOP got to do with anything?
>>>
>>> You haven't been following the discussion. I used the case of a REP
>>> prefix used inside a loop as the example of why the 8086's instruction set
>>> was so poorly designed. The CX and the REP both use the CX so the CX must
>>> be loaded for the REP inside the loop. This means that the current CX
>>> contents must be saved, the CX loaded, the REP done and the CX restored.
>>> This is a lot of extra work.
>>
>>It's less work to just use something else to hold the loop count
>
> Well, that depends on what the hardware has to do for you
> to change that "something else".
>
>>and use DEC and JNZ in place of LOOP (faster too since 80486)
>>
>>One of the other registers or [bp+N] is often a good choice
>>(for apropriate values of N)
>
> Snort. Don't you just love that "appropriate values of N"?
> It implies you have to check it each and every time.

means you have to make room on the stack (where BP offsets are typically used)
for the counter.

--

Bye.
Jasen
From: jasen on
On 2007-02-17, jmfbahciv(a)aol.com <jmfbahciv(a)aol.com> wrote:
> In article <d1ict2h4c5s3m3e5unsu4aagl2fpj0s49n(a)4ax.com>,
> MassiveProng <MassiveProng(a)thebarattheendoftheuniverse.org> wrote:
>>On Fri, 16 Feb 07 12:25:03 GMT, jmfbahciv(a)aol.com Gave us:
>>
>>>> Right now I also have LTSpice running on another
>>>>desktop. I'm typing this while if figures.
>>>
>>>My point is that you should not have to have another computer _system_
>>>to do any other task.
>>
>>
>> He said on another desktop. If you had any modern brains, you would
>>know that that IS the SAME computer, that has multiple "desktops". A
>>feature of Linux GUIs.
>
> IF that is true, the renaming of this term is going to cause a lot
> of problems.

That's never stopped microsoft in the past. (I first encountered virtual
desktops in 1992 when an X-box was a box that did X.)

virtual desktops are a neat hack that works by minimising the "off-screen"
applications and hiding their icons.

--

Bye.
Jasen
From: jmfbahciv on
In article <er7c3b$ijh$5(a)blue.rahul.net>,
kensmith(a)green.rahul.net (Ken Smith) wrote:
>In article <er6rf6$8ss_002(a)s994.apx1.sbo.ma.dialup.rcn.com>,
> <jmfbahciv(a)aol.com> wrote:
>>In article <d1ict2h4c5s3m3e5unsu4aagl2fpj0s49n(a)4ax.com>,
>> MassiveProng <MassiveProng(a)thebarattheendoftheuniverse.org> wrote:
>>>On Fri, 16 Feb 07 12:25:03 GMT, jmfbahciv(a)aol.com Gave us:
>>>
>>>>> Right now I also have LTSpice running on another
>>>>>desktop. I'm typing this while if figures.
>>>>
>>>>My point is that you should not have to have another computer _system_
>>>>to do any other task.
>>>
>>>
>>> He said on another desktop. If you had any modern brains, you would
>>>know that that IS the SAME computer, that has multiple "desktops". A
>>>feature of Linux GUIs.
>>
>>IF that is true, the renaming of this term is going to cause a lot
>>of problems.
>
>It may have been better if a new term was invented. All the existing
>terms had meanings:
>
>"another screen" is bad because many Linux systems have more than one
>screen
>
>"another virtual screen" is bad because many Linux systems have a non
>graphics virtual screen along with the graphics one. You can configure
>for only one "desk top" and still have "another virtual screen". Also
>the "virtual screen" may be larger than the physical hardware screen.
>
>"another window" won't do because the term window is used for a part of
>what is on the screen.

If I understand what you are talking about, on our OS, we would have
used the term job.

/BAH