July 2014 - Pharo-users - lists.pharo.org

I've raised a bug that the Pharo website has a missing video

by Tim Mackinnon

FYI - I've raised a bug that the pharo website doesn't have a video showing how to report bugs anymore. 13553 - Reporting issues video on Pharo website reports "Does not exist" Not sure if it's right to raise an issue - but thought it made sense (and given I can't watch the video... ;) Tim -- View this message in context: http://forum.world.st/I-ve-raised-a-bug-that-the-Pharo-website-has-a-missin… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 15, 2014

Re: [Pharo-users] Package Dependencies Analyzer

by Baptiste QuidÃ©

Stef, please would like to explain how the problem appeared when you loaded the tool via the metacello browser? Thanks! *Baptiste QUIDÃ* *Ãtudiant ingÃ©nieur* *Polytech LilleDÃ©partement Informatique et Statistique (+33)6 21 69 20 09 <%28%2B33%296%2021%2069%2020%2009>* 2014-07-14 15:23 GMT+02:00 stepharo <stepharo(a)free.fr>: > thanks baptiste > > I will try it on polymorph :) > > Stef > > > On 12/7/14 12:34, Baptiste QuidÃ© wrote: > > Hi Stef, > > I think it's not normal. I will fix it when I will be at home or work. Try > the gofer script and everything should be ok > Le 12 juil. 2014 12:26, "stepharo" <stepharo(a)free.fr> a Ã©crit : > >> Hi baptiste >> >> I loaded your tools via the metacello browser in Pharo40 but I do not get >> a menu to invoke it. >> Is it normal? >> >> Stef >> >> On 11/7/14 18:42, Baptiste QuidÃ© wrote: >> >>> Hello Pharo users, >>> >>> let me introduce a new tool that I developed in the RMOD team: package >>> dependencies analyzer. >>> >>> This project provides a tool able to analyze Smalltalk project packages >>> and detect dependencies to other packages. It enables automatic dependency >>> analysis to detect wrong project description (declared dependencies). It's >>> very easy to use and i hope it will be helpful during your development time. >>> >>> As soon as possible, a next version will enable to detect cycle >>> dependencies among packages. >>> >>> The description of the project is on this web-page : >>> http://www.baptistequide.fr/packagedependencies.php >>> It's already available on the Configuration Browser on Pharo. >>> >>> Your feedback and suggestions are mostly welcome to improve this >>> project. I invite you to test the tool. >>> >>> Cheers, >>> >>> Baptiste >>> >>> >>> >> >> >

July 15, 2014

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Tim Mackinnon

Thanks for the tip Ben - yes Cases xxx looks like what I wanted (and I just tried it). Its a bit difficult to know this is available so I wanted to add it to the Pharo Fogbugz wiki but I can't edit that (it also looks like there are other variants too: http://help.fogcreek.com/7772/link-fogbugz-cases-to-changesetscommits-in-ki…) Tim -- View this message in context: http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 15, 2014

Refactoring project moving forward :)

by Mark Rizun

Hi, everyone! The project is developing: small changes, enhancements and fixes are made. You can read about it on my blog <http://myfuncoding.blogspot.com> . Everything is (or will be) included in recent versions of Pharo40. Please be free to introduce your thoughts and ideas about what should be done, or maybe what shouldn't. So, feedback is welcome. Best, Mark -- View this message in context: http://forum.world.st/Refactoring-project-moving-forward-tp4767798.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 15, 2014

Re: [Pharo-users] Storing block closure code

by Norbert Hartl

