- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Jun4Pharo so exciting :)

by Richard Wettel

Hi Steph, I originally used Jun to build CodeCity on top of it, in VW at the time.The main disadvantage I experienced back then was lack of support for hardware acceleration (which made it quite slow). Plus, the developers were Japanese and it was not clear where the product was heading next. The positive side was that Jun provided a pretty solid API which would allow to use OpenGL without the need to go very low-level and tons of examples. Plus, it was pretty much the only OpenGL implementation in VisualWorks for a long time. Cheers Ricky â Sent from Mailbox On Mon, Dec 29, 2014 at 3:36 PM, stepharo <stepharo(a)free.fr> wrote: > https://www.youtube.com/watch?v=sH_P5otiWJM&feature=youtu.be

Dec. 29, 2014

Re: [Pharo-dev] Jun4Pharo so exciting :)

by Sven Van Caekenberghe

> On 29 Dec 2014, at 21:04, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > > > Originally OpenGL package in VW Smalltalk OK, thanks. And how is this different or how does this compare to Athens then ? > On Tue, Dec 30, 2014 at 12:50 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 29 Dec 2014, at 15:36, stepharo <stepharo(a)free.fr> wrote: > > > > https://www.youtube.com/watch?v=sH_P5otiWJM&feature=youtu.be > > It certainly looks nice, but what is Jun exactly ?

Dec. 29, 2014

Re: [Pharo-dev] Jun4Pharo so exciting :)

by S Krish

Originally OpenGL package in VW Smalltalk On Tue, Dec 30, 2014 at 12:50 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 29 Dec 2014, at 15:36, stepharo <stepharo(a)free.fr> wrote: > > > > https://www.youtube.com/watch?v=sH_P5otiWJM&feature=youtu.be > > It certainly looks nice, but what is Jun exactly ? > >

Dec. 29, 2014

Re: [Pharo-dev] A toast

by Sven Van Caekenberghe

Excellent write-up, Esteban, this was very useful. I want to add my 'thank you' to everyone in the Pharo community for making all this possible. > On 29 Dec 2014, at 13:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hello Pharoers, > > (sorry for the long post) > > I'm on holidays so I've been silent this latests days, but I didn't want to let the opportunity goes to propose a toast :) > This year has been a great year (yeah, but not like those annoying facebook cards), one year where we have worked itensively in the patient consolidation of several lines of work. > This has been possible thanks to the great improvement that we have made in the Pharo process itself, which required (and still requires) a massive amount of effort: Since I arrived here (but not necessarily *because* I arrived here: this is the work of everyone in Pharo community, I'm just pointing to what I've seen and collaborated :P), we have changed a lot of things: > > - we have deployed a solid CI infrastructure that can handle our integration cycle without too much complications. Even if we still find problems time to time, this has been an incredible step forward. > - thanks to this we have been able to change our release cycle from "it happens when we believe is ready" to time-boxed releases, so we have created Pharo 1.4, 2.0 and this year what, for me, is one of the most complete and cool releases (up to now) that we have produced: Pharo 3.0. > - We have increased massively the amount of tests in the system (no sure what is the percentage, but is high), so we have been able to change core parts in the system without causing too much pain to developers (yeah, we know there have been some errors some times, but well... "errare humanum est", and I think we have learned from the process and now we do not make same mistakes... in any case they are new mistakes :P). > - We have made huge steps in the "Pharo modularisation project", thanks to the Pharo-minimal images and work we have started to move all into a repeatable configuration (thanks to metacello and tools developed for this). > - We have also incorporated the VM building to this process and testing cycle, so is a lot easier for everyone to build their own VM (if needed), and for us we can be sure (as sure as possible at least) VM is in good shape. > - We have improved documentation and release new books. People have working a lot in a lot of cool and instructive videos that have moved our "learning curve" several steps ahead. > > And this is just one part of the "invisible, ant work of everyday", in the visible part, I will not bore (more than needed :P) with details about previous releases, so I will just point some of the great things we have made for the upcoming release, Pharo 4: > > - Thanks to GTools, we are slowly going to a better set of tools, with new ways of see/handle old things. This is the most visible change this year (and it has caused the most flamed wars, but well... we are a passionate community). This release we have a new inspector, playground and spotter (god, spotter is sooooo cool!), next release we hope to integrate a new debugger and if planets align, a new Coder. > - We introduced OSWindow as a preview, a tool which will allow us to do a lot of years waited features: start UI from image instead from VM (transmiting to the used the decision of having one or not), multi-windows, a vectorial UI instead the good-but-old bitblt we have now. > - We enhanced Athens and introduced the new TxModel. We still do now achieve our objective of migrate our morphic drawing mechanism to athens, but this is a lot of work and will take some time. > - We have improved a lot the development cycle with the introduction of smart suggestions, the upcoming smart breakpoins and reflectivity. > - And of course, we have worked a lot in the cleaning of the system (an invisible and ungrateful work, believe me) > > And this is just a glimpse, what I wrote this morning before breakfast, wanting to thank all of you to let me be part of this super cool community, and wanting to have a toast with you: > > For a 2015 with more stories, more adventures, more Pharo! > > Esteban > >

