- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Evaluate math expression

by Hilaire Fernandes

How will you do it? I have no experience about writting grammar. Thanks Hilaire Le 13/01/2013 22:48, H. Hirzel a Ã©crit : > PetitParser > > --Hannes > > On 1/13/13, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: >> Hello, >> >> What tools will you use to evaluate math expression writen in algebraic >> form as 2*x*cos(5*x+10). >> >> Thanks >> >> >> Hilaire >> >> >> > >

Jan. 14, 2013

Re: [Pharo-project] Spreadsheet widget

by Sabine KnÃ¶fel

Me too;-) I use jqGrid instead from JQueryWidgetBox See examples: http://www.trirand.com/blog/jqgrid/jqgrid.html Sabine On Mon, Jan 14, 2013 at 10:09 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > If we have it, I would be highly interested :) > > Doru > > > On Mon, Jan 14, 2013 at 10:04 AM, Hilaire Fernandes < > hilaire.fernandes(a)edu.ge.ch> wrote: > >> Hello, >> >> Do we have such widget? >> >> Thanks >> >> Hilaire >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Jan. 14, 2013

Re: [Pharo-project] Spreadsheet widget

by Tudor Girba

If we have it, I would be highly interested :) Doru On Mon, Jan 14, 2013 at 10:04 AM, Hilaire Fernandes < hilaire.fernandes(a)edu.ge.ch> wrote: > Hello, > > Do we have such widget? > > Thanks > > Hilaire > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 14, 2013

[Pharo-project] Spreadsheet widget

by Hilaire Fernandes

Hello, Do we have such widget? Thanks Hilaire

Jan. 14, 2013

Re: [Pharo-project] Class initialisation after loading

by Norbert Hartl

Am 14.01.2013 um 09:24 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 14 Jan 2013, at 09:09, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Am 14.01.2013 um 07:54 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >>> Morning, Norbert, >>> >>> On 14 Jan 2013, at 07:44, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> As for every other objects initialize is called when the object is created. Upgrading code might change the shape of the object but then there is no initialize call. Do you want to have initialize called every tiny code change? >>>> Using *cello you can use postLoadDoits to tweak stuff. >>> >>> You mean that, in your opinion, making sure that the #initialize is called in every scenario (new/existing class) can only be done with an explicit action ? >> >> I think that the primary purpose is to initialize newly created space. In case of shape change this doesn't happen. So taking the example you initialize e.g. an instvar with a collection. Do you want to reinitialize it even if you corrected a typo in the comment of a method? >> If I wanted to have control over those things I would on class initialization register a class of mine to the local change notification system in the image. But this isn't easy to do in a cross platform manner. Maybe there are better ways. I'm sure someone will speak up then. > > Let's make it more concrete. Zinc-Resource-Meta-Core is a package that among other thins contains ZnMimeType. ZnMimeType class>>initialize sets up some constants (lists of known mime types, file extension to mime type mappings, you get the idea). When I add new constants in a new source version, I want them to be added when doing an automated CI build, obviously. Right now, this does *not* happen, probably because the class and #initialize method already exist in the image where it is being load in. I understand. The problem is introduced by having a cache of those mime types. That is often a problem because the cache is designed as infinite valid but there is a use case that needs a little less infinite :) I think it depends how often that "adding" takes place. And it seems to me it does not occur very often. Apart from that cache invalidation is one of the more unpleasant things we face. If you want your cache to update you need to check something. But that is what you want to avoid for performance reasons. So I would see a postLoadIt for these rare jobs is a good match. Norbert > Indeed, you would not always want costly initializations to run, but there should at least be a hook to do it, no ? > >>>> Am 14.01.2013 um 07:20 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>>> Hi, >>>>> >>>>> For a long time I have been having troubles with #initialize (not) being sent to classes that just got loaded. >>>>> >>>>> Apparently #initialize is only sent to *newly* loaded classes that did not exist before ? >>>>> >>>>> It does not get sent to existing classes being reloaded/overwritten ? >>>>> >>>>> Does the fact that the #initialize class method itself gets overwritten (actually changes) have anything to do with it ? >>>>> >>>>> What would be the best practice here ? The most portable one ? >>>>> >>>>> I want to be able to make sure #initialize is sent when I want it. >>>>> >>>>> Thx, >>>>> >>>>> Sven >>>>> >>>>> PS: I am looking for a solution that would work for Monticello package loading, via Gofer or Metacello as well as regular #fileIn. >>>>> >>>>> -- >>>>> Sven Van Caekenberghe >>>>> http://stfx.eu >>>>> Smalltalk is the Red Pill >>> >>> >> > >

Jan. 14, 2013

Re: [Pharo-project] SmalltalkHub upgrade

by Nicolas Petton

Hi! Yep, that's a bug ;) Private projects are shown in the explore page. There are a few bugs left, I'll fix them ASAP. Nico Geert Claes <geert.wl.claes(a)gmail.com> writes: > The updated stHub looks good! One thing I noticed is that I get to see the > new 404-lego-head page quite a lot? In the "Recently created projects" the > following projects are not found: Prototype, Odyssey and MukadePM. Maybe > it's because these projects are not public? Doing a search for something > that doesn't exist also gives the "page not found" page. While browsing > around I noticed too that there are projects without "contributors"? > > Anyhow, just fyi because I know its still a wip and its starting to look > pretty nice :) > > > > -- > View this message in context: http://forum.world.st/SmalltalkHub-upgrade-tp4662977p4663245.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Nicolas Petton http://nicolas-petton.fr

Jan. 14, 2013

[Pharo-project] [update 2.0] #20469

by Marcus Denker

