- Pharo-dev - lists.pharo.org

[Pharo-project] Smalltalkhub error messages

by Camillo Bruni

I am having big issues with smalltalkhub. It seems like all the Pinocchio stuff is broken again. I cannot load P4-Kernel-CamilloBruni.10.mcz from my repository http://smalltalkhub.com/#!/~dh83 Furthermore while Clement is loading it, Smalltalkhub blocks completely!

Jan. 14, 2013

Re: [Pharo-project] Evaluate math expression

by Esteban Lorenzano

yes... but of course, not complete (no need of UI or other parsers besides the one you wrote). Also, as it's name marks, it is "petit" :) Esteban On Jan 14, 2013, at 11:12 AM, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > Thanks Hannes for the pointers. I will then take the time to learn. > > Dumb question: when the grammar is written, does PetitParser still need > to be shipped with the final application? > > Hilaire > > > Le 14/01/2013 11:08, H. Hirzel a Ã©crit : >> Hilarie, >> >> It is less difficult than it seems. >> > >

Jan. 14, 2013

Re: [Pharo-project] Evaluate math expression

by Hilaire Fernandes

Thanks Hannes for the pointers. I will then take the time to learn. Dumb question: when the grammar is written, does PetitParser still need to be shipped with the final application? Hilaire Le 14/01/2013 11:08, H. Hirzel a Ã©crit : > Hilarie, > > It is less difficult than it seems. >

Jan. 14, 2013

Re: [Pharo-project] Evaluate math expression

by H. Hirzel

Hilarie, It is less difficult than it seems. Lukas has a tutorial how to develop a grammar in a workspace. You can do it step by step and so have immediate feedback how it goes. Actually a very rewarding exercise. Read his tutorial first [2] and [3]. It is about what you are looking for, a math expression evaluator, just a very simple one. You would have to add the function calls. The thesis [4] has a chapter on PetitParser which is introductory level. The same applies for [5]. My estimate is that for your problem it might take you 2...7 hours to create a math expression evaluator depending on what your requirements are. --Hannes References: [1] http://scg.unibe.ch/research/helvetia/petitparser [2] http://www.lukas-renggli.ch/blog/petitparser-1 [3] http://www.lukas-renggli.ch/blog/petitparser-2 [4] Lukas Renggli. Dynamic Language Embedding With Homogeneous Tool Support. PhD thesis, University of Bern, October 2010. http://scg.unibe.ch/archive/phd/renggli-phd.pdf [5] http://www.themoosebook.org/book/internals/petit-parser On 1/14/13, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > 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

sorry! (I develop for web) On Mon, Jan 14, 2013 at 10:59 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > morphic

Jan. 14, 2013

Re: [Pharo-project] Class initialisation after loading

by Sven Van Caekenberghe

On 14 Jan 2013, at 09:38, Norbert Hartl <norbert(a)hartl.name> wrote: > 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. Thanks for the discussion, Norbert, I still feel that in most cases, when loading code, or when building new images, I want the class initializers of loaded classes to run to make sure everything is in a known, up to date state. Loading code or building images does not happen a lot and it feels strange to load something but not have it initialized. We'll see if somebody else has anything to say about this. >> 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] Spreadsheet widget

by Esteban Lorenzano

but jqGrid is for web/seaside... I think Hilaire is talking about morphic On Jan 14, 2013, at 10:37 AM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Currently, for my requirements the jqGrid is sufficient. > I do not want to invest time in a spreadsheet widget - is think this is much work. > Sabine > > On Mon, Jan 14, 2013 at 10:29 AM, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > Something worth collaborating on? > > Hilaire > > Le 14/01/2013 10:09, Tudor Girba a Ã©crit : > > 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 > > <mailto:hilaire.fernandes@edu.ge.ch>> wrote: > > > > Hello, > > > > Do we have such widget? > > > > Thanks > > > > Hilaire > > > > > > > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Every thing has its own flow" > > > >

Jan. 14, 2013

Re: [Pharo-project] Spreadsheet widget

by Sabine KnÃ¶fel

Currently, for my requirements the jqGrid is sufficient. I do not want to invest time in a spreadsheet widget - is think this is much work. Sabine On Mon, Jan 14, 2013 at 10:29 AM, Hilaire Fernandes < hilaire.fernandes(a)edu.ge.ch> wrote: > Something worth collaborating on? > > Hilaire > > Le 14/01/2013 10:09, Tudor Girba a Ã©crit : > > 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 > > <mailto:hilaire.fernandes@edu.ge.ch>> wrote: > > > > Hello, > > > > Do we have such widget? > > > > Thanks > > > > Hilaire > > > > > > > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Every thing has its own flow" > > > >

Jan. 14, 2013

Re: [Pharo-project] Spreadsheet widget

by Hilaire Fernandes

Something worth collaborating on? Hilaire Le 14/01/2013 10:09, Tudor Girba a Ã©crit : > 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 > <mailto:hilaire.fernandes@edu.ge.ch>> wrote: > > Hello, > > Do we have such widget? > > Thanks > > Hilaire > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Jan. 14, 2013

Re: [Pharo-project] Spreadsheet widget

by Hilaire Fernandes

Something worth collaborating? Hilaire Le 14/01/2013 10:09, Tudor Girba a Ã©crit : > 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 > <mailto:hilaire.fernandes@edu.ge.ch>> wrote: > > Hello, > > Do we have such widget? > > Thanks > > Hilaire > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Jan. 14, 2013