[openbeos] Refactoring Tracker and Add Ons

I was looking to develop the a tracker add on to provide a dialog for adding
BeUnited and Dublin Core attributes to files.

So having the source code for OpenBeOS I looked at the code for the filetype
add-on. It has most of what I wanted, but there is still bugs in my start code.

I realised that my code would be almost identical except for the view and the
handler. I thought I could abstract out the common code and make add-ons easier
to develop. Even Zip-o-Matic is almost the same.

My first issue is that I think tracker add-on libraries and basic tracker
add-ons would be better served as part of the OpenTracker project. The problem
with that is then OpenBeOS may not build without those libraries.

Then there was the discussion on Glass Elevator about the internals of tarcker
and the new 'Add-On' architecture. (I suspect Axel is a code name for a secret
society of beos programmers.)

I thought I might have a look at the code of tracker and see if it was possible
to build the GetInfo dialog as an add-on. But one of it's internal pieces (I
think AttributeStream) depends on PoseView which I know means it depends on the
rest of tracker.

(I will collect answers).

What is a DialogPane? What is a ContainerView?
How do you (can you) overcome a dependancy on PoseView?


Try the new improved Yahoo! Australia & NZ Search at http://www.yahoo.com.au

Other related posts: