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

Re: [Pharo-users] Best wishes for 2014

by Sven Van Caekenberghe

My best wishes to everyone as well. Thank you Stef, Marcus and the rest of the community for pushing Pharo all these years: it has been a very interesting ride. Yes, Pharo belongs to all of us, I am proud to be part of it. I am sure 2014 will be just as exciting. Sven On 31 Dec 2013, at 19:53, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi pharoers > > Sometimes I think that we are crazy to build this system but this is really > important to have dreams and make them becoming true. :) > I really like what we are doing: we are building a strong community and a really great system. > Of course it could be better but it is going in the right direction at full speed. > Now remember that Pharo is not ours but YOURS and you can get an impact! > Pharo is not read-only. > > This year we got some nice and important changes. I think that in 2014 we will have some > important improvements. We will have to finish what we started and build a solid ground for > the next iteration. > > I really like our community because it pushes me forward and because my dreams are becoming > reality :) > > I wish you a lot of success and health. > > Stef -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Jan. 1, 2014

Re: [Pharo-users] Best wishes for 2014

by ÐÐ°ÑÐºÑÑÐ½ Ð ÑÐ·ÑÐ½

Happy New Year! It's nice to read such warm words. Thank you Stef:) Mark. 2014/1/1 Tudor Girba <tudor(a)tudorgirba.com> > Happy New Year, everyone! > > Doru > > > On Tue, Dec 31, 2013 at 7:53 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Hi pharoers >> >> Sometimes I think that we are crazy to build this system but this is >> really >> important to have dreams and make them becoming true. :) >> I really like what we are doing: we are building a strong community and a >> really great system. >> Of course it could be better but it is going in the right direction at >> full speed. >> Now remember that Pharo is not ours but YOURS and you can get an impact! >> Pharo is not read-only. >> >> This year we got some nice and important changes. I think that in 2014 we >> will have some >> important improvements. We will have to finish what we started and build >> a solid ground for >> the next iteration. >> >> I really like our community because it pushes me forward and because my >> dreams are becoming >> reality :) >> >> I wish you a lot of success and health. >> >> Stef >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Jan. 1, 2014

Re: [Pharo-users] towards moose in the pharo ide (gtinspector / gtdebugger)

by Tudor Girba

Thank you, Alain. I am looking forward for all your questions :) Doru On Wed, Jan 1, 2014 at 8:34 AM, Alain Busser <alain.busser(a)gmail.com> wrote: > OK I understood the message :-D > > I plan to test the Moose image with MathsOntologie and you will get plenty > of stupid questions like "how can I do this?" or "why that doesn't work?", > after all this is all that you deserve [?] > > This is my peculiar way to wish to you and all the team an happy and > successful year > > Alain > > > On Mon, Dec 30, 2013 at 9:24 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> Some of you asked how the GTInspector and GTDebugger are different from >> the existing infrastructure. They are quite different from the norm in >> that: they are tiny, and they are highly extensible. Here are some posts >> that describe what makes them different: >> >> >> http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… >> http://www.humane-assessment.com/blog/dissecting-the-gtinspector/ >> >> http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… >> http://www.humane-assessment.com/blog/moldable-gtdebugger >> >> These tools are already the default development tools in the Moose image. >> As you can see, Moose is reshaping the Pharo IDE. I think this is exciting. >> >> This should be just the beginning. To make it better, we need your energy: >> - Apply and extend these tools for your context (this is what makes them >> unique). >> - Tell us what works and what does not work. >> - Ideally, start working with us on this topic. In particular, I am >> looking for people that would like to spend some time working on Morphic >> widgets. >> >> It's your turn now. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 1, 2014

Re: [Pharo-users] Pharo on Android - is it available?

by Alain Busser

