- Pharo-dev - lists.pharo.org

Re: [Pharo-project] SimpleLiteralArray Spec

by Norbert Hartl

April 24, 2012

Re: [Pharo-project] [Esug-list] GSoC news: we have 13 projects!

by Bert Freudenberg

Excellent! Thank you so much, Janko, Carla, mentors, students, and ESUG :) - Bert - On 24.04.2012, at 05:10, Janko MivÅ¡ek wrote: > Dear Smalltalkers! > > We have 13 GSoC projects and let we welcome to all students whose > proposals were accepted: > > 1. Santiago Bragagnolo > Concrete Type Inference -- Call graph > http://gsoc2012.esug.org/projects/type-inference > 2. Lars Wassermann > ARM jitter for Squeak VM > http://gsoc2012.esug.org/projects/arm-jitter > 3. Facundo Mainere > Interactive & social online Smalltalk tutorial > http://gsoc2012.esug.org/projects/interactive-tutorial > 4. Benjamin Van Ryseghem > Nautilus > http://gsoc2012.esug.org/projects/nautilus > 5. MartÃn Dias > Package management with Fuel > http://gsoc2012.esug.org/projects/fuel-packages > 6. Guillermo Polito > Bootstrapping the core-Hazelnut > http://gsoc2012.esug.org/projects/hazelnut > 7. Pablo Estefo > TestSurgeon > http://gsoc2012.esug.org/projects/testsurgeon > 8. Daniel Uber > SciSmalltalk > http://gsoc2012.esug.org/projects/sci-smalltalk > 9. Rustem Khubbatov > HMI (Human-Machine Interface) with Amber > http://gsoc2012.esug.org/projects/mmi-amber > 10. Juan Pablo Sandoval Alcocer > Rizel - Multidimensional Profiler > http://gsoc2012.esug.org/projects/rizel > 11. Saurav Bhattacharya > Export Excel files and other spreadsheet related goodies > http://gsoc2012.esug.org/projects/excel-export > 12. Steve Granda > Finish Physical Etoys port to Sugar > http://gsoc2012.esug.org/projects/etoys-sugar > 13. Paul Kuzovkin > Esse, a framework for visualizing, storing and exploring ideas > http://gsoc2012.esug.org/projects/esse > > 5 students from Argentina, 2 from Chile, 2 from Russia, 1 from Sweden, > France, USA and let we specially welcome our first Indian student! > > Now a Community bonding period started, when students get to know > mentors, read documentation, get up to speed to begin working on their > projects. Until 21.May when coding begin. > > Good luck to everyone! > > Janko @ Carla > > > -- > Smalltalk GSoC Admin Team > http://gsoc2012.esug.org

April 24, 2012

[Pharo-project] [update 2.0] #20009

by Marcus Denker

20009 ----- Issue 5564: Support bit operations on Boolean / Integers http://code.google.com/p/pharo/issues/detail?id=5564 Issue 5641: Unload Deprecated14 http://code.google.com/p/pharo/issues/detail?id=5641 -- Marcus Denker -- http://marcusdenker.de

April 24, 2012

Re: [Pharo-project] SimpleLiteralArray Spec

by Dale Henrichs

April 24, 2012

Re: [Pharo-project] refactoring

by blake

On Thu, Apr 19, 2012 at 2:55 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > It's a will known bug from RPackage which have some issues when importing categorize :S > > This should be fixed soon. > (for retrieving your class, do a Find, then if you right click on the empty class list, you can access the menu, and move the selected invisible class in the package you want) This pops up an error about not being able to find the package--but it does seem to work despite that, thanks! ===Blake===

April 24, 2012

[Pharo-project] JSON, Smalltalk parser and no-point wars

by Miguel CobÃ¡

Friends, what energy! But I don't know why are we discussing this point of JSON choice so long. It is an implementation detail. If he choose to use XML, so be. It is Dale's time and Dale's code. Remember his projects is not to build a inter-dialect metadata format. His project is all about building an inter-dialect package format to store smalltalk. And in that goal he is succeeding! Lets no make a flame war about his choices. What is matters now is to show to as many smalltalk dialects as possible, that code interchange is possible. That is the fucking point. If after that, because the implementation is slow, or some other real after-use problem is detected, then is the time to discuss how to better address that specific problem. Until then, this is a bikeshedding like inane problem. Remember make it work, make it right, make it fast! Dale is in make it work. Every other not putting code on the project is trying to make it right (intelectually and upfront). Lets not stop the work of others by discussing the best way to do it instead of doing it. Some famous people around here made an analogy about a mountain and the people trying to climb it. Don't forget that! Cheer to all. -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

