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

Re: [Pharo-dev] you spin me around...

by Igor Stasenko

On 20 January 2014 23:21, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Juraj worked on rotating text. People have been asking for it for yearsâ¦ > > > > With Roassal 2: > > -=-=-=-=-=-=-=-=-=-= > | v shape | > v := RTView new. > shape := RTRotatedLabel new. > why you need separate class for 'rotated' label? i suppose you also need RTRotatedAndScaledLabel, RTRotatedAndScewedLabel .. as well as other (infinite) number of permutations with 'something-ed' and 'Label'. or its just a prototype? shape angleInDegree: [ :cls | cls numberOfMethods negated / 1.5 ]. > shape text: [ :cls | ' ', cls name ]. > shape color: (Color black alpha: 0.2). > v addAll: (shape elementsOn: Collection withAllSubclasses). > > v canvas color: Color white. > v open > -=-=-=-=-=-=-=-=-=-= > > More screenshots and more examples on: > > https://www.facebook.com/media/set/?set=a.573528479400420.1073741841.340543… > > Excellent job Juraj! > > Before the end of January, we will make a big big announcement. We, the > profilers, are working hard these days on a fantastic infrastructure for a > better and stronger visual experience. > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Best regards, Igor Stasenko.

Jan. 20, 2014

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > In addition, infinite loops of propagation are prevented. Is that what lock is all about? I was wondering... ----- Cheers, Sean -- View this message in context: http://forum.world.st/COTDC-108-NewValueHolder-tp4738066p4738129.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 20, 2014

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by Benjamin

On 20 Jan 2014, at 19:24, Nicolai Hess <nicolaihess(a)web.de> wrote: > we should distinguish between "storing a object" and "change a value". > At the moment, NewValueHolder announces every time we store into this value > holder regardless wether the value changed. Thatâs true. It was not clear enough :) Thanks, Ben

Jan. 20, 2014

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by Nicolai Hess

2014/1/20 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > On 20 Jan 2014, at 15:36, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > I had some questions about NewValueHolder and I figured, why not revive > > COTDC?! > > I loved it :) > > > > > The current comment is: "A NewValueHolder is a new implementation of > > ValueHolder based on Announcements". Of course, ValueHolder doesn't have > a > > class comment. Wikipedia claims a value holder is "a generic object that > > handles the lazy loading behavior, and appears in place of the object's > data > > fields" [1]. So: > > - what is a NewValueHolder? > > I am a class holding any object inside its unique instance variable. > Each time the instance variable value changes, an announcement is emitted. > > we should distinguish between "storing a object" and "change a value". At the moment, NewValueHolder announces every time we store into this value holder regardless wether the value changed.

Jan. 20, 2014

Re: [Pharo-dev] RFB on a headless Pharo 3

by Sebastian Sastre

