Hi, We have gone through most of the Roassal problems, but we still have a couple of issues left. First, we need to be able to export to PNG. Right now, the implementation exports only the visible part of the morph, but it should export the whole canvas. Ideally, we should use the Athens ability of exporting PNGs: https://code.google.com/p/moose-technology/issues/detail?id=1089

Then, we still have a couple of visualizations left to port: PPParser>>visualizeStructureInGraphOn: PPParser>>viewAllNamedParsersWithSelection:previewing:on: Any takers? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Le 02/11/2014 01:33, Nicolai Hess a écrit : > 2014-11-01 22:06 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>>: > > Hi, > > We have gone through most of the Roassal problems, but we still have > a couple of issues left. > > First, we need to be able to export to PNG. Right now, the > implementation exports only the visible part of the morph, but it > should export the whole canvas. Ideally, we should use the Athens > ability of exporting PNGs: > https://code.google.com/p/moose-technology/issues/detail?id=1089 > > > Is there any notion of "view (all shapes) extent"? I am afraid the > extent is only defined by the actual Morph, therefore, we > can only draw and export the visible part in the morph. > view canvas camera encompassingRectangle. the answer is relative to the camera transform and does not include fixed shapes (menu buttons). Thierry > Using Athens for exporting, we need a way to create an AthensSurface > with the correct (enlarged) extent. The problem is, the extent is defined > by TrachelShape but the TRMorph is the one holding the AthensSurface. > > Your proposed solution in > https://code.google.com/p/moose-technology/issues/detail?id=1089#c4 > should work, although it does not go through athenssurface>>writeToPng: > but instead it > creates a form > renders on an athens surface > copies the rendering on to the imageform > export the image form > > If your code creates a rendering error like NBFFICallout > class>>#signalError, it is because > the Athens-Api is picky about Fraction as arguments for surface extents > or transformations: > > TRMorph>>#drawOn: > .... > > cs pathTransform > translateBy: self extent / > 2; "<<----------" > scaleBy: trachelCanvas camera scale asFloat; > translateBy: trachelCanvas camera position negated. > trachelCanvas shapes do: [ :trachelShape | > trachelShape drawOn: cs. > ]. > > ... > > > > > > > > Then, we still have a couple of visualizations left to port: > PPParser>>visualizeStructureInGraphOn: > PPParser>>viewAllNamedParsersWithSelection:previewing:on: > > Any takers? > > Cheers, > Doru > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Thank you! Doru -- www.tudorgirba.com "Every thing has its own flow" On 07 Nov 2014, at 19:55, milton mamani <akevalion(a)gmail.com&gt; wrote: Hi Tudor, I will check the next items this weekend: PPParser>>visualizeStructureInGraphOn: PPParser>>viewAllNamedParsersWithSelection:previewing:on: Cheers, Milton 2014-11-02 3:52 GMT-03:00 Thierry Goubier <thierry.goubier(a)gmail.com&gt;: > Le 02/11/2014 01:33, Nicolai Hess a écrit : > >> 2014-11-01 22:06 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com >> <mailto:tudor@tudorgirba.com>>: >> >> Hi, >> >> We have gone through most of the Roassal problems, but we still have >> a couple of issues left. >> >> First, we need to be able to export to PNG. Right now, the >> implementation exports only the visible part of the morph, but it >> should export the whole canvas. Ideally, we should use the Athens >> ability of exporting PNGs: >> https://code.google.com/p/moose-technology/issues/detail?id=1089 >> >> >> Is there any notion of "view (all shapes) extent"? I am afraid the >> extent is only defined by the actual Morph, therefore, we >> can only draw and export the visible part in the morph. >> > > view canvas camera encompassingRectangle. > > the answer is relative to the camera transform and does not include fixed > shapes (menu buttons). > > Thierry > > >> Using Athens for exporting, we need a way to create an AthensSurface >> with the correct (enlarged) extent. The problem is, the extent is defined >> by TrachelShape but the TRMorph is the one holding the AthensSurface. >> >> Your proposed solution in >> https://code.google.com/p/moose-technology/issues/detail?id=1089#c4 >> should work, although it does not go through athenssurface>>writeToPng: >> but instead it >> creates a form >> renders on an athens surface >> copies the rendering on to the imageform >> export the image form >> >> If your code creates a rendering error like NBFFICallout >> class>>#signalError, it is because >> the Athens-Api is picky about Fraction as arguments for surface extents >> or transformations: >> >> TRMorph>>#drawOn: >> .... >> >> cs pathTransform >> translateBy: self extent / >> 2; "<<----------" >> scaleBy: trachelCanvas camera scale asFloat; >> translateBy: trachelCanvas camera position negated. >> trachelCanvas shapes do: [ :trachelShape | >> trachelShape drawOn: cs. >> ]. >> >> ... >> >> >> >> >> >> >> >> Then, we still have a couple of visualizations left to port: >> PPParser>>visualizeStructureInGraphOn: >> PPParser>>viewAllNamedParsersWithSelection:previewing:on: >> >> Any takers? >> >> Cheers, >> Doru >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> >> "Every thing has its own flow" >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Thanks! Alexandre Le 08-11-2014 à 5:38, Tudor Girba <tudor(a)tudorgirba.com&gt; a écrit : If you are wondering how to trigger the visualizations, you can trigger them on any parser instance. For example: PPArithmeticParser new visualizeStructureInGraph Doru On Fri, Nov 7, 2014 at 9:04 PM, Tudor Girba <tudor(a)tudorgirba.com&gt; wrote: > Thank you! > > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > On 07 Nov 2014, at 19:55, milton mamani <akevalion(a)gmail.com&gt; wrote: > > Hi Tudor, > > I will check the next items this weekend: > > PPParser>>visualizeStructureInGraphOn: > PPParser>>viewAllNamedParsersWithSelection:previewing:on: > > Cheers, > Milton > > > 2014-11-02 3:52 GMT-03:00 Thierry Goubier <thierry.goubier(a)gmail.com&gt;: > >> Le 02/11/2014 01:33, Nicolai Hess a écrit : >> >>> 2014-11-01 22:06 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com >>> <mailto:tudor@tudorgirba.com>>: >>> >>> Hi, >>> >>> We have gone through most of the Roassal problems, but we still have >>> a couple of issues left. >>> >>> First, we need to be able to export to PNG. Right now, the >>> implementation exports only the visible part of the morph, but it >>> should export the whole canvas. Ideally, we should use the Athens >>> ability of exporting PNGs: >>> https://code.google.com/p/moose-technology/issues/detail?id=1089 >>> >>> >>> Is there any notion of "view (all shapes) extent"? I am afraid the >>> extent is only defined by the actual Morph, therefore, we >>> can only draw and export the visible part in the morph. >>> >> >> view canvas camera encompassingRectangle. >> >> the answer is relative to the camera transform and does not include >> fixed shapes (menu buttons). >> >> Thierry >> >> >>> Using Athens for exporting, we need a way to create an AthensSurface >>> with the correct (enlarged) extent. The problem is, the extent is >>> defined >>> by TrachelShape but the TRMorph is the one holding the AthensSurface. >>> >>> Your proposed solution in >>> https://code.google.com/p/moose-technology/issues/detail?id=1089#c4 >>> should work, although it does not go through athenssurface>>writeToPng: >>> but instead it >>> creates a form >>> renders on an athens surface >>> copies the rendering on to the imageform >>> export the image form >>> >>> If your code creates a rendering error like NBFFICallout >>> class>>#signalError, it is because >>> the Athens-Api is picky about Fraction as arguments for surface extents >>> or transformations: >>> >>> TRMorph>>#drawOn: >>> .... >>> >>> cs pathTransform >>> translateBy: self extent / >>> 2; "<<----------" >>> scaleBy: trachelCanvas camera scale asFloat; >>> translateBy: trachelCanvas camera position negated. >>> trachelCanvas shapes do: [ :trachelShape | >>> trachelShape drawOn: cs. >>> ]. >>> >>> ... >>> >>> >>> >>> >>> >>> >>> >>> Then, we still have a couple of visualizations left to port: >>> PPParser>>visualizeStructureInGraphOn: >>> PPParser>>viewAllNamedParsersWithSelection:previewing:on: >>> >>> Any takers? >>> >>> Cheers, >>> Doru >>> >>> >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com> >>> >>> "Every thing has its own flow" >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On Nov 12, 2014, at 12:59 PM, Tudor Girba <tudor(a)tudorgirba.com&gt; wrote: I fixed the PetitParser visualizations. The PNG is almost working (the one pixel problem is still around). That means that we are closing the Moose release. Cheers, Doru On Mon, Nov 10, 2014 at 8:57 AM, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: Hello everyone, Do we have any progress on the visualizations? What about saving to PNG? Any taker? Cheers, Doru On Sat, Nov 8, 2014 at 12:20 PM, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: Thanks! Alexandre Le 08-11-2014 à 5:38, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> a écrit : > If you are wondering how to trigger the visualizations, you can trigger them on any parser instance. > > For example: > PPArithmeticParser new visualizeStructureInGraph > > Doru > > On Fri, Nov 7, 2014 at 9:04 PM, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: > Thank you! > > Doru > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow" > > On 07 Nov 2014, at 19:55, milton mamani <akevalion(a)gmail.com <mailto:akevalion@gmail.com>> wrote: > >> Hi Tudor, >> >> I will check the next items this weekend: >> >> PPParser>>visualizeStructureInGraphOn: >> PPParser>>viewAllNamedParsersWithSelection:previewing:on: >> >> Cheers, >> Milton >> >> >> 2014-11-02 3:52 GMT-03:00 Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>>: >> Le 02/11/2014 01:33, Nicolai Hess a écrit : >> 2014-11-01 22:06 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com> >> <mailto:tudor@tudorgirba.com <mailto:tudor@tudorgirba.com>>>: >> >> Hi, >> >> We have gone through most of the Roassal problems, but we still have >> a couple of issues left. >> >> First, we need to be able to export to PNG. Right now, the >> implementation exports only the visible part of the morph, but it >> should export the whole canvas. Ideally, we should use the Athens >> ability of exporting PNGs: >> https://code.google.com/p/moose-technology/issues/detail?id=1089 <https://code.google.com/p/moose-technology/issues/detail?id=1089> >> >> >> Is there any notion of "view (all shapes) extent"? I am afraid the >> extent is only defined by the actual Morph, therefore, we >> can only draw and export the visible part in the morph. >> >> view canvas camera encompassingRectangle. >> >> the answer is relative to the camera transform and does not include fixed shapes (menu buttons). >> >> Thierry >> >> >> Using Athens for exporting, we need a way to create an AthensSurface >> with the correct (enlarged) extent. The problem is, the extent is defined >> by TrachelShape but the TRMorph is the one holding the AthensSurface. >> >> Your proposed solution in >> https://code.google.com/p/moose-technology/issues/detail?id=1089#c4 <https://code.google.com/p/moose-technology/issues/detail?id=1089#c4> >> should work, although it does not go through athenssurface>>writeToPng: >> but instead it >> creates a form >> renders on an athens surface >> copies the rendering on to the imageform >> export the image form >> >> If your code creates a rendering error like NBFFICallout >> class>>#signalError, it is because >> the Athens-Api is picky about Fraction as arguments for surface extents >> or transformations: >> >> TRMorph>>#drawOn: >> .... >> >> cs pathTransform >> translateBy: self extent / >> 2; "<<----------" >> scaleBy: trachelCanvas camera scale asFloat; >> translateBy: trachelCanvas camera position negated. >> trachelCanvas shapes do: [ :trachelShape | >> trachelShape drawOn: cs. >> ]. >> >> ... >> >> >> >> >> >> >> >> Then, we still have a couple of visualizations left to port: >> PPParser>>visualizeStructureInGraphOn: >> PPParser>>viewAllNamedParsersWithSelection:previewing:on: >> >> Any takers? >> >> Cheers, >> Doru >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> <http://www.tudorgirba.com <http://www.tudorgirba.com/>> >> >> "Every thing has its own flow" >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> <mailto:Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> -- www.tudorgirba.com <http://www.tudorgirba.com/> "Every thing has its own flow" -- www.tudorgirba.com <http://www.tudorgirba.com/> "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev