I am glad to know that a lot of people still like multiple windowed UI and
remember Xcode 3 with warm like me. Of course, it is more suitable for
using multiple screens: one window for each screen, or in the case of CAD
-- one screen for model designing window and one for everything else.
However,
> On 11 Jan 2016, at 23:10, Charles Srstka wrote:
>
> My favorite thing in Xcode is the way that Interface Builder stuffs the
> entire object library into that tiny little space in the lower-right corner
> of the screen. Way back in Xcode 3 (or whenever it was that IB was a separate
> app), t
> On 11 Jan 2016, at 21:06, Lee Ann Rucker wrote:
>
>
>> On Jan 11, 2016, at 7:35 AM, Jim Lee wrote:
>>
>> We have an application, TopXNotes that allows multiple “documents” (notes)
>> to be opened in adjacent views (panes). The notes can be edited
>> individually. One can cut/paste/copy fr
> On 11 Jan 2016, at 16:15, Alex Zavatone wrote:
>
> Way back in the mid '90s, there was some double click tool that simply felt
> like the holy grail to me.
>
> You double clicked or option clicked on the title of a window and it would
> turn that window into the "floating windoid" title bar
> On 12 Jan 2016, at 03:56, Greg Weston wrote:
>
>> (I also don’t want to restart Xcode wars, but I do actually believe that the
>> unified window style that arrived in Xcode 4 was an actual decision about
>> which worked best, made by clever people who actually thought about it. It
>> wasn’t
> (I also don’t want to restart Xcode wars, but I do actually believe that the
> unified window style that arrived in Xcode 4 was an actual decision about
> which worked best, made by clever people who actually thought about it. It
> wasn’t — I believe — merely clueless. I also want to point out
My favorite thing in Xcode is the way that Interface Builder stuffs the entire
object library into that tiny little space in the lower-right corner of the
screen. Way back in Xcode 3 (or whenever it was that IB was a separate app),
the floating palette that they had for the object library let yo
> My reasoning is that if you make it inflexible, you risk getting (say) 50%
> lovers and 50% haters. If you make it flexible, you risk getting 40% lovers
> and 40% haters, and 20% people who are annoyed because it’s too flexible or
> too complicated. That’s a net loss in satisfaction.
I think
> If you make it flexible, you risk getting 40% lovers and 40% haters, and 20%
> people who are annoyed because it’s too flexible or too complicated. That’s a
> net loss in satisfaction.
How about: 40% lovers, 40% haters, and 20% people who *are initially frustrated
by the complexity, and then
On Jan 11, 2016, at 13:06 , Lee Ann Rucker wrote:
>
> no system is going to make everyone happy, so go for the most flexible one if
> you can
I’d like to advocate the opposite point of view: no system is going to make
everyone happy, so go for the the one that works best.
(Yes, I understand w
> On Jan 11, 2016, at 7:35 AM, Jim Lee wrote:
>
> We have an application, TopXNotes that allows multiple “documents” (notes) to
> be opened in adjacent views (panes). The notes can be edited individually.
> One can cut/paste/copy from any text document to/from a seperate text app, or
> from p
FWIW, I find it odd that so many apps these days seem to be following Xcode's
"lead", if you want to call it that. I still miss Xcode 3.2.6 because I could
configure it for the way *I* was most productive. Now you gotta use that
ginormous "plate" window. It shows you what it wants to show you wh
I've seen an advantage to having "attached palettes" like Xcode's Utilities
pane. When set up like this, I can see unique attributes per window and compare
two separate documents. When there's only one shared all over the place, it
might be harder at times to get context at a glance. An example
I'm pleased to see so many in favor of multiple windows. It seems the arguments
in favor of a single monolithic window hinge smaller screens. But I find that
monolithic windows require larger screens (and can't share screens). The thing
about separate windows is they can overlap and still be use
Way back in the mid '90s, there was some double click tool that simply felt
like the holy grail to me.
You double clicked or option clicked on the title of a window and it would turn
that window into the "floating windoid" title bar only. We took this model and
made it so that when you collaps
On Jan 11, 2016, at 2:17 AM, Britt Durbrow wrote:
> My preference would be multiple windows (one primary document window and
> several utility panel windows) that can be snapped into place against each
> other. This gives the freedom to use multiple monitors while also having the
> screen-real
We have an application, TopXNotes that allows multiple “documents” (notes) to
be opened in adjacent views (panes). The notes can be edited individually. One
can cut/paste/copy from any text document to/from a seperate text app, or from
pane to pane. Just one example of something different that I
> On 9 Jan 2016, at 22:19, Rick Mann wrote:
>
> In complex apps (e.g. CAD apps, IDEs) a given document has many auxiliary
> windows. The trend in UI at Apple has been to consolidate these into panes in
> a single window. I've always preferred separate windows (e.g. separate
> toolbar window).
Interesting that so many others like the multiwindow approach. I’ve always
thought that a horrible design, because you constantly have to fool with them
to get them out of the way as you work on a document. I like the approach taken
by Photoshop, where you can dock them them together in the layo
My preference would be multiple windows (one primary document window and
several utility panel windows) that can be snapped into place against each
other. This gives the freedom to use multiple monitors while also having the
screen-real-estate efficiency that a single-window approach would. (FWI
> On Jan 10, 2016, at 8:41 AM, Alex Zavatone wrote:
>
> On Jan 9, 2016, at 5:19 PM, Rick Mann wrote:
>
>> In complex apps (e.g. CAD apps, IDEs) a given document has many auxiliary
>> windows. The trend in UI at Apple has been to consolidate these into panes
>> in a single window. I've always
On Jan 9, 2016, at 5:19 PM, Rick Mann wrote:
> In complex apps (e.g. CAD apps, IDEs) a given document has many auxiliary
> windows. The trend in UI at Apple has been to consolidate these into panes in
> a single window. I've always preferred separate windows (e.g. separate
> toolbar window).
> On 2016 Jan 09, at 14:19, Rick Mann wrote:
>
> Thoughts?
You could argue this both ways until the cows come home, but here is one
thought:
I think the recent move toward one big window, like the move toward full-screen
apps, has been advanced by the increased prevalance of laptops, with th
In complex apps (e.g. CAD apps, IDEs) a given document has many auxiliary
windows. The trend in UI at Apple has been to consolidate these into panes in a
single window. I've always preferred separate windows (e.g. separate toolbar
window).
One more concrete example is in a CAD program: the obje
24 matches
Mail list logo