April 24, 2012

[Pharo-project] Polymorph (and a few other) changes/fixes

by Gary Chambers

Finally found the time to package out. Have tested a bit after fixing some conflicts. A few minor ones left for DropListMorph as it seems the wrapSelector stuff has changed (and appears broken in 2.0 too). Attached cs and description of changes Regards, Gary

April 24, 2012

Re: [Pharo-project] [ANN] Styled Text Editor for Cuis 4.0 Smalltalk

by Dale Henrichs

Juan, Exactly! BTW, I've got just a little more work to do before Cuis will be able to read and write Cypress:) Dale ----- Original Message ----- | From: "Juan Vuletich (mail lists)" <juanlists(a)jvuletich.org> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Tuesday, April 24, 2012 4:55:26 AM | Subject: Re: [Pharo-project] [ANN] Styled Text Editor for Cuis 4.0 Smalltalk | | Hi Dale, | | Quoting Dale Henrichs <dhenrich(a)vmware.com>: | | > Bernhard and Juan, | > | > I was curious enough about Cypress and Cuis to start a Cypress port | > to Cuis[1]. Loaded code and started working through tests: | > | > 19 run, 6 passed, 3 failed, 10 errors | > | > We'll see if I get any farther tonight:) | > | > Dale | > | > [1] https://github.com/CampSmalltalk/cuis-cypress | | This is great, thank you! | | I took a look at your format when thinking on how to do Cuis package | format, and I think that for a Cuis specific package format, a single | file per package will be easier to diff / merge by Git. | | But I really welcome and thank you for this format for cross-dialect | packages! | | Cheers, | Juan Vuletich | | > ----- Original Message ----- | > | From: "Dale Henrichs" <dhenrich(a)vmware.com> | > | To: Pharo-project(a)lists.gforge.inria.fr | > | Sent: Monday, April 23, 2012 1:57:57 PM | > | Subject: Re: [Pharo-project] [ANN] Styled Text Editor for Cuis | > | 4.0 | > Smalltalk | > | | > | Bernhard, | > | | > | With regards to sharing code between dialects, I'd like to | > | recommend | > | that you look into porting Cypress to Cuis (I'm willing to help | > | as | > | much as I can). | > | | > | The Cypress project is aimed from the get go to enable sharing of | > | packages between Smalltalk dialects with a recognition that | > | possibly | > | the most important aspect is a shared VCS (git/github). | > | | > | If you look at the current code base in Cypress, you will see a | > | reference implementation written against Pharo. The reference | > | implementation is a work in progress and the initial | > | implementation | > | was done for Amber[2]. | > | | > | Cypress has Monticello-like packages, but other than taking a few | > | ideas from Monticello (definitions, packages and snapshots ... | > | more | > | than a few:)) the code base is independent of Monticello. The | > | fact | > | that Cypress runs on top of Amber (sans file system access) | > | speaks | > | volumes for it's portability. | > | | > | To paraphrase a point from my STIC talk[3] on this subject: | > | | > | Cypress is not intended to be the primary version control | > | system for any dialect, however, if you want to share code | > | between dialects you should allow your developers to import | > | and export code using the Cypress package format. | > | | > | If you are interested, there are bits and pieces of code in a few | > | other projects that I would want to pull into the Cypress project | > | and couple other things that I'd like to move out of the Cypress | > | project before tackling another port ... | > | | > | We can correspond via private email if you'd like to take me up | > | on | > | the offer of help:) | > | | > | Dale | > | | > | [1] https://github.com/CampSmalltalk/Cypress | > | [2] https://github.com/CampSmalltalk/amber-cypress | > | [3] | > | http://portal.sliderocket.com/vmware/STIC-2012-Practical-Git-for-Smalltalk | > | | > | ----- Original Message ----- | > | | From: "Bernhard Pieber" <bernhard(a)pieber.com> | > | | To: Pharo-project(a)lists.gforge.inria.fr | > | | Sent: Monday, April 23, 2012 9:53:35 AM | > | | Subject: Re: [Pharo-project] [ANN] Styled Text Editor for Cuis | > | | 4.0 | > | | Smalltalk | > | | | > | | Hi GÃ¶ran, | > | | | > | | Thanks for your question! I have posted the announcement of the | > | | Styled Text Editor to the Pharo list as well because I still | > | | have | > | | not given up on the idea to port it to Squeak and Pharo. It is | > | | not | > | | straightforward but I consider it possible. | > | | | > | | Currently the Styled Text Editor is an external package which | > | | is | > | | loaded on top of Cuis 4.0. The API it uses is quite specific to | > | | Cuis | > | | so to port it alone is probably too much effort. What I think | > | | can | > | | be | > | | done is the following: | > | | Split Cuis into three parts, | > | | a) the parts which are not needed for Styled Text Editor, like | > | | the | > | | Cuis tools | > | | b) the parts of Cuis Morphic the Styled Text Editor depends on | > | | ? | > | | this | > | | is in my opinion the most valuable part of Cuis because Juan | > | | spent | > | | years cleaning it | > | | c) the Smalltalk kernel below | > | | | > | | The idea is to port only part b) and the Styled Text Editor. | > | | And it | > | | has to be done automatically by a tool which creates packages | > | | for | > | | Squeak and Pharo, always from the latest code base. In addition | > | | you | > | | will probably need small Cuis portability packages done | > | | manually, | > | | one for Squeak and one for Pharo. | > | | | > | | Being able to always load the latest code base of Styled Text | > | | Editor | > | | and Cuis Morphic as an external package in Pharo is a | > | | prerequisite | > | | to look into possibilities of sharing more of the code. | > | | | > | | I plan to write a more detailed proposal and then to approach | > | | ESUG | > | | and ask for support for the funding. Any ideas for other | > | | sources of | > | | funding are highly welcome and could speed things up | > | | considerably, | > | | of course! ;-) | > | | | > | | I for one have not given up on the idea that it might be | > | | possible | > | | to | > | | develop substantial components as you called it ? thank you for | > | | that | > | | as well ? in a more Squeak-dialect-independent way. ;-) | > | | | > | | Finally, I would like to take the opportunity and kindly ask | > | | everyone | > | | who has not done so yet: Please check out Cuis 4.0 and the | > | | Styled | > | | Text Editor and give us feedback, even if it does not (yet) run | > | | on | > | | your favourite Squeak dialect! Thank you! | > | | | > | | Peace, | > | | Bernhard | > | | | > | | P.S. Thanks to GÃ¶ran and Janko for trying to establish | > | | different | > | | threads for the rather off-topic discussions that my | > | | announcement | > | | posting has caused. | > | | | > | | Am 23.04.2012 um 16:04 schrieb GÃ¶ran Krampe: | > | | > Hi! | > | | > | > | | > On 04/23/2012 03:40 PM, StÃ©phane Ducasse wrote: | > | | >>> Just cloning it off into Pharo and forking seems... less | > | | >>> optimal. | > | | >>> Any ideas or thoughts? | > | | >> | > | | >> I do not get what you mean. I just want to work on our | > | | >> roadmap | > | | >> and | > | | >> make it getting real. | > | | >> It is hard enough to get some momentum and to deliver for | > | | >> real. | > | | >> So can you help us to get focused? | > | | >> People can do what they want. I wrote a vision document. We | > | | >> have | > | | >> a | > | | >> roadmap | > | | >> and we will do it. | > | | > | > | | > Ok, let me clarify. I was just wondering how the Pharo | > | | > community | > | | > wants to handle a case where a substantial component (in this | > | | > case, this new editor) is not *primarily* developed in Pharo | > | | > (in | > | | > this case Cuis). | > | | > | > | | > The simple route is to just copy and fork. But IMHO this | > | | > doesn't | > | | > leverage the team already around this editor, right? We | > | | > (Pharo) | > | | > can't just go around and forking everything and maintaining | > | | > everything for ourselves, right? | > | | > | > | | > I just got interested in that problem - now, later replies | > | | > indicated that it would still need a substantial rewrite for | > | | > Pharo, so perhaps the situation I am describing is not really | > | | > applicable in this case. | > | | > | > | | > regards, GÃ¶ran | > | | > | > | | | > | | | > | | | > | | > | > | | | |

