[Seaside-dev] ShoreComponent portability problems

[Roger Whitney]

The ShoreCompenents in the latest Seaside dev build for VW 7.6 (dev  
build) has several problems, some of which seem to be portability  
issues. However it is not clear to me if they are just VW issues or  
problems in general.

Issue 1. SShoreComponents.ShoreDemo1DatePicker>>initialize calls Date>>+
	IN VW Seaside Date>>- is added in the package Squeak-Chronology, but  
not Date>>+. Should Date>>+ be part of a squeak compatibility layer?

Issue 2. month index and month name

	ShoreComponents.ShoreDemo1DatePicker>>nextMonthOf:
	ShoreComponents.ShoreDemo1DatePicker>>prevYearOf:
	ShoreComponents.ShoreDemo1DatePicker>>prevMonthOf:
	ShoreComponents.ShoreDemo1DatePicker>>nextYearOf:

All use an index when they should use month name. The code does not  
look like it would run in Squeak, so this could be a Shore Component  
problem. At any rate it should be changed to use whatever is the  
outcome of the month name-index debate.

Issue 3. Array>>reversed
	ShoreComponents.ShoreLiveTable>>renderGroupHeader:on:lastHeader:  
calls reversed on an Array. For compatibility VW only defines this  
method for OrderedCollection, but Squeak also defines it in  
SequenceableCollection. Should the VW compatibility layer contain  
this method in SequenceableCollection?

Issue 4 String>>asInteger
	In VW one uses asNumber not asInteger.  
ShoreComponents.ShoreLiveTable sends asInteger to a string. So  
perhaps this should be changed in ShoreComponents. I have not yet  
looked into how to submit changes to Shore Components.

----
Roger Whitney              Department of Computer Science
whitney at cs.sdsu.edu        San Diego State University
http://www.eli.sdsu.edu/   San Diego, CA 92182-7720