Dec. 29, 2014

Re: [Pharo-dev] The Smalltalk Renaissance Program

by horrido

>From "The City on the Edge of Forever": KIRK: Then what is it? GUARDIAN: *A question.* Since before your sun burned hot in space and before your race was born, I have awaited a question. KIRK: What are you? GUARDIAN: I am the Guardian of Forever. KIRK: Are you machine or being? GUARDIAN: I am both and neither. I am my own beginning, my own ending. ----- Clearly, I need to explain myself in greater detail... The efforts of organizations such as STIC and ESUG are laudable. Nevertheless, they have failed to popularize Smalltalk. Today, *Smalltalk is a largely forgotten language*. This can be seen at the TIOBE index where Smalltalk has literally fallen off a cliff (it used to be on the top 100 list, but has since disappeared). At Redmonk and langpop.corger.nl, Smalltalk is somewhere around the 65th position! Smalltalk does not get much developer attention. It doesn't get talked about in the press like Dart and JavaScript and Java do. The language is almost never on the minds of CEOs and CTOs, the business decision makers. I believe I know why. Smalltalk organizations have focussed too much on /technical merit/, and not enough on PR and marketing. Understandable, since engineers are /technically-minded/ and not so much into human behaviour. I think we need to treat developers and businessmen like consumers. We need to sell Smalltalk to them in the same way we sell iPhones and PlayStations. In other words, we need to build /hype/. Let's face it: at the best of times, the subject of Smalltalk is rather staid. STIC and ESUG and the Smalltalk Foundation are not likely to change this. *I want Smalltalk Renaissance to change this.* The Smalltalk Renaissance Program is a highly focussed campaign. Like the language itself, I want to Keep It Simple. (That's why I'm trying to keep the website clean and free of excess baggage.) The SRP cannot succeed without /your/ involvement, your participation. I am not much more than the curator and editor for Smalltalk Renaissance, although I'm also formulating the short-term and long-term strategy. (You can call me "Generalissimo" Eng. ;-) ) One of the things I intend to do is ask members of the Smalltalk community to submit /fresh/ essays and articles on Smalltalk. I have a list of essay topics prepared, carefully chosen for their relevance and impact on the future of Smalltalk. I shall be asking people to pick a topic and run with it. If there are multiple submissions for a particular topic, I shall choose the best one, edit it, and post it on Smalltalk Renaissance. *I guarantee you will look good!* Make no mistake, this is a critical step. *These essays will address the concerns of non-Smalltalk developers.* You need to make compelling arguments. Then we promote these articles and essays on Reddit and Hacker News and so on. In the near future, I will also submit Smalltalk articles to the IT press, such as Wired and InfoWorld. These articles may well benefit from /your contributions/. Another important piece of the strategy is to obtain corporate sponsorship. If not for Apple, the Swift language would never have gotten so much mindshare. If not for Google, Go would've failed to gain a significant following. If not for Microsoft, C# would've been forgotten. In today's highly competitive programming language field, if you don't have a big name backer, you're already behind the eight ball. Grass roots are unlikely to succeed. Getting the imprimatur of a major technology company is a PR coup of inestimable value. But it's also vital for another reason. In the longer term, I want to launch software projects that improve on the Smalltalk technology. Projects such as extending the tooling around the Smalltalk environment (which has been criticized for not playing well with existing file-based tooling). Projects such as improving interoperability with existing (Windows-based) infrastructures in the enterprise (which has been a source of criticism from the likes of Robert Martin). These projects must be financed because open source volunteerism isn't enough, not by a long shot. And this is why we need corporate sponsorship. Before I make a pitch to a CEO, Smalltalk Renaissance must achieve some degree of legitimacy. It can do this by signing up well-known names from the Smalltalk community. Names such as the late James Robertson or StÃ©phane Ducasse. I already have a draft letter prepared for an important CEO. I'm only waiting for a list of SRP signatories before firing off the letter. (Hint, hint.) This is what I've come up with so far in my strategic planning. It's a work-in-progress. As for Pharo, I've downloaded it and played with it briefly. As far as I can tell, the IDE is not much different from Squeak. Like I said, the design has been tweaked and improved, but I don't see anything groundbreaking. Maybe you and I have different ideas of what "groundbreaking" means. Nevertheless, as another poster indicated, we can leave this for the future. For the time being, we need to make Smalltalk, and Pharo in particular, more attractive to the Enterprise. I'm sure Pharo is doing this. Kudos. -- View this message in context: http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797313.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 29, 2014