Sharing some experiencesâ¦ This is on a fresh image with RFB installed and manually patched about the os name and version and removing Beeper invocations. Strangely, after using it with UI and connecting with a vnc client for a while, Iâve stopped the RFB service in this image and then saved Then Iâve tried to run it gui-less suryia:rfb sebastian$ pharo-vm/Pharo.app/Contents/MacOS/Pharo -vm-display-null Pharo.image unknown option: -vm-display-null Usage: [<option>...] [<imageName> [<argument>...]] [<option>...] -- [<argument>...] Common <option>s: --help print this help message, then exit --memory <size>[mk] use fixed heap size (added to image size) --headless run in headless (no window) mode (default: false) --nohandlers disable sigsegv & sigusr1 handlers Notes: <imageName> defaults to `Pharo.image'. If `--memory' is not specified then the heap will grow dynamically. <argument>s are ignored, but are processed by the Squeak image. The first <argument> normally names a Squeak `script' to execute. Precede <arguments> by `--' to use default image. trying with ânodisplay suryia:rfb sebastian$ pharo-vm/Pharo.app/Contents/MacOS/Pharo --nodisplay Pharo.image unknown option: --nodisplay Usage: [<option>...] [<imageName> [<argument>...]] [<option>...] -- [<argument>...] Common <option>s: --help print this help message, then exit --memory <size>[mk] use fixed heap size (added to image size) --headless run in headless (no window) mode (default: false) --nohandlers disable sigsegv & sigusr1 handlers Notes: <imageName> defaults to `Pharo.image'. If `--memory' is not specified then the heap will grow dynamically. <argument>s are ignored, but are processed by the Squeak image. The first <argument> normally names a Squeak `script' to execute. Precede <arguments> by `--' to use default image. trying with âheadless suryia:rfb sebastian$ pharo-vm/Pharo.app/Contents/MacOS/Pharo --headless Pharo.image Usage: [--no-preferences|--preference-file=<FILE>][<subcommand>] [--help] [--copyright] [--version] [--list] [ --no-quit ] --help print this help message --copyright print the copyrights --version print the version for the image and the vm --list list a description of all active command line handlers --no-quit keep the image running without activating any other command line handler <subcommand> a valid subcommand in --list Preference File Modification: --preference-file load the preferences from the given <FILE> --no-default-preferences do not load any preferences from the default locations Documentation: A PharoCommandLineHandler handles default command line arguments and options. The PharoCommandLineHandler is activated before all other handlers. It first checks if another handler is available. If so it will activate the found handler. no crash dumps no PharoDegug.log this time =/ ideas? On Jan 20, 2014, at 3:58 PM, Sebastian Sastre <SEBASTIAN(a)FLOWINGCONCEPT.COM> wrote: > If you want to reproduce the issue: > > > 1. Take a fresh image > wget -O- get.pharo.org/30+vm | bash > > 2. start it with UI and in a workspace load RFB > Gofer new > url:'http://www.smalltalkhub.com/mc/PharoExtras/RFB/main'; > package: 'RFB'; > load. > > 3. then run > RFBServer current > allowRemoteConnections: true; > setFullPassword: âcacaâ; > start: 8. > > 4. connect with chicken VNC or your favourite client to 5908, all should be okay (if you have in mind the bug/fix about os platform) > > 5. quit image saving > > 6. you can now open it with UI and all will be nice and good or youâll have an image that canât start in headless mode =/ > > > still investigating... contributions are very welcome > > sebastian > > o/ > > > > > > On Jan 20, 2014, at 3:47 PM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> Guys >> >> Just checking while investigating the issue... >> >> Were any of you here able to connect a VNC client to a headless Pharo 3? >> >> I can do that to a Pharo 2 (seting a morphic ui manager on it) but I'm having issues with 3 >> >> Did you tried that? any luck? insights? >> >> sebastian >> >> o/ >

Jan. 20, 2014

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by Benjamin

It is the history of a prototype ending in the system :) Ben On 20 Jan 2014, at 18:02, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > NewValueHolder? the name sounds like a Squeak strategy: keep backward compatibility as long as possible. > > Since Pharo values cleanlyDesigned > backwardCompatible, I would expect ValueHolder->LegacyValueHolder and NewValueHolder->ValueHolder. > > We had too many NewParagraph, etc... in the past, history does not necessarily have to repeat itself ;) > > > 2014/1/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > I commented the code in a slice that apparently was not integrated. > But yes this is a good idea. > - to have more code review > - to revive the COTDC!!!! > > > > I had some questions about NewValueHolder and I figured, why not revive > > COTDC?! > > > > The current comment is: "A NewValueHolder is a new implementation of > > ValueHolder based on Announcements". Of course, ValueHolder doesn't have a > > class comment. Wikipedia claims a value holder is "a generic object that > > handles the lazy loading behavior, and appears in place of the object's data > > fields" [1]. So: > > - what is a NewValueHolder? > > - is the "Value Holder" part of the name accurate in light of [1]. Obviously > > repurposing a term people may already be familiar with is a bad idea. In > > fact the important part here seems not the holding of the value, but the > > notification of changes. It seems more like an event in FRP. How about > > ReactiveVariable or AnnouncingVariable, since it combines the storage of a > > variable with announcing of changes? I like Reactive a bit better because > > those familiar with FRP will get the idea that it's notifying dependents, > > Announcing maybe begs the question "announcing what?" > > - should it replace ValueHolder, which is used only by > > ExclusiveWeakMessageSend and WidgetExamples > > > > [1] http://en.wikipedia.org/wiki/Lazy_loading > > > > p.s. [OT] valueChanged: oldValue to: newValue seems fishy. It is only used > > in one place in the image in this weird way "pickedItemsHolder valueChanged: > > true to: item" > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: http://forum.world.st/COTDC-108-NewValueHolder-tp4738066.html > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > >

Jan. 20, 2014

you spin me around...

by Alexandre Bergel

Hi! Juraj worked on rotating text. People have been asking for it for yearsâ¦ With Roassal 2: -=-=-=-=-=-=-=-=-=-= | v shape | v := RTView new. shape := RTRotatedLabel new. shape angleInDegree: [ :cls | cls numberOfMethods negated / 1.5 ]. shape text: [ :cls | ' ', cls name ]. shape color: (Color black alpha: 0.2). v addAll: (shape elementsOn: Collection withAllSubclasses). v canvas color: Color white. v open -=-=-=-=-=-=-=-=-=-= More screenshots and more examples on: https://www.facebook.com/media/set/?set=a.573528479400420.1073741841.340543… Excellent job Juraj! Before the end of January, we will make a big big announcement. We, the profilers, are working hard these days on a fantastic infrastructure for a better and stronger visual experience. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2014

Re: [Pharo-dev] Pharo on a Raspbian

by Eliot Miranda

Hi Jean-Baptiste, On Mon, Jan 20, 2014 at 7:25 AM, Jean Baptiste Arnaud < jbaptiste.arnaud(a)gmail.com> wrote: > > On 18 Jan 2014, at 09:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > One of the problem we are thinking about now is the FFI on ARM (alien or > not alien)â¦. > > +1, we need to think the, best solution is to have NativeBoost on ARM. > We need an agreement between, time to develop and usage. > Maybe first I should fix Alien or FFI. Then one day, port Nativeboost on > ARM. > Did you see the thread on vm-dev about the ARM FFI? When I wrote the FFI-replacement ThreadedFFIPlugin (which is the standard FFI plugin in Cog) I added stubs for ARM and PowerPC. I hope that Doug McPherson is going to be able to fully implement these stubs. If you're interested perhaps you could collaborate? I'm confident that the effort involved in getting this going is a week or two at most. Days for someone who well understands alloca and the ARM ABI. On 17 January 2014 22:59, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Who is JB ? > > > > Jean Baptiste Arnaud. The invaluable asset in any team :) > The hacker who without any help configuring & compiling VM on raspberry. > > > Oh, for real, I'm flattered. > > > Good to know. > > Thanks Jean-Baptiste ! > > > > > > Best Regards > Jean Baptiste Arnaud > jbaptiste.arnaud(a)gmail.com > > > > > > > > -- best, Eliot

Jan. 20, 2014

Re: [Pharo-dev] RFB on a headless Pharo 3

by Sebastian Sastre

Hi Torsten, Thanks for the input. Iâve changed RFBSession>>uninplemented like this: unimplemented "Make some noise when encountering an unimplemented feature. Strictly developer lossage." self log: 'unimplemented'. "Beeper beepPrimitive." Transcript endEntry So it doesnât try to use the Beeper and fail The client opens but the keyboard is not usable (it has an erratic behavior) Maybe the way to handle the keyevents changed from 2 to Pharo 3? sebastian o/ On Jan 20, 2014, at 5:02 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Also try > > RFBLog dumpLogToTranscript: true > > before running. Then a dump on the Transcript will appear. > > There you will see that there is a DNU for a Cursor instance > which does not understand #maskForm in method #sendCursorShape: > > Interesting enough ivar "newCursor" is an instance of Cursor - but and only > subclass like CursorWithMask understand #maskForm. > > > It is initialized in #initServer:socket:reverse: with "Cursor currentCursor" > returning > - either a Cursor instance when I inspect it using the menu > - a CursorWithMask instance when I inspect it using CMD keys > > No time to dig deeper today. Keep us informed about your progress. > An updated ConfigurationOfRFB would be nice... > > Bye > T. >

Jan. 20, 2014

[pharo-project/pharo-core]

by GitHub

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

Jan. 20, 2014