- Pharo-dev - lists.pharo.org

untypeable key combination

by Nicolai Hess

We have a class KMUntypeableSingleKeyCombination this is used for key kombinations with tab arrow backspace .... This is useful for printing key kombinations like Ctrl+TAB "space" does not use the KMUntypeableSingleKeyCombination class, therefore a short cut like Character space shift asKeyCombination looks like " Shift + " shouldn't space use this class? And I find the name a little bit misleading, what is a untypeable key? The key is typeable, otherwise we couldn't use it. Renaming the class to KMUnprintableSingleKeyCombination isn't better, because we can print this keycombination. nicolai

Dec. 7, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40403 Home: https://github.com/pharo-project/pharo-core

Dec. 7, 2014

[pharo-project/pharo-core] 172f0e: 40403

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 172f0e542d76844088db11e23938b50b3572ccd5 https://github.com/pharo-project/pharo-core/commit/172f0e542d76844088db11e2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-07 (Sun, 07 Dec 2014) Changed paths: M Morphic-Widgets-List.package/TreeListMorph.class/instance/private/addSubmorphsAfter_fromCollection_allowSorting_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script403.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40403.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40403 12027 Merge is incredibly slow with Polymorph difference tools, and unusable without https://pharo.fogbugz.com/f/cases/12027 http://files.pharo.org/image/40/40403.zip

Dec. 7, 2014

Re: [Pharo-dev] Monticello and Fuel

by Max Leske

> On 07 Dec 2014, at 19:24, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Max, > > oops, I was being dense... > > On Dec 7, 2014, at 5:14 AM, Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: > >> >>> On 07 Dec 2014, at 04:19, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >>> >>> Hi Max, >> >> Hi Eliot, >> >>> >>> On Sat, Dec 6, 2014 at 1:43 AM, Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: >>> >>>> On 06 Dec 2014, at 04:37, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >>>> >>>> >>>> >>>> On Thu, Dec 4, 2014 at 11:35 PM, Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: >>>> >>>> > On 05 Dec 2014, at 08:02, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >>>> > >>>> > >>>> > >>>> > >>>> >> Am 04.12.2014 um 23:31 schrieb Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>>: >>>> >> >>>> >> Hi all, >>>> >> >>>> >> I'm just wondering. >>>> >> >>>> >> Would it work to have a package format based on Fuel? >>>> >> >>>> > I doubt it would work cross platform. I don't know how fuel serializes WideString, LargePositiveInteger, BoxedFloat64. These differ between smalltalk platforms. The source as string solves that. Strings are written as unicode string and numbers as certain number format etc. >>>> >>>> True. Cross dialect loading isnât something we encourage to do with Fuel. >>>> >>>> @Thierry >>>> You said something about partial loading: that will never be possible with Fuel because of its pickle format. To select any partial graph you have to first read the entire file and rebuild the graph first (ok, you donât strictly have to build the graph but you still need to read the entire file). >>>> >>>> Hi Max, you misunderstand what partial loading means in this context. I designed and implemented partial loading for the Parcel system in VW, and Fuel is essentially a clean reimplementation of parcels. The idea is that one does indeed read the entire object graph, but then only the parts of the graph that mate with the current class hierarchy are installed, and the bits that don't fit are stored for later. Why? So that a component can define extensions on classes in components that may not be present. Why? So that one can maintain a single logical component in a single package instead of decomposing it into independently loadable fragments. >>> >>> Makes sense. Itâs just that I often get asked if it is possible to read / update only parts of a Fuel file, so I wanted to make it clear that that canât work. >>> >>> Right, good point. But is there a use case? For example, in effect is there a difference between being able to patch a part of a Fuel file and loading that file into an image (possibly automatically), patching the object graph and saving a new version? >> >> Yes, performance seems to be the main use case. Fuel files of hundreds of MB take a long time to load and save, even if you only change a single string. One instance where this is relevant is the Moose model. They currently use .mse files, which use a textual representation (if Iâm not mistaken). Usman asked me if Fuel were an option, especially for updating only parts of the model. > > Ah ok. Then yes, I suspect Fuel will be faster, but that patching is more complex because it can't be done in a text editor. How do they edit the .mse file? IME text editors suck on large files. What are the relative frequencies of writing, reading and editing these files? I donât think they can patch the .mse files. Thatâs exactly why they are looking for alternatives. I have no clue about the read / write frenquencies they need. Iâm CCâing this to Usman, maybe can comment on that. > > >>>> Lets take an example like Fuel itself. This may have specialised marshalling and unmarshalling extensions defined on may classes, some of which may be to do with the GUI. If we have partial loading we can load Fuel into a headless image. The extensions on the GUI classes will simply not be installed, *until* we load the GUI. Hence Fuel does not have to be decomposed every time we factor the system into subcomponents. Without partial loading Fuel must be decomposed into a series of fragments so that it can load that part that fits into the headless base, and we have to manage teh dependency to ensure the fragment that loads against the GUI is loaded when the GUI is loaded. Worse still, if we cut the GUI into two (e.g. development vs deployment tools) we have to visit the Fuel GUI component (and potentially many other component) and decompose it into two pieces. In practice this is extremely costly to maintain, verging on chaos. With partial loading things are simple. >>>> >>>> Perhaps I should have called it partial installation, but you get the idea. >>> >>> Thanks for the explanation. >>> >>>> >>>> >>>> > >>>> > Norbert >>>> > >>>> >> Would that make loading faster? >>>> >> >>>> >> Does it already exist? >>>> >> >>>> >> Thanks, >>>> >> >>>> >> Thierry >>>> > >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> best, >>>> Eliot >>> >>> >>> >>> >>> -- >>> best, >>> Eliot

Dec. 7, 2014

Re: [Pharo-dev] Duration year

by Hilaire

Thanks. Looks interesting. Does anyone use it in production? Hilaire Le 07/12/2014 18:36, David T. Lewis a Ã©crit : > On Sun, Dec 07, 2014 at 09:30:06AM +0100, Hilaire wrote: >> Hi, >> >> What is Chalt??n please? > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-April/177938.ht… > > https://github.com/mtaborda/chalten > >> >> Hilaire >> >> Le 02/12/2014 20:53, Maximiliano Taborda a ??crit : >>> Hi all. >>> >>> The same examples using Chalt??n: >>> February twentyninth, 2012 next: 1 yearMeasure. "=> February >>> 28th, 2013" >>> March first, 2011 next: 1 yearMeasure. "=> March 1st, 2012" >>> March first, 2011 next: 12 monthsMeasure. "=> March 1st, 2012" >>> >>> Hilaire, In Chalt??n a year is a year so you don't need to care about of >>> the number of days in it. >>> >>> Regards. >>> Maxi >>> >> >> >> -- >> Dr. Geo - http://drgeo.eu >> iStoa - http://istoa.drgeo.eu >> > > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Dec. 7, 2014

Re: [Pharo-dev] From IRC: is glorp dead?

by Sven Van Caekenberghe

