Skip to content
lauritzthamsen edited this page Feb 24, 2012 · 3 revisions

Clean up and module organization

Smaller Core: Remove unnecessary stuff

What’s really core? What’s still from LK1 and can be removed from our LK2-CORE repo? The following modules/files are at least suspicious and might want to be deleted...

  • lively.OldModel

  • lively.NoMoreModels

  • lively.Data

  • lively.NewMorphicCompat

  • lively.Migration

  • lively.ObjectMigration

  • lively.morphic.CompatLayer

  • Global.DisplayThemes in lively.morphic.Styles

  • cop/MiniBase.js and cop/miniprototype.js:

  • cop/Experiments.js

  • lively.morphic.EventExperiments

  • lively.morphic.WidgetsAddOns

  • ometa/prototype-fix.js

  • ometa/Workspace.js


Organization: Split modules

  • lively.morphic.AdditionalMorphs > 1750 LOC, stupid name
  • lively.morphic.Core, name could indicate that it defines Morph, World, Box, List, .. “CoreMorphs”? And Script, FunctionScript should be in another module
  • lively.morphic.Events > 1750 LOC, separate FileUploader, maybe we can have this module define EventHandler, ScrollableTrait, EventSimulator, while Morph, Text, List, and other widgets implement their event handling in their modules (less extensions, more “complete” class defs)
  • lively.persistence.ObjectExtensions vs. lively.morphic.Serialization
  • Base.js: create a module for modules and namespaces and another one for Lively's class-system

LK 1 vs. LK2:

Config.isNewMorphic - clean up: remove conditionals and use true-branch, remove lively/morphic.js