curious how come you guys did not use Spec ? On Thu, Dec 11, 2014 at 12:12 AM, Aliaksei Syrel <alex.sy...@gmail.com> wrote:
> Hi, > > Why the class you use is not available in Moose 5.0 ? > > There were some failing tests, so maybe new classes were not in the build > (The latest is Glamour-Morphic-Brick.88) > > Brick more or less is nothing special. The main idea was to kill morphic > layouting mechanism and reimplement it from scratch. Also drawing logic was > changed, such that there is no way to draw outside of the parent Brick and > to support z-index. But one of the most important feature for us was to > have a normal support of paddings and margins (like in css). And all bounds > are relative to the parent. > > Cheers, > Alex > > On Wed, Dec 10, 2014 at 10:31 PM, kilon alios <kilon.al...@gmail.com> > wrote: > >> I am very interested into Brick, because I am very interesting into >> anything GUI and graphic wise and I want to push pharo forward in that >> field with my own efforts as best I can. >> >> The scrolling of your examples is actually very smooth. >> >> Why the class you use is not available in Moose 5.0 ? Because a moose 5.0 >> image I have downloaded recently with pharolauncher that it contains >> GTSpotter yet it does not have the class you use here. >> >> On Wed, Dec 10, 2014 at 9:31 PM, Aliaksei Syrel <alex.sy...@gmail.com> >> wrote: >> >>> Hi, >>> >>> in case someone is still interested, a Glamour-Morphic-Brick (extension >>> of morph, that was used to build a Spotter) >>> supports a very large lists. You can try in the latest version: >>> >>> GLMScrollListBrick exampleCollection - to open a list of all classes in >>> the image (each element in the list is a morph). >>> GLMScrollListBrick example - list of 2000 elements >>> GLMScrollListBrick exampleInfinity - list of Float infinity number of >>> elements. >>> >>> if your pharo image is old: >>> >>>> Gofer new >>>> smalltalkhubUser: 'Moose' project: 'Glamour'; >>>> package: 'Glamour-Morphic-Brick'; load. >>> >>> >>> Maybe we will use it instead of default lists in Inspector. >>> >>> Cheers, >>> Alex >>> >>> >>> On Thu, Dec 4, 2014 at 4:04 PM, Ben Coman <b...@openinworld.com> wrote: >>> >>>> Sven Van Caekenberghe wrote: >>>> >>>>> On 04 Dec 2014, at 11:45, p...@highoctane.be wrote: >>>>>> >>>>>> But further than that I want to edit values in inspectors. >>>>>> >>>>> >>>>> Yes ! >>>>> >>>>> And auto refresh ! >>>>> >>>>> Both of these could be depending on presentation, so that heavy >>>>> presentations can opt out. >>>>> >>>>> >>>>> >>>>> >>>>> >>>> It would be good if there was some visual indication of which >>>> presentations auto-refreshed - like a drop pin looking like its "stuck-in" >>>> when not-auto-refreshing. A user might even be able to change the state of >>>> the pin, with the just the default dependent on type of presentation. >>>> cheers -ben >>>> >>>> >>> >> >