Thank you for making Amber known, but you forgot a link to it: I guess you talk about this: http://amber-lang.net/ Alain On Tue, Dec 31, 2013 at 9:35 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > I have tried squeak on my android devices, it basically runs on android > yes but it does not behave well with multi touch its practically unusable. > Basically it does not understand when someone lifts his finger from the > screen , so it can get clicks but its sticky clicks.So moving windows > around and clicking on things is a pain and not usable at all. I suspect > something similar applies for pharo too. > > If you want to develop for mobile devices your best bet right now is > Amber. Amber tries to be as compatible as possible to pharo and compiles to > javascript. You should be able to use pharo as a backend if you want to but > I have not tried to really confirm this, I dont see any reason why this > wont work. The advantage of amber is that any app you develop with it wont > be just a mobile app but also a web app. > > Using pharo for desktop apps is of course perfectly doable and recommended > or as a backend to web apps. But if you have a tablet and want to focus on > this I would say that Amber + Pharo should seal the deal for you and you > will give you access to loads of stuff you can do because amber will give > you immediate access to all Javascript libraries and that can only be a > good thing :) > > Also javascript is probably a very good way to develop Android apps that > also work on iOS. > >

Jan. 1, 2014

Re: [Pharo-users] towards moose in the pharo ide (gtinspector / gtdebugger)

by Alain Busser

OK I understood the message :-D I plan to test the Moose image with MathsOntologie and you will get plenty of stupid questions like "how can I do this?" or "why that doesn't work?", after all this is all that you deserve [?] This is my peculiar way to wish to you and all the team an happy and successful year Alain On Mon, Dec 30, 2013 at 9:24 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Some of you asked how the GTInspector and GTDebugger are different from > the existing infrastructure. They are quite different from the norm in > that: they are tiny, and they are highly extensible. Here are some posts > that describe what makes them different: > > > http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… > http://www.humane-assessment.com/blog/dissecting-the-gtinspector/ > > http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… > http://www.humane-assessment.com/blog/moldable-gtdebugger > > These tools are already the default development tools in the Moose image. > As you can see, Moose is reshaping the Pharo IDE. I think this is exciting. > > This should be just the beginning. To make it better, we need your energy: > - Apply and extend these tools for your context (this is what makes them > unique). > - Tell us what works and what does not work. > - Ideally, start working with us on this topic. In particular, I am > looking for people that would like to spend some time working on Morphic > widgets. > > It's your turn now. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Jan. 1, 2014

Re: [Pharo-users] Best wishes for 2014

by Tudor Girba

Happy New Year, everyone! Doru On Tue, Dec 31, 2013 at 7:53 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi pharoers > > Sometimes I think that we are crazy to build this system but this is really > important to have dreams and make them becoming true. :) > I really like what we are doing: we are building a strong community and a > really great system. > Of course it could be better but it is going in the right direction at > full speed. > Now remember that Pharo is not ours but YOURS and you can get an impact! > Pharo is not read-only. > > This year we got some nice and important changes. I think that in 2014 we > will have some > important improvements. We will have to finish what we started and build a > solid ground for > the next iteration. > > I really like our community because it pushes me forward and because my > dreams are becoming > reality :) > > I wish you a lot of success and health. > > Stef > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 1, 2014

Re: [Pharo-users] Spotlight Demo

by Tudor Girba

Hi, I am in Pharo 3.0, and I think everyone else should be as well at this point :) Doru On Tue, Dec 31, 2013 at 10:26 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Tudor Girba-2 wrote > > - "SpotlightCompletionExample open" does not seem work. > > Would you be more specificâ¦ If I do it in a fresh 2.0 image after using the > Gofer expression above, I get a text field. If I type "int" in the text > field, I get results below. And if I click on one of the results, I it is > entered into the text field. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Spotlight-Demo-tp4733077p4733364.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 1, 2014

Re: [Pharo-users] Spotlight Demo

by DeNigris Sean

Thanks for the feedback everyone! A few enhancements: - Close on escape - Select next on down arrow when open - Show all on down arrow when closed - Select previous on up arrow - Accept on enter - requires an override in PluggableTextFieldMorph, but I think the change can be integrated in Core - For entry completion (unlike our current behavior): - Keyboard focus remains with the text field, so: - you can continue to type - the selected item stays selected as long as it remains visible, even if it moves around in the list (maybe doesn't matter for completion...) I'm off to celebrate... See you in the new year!

Jan. 1, 2014