- Pharo-dev - lists.pharo.org

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

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

Sept. 17, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: ce818b3f743a0a0c94d86ec1471873b2a79c65ab https://github.com/pharo-project/pharo-core/commit/ce818b3f743a0a0c94d86ec1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-17 (Wed, 17 Sep 2014) Changed paths: R Graphics-Display Objects.package/ColorForm.class/instance/color manipulation/ensureTransparentColor.st M ScriptLoader40.package/ScriptLoader.class/instance/ci/compileNewUpdateMethodSilentlyPreLoad_postLoad_.st A ScriptLoader40.package/ScriptLoader.class/instance/ci/publicChangesSilently_user_password_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script230.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40230.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40230 14027 ensureTransparentColor is unused and looks dead https://pharo.fogbugz.com/f/cases/14027 http://files.pharo.org/image/40/40230.zip

1 0

[ANN] SciSmalltalk v0.14
by Serge Stinckwich Sept. 17, 2014

Sept. 17, 2014

Dear all, we are to happy to announce SciSmalltalk v0.14 SciSmalltalk is a new Smalltalk project, similar to existing scientific libraries like NumPy, SciPy for Python or SciRuby for Ruby. SciSmalltalk already provide the following basic functionalities: - complex and quaternions extensions, - random number generators, - fuzzy algorithms, - Didier Besset's numerical methods, - Ordinary Differential Equation (ODE) Solver. Version 0.14 includes new work from Werner Kassens about function fittings: https://github.com/SergeStinckwich/SciSmalltalk/wiki/Math-FunctionFit and math accuracy framework: https://github.com/SergeStinckwich/SciSmalltalk/wiki/Math-AccuracyFramework SciSmalltalk project web page is here: https://github.com/SergeStinckwich/SciSmalltalk All the code is available under the MIT licence. We have more than 506 green unit tests and we run a CI job here: https://ci.inria.fr/pharo-contribution/job/SciSmalltalk/ This version should work on Pharo 3.0/4.0 and also Squeak 4.5 (to be confirmed). We are a small community, we are looking for more volunteers to contribute code and documentation. Please join us at : https://groups.google.com/forum/#!forum/scismalltalk -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

1 0

Re: [Pharo-dev] Monticello superslow/freezing
by Stephan Eggermont Sept. 17, 2014

Sept. 17, 2014

What kind of repo is that? Stephan

2 1

Pharo Launcher Impressions
by Sean P. DeNigris Sept. 17, 2014

Sept. 17, 2014

Pretty cool! And the installers are a great touch. A few ideas: 1. Wouldn't it make sense to cache the latest e.g. Pharo stable? 2. I often like to launch my images from Mac Terminal windows so I can see stdout. Would that be difficult to add? I still think the default Mac image location is wrong in principle - user images belong under Documents, not Library - but at least it's changeable now! For example, I can't use my pharo-ui script to launch via terminal because ~/Library does not show up in the dialog to chose an image /because it's not for documents/. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-Launcher-Impressions-tp4778314.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

7 9

config change ci server Pharo4: run AsmJIT tests
by Marcus Denker Sept. 17, 2014

Sept. 17, 2014

Hi, We disabled running ASMJit tests before releasing Pharo2â¦ (because of random crashed back then). Of course we forgot to turn it on again. I did that now. This is https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-A-L/ Marcus

1 0

[pharo-project/pharo-core] 3350b9: 40229
by GitHub Sept. 17, 2014

Sept. 17, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 3350b900bb8f285775fc46e196411a043845ee1a https://github.com/pharo-project/pharo-core/commit/3350b900bb8f285775fc46e1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-17 (Wed, 17 Sep 2014) Changed paths: M Nautilus.package/AbstractNautilusUI.class/class/menu/classesMenu_.st M Nautilus.package/AbstractNautilusUI.class/instance/test creation/createTestForSelectedClass.st A Ring-Core-Kernel.package/RGMetaclassDefinition.class/instance/accessing/category.st A Ring-Core-Kernel.package/RGMetatraitDefinition.class/instance/accessing/category.st A Ring-Tests-Kernel.package/RGMetaclassDefinitionTest.class/README.md A Ring-Tests-Kernel.package/RGMetaclassDefinitionTest.class/definition.st A Ring-Tests-Kernel.package/RGMetaclassDefinitionTest.class/instance/testing/testAsMetaclassDefinition.st A Ring-Tests-Kernel.package/RGMetatraitDefinitionTest.class/README.md A Ring-Tests-Kernel.package/RGMetatraitDefinitionTest.class/definition.st A Ring-Tests-Kernel.package/RGMetatraitDefinitionTest.class/instance/testing/testAsClassTraitfinition.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script229.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40229.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R SmartSuggestions.package/SugsNautilusContext.class/instance/tools/tools.st Log Message: ----------- 40229 14029 Smart Suggestion Implementors does not work in Nautilus anymore https://pharo.fogbugz.com/f/cases/14029 14023 Nautlilus: Jump to test class should not only work on instance side https://pharo.fogbugz.com/f/cases/14023 14012 RGMetaclassDefinition and RGMetatraitDefinition DNU #category https://pharo.fogbugz.com/f/cases/14012 http://files.pharo.org/image/40/40229.zip

1 0