This was indeed my goal :) Having kind of solid documentation for 3.0 release.
Spec was in 2.0 because we already had some tools already re implemented in Spec but also that people can know it exists before it becomes “mainstream" Ben On 10 Nov 2013, at 04:45, b...@openinworld.com wrote: > Benjamin wrote: >> >> Shame on you dude :P >> >> It points out the huge lack of Spec documentation, so in fact, shame on me :P >> >> Ben >> > > I'm not sure how much Pharo 2.0 focused on the move to Spec for UI (I've > ended up jumping from 1.4 straight to 3.0alpha) but regarding the > professional presentation/reception of Pharo I feel some solid Spec > documentation will be critical to coincide with the 3.0 release (or very > shortly thereafter). Even though there has been a great amount of other work > under-the-hood, Spec is the front-line system that end-user-developers will > be working with. I'm sure that already was your aim. This is just a > supporting note for that action. > > cheers -ben > >> On 09 Nov 2013, at 20:34, Sean P. DeNigris <s...@clipperadams.com> wrote: >> >> >>> Benjamin Van Ryseghem-2 wrote >>> >>>> You just need to override the method #initialExtent >>>> >>> Cool! I didn't know that one. I've been writing ugly #open methods which >>> call #extent:... >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: >>> http://forum.world.st/Adjusting-the-size-of-a-window-using-Spec-tp4719478p4720806.html >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> >> >> >> >
