• 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
[OT] Versions, Documentation, Frameworks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[OT] Versions, Documentation, Frameworks


  • Subject: [OT] Versions, Documentation, Frameworks
  • From: Cyril Godefroy <email@hidden>
  • Date: Tue, 26 Feb 2002 09:12:27 +0100

Only slightly off-topic.

I'm still working on QTKit to bring a more-cocoa framework for Quicktime. The project I have now (not yet commited) has several targets, one being the framework itself and others being applications which demonstrate its use.

One of the issues I have now is how to name the version when this part is over, if it should be 0.2 or 0.11 or 0.15. What's been added are a QTKitMovie, QTKitTrack, and a new app like a QTPlayer. Next on the list is a QTSlider (yes I'm still not finished with that, it's really harder to get into it than I thought and I have to thank cocoa-dev teams at Apple because making such things is really not easy).

Second thing has to do with framework versions (blabla.framework/versions). What use is this and where do I found doc on this? To be used, the framework has to be installed, and I don't want to mess afterwards with version problems. On the same matter, is getting the version as simple as defining a version in the topmost header and asking the framework what version it uses?

Also on the same matter, what are the situations that influence the distribution of a framework by itself vs distribution with the app that uses it? I hope (inginument I would say) that the framework should be used by several apps and maybe putting it in /Library/frameworks or /System/Library will eventually make it user to use.

At last, a framework is pretty useless with proper documentation (spent hours reading OF code to figure what was happening). Is docbook (` la Darwin) the way to go? Are there apps to ease redaction of docbooks and others to transform it to easily accessible html documentation? Are there rules or examples I could take experience from?

Thanks for your comments.
Cyril
_______________________________________________
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: [OT] Versions, Documentation, Frameworks
      • From: Finlay Dobbie <email@hidden>
  • Prev by Date: Re: Can't find mysql.h
  • Next by Date: how to create a bug tracker ?
  • Previous by thread: Multithreaded drawing
  • Next by thread: Re: [OT] Versions, Documentation, Frameworks
  • Index(es):
    • Date
    • Thread