- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Cleaning up SmartRefStream use

by Nicolas Cellier

2011/12/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Indeed this is fun I was doing the same :) > Now I do not understand why some parts of the system uses dataStream, others ReferenceStream and finally others SmartRefStream > why not all of them use SmartRefStream. > > Stef > That's a very good question. Where should design decisions be documented? On one side, we should have requirements that we document with some high level TestCase. But whether the implementation is guided by time/memory efficiency, code simplicity, or just historically available packages is not easily described by tests. Obviously, you would have a hard time discovering this in legacy code (digging squeak wiki and mailing list?). The question should apply to Pharo too. Pharo is young, so maybe all design decisions can be retrieved by virtue of human memory... But will it be the case in 5 years? Nicolas > On Dec 11, 2011, at 10:43 AM, Marcus Denker wrote: > >> Hi, >> >> We should minimize the use of SmartRefStream... so we can remove it eventually. >> >> I already did a little bit (e.g. removing BitmapStreamTests). These are the next steps: >> >> Issue 5081: Â Remve Morph saving to file/loading >> Â Â Â http://code.google.com/p/pharo/issues/detail?id=5081 >> >> Â Â Â Anyone needs this? >> >> Issue 5084: Â Remove textStyle FileOut >> Â Â Â http://code.google.com/p/pharo/issues/detail?id=5084 >> >> Â Â Â Is this used? Strange corner of the system... lots of dead code. >> >> Issue 5083: Â remove unused methods from SmartRefStream >> Â Â Â http://code.google.com/p/pharo/issues/detail?id=5083 >> >> Â Â Â Towards removing it alltogether. >> >> >> >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > >

Dec. 11, 2011

Re: [Pharo-project] Keymapping & OB conflict (was Re: Chasing Browsers)

by Tudor Girba

