[Pharo-project] Issue 3800 in pharo: StaticForm can be removed
Status: Fixed Owner: stephane...@gmail.com Labels: Milestone-1.3 New issue 3800 by stephane...@gmail.com: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 An optimization for Nebraska - a StaticForm does not change once created so it may be cached on the remote end. one method. isStatic ^true and not invoked
Comment #1 on issue 3800 by marianopeck: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 and what are you gonna do with the users of StaticForm ? replace it by Form?
Updates: Status: FixProposed Comment #2 on issue 3800 by marcus.d...@gmail.com: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 (No comment was entered for this change.)
Updates: Status: Started Comment #3 on issue 3800 by marcus.d...@gmail.com: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 (No comment was entered for this change.)
Updates: Status: FixProposed Comment #4 on issue 3800 by marcus.d...@gmail.com: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 fix attached. please add Postscript: HandMorph initialize. SMxHandMorph initialize Attachments: StaticForm.2.cs 1.1 KB
Updates: Status: Closed Comment #5 on issue 3800 by marcus.d...@gmail.com: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 in 14143
participants (1)
-
pharo＠googlecode.com