Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Classes</strong></p> <p>The fact that classes are keys in the <code>Smalltalk</code> global is an implementation detail. As long as there is a single global namespace for class names, it is likely that the implementation will stay the same.</p> <p><strong>Class Categories</strong></p> <p>The class category <em>is</em> very much like a tag. A class can only be in one category at a time. Originally the class category was used by the <code>Browser</code> for organizing the classes in the system. </p> <p>When <code>Monticello</code> was created, the class category was overloaded to also indicate membership in a <em>Monticello package</em> the<code>MCPackage</code> and <code>PackageInfo</code> classes were created to manage this mapping.</p> <p><code>PackageInfo</code> does all the heavy lifting: finding the classes and loose methods that belong to a package.</p> <p><code>MCPackage</code> is a Monticello-specific wrapper for <code>PackageInfo</code> that adds some protocol that wasn't necessarily appropriate for the more general <code>PackageInfo</code>.</p> <p><strong>Packages</strong></p> <p>Overloading the class category for package membership was a neat trick to ease the adoption of <code>Monticello</code> (existing development tools didn't need to be taught <code>Monticello</code>), however, it is still a <strong>trick</strong>. Not to mention the fact that the implementation of <code>PackageInfo</code> was not very efficient.</p> <p><code>RPackage</code> was created to address the performance problems of <code>PackageInfo</code> and to be used as part of the next generation of development tools.</p> <p>Both package implementations will continue to exist until <code>PackageInfo</code> can be phased out.</p> <p><strong>SystemNavigation</strong></p> <p>As Frank says, </p> <blockquote> <p>SystemNavigation is a class that, as its name suggests, permits easy querying of a number of different things: the classes in the image, senders-of, implementors-of, information about packages loaded in the image and so on.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POHow does the organisation of classes in categories and packages work in different versions of Pharo?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDale Henrichs
    1. USDale Henrichs
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow does the organisation of classes in categories and packages work in different versions of Pharo?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat is the relation between a "Monticello package" and a MCPackage? By the name i assumed they were one and the same.
      singulars
      1. PO
      1. USHelene Bilbo
    2. COA Monticello package is a file with extension `.mcz`. An MCPackage is an in-image instance representing that package.
      singulars
      1. PO
      1. USFrank Shearar
    3. COThank you, i updated my question accordingly. So how are MCPackage and PackageInfo or MCPackage and RPackage related? Or do they just live side by side?
      singulars
      1. PO
      1. USHelene Bilbo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload