- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pillar] Font-size on DeckJS

by Yann Dubois

Yes, last week since a presentation in class with Damien Cassou and stepharo, they said that the presentation generated with pillar has a small font size and it would be good to having a way to change that. It s not a pharo issue but I think it could be useful for pillar's users. Le 18 mars 2016 17:44, "Alexandre Bergel" <alexandre.bergel(a)me.com> a Ã©crit : > Is this related to Pharo? > > Alexandre > > > > On Mar 18, 2016, at 5:30 PM, Yann Dubois <yann59.dubois(a)gmail.com> > wrote: > > > > Hello world, > > > > I work today on a problem when we generate a presentation with DeckJS, > the font size is very small on projection. > > > > I've find an issue for this, and you need to create a template with all > deckJS dependancies, and an other css file to change some rules. > > > > > > To change the font-size of a body slide (not title or subtitle), you > need to rewrite this rules like this : > > > > .deck-slide-scaler p { > > font-size: 64px > > } > > > > The scaling always works, and you don't need to touch the deckjs files. > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

March 18, 2016

Re: [Pharo-users] Nesting Builders in Roassal

by Alexandre Bergel

Hi Evan, You are indeed on the edge of what Roassal can do. This is a situation that I have tried to fix. Please play with the solution I propose and complain if this is not what you expect. Try this: -=-=-=-=-=-=-=-=-=-=-=-= v := RTView new. es := RTShape withAllSubclasses collect: [ :cls | b := RTPieBuilder new. b interaction popupText. b objects: cls withAllSuperclasses. b slice: #numberOfMethods. b normalizer distinctColor. b build; asElement. ]. v addAll: es. RTCellLayout new lineItemsCount: 8; on: es. v -=-=-=-=-=-=-=-=-=-=-=-= It produces the following Now, you can send the message #asElement to a builder or a view. This message returns a "compound elementâ (something new I have recently introduced) which can freely be added to a view. Is this what you expect? It is likely that this mechanism will be a foundation of Roassal3 as nesting is a recurrent need. Cheers, Alexandre > On Mar 17, 2016, at 9:59 PM, Evan Donahue <emdonahu(a)gmail.com> wrote: > > Hello, > > I am working with Roassal and trying to write a cell-layout builder that uses RTPieBuilders internally as its nested objects. The nesting docs cover nesting RT elements, but not builders. The composition docs cover composing builders, but not nesting them. I have a partial solution, but it is getting increasingly hacky, to the point where it may be easier to just duplicate the piebuilder code in my builder. Before I go down that road, I wanted to check if there was a more natural way to nest builders. > > Below is a mashup of the Roassal Examples Nesting and Pie Chart builders that gives the basic flavor of what I am trying to accomplish. Notice that I am creating new PieBuilders every time, running them, and extracting their createdElements for my layout. This works well enough, but if I then want to normalize global properties so that all pie slices with the same property get the same color, I have no way to coordinate the newly generated PieBuilders, as each possesses its own normalizer. Likewise, if I have a global PieBuilder, its internal state gets trampled with each iteration. I figured there was likely an easy way to compose builders that I didn't know about, so I thought I would ask. > > | v es b | > v := RTView new. > es := RTEllipse elementsOn: RTShape withAllSubclasses. > v addAll: es. > > RTNest new > for: es > add: [ :group :model | > b := RTPieBuilder new. > b objects: RTShape withAllSubclasses. > b slice: #numberOfMethods. > b normalizer distinctColor. > b view: v. > b build. > group addAll: b createdElements. ]. > > RTCellLayout new lineItemsCount: 8; on: es. > v > > > Thanks, > Evan -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 18, 2016

Re: [Pharo-users] Nesting Builders in Roassal

by Evan Donahue

Hello, Many thanks for the reply. This indeed solves part of my problem, and does what I expect (although in the smalltalkhub / ObjectProfile / development code, only RTView has #asElement, not RTBuilder). Given this, I think I can give an example of the real stumbling block I'm facing (although whether it is a framework limitation or my own ignorance, I cannot say). Note that in the following code, there are two solid pie charts of the same color, but each represents a different object (the numbers 1 and 2 respectively). This is happening because each pie chart is generated with its own normalizer. Is it possible to share a single, global normalizer across many pie charts, or set up a single pie builder outside of the loop and then only vary its objects? I would like every slice in every pie chart that represents the number 1 to be one color, and every slice representing the number 2 to be a different color. Which color they are does not matter so long as they are distinct, and I will not know ahead of time how many different colors I will need or what types of objects I will be representing, so I can't manually assign colors to categories. v := RTView new. data := #((1) (2) (1 2)). es := data collect: [ :d | b := RTPieBuilder new. b interaction popupText. b objects: d. b slice: #value. b normalizer distinctColor. b build. b view asElement. ]. v addAll: es. RTCellLayout new lineItemsCount: 3; on: es. v Thank you, Evan -- View this message in context: http://forum.world.st/Nesting-Builders-in-Roassal-tp4885185p4885372.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 18, 2016

Re: [Pharo-users] [Pillar] Logo for Pillar

by Cyril Ferlicot

Hi, Personally I do not like it. (Maybe I'm difficult :) ). I think that it would be better to have the "illar" at the bottom and not compressed in the middle. The second column look like an "y" and we read "Pillary". And why is there a wave under pillar? I think that things in a logo have to be symbolic and I do not find anything from the wave. Anyway, thank you to invest your time in pillar :) On Friday, 18 March 2016, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: > Hi, > > > With a mate, we've worked on a logo for Pillar. > > We just want feedbacks on it. > > > You can fin the logo join files. > > > thanks :) > > > Good afternoon, > > Thibault > -- Cheers Cyril Ferlicot

March 18, 2016

Re: [Pharo-users] [Pillar] Font-size on DeckJS

by Alexandre Bergel

Is this related to Pharo? Alexandre > On Mar 18, 2016, at 5:30 PM, Yann Dubois <yann59.dubois(a)gmail.com> wrote: > > Hello world, > > I work today on a problem when we generate a presentation with DeckJS, the font size is very small on projection. > > I've find an issue for this, and you need to create a template with all deckJS dependancies, and an other css file to change some rules. > > > To change the font-size of a body slide (not title or subtitle), you need to rewrite this rules like this : > > .deck-slide-scaler p { > font-size: 64px > } > > The scaling always works, and you don't need to touch the deckjs files. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 18, 2016

Re: [Pharo-users] [Pillar] Logo for Pillar

by Alexandre Bergel

Wow!!! Alexandre > On Mar 18, 2016, at 3:30 PM, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: > > Hi, > > With a mate, we've worked on a logo for Pillar. > We just want feedbacks on it. > > You can fin the logo join files. > > thanks :) > > Good afternoon, > Thibault > <pillar2.svg> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 18, 2016

[Pillar] Font-size on DeckJS

by Yann Dubois

Hello world, I work today on a problem when we generate a presentation with DeckJS, the font size is very small on projection. I've find an issue for this, and you need to create a template with all deckJS dependancies, and an other css file to change some rules. To change the font-size of a body slide (not title or subtitle), you need to rewrite this rules like this : .deck-slide-scaler p { font-size: 64px } The scaling always works, and you don't need to touch the deckjs files.

March 18, 2016

Re: [Pharo-users] [Pillar] Logo for Pillar

by Yann Dubois

I'm existing about this logo, it's a very nice logo.

March 18, 2016

[Pillar] Logo for Pillar

by Thibault ARLOING

Hi, With a mate, we've worked on a logo for Pillar. We just want feedbacks on it. You can fin the logo join files. thanks :) Good afternoon, Thibault

March 18, 2016

Generating custom classes based on attributes from XML Document

by Peter UhnÃ¡k

I have a XML like this <packagedElement xmi:type="uml:Class" xmi:id="EAID_4A" name="DCEdge" isAbstract="true">  </packagedElement> <packagedElement xmi:type="uml:Association" xmi:id="EAID_46">  </packagedElement> and I would like to generate UmlClass and UmlAssociation classes for this. I could use XMLPluggableElementFactory, however that only allows me to specify the target class only on the element's name, such as doc := (XMLDOMParser on: someXML) nodeFactory: (XMLPluggableElementFactory new elementClass: GenericElement; handleElement: 'packagedElement' withClass: UmlPackagedElement) parseDocument. However I need better granularity, because I would like to have a different class for 'packagedElement[xmi:type="uml:Class"]' and different class for 'packagedElement[xmi:type="uml:Association"]'. Of course I could use double visitors (so use the Pluggable stuff to get UmlPackagedElement) and then make another pass on it to get the final classes, however I would prefer to have to wanted class directly without the need to go through intermediate representation. Is there a way to do this? Thanks, Peter

March 18, 2016