• 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: Cocoa view design considerations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa view design considerations


  • Subject: Re: Cocoa view design considerations
  • From: "Mark Munz (DevList)" <email@hidden>
  • Date: Thu, 19 May 2005 08:42:24 -0500

Spreadsheets handle drawing differently that a true table. They support the concept of spilling over to the cell next to it (as long as it doesn't have a value). This application is usually only useful in spreadsheets, databases don't normally let you spill data into other columns.

In the paste, I've written a spreadsheet which essentially had row objects; each row had to layout how far across each cell's contents could flow (based on the adjoining cells). Spreadsheets also do weird things like span across cells (that can be to the left as well as to the right of the cell with data), centered text could also flow into the previous cell. In the end, you won't have good spreadsheet functionality (with today's spreadsheet) if you only deal with things inside a single cell's borders.

That's essentially what you would need to do. Create a one column table, then create a subclass of NSCell that lays out the various columns as you need.

Mark Munz

On May 19, 2005, at 6:36 AM, J.M.Brough wrote:


On 19 May 2005, at 05:30, Mark Munz (DevList) wrote:


Is there a reason you need the data in multiple columns.

It would seem you could accomplish what you want by having a single column and then displaying each row appropriately by either fixed horizontal positioning or fixed font.

Columns are really defined as being homogeneous in nature and it seems like your output (because of the labels) breaks that principle. You need to find that sameness aspect of the data you're dealing with, otherwise it may not be the right tool for you.

Mark Munz



Mark,

You're absolutely write...I've been thinking that for a few days now. I guess I'll have to write my own display classes. A while back I wrote a x86 assembler using VB in Excel to learn that applications abilities. It was possible using the spreadsheet. I've seen some pretty amazing apps. using the cocoa framework and was hoping it was flexible enough. Guess not.

Thanks all for the info.


Jason.

_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Cocoa view design considerations
      • From: "J.M.Brough" <email@hidden>
References: 
 >Re: Cocoa view design considerations (From: "J.M.Brough" <email@hidden>)
 >Re: Cocoa view design considerations (From: "J.M.Brough" <email@hidden>)

  • Prev by Date: Re: Lost focus ring in entire application
  • Next by Date: Re: KVO returning nil for old values, and mmalc's Graphics Bindings example
  • Previous by thread: Re: Cocoa view design considerations
  • Next by thread: Re: Cocoa view design considerations
  • Index(es):
    • Date
    • Thread