Hi, On 11 Dec 2011, at 15:49, Esteban Lorenzano wrote: > Hi Lukas, > > I just loaded Magritte2 into Pharo 1.4 and it loads well with all tests in green. > Also, Magritte-Morph loads and seems to run well... just a small change: > > replace: > > PluggableListMorphOfMany > > with: > > PluggableListMorph ... > beMultipleSelection Thanks for looking into this :). > (now, I want to deprecate #description for #magritteDescription and add a pragma builder with <magritte> and <magritteContainer> keywords :) I think that would be most welcome. Cheers, Doru > cheers, > Esteban > > El 11/12/2011, a las 10:58a.m., StÃ©phane Ducasse escribiÃ³: > >> Thanks for this really bad and sad message. >> So you are implying that Seaside, Magritte, Pier, OB, PetitParser >> will not be maintained on Pharo 1.4. >> >> This is important for us to know that and this is a really nice stab in our back and this will kill >> a lot of the effort we build over the years. >> >> Thanks again lukas! >> At least this is clear. >> >> Stef >> >> On Dec 11, 2011, at 12:33 PM, Lukas Renggli wrote: >> >>>> - then that OB can be loaded on top of Pharo. Remember we are not against OB we just do not have >>>> the knowledge to maintain it. So if lukas gets OB working for 1.4 beta then we will probably include in Pharo. >>>> Now if OB is working for 1.4 only three months after 1.4 is released then we will not include it. >>> >>> Yes please, do not wait for me. >>> >>> Just to repeat myself: With Pharo 1.4 having uncountable changes in >>> core parts of the system and with the system including more and more >>> forked and increasingly incompatible versions of packages (AST, RB, >>> FS, Shout, Regex, ...) I am unwilling to go through the same pain as >>> with Pharo 1.3 again. In the current state, I don't see any of the >>> code I am involved with (including Seaside, Magritte, Pier, OB, >>> PetitParser, ...) to move forward. I suspect that moving to another >>> development platform soon causes less pain than to move to adopt the >>> next Pharo :-( >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> > > -- www.tudorgirba.com "Quality cannot be an afterthought."

Dec. 11, 2011

Re: [Pharo-project] Keymapping & OB conflict (was Re: Chasing Browsers)

by Esteban Lorenzano

Hi Lukas, I just loaded Magritte2 into Pharo 1.4 and it loads well with all tests in green. Also, Magritte-Morph loads and seems to run well... just a small change: replace: PluggableListMorphOfMany with: PluggableListMorph ... beMultipleSelection (now, I want to deprecate #description for #magritteDescription and add a pragma builder with <magritte> and <magritteContainer> keywords :) cheers, Esteban El 11/12/2011, a las 10:58a.m., StÃ©phane Ducasse escribiÃ³: > Thanks for this really bad and sad message. > So you are implying that Seaside, Magritte, Pier, OB, PetitParser > will not be maintained on Pharo 1.4. > > This is important for us to know that and this is a really nice stab in our back and this will kill > a lot of the effort we build over the years. > > Thanks again lukas! > At least this is clear. > > Stef > > On Dec 11, 2011, at 12:33 PM, Lukas Renggli wrote: > >>> - then that OB can be loaded on top of Pharo. Remember we are not against OB we just do not have >>> the knowledge to maintain it. So if lukas gets OB working for 1.4 beta then we will probably include in Pharo. >>> Now if OB is working for 1.4 only three months after 1.4 is released then we will not include it. >> >> Yes please, do not wait for me. >> >> Just to repeat myself: With Pharo 1.4 having uncountable changes in >> core parts of the system and with the system including more and more >> forked and increasingly incompatible versions of packages (AST, RB, >> FS, Shout, Regex, ...) I am unwilling to go through the same pain as >> with Pharo 1.3 again. In the current state, I don't see any of the >> code I am involved with (including Seaside, Magritte, Pier, OB, >> PetitParser, ...) to move forward. I suspect that moving to another >> development platform soon causes less pain than to move to adopt the >> next Pharo :-( >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > >

Dec. 11, 2011

Re: [Pharo-project] Keymapping & OB conflict (was Re: Chasing Browsers)

by Tudor Girba

Hello gentlemen, Let's loosen up a bit, please :). These are important pieces that nobody wants to see remain behind. But, before we go on, we should first identify the root of these concerns. @Lukas: please, could you point out what are the expected problems? For example, all PetitParser-Tests are green out of the box in the latest 1.4. Cheers, Doru On 11 Dec 2011, at 14:58, StÃ©phane Ducasse wrote: > Thanks for this really bad and sad message. > So you are implying that Seaside, Magritte, Pier, OB, PetitParser > will not be maintained on Pharo 1.4. > > This is important for us to know that and this is a really nice stab in our back and this will kill > a lot of the effort we build over the years. > > Thanks again lukas! > At least this is clear. > > Stef > > On Dec 11, 2011, at 12:33 PM, Lukas Renggli wrote: > >>> - then that OB can be loaded on top of Pharo. Remember we are not against OB we just do not have >>> the knowledge to maintain it. So if lukas gets OB working for 1.4 beta then we will probably include in Pharo. >>> Now if OB is working for 1.4 only three months after 1.4 is released then we will not include it. >> >> Yes please, do not wait for me. >> >> Just to repeat myself: With Pharo 1.4 having uncountable changes in >> core parts of the system and with the system including more and more >> forked and increasingly incompatible versions of packages (AST, RB, >> FS, Shout, Regex, ...) I am unwilling to go through the same pain as >> with Pharo 1.3 again. In the current state, I don't see any of the >> code I am involved with (including Seaside, Magritte, Pier, OB, >> PetitParser, ...) to move forward. I suspect that moving to another >> development platform soon causes less pain than to move to adopt the >> next Pharo :-( >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

Dec. 11, 2011

Re: [Pharo-project] small typo on pharo-project.org

by Tudor Girba

Yuppe. My fix got integrated :) Doru On 11 Dec 2011, at 15:03, Marcus Denker wrote: > On Sun, Dec 11, 2011 at 1:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> My contribution for the month: >> >> http://www.pharo-project.org/pharo-download/unstable-1-4 >> Jenkis should be Jenkins :) >> > > fixed. > > >> Doru >> >> -- >> www.tudorgirba.com >> >> "One cannot do more than one can do." >> >> >> >> > > > > -- > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de > -- www.tudorgirba.com "Don't give to get. Just give."

Dec. 11, 2011

Re: [Pharo-project] [ANN] Eclipse Icons for Pharo

by StÃ©phane Ducasse

On Dec 11, 2011, at 1:59 PM, Esteban Lorenzano wrote: > Hi Fernando, > > oops... I forgot your icon importer, sorry :P > > I would like âfor a futureâ to integrate it to pharo and replace current ThemeIcons with an icon strategy based on your package... maybe that is the best "future scenario" for icons. Yes esteban could you evaluate the work of fernando and provide an analysis to see if it makes sense for us to integrate it. Then we build a plan and integrate it. Stef > > best, > Esteban > > El 11/12/2011, a las 8:49a.m., Fernando Olivero escribiÃ³: > >> Hi Esteban, nice work! >> For importing the icons you can use the toolset i've developed: it >> automates completely the process of importing a complete set of icons >> of a given family. >> >> ExternalIconFamily @ squeaksource. >> I've used it for importing the Oxygen icon set, and others (you can >> google the list for previous related emails). >> >> Fernando >> >> On Sun, Dec 11, 2011 at 10:38 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> Esteban >>> I know that feeling :) >>> >>> :) >>> Now I'm not sure that I would like to carry the Eclipse License around in Pharo :) >>> What are the other icons sets we could use with a nice license and we do it :). >>> famfam? >>> >>> We should clean also the old icons because some are really old. >>> Thanks for pushing that. I would love to have new icons for Pharo. >>> Stef >>> >>> >>> >>> On Dec 11, 2011, at 3:15 AM, Esteban Lorenzano wrote: >>> >>>> Hi, >>>> >>>> Today I was bored and not wanting to think too much... but I wanted to do something for Pharo... and I never liked the current Pharo icons, so I took one icon library I really like and changed all needed icons (well... all that I saw). >>>> Here a couple of screen shots: >>>> >>>> <Captura de pantalla 2011-12-10 a la(s) 23.05.55.png> >>>> <Captura de pantalla 2011-12-10 a la(s) 23.06.20.png> >>>> >>>> Of course, I don't think they are perfect (also maybe I didn't pick the best icons), but I think they look a lot better than the older. >>>> >>>> If you want to see how they look, this are the packages: >>>> >>>> for Pharo 1.3: >>>> >>>> <Eclipse-Icons-EstebanLorenzano.2.mcz> >>>> >>>> for Pharo 1.4: >>>> >>>> <Eclipse-Icons-EstebanLorenzano.4.mcz> >>>> >>>> >>>> Then you execute: >>>> >>>> ThemeIcons initializeIcons. >>>> World resetWorldMenu. >>>> >>>> ... and enjoy your new icons :) >>>> >>>> btw... this icons are in an open-source license, the EPL: http://www.eclipse.org/legal/epl-v10.html >>>> so, maybe âif all agreeâ, we can add this icons to regular distribution :) >>>> >>>> best, >>>> Esteban >>>> >>> >>> >> > >

Dec. 11, 2011

Re: [Pharo-project] Pharo 1.3 vs 1.2.1 some results for ConfigurationOfODBC

by Mariano Martinez Peck

Hi. Just as a test, would you like to test the attached VM? change xxx with zip. Just make sure odbc libraries are findable by Windows. Cheers On Sun, Dec 11, 2011 at 6:45 AM, Ben Coman <btc(a)openinworld.com> wrote: > Fadi Mansour wrote: > >> Hi, >> >> I'm having the same issue while trying to use ODBC with Pharo's OnClick >> image 1.3. >> >> Did you find anything about the issue here? >> >> Regards, >> >> Fadi >> >> >> >> >> >> > I've been offline while attending to a machine rebuild shutdown on a mine > site. I've only just got back today to start having a look at it again. > > -- Mariano http://marianopeck.wordpress.com

Dec. 11, 2011

Re: [Pharo-project] Keymapping & OB conflict (was Re: Chasing Browsers)

by StÃ©phane Ducasse

Lukas I really think that you are exaggerating. Now how can we make progress if we do not change Pharo? You were against changing RB, so how can we do remote tooling? Alain fixed a lot of the problems of 1.3. I think that your bad energy will damage us and I'm immensely sad. May be a dead pharo is better for you. Stef >> - then that OB can be loaded on top of Pharo. Remember we are not against OB we just do not have >> the knowledge to maintain it. So if lukas gets OB working for 1.4 beta then we will probably include in Pharo. >> Now if OB is working for 1.4 only three months after 1.4 is released then we will not include it. > > Yes please, do not wait for me. > > Just to repeat myself: With Pharo 1.4 having uncountable changes in > core parts of the system and with the system including more and more > forked and increasingly incompatible versions of packages (AST, RB, > FS, Shout, Regex, ...) I am unwilling to go through the same pain as > with Pharo 1.3 again. In the current state, I don't see any of the > code I am involved with (including Seaside, Magritte, Pier, OB, > PetitParser, ...) to move forward. I suspect that moving to another > development platform soon causes less pain than to move to adopt the > next Pharo :-( > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Dec. 11, 2011

Re: [Pharo-project] small typo on pharo-project.org

by Marcus Denker

On Sun, Dec 11, 2011 at 1:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > My contribution for the month: > > http://www.pharo-project.org/pharo-download/unstable-1-4 > Jenkis should be Jenkins :) > fixed. > Doru > > -- > www.tudorgirba.com > > "One cannot do more than one can do." > > > > -- -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

Dec. 11, 2011

Re: [Pharo-project] [ANN] Magma 1.3

by Stephan Eggermont

Hi Chris, Great! I'd love to have someone explain and demo Magma at the FOSDEM2011 devroom (Feb 5, Brussels). You already told me you'd not be available. Anyone else capable & willing to do a presentation? Stephan

Dec. 11, 2011