- Pharo-users - lists.pharo.org

Re: [Pharo-users] X11 options on Ubuntu VM / Athens rendering problems

by Igor Stasenko

On 29 September 2017 at 11:23, Hilaire <hilaire(a)drgeo.eu> wrote: > Beside the official ones, are you using alternate repositories? It can > become a hell. > > In your posting, a Thoera dependency appeared... > > it looks like there's an error in dependency spec. because i have 64-bit cairo installed, and uninstalling theora drags half of the desktop stuff after itself.. oh.. looks like i found why: sudo dpkg -i libcairo2_1.14.8-1_i386.deb Selecting previously unselected package libcairo2:i386. (Reading database ... 541684 files and directories currently installed.) Preparing to unpack libcairo2_1.14.8-1_i386.deb ... De-configuring libcairo2:amd64 (1.15.2-0intel1) ... Unpacking libcairo2:i386 (1.14.8-1) ... dpkg: error processing package libcairo2:i386 (--install): package libcairo2:i386 1.14.8-1 cannot be configured because libcairo2:amd64 is at a different version (1.15.2-0intel1) dpkg: error processing package libcairo2:amd64 (--install): package libcairo2:amd64 1.15.2-0intel1 cannot be configured because libcairo2:i386 is at a different version (1.14.8-1) Processing triggers for libc-bin (2.24-9ubuntu2.2) ... Errors were encountered while processing: now where the heck i can find binary of appropriate version libcairo2:i386 1.15.2 (googling doesn't helps) > Hilaire > > Le 28/09/2017 Ã 19:51, Igor Stasenko a Ã©crit : > >> >> I got libsdl and libcairo 32bits installed fine on 64bits Ubuntu >> 17.04. >> >> weird.. >> > > -- > Dr. Geo > http://drgeo.eu > > -- Best regards, Igor Stasenko.

Sept. 29, 2017

Re: [Pharo-users] [Demo] Creating Bloc Widgets with Pharo

by Stephan Eggermont

On 29/09/17 00:51, Igor Stasenko wrote: > Stephan , you said you cannot replace the last one in the video. > I think you can have an easy solution: you should treat a pane that you > are currently over - the one you are going to replace, so if you drag > over something which is not placeholder, > then it should automatically be shifted and replaced by placeholder. Thanks. This works. I forgot that there is always one more dropping place possible than there are elements dragEvent: anEvent | dragOver | anEvent consumed: true. dragOver := inspector children first. inspector childrenDo: [ :c | c boundsInSpace center y < (anEvent position y + dragOffset y) ifTrue: [ dragOver := c ] ]. (dragOver ~= placeHolder ) ifTrue: [ (inspector childIndexOf: placeHolder) > 0 ifTrue: [inspector removeChild: placeHolder]. inspector children last boundsInSpace bottom < (anEvent position y + dragOffset y) ifTrue: [ inspector addChild: placeHolder at: (1+(inspector childIndexOf: dragOver))] ifFalse: [ inspector addChild: placeHolder at: (inspector childIndexOf: dragOver)]]. anEvent currentTarget position: (anEvent position - dragOffset).

Sept. 29, 2017

Re: [Pharo-users] [Demo] Creating Bloc Widgets with Pharo

by Ben Coman

On Fri, Sep 29, 2017 at 12:04 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Bloc is ready for your experiments. Here is my first one. > Please let me know what and how to improve. > > Bloc allows for the creation of beautiful widgets. > Here is a panel containing collapsible subpanels > that can be reordered with drag-and-drop. > > https://vimeo.com/235934701 > > Stephan > Thanks Stephan. That provides a good insight into using Bloc. More encouragement to try it out myself. cheers -ben

Sept. 29, 2017

Re: [Pharo-users] X11 options on Ubuntu VM / Athens rendering problems

by Hilaire

Beside the official ones, are you using alternate repositories? It can become a hell. In your posting, a Thoera dependency appeared... Hilaire Le 28/09/2017 Ã 19:51, Igor Stasenko a Ã©critÂ : > > I got libsdl and libcairo 32bits installed fine on 64bits Ubuntu > 17.04. > > weird.. -- Dr. Geo http://drgeo.eu

Sept. 29, 2017

Re: [Pharo-users] [Demo] Creating Bloc Widgets with Pharo

by Igor Stasenko

