Daily Commit Log

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Daily Commit Log

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours:


Name: SystemReporter-mt.26
Ancestors: SystemReporter-eem.25

Fix spelling.



Name: 51Deprecated-mt.28
Ancestors: 51Deprecated-mt.27

Deprecate #includesSubString: with capital S.



Name: Collections-mt.692
Ancestors: Collections-mt.691

Deprecate #includesSubString: with capital S.



Name: Morphic-mt.1144
Ancestors: Morphic-kb.1143

Fixes an older issue where it was not possible to set the keyboard focus of a text morph w/o discarding its selection. Most prominent in the System Browser where one could not simply overwrite the method template but had to re-select everything.

This only affects users who disable "Focus follows mouse" and "mouseOverForKeyboardFocus".

Here is the trick: Clicking inside the text morph's bounds still discards the selection. Embedded in a pluggable text morph, however, it is possible to click outside the text morph but inside the pluggable text morph. In this case, just do not handle the event except for context menu and keyboard focus.

This does still not work for pluggable text morphs whose text morphs fill out the whole (scrollable) viewpoint.



Name: System-mt.829
Ancestors: System-mt.828

Use only one implementation to remove all but one project from the system.



Name: EToys-mt.136
Ancestors: EToys-mt.135

When eToys clean-up aggressively, let it not mess around with the project hierarchy in general. This is the job of ReleaseBuilder. Only dump presenters in all morphic projects. As user objects are now in the more generic category "UserObjects", also let the ReleaseBuilder discard those uni-classes in a clean fashion.

We do not know about the order of clean-up calls, so ReleaseBuilder >> #discardUserObjects is still useful.



Name: ReleaseBuilder-mt.132
Ancestors: ReleaseBuilder-mt.131

More refactoring. Separate image preparation into a) preparing source code and b) preparing environment. Seperating environment preparation into 1) clear caches, 2) configure tools, 3) set preferences, and 4) configure desktop/content. The steps 2) and 3) are somewhat similar. 3) means the (pragma) preferences mechanism only whereas 2) addresses configuration in other ways.



Name: Morphic-mt.1145
Ancestors: Morphic-mt.1144

Pluggable text morphs can keep their selection/offset w/o using deferred UI messages. This is more robust when add/remove instance variables in classes related to text editing and tools.

No need for locking the offset in scroll panes anymore. Was a left-over from 4.5.



Name: Morphic-mt.1146
Ancestors: Morphic-mt.1145

Forgot to restore the "== true" pattern here. Be more robust against strange models...



Name: Morphic-mt.1147
Ancestors: Morphic-mt.1146

Remove the lockOffset variable. Let's hope that all open tools survive this...



Name: ReleaseBuilder-mt.133
Ancestors: ReleaseBuilder-mt.132

Condense changes.

Note that we may want to have more control about the contents in the changes file for the release process. Right now, it is based on the local changes only. We could, for example, fetch all updates since the last release and rewrite the changes file. This would yield a consistent output and the versions browser would be more fun to use in a new release.



Name: ReleaseBuilder-mt.134
Ancestors: ReleaseBuilder-mt.133

We can only condense the changes once we have written the new changes/image files. Otherwise, we will break our master image because its changes file would be inconsistent to the image.

I wonder why #condenseChanges does not automatically snapshot the image. It is dangerous.



Name: Collections-mt.693
Ancestors: Collections-mt.692

Extend the TranscriptStream's model protocol to support "Window Active On First Click" preference. Usually, only subclasses of Model behave accordingly. Other "models" have to mimick the protocol.



Name: Compiler-eem.322
Ancestors: Compiler-nice.321

Add bytecode scanning machinery to identify "synthetic" stores, i.e. the stores of indirect temp vectors at the start of methods containing closures.

Add a "high-quality" pcPreviousTo:in:for: that answers nil for the first pcs of blocks, and answers the block creation bytecode's pc for the pc following an embedded block, and use it to disambiguate bytecode sequences that look like pushNewArray of an empty array..

Add isTempStoreAt:in: & pcFollowingBlockAt:in: to support the above.



Name: Tests-eem.340
Ancestors: Tests-ul.339

Add tests for the new bytecode scanning machinery (see Compiler-eem.322).  Nuke some misplaced class vars.



Name: Kernel-eem.1022
Ancestors: Kernel-bf.1021

Revise the fix in Kernel-bf.1019 (Debugger: step over temp vector initializer when entering method).  Use the new bytecode scanning mahcinery from Compiler-eem.322 to implement willReallyStore and use it in stepToSendOrReturn to filter-out stores of indirect temp vectors.



Name: Kernel-eem.1023
Ancestors: Kernel-eem.1022

CompiledMethod>>pcPreviousTo: is used in places other thna the debugger, so it has to be in kernel.  Some time it may be replaceable with the new BytecodeEncoder class>>#pcPreviousTo:in:for:, but for now put it in the right package.



Name: Tools-eem.702
Ancestors: Tools-bf.701

See Kernel-eem.1023.  CompiledMethod>>pcPreviousTo: is used in places other thna the debugger, so it has to be in kernel.