20469 ----- Issue 7224: Failing test related to RB http://code.google.com/p/pharo/issues/detail?id=7224 Issue 6957: ConfiugrationCommandLineHandler tries to open file on --help in non-headless mode http://code.google.com/p/pharo/issues/detail?id=6957 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-CommandLine-MarcusDenker.69.diff http://ss3.gemstone.com/ss/Pharo20/Refactoring-Tests-Core-MarcusDenker.59.d… http://ss3.gemstone.com/ss/Pharo20/Refactoring-Core-MarcusDenker.169.diff http://ss3.gemstone.com/ss/Pharo20/NativeBoost-Core-MarcusDenker.98.diff http://ss3.gemstone.com/ss/Pharo20/ConfigurationCommandLineHandler-Core-Mar…

Jan. 14, 2013

Re: [Pharo-project] Class initialisation after loading

by Sven Van Caekenberghe

On 14 Jan 2013, at 09:09, Norbert Hartl <norbert(a)hartl.name> wrote: > Am 14.01.2013 um 07:54 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> Morning, Norbert, >> >> On 14 Jan 2013, at 07:44, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> As for every other objects initialize is called when the object is created. Upgrading code might change the shape of the object but then there is no initialize call. Do you want to have initialize called every tiny code change? >>> Using *cello you can use postLoadDoits to tweak stuff. >> >> You mean that, in your opinion, making sure that the #initialize is called in every scenario (new/existing class) can only be done with an explicit action ? > > I think that the primary purpose is to initialize newly created space. In case of shape change this doesn't happen. So taking the example you initialize e.g. an instvar with a collection. Do you want to reinitialize it even if you corrected a typo in the comment of a method? > If I wanted to have control over those things I would on class initialization register a class of mine to the local change notification system in the image. But this isn't easy to do in a cross platform manner. Maybe there are better ways. I'm sure someone will speak up then. Let's make it more concrete. Zinc-Resource-Meta-Core is a package that among other thins contains ZnMimeType. ZnMimeType class>>initialize sets up some constants (lists of known mime types, file extension to mime type mappings, you get the idea). When I add new constants in a new source version, I want them to be added when doing an automated CI build, obviously. Right now, this does *not* happen, probably because the class and #initialize method already exist in the image where it is being load in. Indeed, you would not always want costly initializations to run, but there should at least be a hook to do it, no ? >>> Am 14.01.2013 um 07:20 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>>> Hi, >>>> >>>> For a long time I have been having troubles with #initialize (not) being sent to classes that just got loaded. >>>> >>>> Apparently #initialize is only sent to *newly* loaded classes that did not exist before ? >>>> >>>> It does not get sent to existing classes being reloaded/overwritten ? >>>> >>>> Does the fact that the #initialize class method itself gets overwritten (actually changes) have anything to do with it ? >>>> >>>> What would be the best practice here ? The most portable one ? >>>> >>>> I want to be able to make sure #initialize is sent when I want it. >>>> >>>> Thx, >>>> >>>> Sven >>>> >>>> PS: I am looking for a solution that would work for Monticello package loading, via Gofer or Metacello as well as regular #fileIn. >>>> >>>> -- >>>> Sven Van Caekenberghe >>>> http://stfx.eu >>>> Smalltalk is the Red Pill >> >> >

Jan. 14, 2013

Re: [Pharo-project] Class initialisation after loading

by Norbert Hartl

Am 14.01.2013 um 07:54 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Morning, Norbert, > > On 14 Jan 2013, at 07:44, Norbert Hartl <norbert(a)hartl.name> wrote: > >> As for every other objects initialize is called when the object is created. Upgrading code might change the shape of the object but then there is no initialize call. Do you want to have initialize called every tiny code change? >> Using *cello you can use postLoadDoits to tweak stuff. > > You mean that, in your opinion, making sure that the #initialize is called in every scenario (new/existing class) can only be done with an explicit action ? I think that the primary purpose is to initialize newly created space. In case of shape change this doesn't happen. So taking the example you initialize e.g. an instvar with a collection. Do you want to reinitialize it even if you corrected a typo in the comment of a method? If I wanted to have control over those things I would on class initialization register a class of mine to the local change notification system in the image. But this isn't easy to do in a cross platform manner. Maybe there are better ways. I'm sure someone will speak up then. Norbert > Sven > >> Norbert >> >> Am 14.01.2013 um 07:20 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >>> Hi, >>> >>> For a long time I have been having troubles with #initialize (not) being sent to classes that just got loaded. >>> >>> Apparently #initialize is only sent to *newly* loaded classes that did not exist before ? >>> >>> It does not get sent to existing classes being reloaded/overwritten ? >>> >>> Does the fact that the #initialize class method itself gets overwritten (actually changes) have anything to do with it ? >>> >>> What would be the best practice here ? The most portable one ? >>> >>> I want to be able to make sure #initialize is sent when I want it. >>> >>> Thx, >>> >>> Sven >>> >>> PS: I am looking for a solution that would work for Monticello package loading, via Gofer or Metacello as well as regular #fileIn. >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill > >

Jan. 14, 2013

Re: [Pharo-project] SmalltalkHub upgrade

by Geert Claes

The updated stHub looks good! One thing I noticed is that I get to see the new 404-lego-head page quite a lot? In the "Recently created projects" the following projects are not found: Prototype, Odyssey and MukadePM. Maybe it's because these projects are not public? Doing a search for something that doesn't exist also gives the "page not found" page. While browsing around I noticed too that there are projects without "contributors"? Anyhow, just fyi because I know its still a wip and its starting to look pretty nice :) -- View this message in context: http://forum.world.st/SmalltalkHub-upgrade-tp4662977p4663245.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 14, 2013