Ok, I think that's what you get if you forget a tiny little detail and that is enough so everything is discussed just not what you wanted to know :) My concern is not security. I know pretty well it would be a stupid to let anyone inject smalltalk code via http interface. If I were about security I would do the same as Esteban: Defining a allowed set of operations and make classes for them. My point is that it is purely internal what I like to use. And I think I would like it not to be restricted in the kind of queries I do. Hence the idea of using smalltalk. I'm only interested in the drawbacks that blocks might have. As they are created from string to only thing they might depend on context-wise would be self (if I decide to use a helper). My question was if there is anything besides that could make the use of blocks and serializing/materializing troublesome. thanks, norbert Am 14.07.2014 um 21:05 schrieb Dale Henrichs <dale.henrichs(a)gemtalksystems.com>: > Ben, > > It's not just Global references that you have to worry about ... `self environment` is an easy way to get direct access to `Smalltalk` ... you can use `self superclass superclass subclasses...` to navigate to just about any class in the system ...and this is only with a couple minutes of thought:) .... to be truly safe you have to work a bit harder and construct a sandbox that is a subset of the standard environment ... > > Dale > > > On Mon, Jul 14, 2014 at 11:05 AM, Ben Coman <btc(a)openinworld.com> wrote: > Esteban A. Maringolo wrote: >> >> Are you going to be the end user of this? >> >> I wouldn't let users compile whatever Smalltalk expressions they want. >> You can't scope the globals that can be accessed by the compiler. >> > > CompilationContext had instance variable /environment/ that contains a SystemDictionary(lots of globals). I wonder how effective it would be, or how horribly it would break things, to change that for a limited list. > cheers -ben > > >> What I would do is model a hierarchy of "Condition" objects used by >> "Filter" objects, which are composable, and know how to translate >> themselves to SQL, Mongo condition, or even Smalltalk expressions to >> apply the conditions to a collection of objects. >> >> The other way is to have a DSL, but that's a longer road if what you >> plan is simply to apply filters. >> >> We've done both in my previous job and worked perfectly. >> >> >> Regards! >> >> >> >> Esteban A. Maringolo >> >> >> 2014-07-14 12:19 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: >> >>> I was looking for a solution where I can have a textual grammar for a DSL in order to specify filters on objects. I didn't really search the net because I know a cute little DSL for that already. It is called smalltalk, you might have heard of it. >>> >>> So what I do is putting the filter spec into the image via an http interface, materialize the filter in image and store it in a database to have them survive image restart. A filter spec could look like this >>> >>> [ :value | ( self sectionLabelOf: value ) = 'device' ] >>> >>> I want to know if there is any trouble to expect if I'm using plain block syntax for that task. As the blocks are injected using an http interface there is no environment/context problem. I would have some helper class as a facade to ease the filtering let's call it >>> >>> FilterHelper (would have a class side method #sectionLabelOf:) >>> >>> So getting the block code via HTTP I could do >>> >>> block := Smalltalk compiler >>> evaluate: request contents >>> for: FilterHelper >>> logged: false >>> >>> And I would serialize it into a database as a string again doing >>> >>> self store: block sourceNode formattedCode >>> >>> Are there any possible drawbacks using it this way? >>> >>> thanks, >>> >>> Norbert >>> >>> >>> >> > >

July 15, 2014

Busy week :)

by stepharo

