September 2014 - Pharo-dev - lists.pharo.org

Why Bloc?
by Sean DeNigris Sept. 18, 2014

Sept. 18, 2014

<not trolling, genuinely curious> When SimpleMorphic was released, the problem was that we didnât know how to integrate it into our existing Morphic. Also, the problem with starting with CUISâs Morphic was IIRC that it didnât properly handle internationalization. Now that weâre heading toward a total replacement anyway, why start from scratch when there are these projects, Morphic 3, and who-knows-what-else already available? </not trolling, genuinely curious> - S

4 8

[pharo-project/pharo-core]
by GitHub Sept. 18, 2014

Sept. 18, 2014

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

1 0

[pharo-project/pharo-core] 8e48ab: 40231
by GitHub Sept. 18, 2014

Sept. 18, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 8e48ab60bf74e2c1c11c78517c08a26eb44b4a7a https://github.com/pharo-project/pharo-core/commit/8e48ab60bf74e2c1c11c7851… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-18 (Thu, 18 Sep 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script231.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40231.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/widget API/selectedTab_.st A Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/widget API/tabSelected_.st Log Message: ----------- 40231 14030 MorphicTabManagerAdapter>>doesNotUnderstand: #tabSelected: https://pharo.fogbugz.com/f/cases/14030 http://files.pharo.org/image/40/40231.zip

1 0

[pharo-project/pharo-core]
by GitHub Sept. 18, 2014

Sept. 18, 2014

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

1 0

[Review: 12111] (Date readFrom: '4.2.2013' readStream pattern: 'd.m.yy') ==>> 4 February 2020
by Max Leske Sept. 17, 2014

Sept. 17, 2014

In the spirit of Markusâ cleanup please review this suggested fix to date parsing (from november 2013 originallyâ¦). Iâve ported the fix forward to 40 (which has the same issue). https://pharo.fogbugz.com/f/cases/12111/Date-readFrom-4-2-2013-readStream-p… Cheers, Max

1 0

[ANN] Pharo Sprint Lille 26th september
by Marcus Denker Sept. 17, 2014

Sept. 17, 2014

What? Pharo Sprint When? Friday, 26th September, starting at 10:00am Where? RMoD, Inria Lille, Building B, third floor http://rmod.lille.inria.fr/web/pier/contact As the building is not open to the public, please contact us before if you plan to come.

2 3

Re: [Pharo-dev] [squeak-dev] Re: The Dilemma: Building a Futuristic GUI for Ephestos
by Eliot Miranda Sept. 17, 2014

Sept. 17, 2014