April 24, 2012

Re: [Pharo-project] How to disable development tools on Pharo 1.4

by Noury Bouraqadi

thanx. Done. On 20 avr. 2012, at 17:28, Esteban Lorenzano wrote: > Hi Noury, > > I opened the project (I don't know why it was closed)... please upload your changes :) > > best, > Esteban > > > On Apr 20, 2012, at 5:14 PM, Noury Bouraqadi wrote: > >> Hi, >> >> I tried it with WorldSwitch-Preferences from SS3. >> A minor fix was required to have it run on 1.4 (use rehash instead of rehachWithoutBecome not in the system anymore). >> Attached the fixed version since I can't write on the repo. >> >> I get a "closed" image. I don't know how to test it further. >> >> Noury >> >> >> >> >> Afin de contribuer au respect de l'environnement, >> >> >> merci de n'imprimer ce courriel qu'en cas de necessite >> >> >> >> >> >> Please consider the environment before you print >> >> >> >> >> >> <WorldSwitch-Preferences-NouryBouraqadi.2.mcz> >> >> On 2 fÃ©vr. 2012, at 14:32, Esteban Lorenzano wrote: >> >>> Hi Noury, >>> >>> I packaged what I have. And even create a settings configuration for it (under "Deployment" category). >>> Notice that is very hacky and ugly and needs a lot (and I mean A LOT) of polish... but is a start :) >>> >>> see WSSettings class>>#setDeployment: for a start. >>> >>> <WorldSwitch-Preferences-EstebanLorenzano.2.mcz> >>> >>> best, >>> Esteban >>> >>> El 02/02/2012, a las 6:40a.m., Noury Bouraqadi escribiÃ³: >>> >>>> Hi Esteban, >>>> >>>> On 31 janv. 2012, at 14:23, Esteban Lorenzano wrote: >>>> >>>>> Hi, >>>>> >>>>> in fact, what Mariano posted is just a part... disable everything is complicated, because code is everywhere... I'm collection all of this changes in a package, to see in advance if it is possible to abstract that. >>>> >>>> Thanks Esteban! >>>> Do you have a version of this package already? >>>> Otherwise, I'll start packaging what Mariano sent. >>>> >>>> >>>>> Ideally, we should have a preference "Disable Development Mode", or something like that to allow desktop developers to easily switch... >>>>> >>>> Yes. We should have a menu for this. It's part of dev tools. >>>> It's a shame that this critical feature isn't available yet. >>>> >>>> Noury >>>> >>>>> best, >>>>> Esteban >>>>> >>>>> El 31/01/2012, a las 10:16a.m., Ben Coman escribiÃ³: >>>>> >>>>>> Noury Bouraqadi wrote: >>>>>>> I remember having seen some time in the past a menu that allows to shrink the image and disable the world menu. >>>>>>> But, I can't retrieve any thing related. I don't care about the menu per se. I'd be happy with a message to send to some object that does the job. >>>>>>> >>>>>>> >>>>>>> Noury >>>>>>> -- >>>>>>> http://twitter.com/#!/NouryBouraqadi >>>>>>> http://www.kroobe.com/profile/noury >>>>>>> >>>>>>> >>>>>> Squeak 3.9 based, but perhaps something useful... >>>>>> "Prepare For Application Deployment" http://squeak.preeminent.org/tut2007/html/205.html >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> Noury >>>> -- >>>> http://twitter.com/#!/NouryBouraqadi >>>> http://www.kroobe.com/profile/noury >>>> >>>> >>>> Afin de contribuer au respect de l'environnement, >>>> merci de n'imprimer ce courriel qu'en cas de necessite >>>> >>>> Please consider the environment before you print >>>> >>>> >>>> >>>> >>> >> >> Noury >> -- >> http://twitter.com/#!/NouryBouraqadi >> http://www.kroobe.com/profile/noury >> > > Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

April 24, 2012

Re: [Pharo-project] Pharo and the rest of the ecosystem

by Edgar De Cleene

El 4/24/12 9:09 AM, "Fernando Olivero" <fernando.olivero(a)usi.ch> escribiÃ³: > The community behind Pharo, shouldnt be required to always be aware of > external enhancements. And vice-versa for the remaining forks. > > Fernando Un libro sabio dice: Los hermanos sean unidos.... A wise book says: The brothers are united... Or Pharo is not descendent of ...... Don't put name here for not irritate people Edgar

April 24, 2012