http://pharoweekly.wordpress.com/2014/07/15/another-busy-week-in-pharoland/ Such list is always providing a warm and positive feeling. Thanks you for your contributions. 40084 13548 Move LabelMorph, FuzzyLabelMorph and MultistateLabelMorph to the Package of StringMorph https://pharo.fogbugz.com/f/cases/13548 13531 RBMissingSubclassResponsibilityRule missing test cases https://pharo.fogbugz.com/f/cases/13531 13549 Move incrementalSliderMorph to the package of SliderMorph https://pharo.fogbugz.com/f/cases/13549 13547 Move LabelClicked close to its only user: CheckBoxMorph https://pharo.fogbugz.com/f/cases/13547 40083 13527 Moving class with overridden method and green override icon gives MNU âmethodClassâ is nil when clicked https://pharo.fogbugz.com/f/cases/13527 13542 Better #printOn: method for RPackageTag https://pharo.fogbugz.com/f/cases/13542 13543 use UserManager default instead of Smalltalk tools userManager https://pharo.fogbugz.com/f/cases/13543 40082 13546 Move EdgeGripMorph and WindowEdgeGripMorph to Morphic-Widgets-Window https://pharo.fogbugz.com/f/cases/13546 13544 Move ThreadSafeTranscriptPluggableTextMorph close to Transcript https://pharo.fogbugz.com/f/cases/13544 13545 Move extension methods from Polymorph-Tools-Diff into MCMergeBrowser https://pharo.fogbugz.com/f/cases/13545 40081 13537 Merging some polymorph and spec to PluggableListMorph https://pharo.fogbugz.com/f/cases/13537 13495 deprecate #ifLocked: in PluggableTextMoprh https://pharo.fogbugz.com/f/cases/13495/ 13522 Add Back SimpleSwicthMorph https://pharo.fogbugz.com/f/cases/13522 40080 13530 Add api to remove selection of text model https://pharo.fogbugz.com/f/cases/13530 13533 Smart Suggestions for more tools https://pharo.fogbugz.com/f/cases/13533 13534 Remove some unused âto be removed as soon as possibleâ methods from Ring https://pharo.fogbugz.com/f/cases/13534 40079 13529 Move PluggableSlider and subclasses to the same package as Slider https://pharo.fogbugz.com/f/cases/13529 13375 Should create a package Morphic-Widgest-ColorSelector https://pharo.fogbugz.com/f/cases/13375 40078 13502 basic UserManager cleanup https://pharo.fogbugz.com/f/cases/13502 13520 remove all but one direct reference to Compiler https://pharo.fogbugz.com/f/cases/13520 40077 13508 CachingMorph is unused https://pharo.fogbugz.com/f/cases/13508 13451 For Pharo4: 13422 Image crashes because an open Nautilus browser hangs onto many objects https://pharo.fogbugz.com/f/cases/13451 40076 13501 EyeInspector has a slow refresh time (part 1) https://pharo.fogbugz.com/f/cases/13501 13510 MatrixTransformMorph is not used https://pharo.fogbugz.com/f/cases/13510 13514 delete empty packages KeyChain and Settings-Compiler https://pharo.fogbugz.com/f/cases/13514 40075 13509 PSMCSystemSettings â> move to class https://pharo.fogbugz.com/f/cases/13509 13511 Move CompilerSettings to OpalCompiler package https://pharo.fogbugz.com/f/cases/13511 13507 ExtendedTabPanelBorder is dead code https://pharo.fogbugz.com/f/cases/13507 13512 Move BalloonCanvas to Balllon Package https://pharo.fogbugz.com/f/cases/13512 40074 13506 Move some Settings-Polymorph to the class https://pharo.fogbugz.com/f/cases/13506 13505 Small Morph clean: SimpleSwitch is not used, move Lazy*List to the sole user: PluggableList https://pharo.fogbugz.com/f/cases/13505 13504 MorphListItemWrapper is dead code https://pharo.fogbugz.com/f/cases/13504 40072 13494 Merge Settings-Display and FreeType into the packages https://pharo.fogbugz.com/f/cases/13494 13496 failing test: testClassRespectsPolymorphismWithTrait https://pharo.fogbugz.com/f/cases/13496 13487 Bytecode set settings https://pharo.fogbugz.com/f/cases/13487 40071 13488 Small recategorization of Classes in Kernel https://pharo.fogbugz.com/f/cases/13488 13485 Move RPackageOrganizer>>#renamePackage:in: to Deprecated40 https://pharo.fogbugz.com/f/cases/13485 13477 Small critique cleanup RPackage https://pharo.fogbugz.com/f/cases/13477 40070 Merging Opal branch with the trunk. 40069 13483 Preference to always show experimental slot class template https://pharo.fogbugz.com/f/cases/13483 12373 Class>>name: should be deprecated https://pharo.fogbugz.com/f/cases/12373 40068 13471 Refactoring in contextual menu in Message Browser https://pharo.fogbugz.com/f/cases/13471 13458 Rendering text with Athens and StrikeFonts https://pharo.fogbugz.com/f/cases/13458 13478 The History Package has two classes that are support for tools â> move to Tools-Base https://pharo.fogbugz.com/f/cases/13478 40067 13482 (Untitled)fix failing opal tests https://pharo.fogbugz.com/f/cases/13482 13338 FileDirectoryWrapper should be moved to the package containing FileList https://pharo.fogbugz.com/f/cases/13338 13476 Move TSortable to Collections-Abstract https://pharo.fogbugz.com/f/cases/13476 40066 12786 Review SmalltalkImageTest>>testImageName https://pharo.fogbugz.com/f/cases/12786 13475 ClassOrganizer: commentRemoteStr â> commentRemoteStrig https://pharo.fogbugz.com/f/cases/13475 12767 FontTest has extension from Font package https://pharo.fogbugz.com/f/cases/12767 5685 offImage is private but used and it is exactly the same as offIcon https://pharo.fogbugz.com/f/cases/5685 13481 Unload tests for the old Compiler https://pharo.fogbugz.com/f/cases/13481 40065 13357 ScriptLoader should automatically reassign repository https://pharo.fogbugz.com/f/cases/13357 13370 Polymorph-Tools-Diff extensions should be moved to their class. https://pharo.fogbugz.com/f/cases/13370 13474 Small cleanup for RecentMessageList https://pharo.fogbugz.com/f/cases/13474