On Tue, Sep 16, 2014 at 2:55 PM, Chris Muller <ma.chris.m(a)gmail.com> wrote: > >> On Tue, Sep 16, 2014 at 2:18 PM, Esteban A. Maringolo > >> <emaringolo(a)gmail.com> wrote: > >> > 2014-09-16 14:37 GMT-03:00 Sebastian Sastre > >> > <sebastian(a)flowingconcept.com>: > >> > > >> >> Well, a while ago in the business list Iâve raised the idea that > making > >> >> Pharo able to do native OS windows would help it to gain market space > >> >> (as in > >> >> the opposite of staying at the margins of it). > >> >> > >> >> So, Iâd be very positively curious about being able to use Pharo to > do > >> >> multiplatform native apps > >> > > >> > The trend is shifting to mobile devices, iOS and Android are eating > >> > the whole market. So if it is about the potential market size, native > >> > mobile (tablets/phones/TVs) should come as the first option, before > >> > desktop. > >> > >> +1. Desktop apps are "dead" aren't they? I'm doubtful that native > >> windows would help Smalltalk's popularity, as evidenced, I guess, by > >> the fact VA and VW have supported them for a long time; did they take > >> over the world yet? > >> > >> > For development, native windows could prove very useful. > >> > >> How so? For me, one of the worst aspects of trying to develop in > >> VisualAge or VisualWorks *is* the multiple host windows. It makes it > >> virtually impossible to work in more than one image, and reinforces > >> the "grand cathedral" thinking about Smalltalk; e.g. you're not > >> supposed to want or need anything outside your one, true, image. > >> Dinosaur! > >> > >> I constantly work in multiple images, not only for separate projects > >> but for the ability to quickly and easily fork images for multicore > >> processing on the same project. Other times simply to try something > >> temporary and possibly dangerous. The memory isolation is critical > >> for productivity, the UI isolation for usability, and the multi-core > >> capability for performance. > >> > >> I think we should focus on how to move to more and smaller > >> intercommunicating images rather than one big image. I understand its > >> appeal for _deploying_ an off-the-shelf desktop app, but I'm not aware > >> of any other use-cases where multiple host windows would be preferable > >> to one host window per image. > > > > > > That all makes sense from an experienced Smalltalker's POV. But for > people > > exploring the technology the lack of native windows is usually a huge > > turn-off and often reason to reject the technology. The nice thing about > > Vassili's work is that it allows one to have *both*, without losing > window > > state, and one can switch dynamically, and, IIRC, mix both, e.g. for > > development. So it isn't an exclusive choice. > > Ah, good. Choice is good. :) > > > Re VisualWorks' support for native windows it was an essential component > to > > VW staying in the market-place. If it hadn't supported native windows it > > would have died the commercial death long ago. Pre-web, one /had/ to > have > > native windows for industry, and now with mobile native look and feel is > > even more important. Further, VWs huge lack in its GUI was lack of > support > > for native widgets. We always used to tout MSWord's use of emulated > widgets > > (apparently for performance reasons) as a defence but it didn't convince. > > The customer was always provided with poor emulations and a limited > supply. > > IMO, native widgets would have made a big difference in hwo > well-received VW > > was for GUI applications, where those using Windows could always turn to > > VSE. > > Yes, I don't doubt that at all, especially during the time when > Windows NT / XP was the defacto platform one could expect anywhere and > everywhere. > > I am curious now, however, in this technologically-splintered world > where Windows XP dying out, Windows 7 barely hanging on, everybody > hating Windows 8, and the promise of cheap upgrade to Windows 9, Plus > don't forget OSX widgets and then all the "widgets" people use on > their phones and tablets being basically different from app to app: > what IS "native" widgets these days? Native widgets means simply use of the platforms native widget set in constructing user interfaces. I don't dsee different widgets across iOS devices. I see lots of consistency. > I wonder what those manager > folks who shunned the > non-native-but-perfectly-usable-and-in-some-cases-better widgets are > asking for now? :) > I assume good looking applications using native widgets in the host look-and-feel that follow the platform's style and usability guidelines. Thats a reasonable request. Look at how coherent and well-engineered the interface components in something like Apple's iOS is are and one soon realises one the one hand the interface quality is high and on the other that the only feasible way to construct interactive applications in that context is to build it out of those widgets, not emulate, not provide an alternative. There are exceptions, e.g. parts of games where all one needs is touch events and all imagery is custom. But for stereotypical interaction one surely has to use native widgets. -- best, Eliot

1 0

Monticello superslow/freezing
by phil＠highoctane.be Sept. 17, 2014

Sept. 17, 2014

Monticello kinds of freezes my image for a *very* long time. Long, meaning that it never completes I guess. Memory use shoots through the roof. What could cause that? I have been saving more than 200 versions of my package. Thanks for some advice from the trenches. Phil

4 6

Multiple lines parameters editable spec interface
by Serge Stinckwich Sept. 17, 2014

Sept. 17, 2014

Hi Pharo, I would like to design a spec UI for modifying a list of parameters. One line will be composed with the name of the parameter and one editable field. Should I use a MultipleColumnListModel or should I define a new widget of one line and after that composed multiple instance of this widget ? Thank you. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

1 0

[pharo-project/pharo-core]
by GitHub Sept. 17, 2014

Sept. 17, 2014

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

1 0