Examples of edu.mit.blocks.workspace.Page

• edu.mit.blocks.workspace.Page
  A Page serves as both an abstract container of blocks and also a graphical panel that renders its collection of blocks. Abstractly, a page has seven abstract fields: a color, a name, a font, a drawer, width, a height, and a set of blocks. How it renders these abstract fields depends on the state of the page, including: zoom level, and minimumPixelWidth. A Page exists as a WorkspaceWidget, a SearchableContainer, ISupportMemento, an RBParent, a Zoomable object, and a JPanel. As a WorkspaceWidget, it can add, remove, blocks and manage block manipulations within itself. As a searchableContainer, it can notify users that certain blocks have been queried. As an ISupportMomento, it can undo the current values of abstract fields. As an RBParent, it can highlight blocks. Since a Page is both a Zoomable object and JPanel, Pages separate its abstract model and view by allowing clients to mutate its abstract fields directly. But clients must remember to reform the pages in order to synchronize the data between the model and view. A page's abstract color is rendered the same no matter what state the page is in. A page's abstract name is rendered thrice centered at every fourth of the page. The name is rendered with a size depending on the zoom level of that page (it tries to maintain a constant aspect ratio). The drawer name is not rendered. The width and height of the page is rendered differently depending on the zoom level and minimumPixelWidth. Using the zoom level, it tries to maintain a constant aspect ratio but the absolute sizes varies with a bigger/smaller zoom level. the minimumPixelWidth limits the width from going below a certain size, no matter what the system tries to set the abstract width to be. Finally the set of blocks are rendered directly onto the page with the same transformation as the ones imposed on the width and height of the page. As an implementation detail, a page tries to maintain a separation between its abstract states and its view. Clients of Pages should use reform*() methods to validate information between the abstract states and view. Clients of Pages are warned against accessing Page.getJComponent(), as the method provides clients a way to unintentionally mutate an implementation specific detail of Pages. A Page implements ExplorerListener i.e. it listens for possible changes in an explorer that affects the display of the page. When an explorer event happens the page changes its display accordingly

Related Classes of edu.mit.blocks.workspace.Page