Hi everybody,

In the course of developing the application I'm working on, I got
frustrated with having to create dummy data sources for my static
source list outline views.  They result in quite a bit of code that
can be a mess to alter when you want to later add an item to the
source list, they make localization difficult, and illogically put
static interface-related data in code.

Combine this with the other annoying source list nits (overriding
NSOutlineView just to implement -frameOfOutlineCellAtRow:, for
example, when it should be a delegate method) and I decided to fight
back with a framework and Interface Builder plugin I'm calling
KSOutlineView.

Right now it contains two classes: KSStaticTreeController, which when
used in IB presents an interface for editing a static tree of data,
and KSOutlineView, which doesn't do all that much differently from
NSOutlineView.  Right now the best immediate benefit is that binding a
plain-vanilla NSOutlineView to a KSStaticTreeController results in a
fully-usable outline view in the simulator.  Ideally, I'd like
KSOutlineView to present an interface for editing items directly in
design mode and a mechanism for pulling data from multiple
NSTreeControllers, so that you may for example have a static overall
source list structure with certain subtrees fed by bindings.

There are also a few issues, not the least of which is that Interface
Builder doesn't recognize changes to a KSStaticTreeController's
content, and thus does not mark the document as dirty.  This code is
very untested, since I wrote it today.

If you'd like to take a gander at it, and maybe help me improve it,
check it out at http://ksoutlineview.googlecode.com .

Thanks!
--Kyle Sluder
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to