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

Re: [Pharo-dev] process to collaborate on cleaning morphic

by Pharo4Stef

On 29 Jan 2014, at 16:37, J.F. Rick <self(a)je77.com> wrote: > On Wed, Jan 29, 2014 at 3:36 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > I would like to continue in the direction started with the Morphic-Core. It's a subset of Morphic that is able to be loaded into a headless image, initialize itself and show world with one basic responsive morph. > > There's a question of what is necessary for a modern GUI core. To me, we need to get out of BitBlt rendering completely and towards vectors. Reliance on BitBlt makes Pharo seem slow and outdated. + 1 This is why I asked igor to work on Athens and we are nearly there. We need this ^%^%&^( texteditor and to move the morph to drawOnAtehns however it will not come automagically. When ronie will be back in chile Igor and christophe should pay program on the text editor. > Pixelation is so early 1990s. Novices also don't understand that a slow GUI isn't indicative of everything being slow. There's no reason Pharo's UI can't be fast enough that you can't tell the difference between it and a native app. That would do a lot to make Pharo more palatable to newcomers. First impressions are critical. + retina :) > We should also make it easy for people to build animations and build them into the core tools (when it makes sense). Most modern OSs feature great support for animation. Even if these things are largely eye candy, they do change people's perceptions. I'd love to be able to do something like this: > aMorph resizeToBounds: (100 @ 100 extent: 200 @ 200) inSeconds: 2. Did you check Viva on petitsBazars on my repo because this is proto that igor built for a GSOC project (that failed) > Speaking of which, it would be nice if orientation could be included into the equation. Perhaps support for affine transforms would be standard. There also should be substantial support for vector graphics. The Athens SVG input is a good step forward, but I'd like to see something that seems very Pharo-native and that can be exported to SVG, rather than something that seems very close to SVG XML (as is now the case). Ideally, I'd like to do the old demo of rotating a browser and still using it but have it still look smooth (i.e., no pixelation). Yes I think that this is already possible (but without text) > Another thing to perhaps address is how morphs are controlled and resized. Currently, when we change the extent, then the top left corner remains the same. For most cases, keeping the center the same would be more intuitive; vvvv does that and is fairly easy for programming novices to use. It would also allow us to combine rotation and scaling in some ways: > aMorph rotateAndScaleBottomLeftTo: 300 @ 20. "keep the center stationaryâ I (with esteban) already cleaned the margin mess by introducing Margin and it cleaned some code. We cleaned a lot 200 users of layoutFrame with Igor. Nobody noticed it but we fixed a lot of code. Stef > > Cheers, > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick

Jan. 29, 2014

Re: [Pharo-dev] process to collaborate on cleaning morphic

by Pharo4Stef

w > > What about a brutal scheme, independent of all code quality considerations: > > - dedicate a Pharo release process *only* to Morphic cleaning so people > will know it gona be brutal This is not that easy. Because we should really learn about morph internals. And this what we were planning to do with fernando but he left. and we had to reorganise. stef > - mark as deprecated all morphic methods unsused in the system. When a > client (like me with DrGeo), use some of the deprecated method, fill a > bug ticket, then discussion should arise about what to do: > i. unmark it as deprecated > ii. move it in external package > iii. adoption by the client in its application code > - do the same with unused classes from the Morph hierarchy. > > > I guess Steph already did some of this in the past. > > The idea is you don't want to refactor unused code, right? > > I would like to continue in the direction started with the Morphic-Core. It's a subset of Morphic that is able to be loaded into a headless image, initialize itself and show world with one basic responsive morph. > We can clean it and continue with basic fonts support, windows support etc. Every step will produce one package that can be loaded on top others, will heave well defined dependencies, will be small in size, easier to understand, maintain and refactor. > It looks hard but in fact it is not so horrible. In one of my previous testing image I was able to reach the state where Morphic-Core was clear - generated no new unimplemented classes and similar mess. > We only need to define it as a common goal. > > Cheers, > -- Pavel > > > > -- > Dr. Geo http://drgeo.eu > > >