Re: [Pharo-dev] Jun4Pharo so exciting :)

by Sven Van Caekenberghe

> On 29 Dec 2014, at 15:36, stepharo <stepharo(a)free.fr> wrote: > > https://www.youtube.com/watch?v=sH_P5otiWJM&feature=youtu.be It certainly looks nice, but what is Jun exactly ?

Dec. 29, 2014

Re: [Pharo-dev] ToolRegistry need to support multiple registrations per tool

by stepharo

Yes less is more ;) Le 29/12/14 12:20, Marcus Denker a Ã©crit : >> On 19 Dec 2014, at 16:21, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >> >> There used to be a class called AppRegistry in Pharo, which was nothing more than a selection in a list, with an API's for adding/removing options and changing the current selection. (only through popups, but that could easily be extended to provide settings entries). The code might've needed a bit of cleanup (making collection of available options weak, for example), but the concept was sound. >> >> IMHO, rather than the delegation through ToolRegistry, it would've been nice to have built upon AppRegistry and have Inspector/Browser/Debugger as subclasses of that. >> Then you'd still maintain indirection of which ToolX are available / currently in use, and code would be nice and understandable like: >> ToolX open instead of >> ToolRegistry openToolX. >> >> When new tools classifications are added, you'd also avoid progressively extending ToolRegistry into a behemoth of #openToolX etc. methods (ref. UIManager). >> >> Sadly, SoundService was the only real App classification in use, and the code seems to have been removed in 4.0. >> > In retrospect, maybe I should have unified towards the AppRegistryâ¦ but on the other hand, the good thing is that we now have *one* mechanism, not 2-and-a-half > mixed like it used to be. This means we can replace/enhance it as neededâ¦ > > Marcus > > >

Dec. 29, 2014

Re: [Pharo-dev] Source code formatting guidelines

by Marcus Denker

