Re: Documents and Projects
Re: Documents and Projects
- Subject: Re: Documents and Projects
- From: April Gendill <email@hidden>
- Date: Tue, 30 Mar 2004 19:59:56 -0700
What kinds of messages need to be sent? I mean are you able to alter
the project from a member's window? Or do you want to make sure that an
alteration in the project would be reflected in a member even if the
member was opened before the project?
On Mar 30, 2004, at 5:08 PM, Seth Willits wrote:
On Mar 30, 2004, at 2:59 PM, Glenn Andreas wrote:
My LGPLed IDEKit framework has the start of such a beast (and
provides a UI for project management - heirarchical groups, reording,
etc...)
You can download it from http://projects.gandreas.com/idekit
Taking a look at PyOXIDE, I don't see what the project file actually
does.
If you use GoLive, that type of project management is what I'm looking
for. Not nearly as complex, but the project window listing files in
the project, documents can be opened separately or from within the
project, and if a document is opened before a project, after the
project is opened, both the project and the document know that the
document belongs to the opened project.
Possible structures I see are:
1) The NSDocument subclassing being a project with a window controller
allowing different files to be opened from the project. If no project
is open the "project" is empty and no window is show, just an
individual file. This does not seem like a good way to do it, but it
sounds like it's possible.
2) The more likely method, would be to have a separate document type
for the project, and have some model of communication between
documents. Specifically, there'd need to be a way for one document to
ask every other document "hey, are you a project?" and then be able to
store a reference to it, so that the project/document relationship can
be established. This is the best way I see, but I wonder if this means
I simply need a way to communicate between documents (do I use the
shared document controller to talk to them?) or do if I should
subclass the document controller and tell documents and projects to
communicate.
sharedDocumentController. You can use it as an arbiter between the
mainmenu controller, other documents or anything else that you'd like.
The door can swing both ways if you need to communicate document to
controller and controller to document.
I could be missing what your goal is though. I mean working in a
project like that, it is easy to find out the path of each open
document and if the open document is a child of the project you can
send messages by accessing it in the array of open documents or through
the shared controller.
April.
I hope that makes sense.
Seth Willits
-----------------------------------------------------------------------
----
President and Head Developer of Freak Software - http://www.freaksw.com
REALbasic Guru at ResExcellence -
http://www.resexcellence.com/realbasic
Webmaster for REALbasic Game Central - http://www.freaksw.com/rbgames
"Black holes are where God divided by zero."
-- Steven Wright
-----------------------------------------------------------------------
----
_______________________________________________
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.
_______________________________________________
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.