Jan. 29, 2014

Re: [Pharo-dev] process to collaborate on cleaning morphic

by Pharo4Stef

We will get there :) Stef On 29 Jan 2014, at 15:36, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > 2014-01-29 Hilaire Fernandes <hilaire.fernandes(a)gmail.com> > Le 28/01/2014 18:41, Pharo4Stef a Ã©crit : > > this is years since I clean Morphic (may be Iâm that good at it) but this is important to > > go step by step. So I would really like to get a list of simple actions. > > Do you have an idea? > > > What about a brutal scheme, independent of all code quality considerations: > > - dedicate a Pharo release process *only* to Morphic cleaning so people > will know it gona be brutal > - mark as deprecated all morphic methods unsused in the system. When a > client (like me with DrGeo), use some of the deprecated method, fill a > bug ticket, then discussion should arise about what to do: > i. unmark it as deprecated > ii. move it in external package > iii. adoption by the client in its application code > - do the same with unused classes from the Morph hierarchy. > > > I guess Steph already did some of this in the past. > > The idea is you don't want to refactor unused code, right? > > I would like to continue in the direction started with the Morphic-Core. It's a subset of Morphic that is able to be loaded into a headless image, initialize itself and show world with one basic responsive morph. > We can clean it and continue with basic fonts support, windows support etc. Every step will produce one package that can be loaded on top others, will heave well defined dependencies, will be small in size, easier to understand, maintain and refactor. > It looks hard but in fact it is not so horrible. In one of my previous testing image I was able to reach the state where Morphic-Core was clear - generated no new unimplemented classes and similar mess. > We only need to define it as a common goal. > > Cheers, > -- Pavel > > > > -- > Dr. Geo http://drgeo.eu > > >

Jan. 29, 2014

Re: [Pharo-dev] Issues 12717 and 12684

by Nicolas Cellier

2014-01-29 Sean P. DeNigris <sean(a)clipperadams.com> > Nicolas Cellier wrote > > So maybe PropertyBinding could do it... > > Where is the "binding"? It's purpose is announcing changes. I don't get how > "binding" epxresses that intent. What am I missing? > > > Binding is so generic... The question is what do you bind? With any value holder, you somehow bind several dependents of a value... With the annoucement, your intention is to monitor a change of value. MonitoredBinding? MonitoredValue? > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Issues-12717-and-12684-tp4739761p4740176.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Jan. 29, 2014

Re: [Pharo-dev] Pharo Success Story: Reflex Vacances

by Torsten Bergmann

> runs 100% in Pharo + Iliad + MongoDB. "Look ma - no apache or nginx". According to responses it runs "KomHttpServer/7.1.3 (unix)". Also for resources like images. And it is fast. Would be interesting to know more about the architecture, speed of machine, optimizations done, ... Anyone know more about it and able to share some insights. Thx T.

Jan. 29, 2014

Re: [Pharo-dev] Issues 12717 and 12684

by Sean P. DeNigris

Nicolas Cellier wrote > So maybe PropertyBinding could do it... Where is the "binding"? It's purpose is announcing changes. I don't get how "binding" epxresses that intent. What am I missing? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issues-12717-and-12684-tp4739761p4740176.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 29, 2014

Re: [Pharo-dev] Issues 12717 and 12684

by Nicolas Cellier