> On 29 Dec 2014, at 15:30, stepharo <stepharo(a)free.fr> wrote: > > As far as I remember it was just the stock RB(Configurable?)Formatter with custom settings. Let me dig out my Dolphin Image. > > This is the same in Pharo. Lukas improved it. I think the âtoo many line breaksâ is actually a bug. It adds line breaks where it should not. >> >>>> >>>> Especially as the format hotkey doesn't work reliably on Mac OS X - >>>> still have to chase why. >>> >>> Yes I would like to have. >>> >>>> >>>>> And concretely I would like to format all the code. I'm doing that when >>>>> I change something. >>>> >>>> CU, >>>> >>>> Udo >> >> >> >> >> > >

Dec. 29, 2014

Jun4Pharo so exciting :)

by stepharo

https://www.youtube.com/watch?v=sH_P5otiWJM&feature=youtu.be

Dec. 29, 2014

Re: [Pharo-dev] A toast

by stepharo

Thanks! http://pharoweekly.wordpress.com/2014/12/29/a-toast/ Le 29/12/14 13:59, Esteban Lorenzano a Ã©crit : > Hello Pharoers, > > (sorry for the long post) > > I'm on holidays so I've been silent this latests days, but I didn't want to let the opportunity goes to propose a toast :) > This year has been a great year (yeah, but not like those annoying facebook cards), one year where we have worked itensively in the patient consolidation of several lines of work. > This has been possible thanks to the great improvement that we have made in the Pharo process itself, which required (and still requires) a massive amount of effort: Since I arrived here (but not necessarily*because* I arrived here: this is the work of everyone in Pharo community, I'm just pointing to what I've seen and collaborated :P), we have changed a lot of things: > > - we have deployed a solid CI infrastructure that can handle our integration cycle without too much complications. Even if we still find problems time to time, this has been an incredible step forward. > - thanks to this we have been able to change our release cycle from "it happens when we believe is ready" to time-boxed releases, so we have created Pharo 1.4, 2.0 and this year what, for me, is one of the most complete and cool releases (up to now) that we have produced: Pharo 3.0. > - We have increased massively the amount of tests in the system (no sure what is the percentage, but is high), so we have been able to change core parts in the system without causing too much pain to developers (yeah, we know there have been some errors some times, but well... "errare humanum est", and I think we have learned from the process and now we do not make same mistakes... in any case they are new mistakes :P). > - We have made huge steps in the "Pharo modularisation project", thanks to the Pharo-minimal images and work we have started to move all into a repeatable configuration (thanks to metacello and tools developed for this). > - We have also incorporated the VM building to this process and testing cycle, so is a lot easier for everyone to build their own VM (if needed), and for us we can be sure (as sure as possible at least) VM is in good shape. > - We have improved documentation and release new books. People have working a lot in a lot of cool and instructive videos that have moved our "learning curve" several steps ahead. > > And this is just one part of the "invisible, ant work of everyday", in the visible part, I will not bore (more than needed :P) with details about previous releases, so I will just point some of the great things we have made for the upcoming release, Pharo 4: > > - Thanks to GTools, we are slowly going to a better set of tools, with new ways of see/handle old things. This is the most visible change this year (and it has caused the most flamed wars, but well... we are a passionate community). This release we have a new inspector, playground and spotter (god, spotter is sooooo cool!), next release we hope to integrate a new debugger and if planets align, a new Coder. > - We introduced OSWindow as a preview, a tool which will allow us to do a lot of years waited features: start UI from image instead from VM (transmiting to the used the decision of having one or not), multi-windows, a vectorial UI instead the good-but-old bitblt we have now. > - We enhanced Athens and introduced the new TxModel. We still do now achieve our objective of migrate our morphic drawing mechanism to athens, but this is a lot of work and will take some time. > - We have improved a lot the development cycle with the introduction of smart suggestions, the upcoming smart breakpoins and reflectivity. > - And of course, we have worked a lot in the cleaning of the system (an invisible and ungrateful work, believe me) > > And this is just a glimpse, what I wrote this morning before breakfast, wanting to thank all of you to let me be part of this super cool community, and wanting to have a toast with you: > > For a 2015 with more stories, more adventures, more Pharo! > > Esteban >

Dec. 29, 2014