Stephan , you said you cannot replace the last one in the video. I think you can have an easy solution: you should treat a pane that you are currently over - the one you are going to replace, so if you drag over something which is not placeholder, then it should automatically be shifted and replaced by placeholder. Cheers :) On 29 September 2017 at 00:56, stephan <stephan(a)stack.nl> wrote: > On 28-09-17 21:07, Stephane Ducasse wrote: > >> For example why a BlElement cannot get >> invisible and visible in addition to visibility: BlVisibility visible. >> > > It can, and if we do that systematically we end up with a BlElement with a > thousand methods. There are so many aspects that an element might need to > handle. Handling children, layout, styling, drawing, fonts, events, > visibility. Where should the border be? > > One thing I noted is that in Bloc we don't have a way to decide where to > add a dropped element in a parent that has a specified layout. In Morphic > that is also a responsibility of the layout. > > Stephan > > > > > > > -- Best regards, Igor Stasenko.

Sept. 28, 2017

Re: [Pharo-users] [Demo] Creating Bloc Widgets with Pharo

by stephan

On 28-09-17 21:07, Stephane Ducasse wrote: > For example why a BlElement cannot get > invisible and visible in addition to visibility: BlVisibility visible. It can, and if we do that systematically we end up with a BlElement with a thousand methods. There are so many aspects that an element might need to handle. Handling children, layout, styling, drawing, fonts, events, visibility. Where should the border be? One thing I noted is that in Bloc we don't have a way to decide where to add a dropped element in a parent that has a specified layout. In Morphic that is also a responsibility of the layout. Stephan

Sept. 28, 2017

Re: [Pharo-users] [Demo] Creating Bloc Widgets with Pharo

by stephan

On 28-09-17 21:03, Stephane Ducasse wrote: > Now how do you validate the API of your widgets. Good question. In Morphic I had everything centralized in the Morph. The advantage is that it is clear what influences what, the disadvantage is that it easily results in very complex code. Here I have event handling spread over multiple objects. That gives here a better separation of concerns. The pane itself handles clicking, the dragInteraction object the drag and drop. Separating these two works, but in a more complex application there could be e.g. multiple drag and drop relationships. > I think that write test is a really because in that it will force us > to have fully scriptable widgets. Indeed. At the moment I am still trying to find out how I want to distribute responsibilities. I welcome ideas on how to improve this. And of course I would like the dropping to also work on the last position. Stephan

Sept. 28, 2017

Re: [Pharo-users] Is a non-break space whitespace?

by JuliÃ¡n Maestri

The non breaking space, is a whitespace character or separator depending on the context. As far as i know it's not considered as a separator only when deciding text layout, it means do not break the line here: eg: "A distance of 100 meters" (nbsp between 100 and meters) should be rendered as either: > A distance of 100 meters or: > A distance of > 100 meters But not: > A distance of 100 > meters There's an opposite character (don't remember the code) which means <you can break here if you need to> which is NOT a whitespace. On 25 September 2017 at 10:21, stephan <stephan(a)stack.nl> wrote: > On 25-09-17 09:53, Richard Sargent wrote: > >> Rather than off-the-cuffing anything, please honour the Unicode Character >> Properties. Refer to >> https://en.wikipedia.org/wiki/Unicode_character_property#Whitespace, >> among >> others. >> > > That is a good idea. And it won't help you if you scrape data from the > web, as you'll find plenty of bad encoding. And unclarity over which > version of which standard was used (see mongolian vowel separator) > > Stephan > > >

Sept. 28, 2017

Re: [Pharo-users] [Demo] Creating Bloc Widgets with Pharo

by Stephane Ducasse

I was wondering how we could provide a "better" interface for object. For example why a BlElement cannot get invisible and visible in addition to visibility: BlVisibility visible. Stef On Thu, Sep 28, 2017 at 9:03 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Thanks Stefan > I will have a look. > Now how do you validate the API of your widgets. > I think that write test is a really because in that it will force us > to have fully scriptable widgets. > > stef > > > On Thu, Sep 28, 2017 at 6:04 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: >> Bloc is ready for your experiments. Here is my first one. >> Please let me know what and how to improve. >> >> Bloc allows for the creation of beautiful widgets. >> Here is a panel containing collapsible subpanels >> that can be reordered with drag-and-drop. >> >> https://vimeo.com/235934701 >> >> Stephan

Sept. 28, 2017

Re: [Pharo-users] [Demo] Creating Bloc Widgets with Pharo

by Stephane Ducasse

Thanks Stefan I will have a look. Now how do you validate the API of your widgets. I think that write test is a really because in that it will force us to have fully scriptable widgets. stef On Thu, Sep 28, 2017 at 6:04 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Bloc is ready for your experiments. Here is my first one. > Please let me know what and how to improve. > > Bloc allows for the creation of beautiful widgets. > Here is a panel containing collapsible subpanels > that can be reordered with drag-and-drop. > > https://vimeo.com/235934701 > > Stephan

Sept. 28, 2017