Le 19 mai 2015 à 16:03, Sergio Fedi a écrit :
<DolphinPackageBrowser.png> â Top left pane: File system tree where packages are located Down left pane: Packages in the file system location selected above
Tabs: Comment - Whatever text you put Classes - Classes defined by the package Loose methods - Methods in classes added by the package that are not in classes defined by the package Resources - Objects embedded in the package (that is, serialized instances) Mainly used for window views. Globals - Entries in the system dictionary that are defined by the package Scripts - This tab has four subtabs: preinstall, postinstall, preuninstall, postuninstall These scripts where ran in the appropriate stage of installing/uninstalling the package Prerequisites - Depending on the classes, globals, etc, referenced by the classes and methods,etc from the package, the browser determined it's dependencies and this information would be then saved in the package itself. If the package had circular dependencies, then it wouldn't allow you to save it. The prerequisites listed you the packages which yoyr package depended on and why. That is, a list of which method referenced something outside the package. Dependents - As prerequisites, but shows the packages that depend on your package, and why
Example of Dependents:
<DolphinDependentsFeature.png> â
The second dependency is created because the method references a class:
agent "Answers the IAgentCtl for the receiver's avatars"
agent isNull ifTrue: [ agent := IAgentCtlEx new. agent connected: true ]. ^agent
thanks for the information.