July 15, 2014

Re: [Pharo-users] Roassal2 Composite Shape

by Peter UhnÃ¡k

Well in the long run I will probably need much more shapes that are currently present so I will probably end up making both TRShape and RTShape anyway. As far as contribution goes, I'd be happy to contribute but I'm still quite new to both Pharo and Smalltalk so I'm quite skeptical about the code quality. I've actually already made both shapes for rounded box but it will need some testing first; so I'll keep you posted. Peter On Mon, Jul 14, 2014 at 10:47 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Indeed, Roassal does not have a rectangle with rounded corner. Having it > in Roassal means you need a new TRShape and a new RTShape. > > I could easily do the RTShape. But we need the TRShape first. Do you feel > like doing it? This will be a valuable addition to Roassal. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Jul 13, 2014, at 9:57 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Thank you, the example now works. However as I've mentioned in > previous post I'm not sure about the rest of the shapes posted in the > attachment. E.g. I haven't seen any notion of "box with rounded > corners". I could compose it from four RTArc nad four RTLine but it > seems to me overly complex compared to creating new Trachert/Roassal > classes. The same would go for the other shapes. What are your > thoughts/recommendations on that? > > Peter > > On Sun, Jul 13, 2014 at 3:25 PM, Alexandre Bergel > <alexandre.bergel(a)me.com> wrote: > > Sorry, the version was not properly saved in SmalltalkHub. If you update > Roassal2 and Trachel, you should be able to execute the code snippet Iâve > sent you. Maybe you want to add âv openâ at the end. If you are using > GTInspector, this is not necessary. > > As far as I understand your description of the problem, you do not need to > create your own shape. > > Let me know how it goes. > > Cheers, > Alexandre > > > On Jul 13, 2014, at 10:38 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Thank you both for suggestions. > > According to Monticello I have latest Roassal2 and yet I don't see > RTMultiCompositeShape, but I would assume it should be what I was looking > for originally. > > In the meantime I chose to do it manually - creating a custom shape in > both Roassal and Trachert: > I've done it in a single path because it seems that having multiple > separate paths just creates more trouble. > ======== > computePath > canvas ifNil: [ ^ self ]. > path := self athensCanvas > createPath: [ :builder | > builder absolute. > self ccwCirclePath: builder radius: 0.5. "building > circular path with specified radius" > self cwCirclePath: builder radius: 0.48. > self ccwCirclePath: builder radius: 0.4 ] > ======== > > But even if I could manage to do this with MultiCompositeShape I'm not > sure about the rest of the shapes (see attachment). > > Peter > > > > > On Sun, Jul 13, 2014 at 1:18 AM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > Hi Peter, > > I am not sure what you try to do. Having two ellipses with the same > center? But different radius? > > Something like that maybe: > -=-=-=-=-=-=-=-=-= > | v | > v := RTView new. > v @ RTDraggableView. > > shape := RTMultiCompositeShape new. > shape add: (RTEllipse new color: (Color yellow alpha: 0.3); size: [:c | c > numberOfMethods sqrt * 10 ]). > shape add: (RTEllipse new color: (Color green alpha: 0.3); size: [:c | c > numberOfLinesOfCode sqrt * 10 ]). > > v addAll: (shape elementsOn: RTShape withAllSubclasses). > RTFlowLayout on: v elements. > > v > -=-=-=-=-=-=-=-=-= > > <Screen Shot 2014-07-13 at 1.18.36 AM.png> > > Alexandre > > > On Jul 11, 2014, at 11:05 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi > > I'm trying to draw an ellipse inside another ellipse but to no avail. I've > tried using RTCompositeShape but that just expands the size of the smaller > shape. Is there something else I'm missing (like fixing dimensions so they > won't get updated) or should I subclass RTAbstractCompositeShape and try to > make something on my own? > > Thanks, > Peter > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > <shapes.png> > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

July 15, 2014

Re: [Pharo-users] Roassal2 Composite Shape

by Alexandre Bergel

Indeed, Roassal does not have a rectangle with rounded corner. Having it in Roassal means you need a new TRShape and a new RTShape. I could easily do the RTShape. But we need the TRShape first. Do you feel like doing it? This will be a valuable addition to Roassal. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jul 13, 2014, at 9:57 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Thank you, the example now works. However as I've mentioned in > previous post I'm not sure about the rest of the shapes posted in the > attachment. E.g. I haven't seen any notion of "box with rounded > corners". I could compose it from four RTArc nad four RTLine but it > seems to me overly complex compared to creating new Trachert/Roassal > classes. The same would go for the other shapes. What are your > thoughts/recommendations on that? > > Peter > > On Sun, Jul 13, 2014 at 3:25 PM, Alexandre Bergel > <alexandre.bergel(a)me.com> wrote: >> Sorry, the version was not properly saved in SmalltalkHub. If you update Roassal2 and Trachel, you should be able to execute the code snippet Iâve sent you. Maybe you want to add âv openâ at the end. If you are using GTInspector, this is not necessary. >> >> As far as I understand your description of the problem, you do not need to create your own shape. >> >> Let me know how it goes. >> >> Cheers, >> Alexandre >> >> >> On Jul 13, 2014, at 10:38 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >>> Thank you both for suggestions. >>> >>> According to Monticello I have latest Roassal2 and yet I don't see RTMultiCompositeShape, but I would assume it should be what I was looking for originally. >>> >>> In the meantime I chose to do it manually - creating a custom shape in both Roassal and Trachert: >>> I've done it in a single path because it seems that having multiple separate paths just creates more trouble. >>> ======== >>> computePath >>> canvas ifNil: [ ^ self ]. >>> path := self athensCanvas >>> createPath: [ :builder | >>> builder absolute. >>> self ccwCirclePath: builder radius: 0.5. "building circular path with specified radius" >>> self cwCirclePath: builder radius: 0.48. >>> self ccwCirclePath: builder radius: 0.4 ] >>> ======== >>> >>> But even if I could manage to do this with MultiCompositeShape I'm not sure about the rest of the shapes (see attachment). >>> >>> Peter >>> >>> >>> >>> >>> On Sun, Jul 13, 2014 at 1:18 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Hi Peter, >>> >>> I am not sure what you try to do. Having two ellipses with the same center? But different radius? >>> >>> Something like that maybe: >>> -=-=-=-=-=-=-=-=-= >>> | v | >>> v := RTView new. >>> v @ RTDraggableView. >>> >>> shape := RTMultiCompositeShape new. >>> shape add: (RTEllipse new color: (Color yellow alpha: 0.3); size: [:c | c numberOfMethods sqrt * 10 ]). >>> shape add: (RTEllipse new color: (Color green alpha: 0.3); size: [:c | c numberOfLinesOfCode sqrt * 10 ]). >>> >>> v addAll: (shape elementsOn: RTShape withAllSubclasses). >>> RTFlowLayout on: v elements. >>> >>> v >>> -=-=-=-=-=-=-=-=-= >>> >>> <Screen Shot 2014-07-13 at 1.18.36 AM.png> >>> >>> Alexandre >>> >>> >>> On Jul 11, 2014, at 11:05 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>>> Hi >>>> >>>> I'm trying to draw an ellipse inside another ellipse but to no avail. I've tried using RTCompositeShape but that just expands the size of the smaller shape. Is there something else I'm missing (like fixing dimensions so they won't get updated) or should I subclass RTAbstractCompositeShape and try to make something on my own? >>>> >>>> Thanks, >>>> Peter >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> <shapes.png> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >

July 14, 2014

Re: [Pharo-users] Storing block closure code

by Dale Henrichs

Ben, It's not just Global references that you have to worry about ... `self environment` is an easy way to get direct access to `Smalltalk` ... you can use `self superclass superclass subclasses...` to navigate to just about any class in the system ...and this is only with a couple minutes of thought:) .... to be truly safe you have to work a bit harder and construct a sandbox that is a subset of the standard environment ... Dale On Mon, Jul 14, 2014 at 11:05 AM, Ben Coman <btc(a)openinworld.com> wrote: > Esteban A. Maringolo wrote: > > Are you going to be the end user of this? > > I wouldn't let users compile whatever Smalltalk expressions they want. > You can't scope the globals that can be accessed by the compiler. > > > > CompilationContext had instance variable /environment/ that contains a > SystemDictionary(lots of globals). I wonder how effective it would be, or > how horribly it would break things, to change that for a limited list. > cheers -ben > > > What I would do is model a hierarchy of "Condition" objects used by > "Filter" objects, which are composable, and know how to translate > themselves to SQL, Mongo condition, or even Smalltalk expressions to > apply the conditions to a collection of objects. > > The other way is to have a DSL, but that's a longer road if what you > plan is simply to apply filters. > > We've done both in my previous job and worked perfectly. > > > Regards! > > > > Esteban A. Maringolo > > > 2014-07-14 12:19 GMT-03:00 Norbert Hartl <norbert(a)hartl.name> <norbert(a)hartl.name>: > > > I was looking for a solution where I can have a textual grammar for a DSL in order to specify filters on objects. I didn't really search the net because I know a cute little DSL for that already. It is called smalltalk, you might have heard of it. > > So what I do is putting the filter spec into the image via an http interface, materialize the filter in image and store it in a database to have them survive image restart. A filter spec could look like this > > [ :value | ( self sectionLabelOf: value ) = 'device' ] > > I want to know if there is any trouble to expect if I'm using plain block syntax for that task. As the blocks are injected using an http interface there is no environment/context problem. I would have some helper class as a facade to ease the filtering let's call it > > FilterHelper (would have a class side method #sectionLabelOf:) > > So getting the block code via HTTP I could do > > block := Smalltalk compiler > evaluate: request contents > for: FilterHelper > logged: false > > And I would serialize it into a database as a string again doing > > self store: block sourceNode formattedCode > > Are there any possible drawbacks using it this way? > > thanks, > > Norbert > > > > > > >

July 14, 2014

Re: [Pharo-users] Storing block closure code

by Ben Coman

July 14, 2014