老地方冰果室交流區

歡迎冰果室讀者在此交流
現在的時間是 12/06/2019 10:08 am

所有顯示的時間為 UTC + 8 小時




發表新文章 回覆主題  [ 1 篇文章 ] 
發表人 內容
文章發表於 : 03/22/2003 1:22 am 
離線
討論區管理員
頭像

註冊時間: 05/02/2001 1:01 am
文章: 1297
DarwinPorts.app 差不多功臣身退啦,現在 PortsManager.app 準備登場。

http://www.opendarwin.org/pipermail/cvs ... 00050.html

PortsManager.app is a graphical front-end for the darwinports system written
in COCOA. It is derived from the earlier DarwinPorts.app sources but the
architecture, GUI and source have changed significantly.

You need to have installed and configured the command-line ports system
before PortsManager.app will run.

PortsManager.app is not complete at this time but it should be at least as
functional as DarwinPorts.app was and provides a better architectural basis
for future development work. I am checking it in now so other people can
have a look at it and hopefully help finish it up.

So what's different/better about PortsManager compared to DarwinPorts.app?

The GUI for browsing the ports collection has been completely overhauled.
You can now browse by category. You can now have multiple independent
browser windows open. Many glitches with the outlineview presentation of
the port tree have been fixed. A detailed rich-text inspector view has
been added. The filter-widget now works more like Mail.apps and there are
a number of other minor UI tweaks.

The console log has been moved to it's own window. There is now a pop-up
which dynamically controls the level of detail presented.

Architecturally, the app has been split into a GUI front-end
(PortsManager.app) and a faceless helper process (dpagent).
Communication between the two happens using Distributed Objects. The
intent is that the helper process can run suid root if desired and avoid
the security pitfalls of having an appkit app running as root. This
split architecture also allows the GUI app to remain single-threaded
and still responsive and we only have to worry about multi-threading in
the helper agent.

The wrappers for the TCL interpreter have also been simplified to reduce
the need to keep converting back and forth between TCL and obj-c data types.

All operations on ports are currently multi-threaded but serialized
(e.g. you can start an install of a port, keep browsing the ports collection,
request another port to be installed but the second port won't start
installing until the first port finishes installing.) This was done to
simplify implementation and prevent conflicts from trying to install/
uninstall multiple ports simultaneously which both might share a dependency.

For more info there are comments in the .m source files explaining
various design decisions and pointing out places where the
current implementation is incomplete or needs improvement.

_________________
[digdog dig];


回頂端
 個人資料  
 
顯示文章 :  排序  
發表新文章 回覆主題  [ 1 篇文章 ] 

所有顯示的時間為 UTC + 8 小時


不能 在這個版面發表主題
不能 在這個版面回覆主題
不能 在這個版面編輯您的文章
不能 在這個版面刪除您的文章
不能 在這個版面上傳附加檔案

搜尋:
前往 :  
POWERED_BY
正體中文語系由 竹貓星球 維護製作