2014-01-29 Nicolai Hess <nicolaihess(a)web.de> > 2014-01-29 Sean P. DeNigris <sean(a)clipperadams.com> > >> Nicolai Hess wrote >> > And I don't like the name either. >> > I would prefere Binding or ValueBinding. >> >> Guys, I don't love the name either, but can we do a little better than "I >> don't like it". The purpose of ValueHolder's existence was to notify >> changes >> to its value. A reactive variable, from FRP, kinda-sorta does that. How >> does >> Binding = 'I will notify of changes to my value'?! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Issues-12717-and-12684-tp4739761p4740024.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > We don't need to argue about names, > ReactiveVariable is not wrong, I just don't like it:-) > > I just wanted to emphase on the missing discussion. > Doing this change after the Pharo3 release may be more > difficult than now. Even if it is a bit late. > So, I am happy we have at least both. (We should > try to force the use of the new name.) > > > (Binding or PropertyBinding is how it is called in > QTs QML) > > > Nicolai > Binding already has another semantic in Smalltalk. It's a kind of value holder used for shared variables (global/class/pool variables). It is not equipped with events mechanism nor mutex. So maybe PropertyBinding could do it...

Jan. 29, 2014

Re: [Pharo-dev] iPad version does not work ?

by Esteban Lorenzano

oksâ¦ I will take a lookâ¦ as soon as I can :S (damnâ¦ I need to learn how to do a mitosisâ¦) On 29 Jan 2014, at 17:28, jannik laval <jannik.laval(a)gmail.com> wrote: > I confirm that it does not work: the simulator compile (but not the non-simulator). > Then the image cannot be open: I have a white screen. > Here is my process: > > === > 1) git clone https://github.com/pharo-project/pharo-vm.git > 2) in ./image dir prepare a VMMaker image (including download of a pharo 2.0): > ./newImage.sh > > 3)open the generated.image and execute: > === > PharoIPhoneBuilder buildIPhone. > â or â > PharoIPhoneBuilder buildIPhoneSimulator. > > 4) Generate your iPhone image in iosbuild/resources/ > ./generate.sh > > 5) In dir ./build: > sh build.sh > === > > Cheers, > Jannik > > > > 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> > and btwâ¦ > > iosbuild/resource$ ./generate.sh > > should generate a 1.4 image that *should* work in ipad (no idea if that will be the case, its been more than 6months since I do not test it and vm changed since then). > > Esteban > > > On 29 Jan 2014, at 10:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> PharoIPhoneBuilder buildIPhone. >> >> it should generate all sources and a âbuild.shâ >> >> then >> >> build$ sh build.sh >> >> will generate an xcode project. >> >> and let me rememberâ¦ mmmâ¦ yeah, that was all :) >> >> >> >> On 29 Jan 2014, at 08:10, jannik laval <jannik.laval(a)gmail.com> wrote: >> >>> Hi Esteban, >>> >>> Hum, this means that my instructions are outdated. >>> Where are the right instructions ? The ones on Github do not mention IOS. >>> >>> Cheers, >>> Jannik >>> >>> >>> 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> >>> >>> On 29 Jan 2014, at 00:18, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> >>>> >>>> >>>> >>>> On Tue, Jan 28, 2014 at 2:46 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> because you are not following the instructions ;) >>>> >>>> basicallyâ¦ you can generate them by: >>>> >>>> build$ ../scripts/extract-commit-info.sh >>>> >>>> I asked for this info last week ;-). Thanks! >>> >>> hey! I answered you! :P >>> >>> >>>> >>>> But this is alarming: >>>> >>>> McStalker.pharovm$ ./scripts/extract-commit-info.sh >>>> readlink: ./scripts/extract-commit-info.sh Invalid argument >>>> >>>> I suggest changing >>>> SCRIPT_DIR=`readlink "$0"` || SCRIPT_DIR="$0"; >>>> to read >>>> SCRIPT_DIR=`readlink "$0" >/dev/null` || SCRIPT_DIR="$0"; >>>> >>>> >>>> Esteban >>>> >>>> On 28 Jan 2014, at 23:15, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>> >>>>> Thank you, I am trying the latest one. >>>>> >>>>> When compiling for IOS, I have an error in sqSCCSVersion.h >>>>> >>>>> #include "vmVersionInfo.h" // defines REVISION_STRING >>>>> the file is not found. >>>>> >>>>> Anyone knows where is this file ? >>>>> >>>>> Cheers, >>>>> Jannik >>>>> >>>>> On Jan 28, 2014, at 8:58 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >>>>> >>>>>> jannik the latest vm is not on gitoruous anymore but git >>>>>> >>>>>> >>>>>> On 27 Jan 2014, at 22:03, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>>> >>>>>>> Hum, have I the correct repository ? >>>>>>> I used this one: https://git.gitorious.org/cogvm/cog-osx.git >>>>>>> >>>>>>> But, I just saw that this one exists: https://github.com/pharo-project/pharo-vm >>>>>>> I should use it no? >>>>>>> >>>>>>> Jannik >>>>>>> >>>>>>> >>>>>>> 2014-01-27 Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>> 1.4 and 2.0 worked out of the boxâ¦ and after my latest integration, 3.0 should work too. >>>>>>> I will take a look as soon as I have half and hour to spare. >>>>>>> >>>>>>> Esteban >>>>>>> >>>>>>> >>>>>>> On 27 Jan 2014, at 14:27, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>>>> >>>>>>>> Hi list, >>>>>>>> >>>>>>>> Does anyone try to load Pharoon iPad ? >>>>>>>> In the past, the version 1.4 worked with XCode 4.4. >>>>>>>> >>>>>>>> I just tried to recompile it with the new XCode (5.0.2). >>>>>>>> The VM seems to work, but the pharo 1.4 image freezes. >>>>>>>> >>>>>>>> Any idea ? >>>>>>>> >>>>>>>> -- >>>>>>>> ~~Jannik Laval~~ >>>>>>>> Ãcole des Mines de Douai >>>>>>>> Enseignant-chercheur >>>>>>>> http://www.jannik-laval.eu >>>>>>>> http://car.mines-douai.fr/ >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ~~Jannik Laval~~ >>>>>>> Ãcole des Mines de Douai >>>>>>> Enseignant-chercheur >>>>>>> http://www.jannik-laval.eu >>>>>>> http://car.mines-douai.fr/ >>>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>>> >>>> -- >>>> best, >>>> Eliot >>> >>> >>> >>> >>> -- >>> ~~Jannik Laval~~ >>> Ãcole des Mines de Douai >>> Enseignant-chercheur >>> http://www.jannik-laval.eu >>> http://car.mines-douai.fr/ >>> >> > > > > > -- > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ >

Jan. 29, 2014

Re: [Pharo-dev] iPad version does not work ?

by jannik laval

I confirm that it does not work: the simulator compile (but not the non-simulator). Then the image cannot be open: I have a white screen. Here is my process: === 1) git clone https://github.com/pharo-project/pharo-vm.git 2) in ./image dir prepare a VMMaker image (including download of a pharo 2.0): ./newImage.sh 3)open the generated.image and execute: === PharoIPhoneBuilder buildIPhone. -- or -- PharoIPhoneBuilder buildIPhoneSimulator. 4) Generate your iPhone image in iosbuild/resources/ ./generate.sh 5) In dir ./build: sh build.sh === Cheers, Jannik 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> > and btw... > > iosbuild/resource$ ./generate.sh > > should generate a 1.4 image that *should* work in ipad (no idea if that > will be the case, its been more than 6months since I do not test it and vm > changed since then). > > Esteban > > > On 29 Jan 2014, at 10:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > PharoIPhoneBuilder buildIPhone. > > it should generate all sources and a "build.sh" > > then > > build$ sh build.sh > > will generate an xcode project. > > and let me remember... mmm... yeah, that was all :) > > > > On 29 Jan 2014, at 08:10, jannik laval <jannik.laval(a)gmail.com> wrote: > > Hi Esteban, > > Hum, this means that my instructions are outdated. > Where are the right instructions ? The ones on Github do not mention IOS. > > Cheers, > Jannik > > > 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> > >> >> On 29 Jan 2014, at 00:18, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> >> >> >> On Tue, Jan 28, 2014 at 2:46 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: >> >>> because you are not following the instructions ;) >>> >>> basically... you can generate them by: >>> >>> build$ ../scripts/extract-commit-info.sh >>> >> >> I asked for this info last week ;-). Thanks! >> >> >> hey! I answered you! :P >> >> >> >> But this is alarming: >> >> McStalker.pharovm$ ./scripts/extract-commit-info.sh >> readlink: ./scripts/extract-commit-info.sh Invalid argument >> >> I suggest changing >> SCRIPT_DIR=`readlink "$0"` || SCRIPT_DIR="$0"; >> to read >> SCRIPT_DIR=`readlink "$0" >/dev/null` || SCRIPT_DIR="$0"; >> >> >> Esteban >>> >>> On 28 Jan 2014, at 23:15, jannik.laval <jannik.laval(a)gmail.com> wrote: >>> >>> Thank you, I am trying the latest one. >>> >>> When compiling for IOS, I have an error in sqSCCSVersion.h >>> >>> #include "vmVersionInfo.h" // defines REVISION_STRING >>> the file is not found. >>> >>> Anyone knows where is this file ? >>> >>> Cheers, >>> Jannik >>> >>> On Jan 28, 2014, at 8:58 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >>> >>> jannik the latest vm is not on gitoruous anymore but git >>> >>> >>> On 27 Jan 2014, at 22:03, jannik laval <jannik.laval(a)gmail.com> wrote: >>> >>> Hum, have I the correct repository ? >>> I used this one: https://git.gitorious.org/cogvm/cog-osx.git >>> >>> But, I just saw that this one exists: >>> https://github.com/pharo-project/pharo-vm >>> I should use it no? >>> >>> Jannik >>> >>> >>> 2014-01-27 Esteban Lorenzano <estebanlm(a)gmail.com> >>> >>>> 1.4 and 2.0 worked out of the box... and after my latest integration, 3.0 >>>> should work too. >>>> I will take a look as soon as I have half and hour to spare. >>>> >>>> Esteban >>>> >>>> >>>> On 27 Jan 2014, at 14:27, jannik laval <jannik.laval(a)gmail.com> wrote: >>>> >>>> Hi list, >>>> >>>> Does anyone try to load Pharoon iPad ? >>>> In the past, the version 1.4 worked with XCode 4.4. >>>> >>>> I just tried to recompile it with the new XCode (5.0.2). >>>> The VM seems to work, but the pharo 1.4 image freezes. >>>> >>>> Any idea ? >>>> >>>> -- >>>> >>>> ~~Jannik Laval~~ >>>> Ãcole des Mines de Douai >>>> Enseignant-chercheur >>>> http://www.jannik-laval.eu >>>> http://car.mines-douai.fr/ >>>> >>>> >>>> >>> >>> >>> -- >>> >>> ~~Jannik Laval~~ >>> Ãcole des Mines de Douai >>> Enseignant-chercheur >>> http://www.jannik-laval.eu >>> http://car.mines-douai.fr/ >>> >>> >>> >>> >>> >> >> >> -- >> best, >> Eliot >> >> >> > > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ > > > > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

Jan. 29, 2014

Re: [Pharo-dev] No more MouseWheelEvents?

by Nicolai Hess

2014-01-29 Sean P. DeNigris <sean(a)clipperadams.com> > Nicolai Hess wrote > > The blue rectangle looks like a drop indicator. you can drag another > > window > > over nautilus' package tree and you'll the this rectangle moving. > > Yes, and there is a bug. If you accidentally drop a non-package-related > Morph on a Nautilus tree package pane, you will get a DNU #passenger and > your Morph will disappear! > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/No-more-MouseWheelEvents-tp4739999p4740104.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > Cool, a morph trash can.

Jan. 29, 2014