seandenigris / seansoutbox Goto Github PK

Problem

When creating a chain of derived units, things can get sloppy. With milliseconds as the BaseUnit, we have:
Derived Factor
second 1000
minute 60 * 1000
hour 60 * 60 * 1000
day 24 * 60 * 60 * 1000

Solution

Allow proportional units to be constructed from either a BaseUnit, or another proportional unit with the same base unit as the new unit. Now we can think more intuitively:
Unit Factor
millisecond
second 1000
minute 60
hour 60
day 24

NB:

• the same objects are created in both scenarios; now some of the complication is simply hidden, offloaded to the constructor
• #baseUnit:conversionFactor:nameForOne:nameForMany:sign: is now a bit misleading, but since it's so central to the API I didn't want to change it
• it might be extendable to non-proportional units too, but I've never used them

From http://forum.world.st/Proxies-Subclassing-nil-tp4816443p4816618.html:
something that would be super super cool is to take the proxies I implemented for Marea and adapt them as custom Ghost proxies. Because the idea of Ghost was mostly the design, not the code itself. The code was very very little. So in Marea proxies you can see how I:

1. Created a few different proxies for different purposes. For example, I created special proxies for classes and metaclasses. And each of them implements custom messages to avoid unnecessary interception (for example, MARMetaclassProxy implements #isMeta answering true. Both, proxy for Class and Metaclass implement:

isKindOf: aClass
    ^ (aClass == Class) 
        ifTrue: [ true ]
        ifFalse: [ super isKindOf: aClass  ] "would be intercepted"

and so on....

So basically....you are able to implement custom proxies and implement custom messages so that you avoid intercepting them.

2. In Marea, I have multiple proxies that store the information differently. So for example, Marea proxies needed a graph id and a "position" (an integer). If both were small enough, I was doing a bitShift and storing them in a super compact proxy class that would have only one small integer.

So....what I want to say is that while ghost code is OK, the most interesting usage and development of those proxies is in Marea, in the category 'Marea-Proxies'.

6 common properties e.g. stickiness add ~8 methods each (e.g. toggleXyz, isXyz). The ugliest is xyzString, which returns... an association! for the halo menu item

The dual Morphic/Seaside rendering seems to be the exact use case for multiple visitors, but instead we have two totally separate class hierarchies, making 3 classes per description type.

In BBS image on MB Air, see #readMeasureFromAmount: and MABbsReplacementPriceDescription

Move to GitHub per http://forum.world.st/Issue-Tracker-tt4814743.html, but I emailed Lukas first to get his opinion.

Default to NullUpdatingStrategy, and how about #announcerClass: sets AnnouncementStrategy?

Aconcagua-Tests-SeanDeNigris.3.1.1