April 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] XMLParser GTInspector extensions

by Ben Coman

Arising out of this I am wondering if there is some existing way for an XMLNode to customise its printString based on the application's custom tags ? I am looking into an importer for VisualWorks Parcels (btw, has anyone done this already?). In this case the GT-InspectorExtensions-XML [Tree] tab is not ideal since the tree-items only show the element tag but no identifying name (see XMLScreenShot.png). XMLElement>>gtDisplayOn: shows attributes, so ideally there would be an identifying attribute like "name", but with Parcels the "name" is a sub-element rather than an attribute. My own first pass GT extension... XMLNodeWithChildren>>gtInspectorNodesIn: composite <gtInspectorPresentationOrder: 5> composite list title: 'Nodes'; display: [ self nodes ] ; format: [ :each | each printString lineNumber: 1 ]. ...got around this by displaying the whole first line (see XMLScreenShot2.png) -- but I realise now this works sort of by accident, just for this particular case. Other cases might not have significant info on the first line. What I'd really like to be able to do is customise the XMLNode #printString to my application's XML tags. The approach I forsee is the application adds extension methods to XMLNode and friends (e.g. XMLNode>>myPrintOn:) that are called from a new class MyNodePrinter. Then you do something like... xmlDoc := XMLDOMParser parseFileNamed: 'PDFDevelopment.pst' . xmlDoc setNodePrinter: MyNodePrinter new. Alternatively the extension method could be referenced directly... xmlDoc := XMLDOMParser parseFileNamed: 'PDFDevelopment.pst' . xmlDoc nodePrinterMethod: #myPrintOn: In either case, this could be stored either: 1. In the document root such that each XMLNode needs follow the parent chain back to the document root to determine how to be printed. 2. An instance variable in XMLNode such that #setNodePrinter: descends the tree copying theMyNodePrinter into each node. So, is this way off base? Would it be useful? Could it be made workable? cheers -ben On Mon, Apr 27, 2015 at 3:19 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > There already exists a GT-InspectorExtensions-XML which is already > published in the GT repository. > > I would prefer to qualify the extensions by the tool they refer to: > GT-InspectorExtnesions-*, GT-SpotterExtensions-* etc. > > gtDisplayOn: should be more in the inspector, but probably some were added > mostly in the spotter so they ended up in the less optimal package. > > Cheers, > Doru > > > > On Sun, Apr 26, 2015 at 8:30 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> I happened to need to use and XML Parser for the first time and found >> inspecting the structure awkward, so I added some GTInspector extensions to >> XML-Parser. This is uploaded as XML-Parser-BenComan.304 to >> http://smalltalkhub.com/#!/~PharoExtras/XMLParser. Could someone who >> uses XML regularly check if these are reasonable? >> >> Now should these methods be packaged separately somehow, since they are >> likely not of interest to other Smalltalk flavours? >> >> btw I gave them a protocol of "GT-Extensions" - but I also considered >> "moldable-tools" and "tools-extensions". If there a preference? This will >> likely be a common occurrence across the community, so we should try for a >> consistent convention across the community for such extensions. >> >> btw2, I notice that #gtDisplayOn: implementors are fairly evenly split >> between [GT-InspectorExtensions-Core] and [GT-SpotterExtensions-Core]. Are >> they really separated like this in their use? >> >> cheers -ben >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

April 27, 2015

Re: [Pharo-users] Woden-Roassal 3d object rotations

by Lusa Nicolas

Here is the fix. Check it out. Cheers, Nicolas

April 27, 2015

Postdoc position at the University of Chile

by Alexandre Bergel

Dear All, There is a possibility to do a postdoc at the University of Chile. The position is competitive: 3 years, good salary, and a budget you can spend as you wish. Get in touch with me for more info. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 27, 2015

Re: [Pharo-users] Woden-Roassal 3d object rotations

by Lusa Nicolas