> On 07 Dec 2014, at 19:21, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> wrote: > > Since this is a recurring question, I would be super if you could write a short article about your experiences. > > It's possible, but what exactly means "article"? > More specifically: where such an article should be posted to? It can be anything, a blog post too, anywhere you like. What I've used it just Markdown in GitHub which is very technical (https://github.com/svenvc/docs) Medium which is more like a normal publication and it looks very good (https://medium.com/@svenvc) as well as Pharo Pillar documentation (http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ - https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf…) But really anything you like or are comfortable with. > 2014-12-07 20:49 GMT+03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 07 Dec 2014, at 17:59, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> wrote: > > > > GLORP-based applications is main source of income for me for last several yers. It works just now. And it definetely works in Ubuntu x64, if it's important. And also works fine in Windows. > > Yes, I know, but sometimes it is a bit difficult to set things up, giving all the different platforms. > > Since this is a recurring question, I would be super if you could write a short article about your experiences. > > Another simple Glorp introduction is https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 > > > 2014-12-07 18:31 GMT+03:00 Brad <bsselfridge(a)gmail.com>: > > No, it's not dead, just pretty sleepy. I've got it working with MySQL on an Ubuntu 14.04 32bit OS, but not yet on a 64bit OS. > > > > Once I get my 64bit OS working, I'm going to work on getting Glorp/DBXTalk working for real business activity. > > > > Look here for some resources http://dbxtalk.smallworks.eu > > > > Brad Selfridge > > 913-269-2385 > > > > > On Dec 7, 2014, at 8:25 AM, Max Leske <maxleske(a)gmail.com> wrote: > > > > > > From the IRC: > > > > > > LudicrousMango: Hi can anyone tell me is Glorp dead? I was trying to evaluate pharo as a replacement for an existing rails project, but I can't even find a way of connecting to my postgresql database. > > > LudicrousMango: can someone help point me in the right direction. The Enterprise book leaves the setup part of glorp blank. > > > LudicrousMango: and the glorp.org site has expired > > > maxleske: LudicrousMango: good question. Iâll forward it to the dev mailing list > > > > > > > > > Cheers, > > > Max > > > > > > >

Dec. 7, 2014

Re: [Pharo-dev] Repeatable VM crash

by Eliot Miranda

Hi Mariano, On Dec 7, 2014, at 10:21 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Sun, Dec 7, 2014 at 3:09 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> Hi Hilaire, >> >> >> On Dec 7, 2014, at 12:35 AM, Hilaire <hilaire(a)drgeo.eu> wrote: >> >> > I download this one >> > http://www.mirandabanda.org/files/Cog/VM/VM.r3164/coglinux-14.48.3164.tgz >> > >> > and the crash is still there. Attached crash dump. >> >> different bugs. The 3164 VMs fix a 32-bit Spur bug. Your image is showing a bug in Cog that looks to be to do with the decompression primitive. I haven't had time to look at it deeply yet but can see it and should be able to fix it soon. > > You mean GZip stuff? Because I have found a similar issue years ago: http://forum.world.st/Re-Pharo-project-GZipWriteStream-crashing-my-VM-when-… No. That bug got fixed recently. This is a bug in the custom huffman-ciding bitmap decompression routine (selector begins with "decompress") that's compiled to a primitive. > >> >> > >> > Thanks >> > >> > Hilaire >> > >> > Le 06/12/2014 22:57, Eliot Miranda a Ã©crit : >> >> Hi Esteban, >> >> >> >> plausibly the fix to the latest VM might fix your crash. You might >> >> test? Fingers crossed. >> >> >> >> On Fri, Dec 5, 2014 at 11:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com >> >> <mailto:estebanlm@gmail.com>> wrote: >> >> >> >> yes, but the first step is to be sure you have the latest vm version :) >> >> >> >> Esteban >> > >> > >> > -- >> > Dr. Geo - http://drgeo.eu >> > iStoa - http://istoa.drgeo.eu >> > <crash.dmp> > > > > -- > Mariano > http://marianopeck.wordpress.com

Dec. 7, 2014

Re: [Pharo-dev] Monticello and Fuel

by Eliot Miranda

Hi Max, oops, I was being dense... On Dec 7, 2014, at 5:14 AM, Max Leske <maxleske(a)gmail.com> wrote: > >> On 07 Dec 2014, at 04:19, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Max, > > Hi Eliot, > >> >> On Sat, Dec 6, 2014 at 1:43 AM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>>> On 06 Dec 2014, at 04:37, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>>> >>>> >>>> >>>> On Thu, Dec 4, 2014 at 11:35 PM, Max Leske <maxleske(a)gmail.com> wrote: >>>>> >>>>> > On 05 Dec 2014, at 08:02, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>> > >>>>> > >>>>> > >>>>> > >>>>> >> Am 04.12.2014 um 23:31 schrieb Thierry Goubier <thierry.goubier(a)gmail.com>: >>>>> >> >>>>> >> Hi all, >>>>> >> >>>>> >> I'm just wondering. >>>>> >> >>>>> >> Would it work to have a package format based on Fuel? >>>>> >> >>>>> > I doubt it would work cross platform. I don't know how fuel serializes WideString, LargePositiveInteger, BoxedFloat64. These differ between smalltalk platforms. The source as string solves that. Strings are written as unicode string and numbers as certain number format etc. >>>>> >>>>> True. Cross dialect loading isnât something we encourage to do with Fuel. >>>>> >>>>> @Thierry >>>>> You said something about partial loading: that will never be possible with Fuel because of its pickle format. To select any partial graph you have to first read the entire file and rebuild the graph first (ok, you donât strictly have to build the graph but you still need to read the entire file). >>>> >>>> Hi Max, you misunderstand what partial loading means in this context. I designed and implemented partial loading for the Parcel system in VW, and Fuel is essentially a clean reimplementation of parcels. The idea is that one does indeed read the entire object graph, but then only the parts of the graph that mate with the current class hierarchy are installed, and the bits that don't fit are stored for later. Why? So that a component can define extensions on classes in components that may not be present. Why? So that one can maintain a single logical component in a single package instead of decomposing it into independently loadable fragments. >>> >>> Makes sense. Itâs just that I often get asked if it is possible to read / update only parts of a Fuel file, so I wanted to make it clear that that canât work. >> >> Right, good point. But is there a use case? For example, in effect is there a difference between being able to patch a part of a Fuel file and loading that file into an image (possibly automatically), patching the object graph and saving a new version? > > Yes, performance seems to be the main use case. Fuel files of hundreds of MB take a long time to load and save, even if you only change a single string. One instance where this is relevant is the Moose model. They currently use .mse files, which use a textual representation (if Iâm not mistaken). Usman asked me if Fuel were an option, especially for updating only parts of the model. Ah ok. Then yes, I suspect Fuel will be faster, but that patching is more complex because it can't be done in a text editor. How do they edit the .mse file? IME text editors suck on large files. What are the relative frequencies of writing, reading and editing these files? >>>> Lets take an example like Fuel itself. This may have specialised marshalling and unmarshalling extensions defined on may classes, some of which may be to do with the GUI. If we have partial loading we can load Fuel into a headless image. The extensions on the GUI classes will simply not be installed, *until* we load the GUI. Hence Fuel does not have to be decomposed every time we factor the system into subcomponents. Without partial loading Fuel must be decomposed into a series of fragments so that it can load that part that fits into the headless base, and we have to manage teh dependency to ensure the fragment that loads against the GUI is loaded when the GUI is loaded. Worse still, if we cut the GUI into two (e.g. development vs deployment tools) we have to visit the Fuel GUI component (and potentially many other component) and decompose it into two pieces. In practice this is extremely costly to maintain, verging on chaos. With partial loading things are simple. >>>> >>>> Perhaps I should have called it partial installation, but you get the idea. >>> >>> Thanks for the explanation. >>> >>>> >>>>> >>>>> > >>>>> > Norbert >>>>> > >>>>> >> Would that make loading faster? >>>>> >> >>>>> >> Does it already exist? >>>>> >> >>>>> >> Thanks, >>>>> >> >>>>> >> Thierry >>>>> > >>>> >>>> >>>> >>>> -- >>>> best, >>>> Eliot >> >> >> >> -- >> best, >> Eliot >

Dec. 7, 2014

Re: [Pharo-dev] Repeatable VM crash

by Mariano Martinez Peck

On Sun, Dec 7, 2014 at 3:09 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Hilaire, > > > On Dec 7, 2014, at 12:35 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > > > I download this one > > > http://www.mirandabanda.org/files/Cog/VM/VM.r3164/coglinux-14.48.3164.tgz > > > > and the crash is still there. Attached crash dump. > > different bugs. The 3164 VMs fix a 32-bit Spur bug. Your image is > showing a bug in Cog that looks to be to do with the decompression > primitive. I haven't had time to look at it deeply yet but can see it and > should be able to fix it soon. > You mean GZip stuff? Because I have found a similar issue years ago: http://forum.world.st/Re-Pharo-project-GZipWriteStream-crashing-my-VM-when-… > > > > > Thanks > > > > Hilaire > > > > Le 06/12/2014 22:57, Eliot Miranda a Ã©crit : > >> Hi Esteban, > >> > >> plausibly the fix to the latest VM might fix your crash. You might > >> test? Fingers crossed. > >> > >> On Fri, Dec 5, 2014 at 11:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com > >> <mailto:estebanlm@gmail.com>> wrote: > >> > >> yes, but the first step is to be sure you have the latest vm version > :) > >> > >> Esteban > > > > > > -- > > Dr. Geo - http://drgeo.eu > > iStoa - http://istoa.drgeo.eu > > <crash.dmp> > > -- Mariano http://marianopeck.wordpress.com

Dec. 7, 2014

Re: [Pharo-dev] From IRC: is glorp dead?

by Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾

> > Since this is a recurring question, I would be super if you could write a > short article about your experiences. It's possible, but what exactly means "article"? More specifically: where such an article should be posted to? 2014-12-07 20:49 GMT+03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 07 Dec 2014, at 17:59, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> wrote: > > > > GLORP-based applications is main source of income for me for last > several yers. It works just now. And it definetely works in Ubuntu x64, if > it's important. And also works fine in Windows. > > Yes, I know, but sometimes it is a bit difficult to set things up, giving > all the different platforms. > > Since this is a recurring question, I would be super if you could write a > short article about your experiences. > > Another simple Glorp introduction is > https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 > > > 2014-12-07 18:31 GMT+03:00 Brad <bsselfridge(a)gmail.com>: > > No, it's not dead, just pretty sleepy. I've got it working with MySQL on > an Ubuntu 14.04 32bit OS, but not yet on a 64bit OS. > > > > Once I get my 64bit OS working, I'm going to work on getting > Glorp/DBXTalk working for real business activity. > > > > Look here for some resources http://dbxtalk.smallworks.eu > > > > Brad Selfridge > > 913-269-2385 > > > > > On Dec 7, 2014, at 8:25 AM, Max Leske <maxleske(a)gmail.com> wrote: > > > > > > From the IRC: > > > > > > LudicrousMango: Hi can anyone tell me is Glorp dead? I was trying to > evaluate pharo as a replacement for an existing rails project, but I can't > even find a way of connecting to my postgresql database. > > > LudicrousMango: can someone help point me in the right direction. The > Enterprise book leaves the setup part of glorp blank. > > > LudicrousMango: and the glorp.org site has expired > > > maxleske: LudicrousMango: good question. Iâll forward it to the dev > mailing list > > > > > > > > > Cheers, > > > Max > > > > > > >

Dec. 7, 2014