• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: tables cells and views
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tables cells and views


  • Subject: Re: tables cells and views
  • From: Andy Lee <email@hidden>
  • Date: Sun, 28 Apr 2002 13:50:06 -0400

At 7:14 PM +0200 4/28/02, nicolas berloquin wrote:
If you just want a list view that uses subviews instead of cells, you can create it yourself. (Hint: -addSubview and -removeFromSuperview.) You'll have to write your own logic to manage the layout of the subviews, but that should be a straightforward exercise. You might see a cost in performance, but maybe not.

you're right on the point, why not have a class that handles everything like a tableview/columnview does, BUT has nsviews inside it ?

The same could be asked of many things Apple doesn't provide that could be useful -- calendar controls come to mind, and rotatable tab views. I'm sure the answers vary -- they only have finite resources, they don't believe feature X is a good idea, there are perfectly good third-party solutions, they simply never thought of it, it's coming in the next release, or whatever.

From our point of view, I think the more important question is whether Cocoa allows you to add feature X yourself if you really, "legitimately" need it (setting aside the fact that "legitimacy" is often debatable).

here's an example you might have already seen: a list of downloading files in a web application. You may want more than just text in your table, you'd have the filename,
a progress indicator, and maybe a button to stop/pause the download.... and this is not a far-fetched example...

I agree, not far-fetched at all.

OmniWeb has progress indicators in their download window. You might want to check out their free frameworks, which I haven't used but from all indications are incredibly rich. One difference from what you describe is that OmniWeb does not put a Cancel button in each cell. It puts a single button for that purpose at the top of the window. Likewise, Internet Explorer provides a contextual menu rather than a Cancel button for each item being downloaded. I'm not saying these are better UI designs -- maybe these apps were designed this way *because* of the limitations of NSCell! -- but it's an approach to consider.

(Come to think of it, LimeWire also uses the single-Cancel-button approach, and it's written in Java.)

--Andy
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: tables cells and views
      • From: Ondra Cada <email@hidden>
References: 
 >Re: tables cells and views (From: nicolas berloquin <email@hidden>)

  • Prev by Date: Re: tables cells and views
  • Next by Date: Strings crossing the Java bridge
  • Previous by thread: Re: tables cells and views
  • Next by thread: Re: tables cells and views
  • Index(es):
    • Date
    • Thread