Hello it's me again, I've been playing around a little and found a bug which makes all rotations the same. No matter which rotation you call it is always going to rotate around the X axis. I guess that is due the fact that all the three rotations end up calling: (self class xrot: angle) * self, in the respective method. (i.e. WDMatrix3>>#RotatedByY:). The fix is just to change the xrot with the respective rot of the axis that we are rotating. Thanks again for the rotations. Cheers, Nicolas On Apr 27, 2015, at 10:30 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch<mailto:nicolas.lusa@usi.ch>> wrote: Hello mr. Salgado, I've just tried it out really quickly and it looks awesome! Looking forward to use it in my project. Thank you! Cheers, Nicolas On Apr 27, 2015, at 9:36 AM, Ronie Salgado <roniesalg(a)gmail.com<mailto:roniesalg@gmail.com>> wrote: Hello Mr. Lusa, Sorry for not answering earlier, I added the missing support for the rotations by adding some methods that changes the internal scene node orientation. I also did a small refactoring in the support for orientation, because I received email with an implementation of quaternions that I have review and integrate during the week. Try the following in the playground: v := RWView new. element := RWCube element. element rotateByXDegrees: 60. v add: element. v open. Best regards, Ronie 2015-04-27 3:55 GMT-03:00 Lusa Nicolas <nicolas.lusa(a)usi.ch<mailto:nicolas.lusa@usi.ch>>: Hello mr. Bergel, I actually have done something really simple. On the construction of a cube shape in WDGeometryBuilder I simply made a method looking as follows: WDGeometryBuilder>>#addCubeWithWidth: height: depth: rotatedBy: . In the method I simply use the angle to compute the rotation when creating every single triangle (rotating every point of such triangle with respect to the y axis). It would work smoothly if only few shapes would have been instantiated but unfortunately this results in a severe drop of performance since a new shape is created for every instance of an object (because the angle rotation is different for each shape). If you still want the code I wrote for such rotation I can provide it to you, but probably that's not how proper rotations should be performed in woden. Hopefully we can find a better solution that doesn't influence performance in such way. Cheers, Nicolas P.S. I apologize for the misleading subject of the mail. I am not using Roassal3d but I am using a package called Woden-Roassal, which works almost exactly like Roassal3d (in fact I guess they are related somehow), that is in the Woden project as default. A more appropriate e-mail subject would have been: Woden-Roassal (3d object rotations). On Apr 24, 2015, at 10:49 PM, Alexandre Bergel <alexandre.bergel(a)me.com<mailto:alexandre.bergel@me.com>> wrote: Hi Lusa, Well spotted! I worked on the connection Woden <â> Roassal3d. I should be able to hook your rotation into roassal. Can you provide your fix for the rotation please? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu<http://www.bergel.eu/> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Apr 22, 2015, at 9:07 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch<mailto:nicolas.lusa@usi.ch>> wrote: Hi, I am still working with Woden, in particular with Woden-Roassal and I noticed that rotations on objects are missing (I feel that this is weird that it doesn't have such feature so I am not excluding that I can be wrong but I didn't manage to find anything in the code to rotate objects). Now if I would like to rotate objects it wouldn't be too bad if I were using Woden at his "lowest layer" but I am actually building cubes with Woden-Roassal and there I get lost. I already made some rotations on Woden built arbitrary objects, now I would like to extend it to objects built from Woden-Roassal but I honestly miss on finding the connection between the two. I saw that the base shape is built in: RWCube>>#createBaseShapeNode, I would be able to build a rotated shape from there but that would result in all shapes being rotated in such way since in RWSimpleShape>>#buildRenderableFor:view: when we select the shape: baseShape := aView baseShapeNodeNamed: self baseShapeName ifAbsentPut: [ self createBaseShapeNode ]. we would get back the previous base shape defined. Any suggestions on how to do it? Cheers, Nicolas

April 27, 2015

Re: [Pharo-users] The Pillar TextMate plugin can now preview Pillar files

by Luc Fabresse

ok Cyril was right, the problem was because of generated filename changes in Pillar. It is now fixed in the latest version of the plugin. #Luc 2015-04-25 22:26 GMT+02:00 Luc Fabresse <luc.fabresse(a)gmail.com>: > > Perhaps I answered too fast and Cyril is right. > Stef, tell me if this is the case and I will patch the plugin. > > #Luc > > 2015-04-25 22:21 GMT+02:00 Luc Fabresse <luc.fabresse(a)gmail.com>: > >> Hey, I wrote a six line README on >> https://github.com/pillar-markup/Pillar.tmbundle >> and you miss the latest step apparently ;-) >> >> >> - Open TextMate preferences and add these 2 shell variables : >> - PHARO_VM that gives the absolute path to the PharoVM Example: >> /Users/bob/Pharo/VirtualMachines/pharo >> - PILLAR_IMAGE that gives the absolute path to the image to use >> for processing Pillar files Example: >> /Users/bob/Repositories/PharoBooks/BookSkeleton.git/Pharo.image >> >> >> #Luc >> >> 2015-04-25 22:15 GMT+02:00 stepharo <stepharo(a)free.fr>: >> >>> hi luc >>> >>> I did >>> >>> git clone https://github.com/pillar-markup/Pillar.tmbundle >>> cd Pillar.tmbundle >>> open . >>> and mate asked me if I want to plugin >>> did yes >>> >>> commd-R >>> >>> Typeset and view: line 15: pillar: command not found cat: >>> /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/FunWithPharo/TinyChat/TinyChat.pillar.html: >>> No such file or directory >>> >>> What is the pillar command? >>> >>> Stef >>> >>> Le 25/4/15 11:42, Cyril Ferlicot a Ã©crit : >>> >>> Thank you ! :) >>> >>> Le samedi 25 avril 2015, Luc Fabresse <luc.fabresse(a)gmail.com> a Ã©crit : >>> >>>> Hi Happy Pharoers, >>>> >>>> Since I am editing more and more Pillar files these days, I enhanced >>>> the Pillar TextMate2 plugin made by Uko (thanks ;-)) to easily have a web >>>> preview (just by pressing âR). >>>> >>>> The plugin is here: https://github.com/pillar-markup/Pillar.tmbundle >>>> >>>> Have fun, >>>> >>>> #Luc >>>> >>>> [image: Images intÃ©grÃ©es 2]Hi >>>> >>> >>> >>> -- >>> Cheers >>> Cyril Ferlicot >>> >>> >>> >> >

April 27, 2015

Question about Text Editor.

by Cyril Ferlicot

Hi, I wanted to do a little text editor and I would like to know if someone already did one with simple features like open a file, save a file etc... I don't want to lose too much time in something that already exist. -- Cheers Cyril Ferlicot

April 27, 2015

Re: [Pharo-users] Woden-Roassal 3d object rotations

by Lusa Nicolas

Hello mr. Salgado, I've just tried it out really quickly and it looks awesome! Looking forward to use it in my project. Thank you! Cheers, Nicolas On Apr 27, 2015, at 9:36 AM, Ronie Salgado <roniesalg(a)gmail.com<mailto:roniesalg@gmail.com>> wrote: Hello Mr. Lusa, Sorry for not answering earlier, I added the missing support for the rotations by adding some methods that changes the internal scene node orientation. I also did a small refactoring in the support for orientation, because I received email with an implementation of quaternions that I have review and integrate during the week. Try the following in the playground: v := RWView new. element := RWCube element. element rotateByXDegrees: 60. v add: element. v open. Best regards, Ronie 2015-04-27 3:55 GMT-03:00 Lusa Nicolas <nicolas.lusa(a)usi.ch<mailto:nicolas.lusa@usi.ch>>: Hello mr. Bergel, I actually have done something really simple. On the construction of a cube shape in WDGeometryBuilder I simply made a method looking as follows: WDGeometryBuilder>>#addCubeWithWidth: height: depth: rotatedBy: . In the method I simply use the angle to compute the rotation when creating every single triangle (rotating every point of such triangle with respect to the y axis). It would work smoothly if only few shapes would have been instantiated but unfortunately this results in a severe drop of performance since a new shape is created for every instance of an object (because the angle rotation is different for each shape). If you still want the code I wrote for such rotation I can provide it to you, but probably that's not how proper rotations should be performed in woden. Hopefully we can find a better solution that doesn't influence performance in such way. Cheers, Nicolas P.S. I apologize for the misleading subject of the mail. I am not using Roassal3d but I am using a package called Woden-Roassal, which works almost exactly like Roassal3d (in fact I guess they are related somehow), that is in the Woden project as default. A more appropriate e-mail subject would have been: Woden-Roassal (3d object rotations). On Apr 24, 2015, at 10:49 PM, Alexandre Bergel <alexandre.bergel(a)me.com<mailto:alexandre.bergel@me.com>> wrote: Hi Lusa, Well spotted! I worked on the connection Woden <â> Roassal3d. I should be able to hook your rotation into roassal. Can you provide your fix for the rotation please? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu<http://www.bergel.eu/> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Apr 22, 2015, at 9:07 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch<mailto:nicolas.lusa@usi.ch>> wrote: Hi, I am still working with Woden, in particular with Woden-Roassal and I noticed that rotations on objects are missing (I feel that this is weird that it doesn't have such feature so I am not excluding that I can be wrong but I didn't manage to find anything in the code to rotate objects). Now if I would like to rotate objects it wouldn't be too bad if I were using Woden at his "lowest layer" but I am actually building cubes with Woden-Roassal and there I get lost. I already made some rotations on Woden built arbitrary objects, now I would like to extend it to objects built from Woden-Roassal but I honestly miss on finding the connection between the two. I saw that the base shape is built in: RWCube>>#createBaseShapeNode, I would be able to build a rotated shape from there but that would result in all shapes being rotated in such way since in RWSimpleShape>>#buildRenderableFor:view: when we select the shape: baseShape := aView baseShapeNodeNamed: self baseShapeName ifAbsentPut: [ self createBaseShapeNode ]. we would get back the previous base shape defined. Any suggestions on how to do it? Cheers, Nicolas

April 27, 2015

Re: [Pharo-users] Woden-Roassal 3d object rotations

by Ronie Salgado

Hello Mr. Lusa, Sorry for not answering earlier, I added the missing support for the rotations by adding some methods that changes the internal scene node orientation. I also did a small refactoring in the support for orientation, because I received email with an implementation of quaternions that I have review and integrate during the week. Try the following in the playground: v := RWView new. element := RWCube element. element rotateByXDegrees: 60. v add: element. v open. Best regards, Ronie 2015-04-27 3:55 GMT-03:00 Lusa Nicolas <nicolas.lusa(a)usi.ch>: > Hello mr. Bergel, > > I actually have done something really simple. On the construction of a > cube shape in WDGeometryBuilder I simply made a method looking as follows: > WDGeometryBuilder>>#addCubeWithWidth: height: depth: rotatedBy: . > In the method I simply use the angle to compute the rotation when creating > every single triangle (rotating every point of such triangle with respect > to the y axis). > It would work smoothly if only few shapes would have been instantiated but > unfortunately this results in a severe drop of performance since a new > shape is created for every instance of an object (because the angle > rotation is different for each shape). > If you still want the code I wrote for such rotation I can provide it to > you, but probably that's not how proper rotations should be performed in > woden. > > Hopefully we can find a better solution that doesn't influence > performance in such way. > > Cheers, > Nicolas > > P.S. I apologize for the misleading subject of the mail. I am not using > Roassal3d but I am using a package called Woden-Roassal, which works almost > exactly like Roassal3d (in fact I guess they are related somehow), that is > in the Woden project as default. A more appropriate e-mail subject would > have been: Woden-Roassal (3d object rotations). > > On Apr 24, 2015, at 10:49 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > Hi Lusa, > > Well spotted! > I worked on the connection Woden <â> Roassal3d. I should be able to hook > your rotation into roassal. Can you provide your fix for the rotation > please? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Apr 22, 2015, at 9:07 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch> wrote: > > Hi, > > I am still working with Woden, in particular with Woden-Roassal and I > noticed that rotations on objects are missing (I feel that this is weird > that it doesn't have such feature so I am not excluding that I can be wrong > but I didn't manage to find anything in the code to rotate objects). > > Now if I would like to rotate objects it wouldn't be too bad if I were > using Woden at his "lowest layer" but I am actually building cubes with > Woden-Roassal and there I get lost. > > I already made some rotations on Woden built arbitrary objects, now I > would like to extend it to objects built from Woden-Roassal but I honestly > miss on finding the connection between the two. > > I saw that the base shape is built in: RWCube>>#createBaseShapeNode, I > would be able to build a rotated shape from there but that would result in > all shapes being rotated in such way since in > RWSimpleShape>>#buildRenderableFor:view: when we select the shape: > baseShape := aView baseShapeNodeNamed: self baseShapeName ifAbsentPut: [ > self createBaseShapeNode ]. > we would get back the previous base shape defined. > > Any suggestions on how to do it? > > Cheers, > Nicolas > > > >

April 27, 2015

Re: [Pharo-users] Woden-Roassal 3d object rotations

by Lusa Nicolas

Hello mr. Bergel, I actually have done something really simple. On the construction of a cube shape in WDGeometryBuilder I simply made a method looking as follows: WDGeometryBuilder>>#addCubeWithWidth: height: depth: rotatedBy: . In the method I simply use the angle to compute the rotation when creating every single triangle (rotating every point of such triangle with respect to the y axis). It would work smoothly if only few shapes would have been instantiated but unfortunately this results in a severe drop of performance since a new shape is created for every instance of an object (because the angle rotation is different for each shape). If you still want the code I wrote for such rotation I can provide it to you, but probably that's not how proper rotations should be performed in woden. Hopefully we can find a better solution that doesn't influence performance in such way. Cheers, Nicolas P.S. I apologize for the misleading subject of the mail. I am not using Roassal3d but I am using a package called Woden-Roassal, which works almost exactly like Roassal3d (in fact I guess they are related somehow), that is in the Woden project as default. A more appropriate e-mail subject would have been: Woden-Roassal (3d object rotations). On Apr 24, 2015, at 10:49 PM, Alexandre Bergel <alexandre.bergel(a)me.com<mailto:alexandre.bergel@me.com>> wrote: Hi Lusa, Well spotted! I worked on the connection Woden <â> Roassal3d. I should be able to hook your rotation into roassal. Can you provide your fix for the rotation please? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu<http://www.bergel.eu/> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Apr 22, 2015, at 9:07 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch<mailto:nicolas.lusa@usi.ch>> wrote: Hi, I am still working with Woden, in particular with Woden-Roassal and I noticed that rotations on objects are missing (I feel that this is weird that it doesn't have such feature so I am not excluding that I can be wrong but I didn't manage to find anything in the code to rotate objects). Now if I would like to rotate objects it wouldn't be too bad if I were using Woden at his "lowest layer" but I am actually building cubes with Woden-Roassal and there I get lost. I already made some rotations on Woden built arbitrary objects, now I would like to extend it to objects built from Woden-Roassal but I honestly miss on finding the connection between the two. I saw that the base shape is built in: RWCube>>#createBaseShapeNode, I would be able to build a rotated shape from there but that would result in all shapes being rotated in such way since in RWSimpleShape>>#buildRenderableFor:view: when we select the shape: baseShape := aView baseShapeNodeNamed: self baseShapeName ifAbsentPut: [ self createBaseShapeNode ]. we would get back the previous base shape defined. Any suggestions on how to do it? Cheers, Nicolas

April 27, 2015

{ANN] TMM (Teapot, Mustache, Mongo) web application stack

by Yanni Chiu

Hi, I cleaned up and released some demo code I put together for a Smalltalk user group meeting. The code was extracted from a project Iâve been working on. It also uses Magritte3, Voyage, and ZincSSO, but thatâs too many pieces to include in the web-app-stack name I was working in Pharo3, so I took the opportunity to upgrade to Pharo4. I had no problems with Pharo4 itself, but I had some minor issues with the updated Teapot and VoyageMongo versions: - VoyageMongo - <mongoContainer> pragma is now expected on class-side, not the instance-side - Teapot - To read/parse template files on each request (which is convenient during development) I had intercepted an internal API. This API changed slightly, which needed a simple fix, but it was hard to find I also decided to use a âgitâ repository. This turned out to be one of the hardest parts, but I think it was worth the effort. To try TMM, follow the instructions at: https://github.com/yannij/TMM Enhancements are welcome, but I donât quite know how this git workflow will pan out. Iâve already got a few changes to port over: - a more integrated file upload example - an email/passwordHash stored in the User object in mongo. â Yanni

April 27, 2015