- Pharo-users - lists.pharo.org

Re: [Pharo-users] Spotlight Demo

by Nicolai Hess

What is this "New-Pharo-IDE"? 2013/12/30 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> > Cool :P > > Did you had a look at: > https://ci.inria.fr/pharo-contribution/job/New-Pharo-IDE/ > There is also a Spotlight thingy there :) > > Ben > > On 30 Dec 2013, at 15:23, Sean DeNigris <sean(a)clipperadams.com> wrote: > > I needed an entry completion with groups, like Mac's Spotlight. While I > was at it, I figured it would also be useful as a UI for the existing > Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone > Morph, which is a textField + results morph, and an adaptor for > EntryCompetion, SpotlightEntryCompletion, which can be passed to > #entryCompletion: > > A short screencast will be available at https://vimeo.com/82953583 in > about 45 minutes. > > And here's a screenshot for the impatient ;) > > <Screen Shot 2013-12-30 at 9.23.02 AM.png> > > > To load (tested in Pharo 2.0 latest): > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; > package: 'Spotlight'; > load. > > Then try: > SpotlightCompletionExample open. > or > SpotlightMorphExample exampleFileSearch. > or > SpotlightMorphExample exampleSmalltalkSearch. > > >

Dec. 31, 2013

Re: [Pharo-users] Spotlight Demo

by Tudor Girba

Hi Sean, Thanks for this! I wanted a widget like this for a long time. Indeed, Ben worked on a similar idea, but I think your rendering works much better and your code is at the Morphic level. It would certainly be interesting to join forces here. I reviewed a bit your code. Here is what I liked: - I like it that you have explicit models for each section. - I like the rendering of the sections. - I like the Announcements. - I like the fluent API for defining results. Here is what I think could be improved: - Computing the result list should not block the UI (it can take long). - The amount of items in a section should be limited and if there are more of them they should be seen in a separate list or something like that. The idea would be to limit the vertical size of the widget. - The input text should be a field (so, no enter should be allowed). - The widget should be dismissible with Esc. - The list of results should not allow editing (it now does so). - Pressing the up/down arrows should move in the list. Any other typed character should continue modifying the text field area. - The first element in the list should be selected all the time. Like this, you can type and then press Enter without using arrows and the mouse. - "SpotlightCompletionExample open" does not seem work. What do you say? I would be happy to review more code. Cheers, Doru On Mon, Dec 30, 2013 at 3:23 PM, Sean DeNigris <sean(a)clipperadams.com>wrote: > I needed an entry completion with groups, like Mac's Spotlight. While I > was at it, I figured it would also be useful as a UI for the existing > Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone > Morph, which is a textField + results morph, and an adaptor for > EntryCompetion, SpotlightEntryCompletion, which can be passed to > #entryCompletion: > > A short screencast will be available at https://vimeo.com/82953583 in > about 45 minutes. > > And here's a screenshot for the impatient ;) > > > > To load (tested in Pharo 2.0 latest): > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; > package: 'Spotlight'; > load. > > Then try: > SpotlightCompletionExample open. > or > SpotlightMorphExample exampleFileSearch. > or > SpotlightMorphExample exampleSmalltalkSearch. > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 31, 2013

Re: [Pharo-users] [Pharo-dev] Spotlight Demo

by StÃ©phane Ducasse

Sounds really cool and yes the new ide guys wanted a widgets and behavior like that. How about to add Packages? > I needed an entry completion with groups, like Mac's Spotlight. While I was at it, I figured it would also be useful as a UI for the existing Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone Morph, which is a textField + results morph, and an adaptor for EntryCompetion, SpotlightEntryCompletion, which can be passed to #entryCompletion: > > A short screencast will be available at https://vimeo.com/82953583 in about 45 minutes. > > And here's a screenshot for the impatient ;) > > <Screen Shot 2013-12-30 at 9.23.02 AM.png> > > To load (tested in Pharo 2.0 latest): > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; > package: 'Spotlight'; > load. > > Then try: > SpotlightCompletionExample open. > or > SpotlightMorphExample exampleFileSearch. > or > SpotlightMorphExample exampleSmalltalkSearch.

Dec. 30, 2013

Re: [Pharo-users] Spotlight Demo

by kilon alios

I think your GUI takes too much space on screen , there is too much open space and that for me is not good. Also I would love to see it work in Pharo 3, I have no reason to work on Pharo 2 and loads of reasons to work on Pharo 3 :) I would also like to have a sticky window on demand so it does not disappear each time I click away. Of course I welcome any effort to improve spotlight , its definitely a very useful and important feature for pharo. On Mon, Dec 30, 2013 at 4:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > looks coolâ¦ but it does not works in 3.0 :( > > in any case, I vote to include the UI part (at least) in the new-pharo-ide > :) > > Esteban > > > On 30 Dec 2013, at 15:26, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> > wrote: > > Cool :P > > Did you had a look at: > https://ci.inria.fr/pharo-contribution/job/New-Pharo-IDE/ > There is also a Spotlight thingy there :) > > Ben > > On 30 Dec 2013, at 15:23, Sean DeNigris <sean(a)clipperadams.com> wrote: > > I needed an entry completion with groups, like Mac's Spotlight. While I > was at it, I figured it would also be useful as a UI for the existing > Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone > Morph, which is a textField + results morph, and an adaptor for > EntryCompetion, SpotlightEntryCompletion, which can be passed to > #entryCompletion: > > A short screencast will be available at https://vimeo.com/82953583 in > about 45 minutes. > > And here's a screenshot for the impatient ;) > > <Screen Shot 2013-12-30 at 9.23.02 AM.png> > > To load (tested in Pharo 2.0 latest): > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; > package: 'Spotlight'; > load. > > Then try: > SpotlightCompletionExample open. > or > SpotlightMorphExample exampleFileSearch. > or > SpotlightMorphExample exampleSmalltalkSearch. > > > >

Dec. 30, 2013

Re: [Pharo-users] Spotlight Demo

by Esteban Lorenzano

looks coolâ¦ but it does not works in 3.0 :( in any case, I vote to include the UI part (at least) in the new-pharo-ide :) Esteban On 30 Dec 2013, at 15:26, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Cool :P > > Did you had a look at: https://ci.inria.fr/pharo-contribution/job/New-Pharo-IDE/ > There is also a Spotlight thingy there :) > > Ben > > On 30 Dec 2013, at 15:23, Sean DeNigris <sean(a)clipperadams.com> wrote: > >> I needed an entry completion with groups, like Mac's Spotlight. While I was at it, I figured it would also be useful as a UI for the existing Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone Morph, which is a textField + results morph, and an adaptor for EntryCompetion, SpotlightEntryCompletion, which can be passed to #entryCompletion: >> >> A short screencast will be available at https://vimeo.com/82953583 in about 45 minutes. >> >> And here's a screenshot for the impatient ;) >> >> <Screen Shot 2013-12-30 at 9.23.02 AM.png> >> >> To load (tested in Pharo 2.0 latest): >> Gofer it >> smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; >> package: 'Spotlight'; >> load. >> >> Then try: >> SpotlightCompletionExample open. >> or >> SpotlightMorphExample exampleFileSearch. >> or >> SpotlightMorphExample exampleSmalltalkSearch. >

Dec. 30, 2013

Re: [Pharo-users] Spotlight Demo

by Benjamin

Cool :P Did you had a look at: https://ci.inria.fr/pharo-contribution/job/New-Pharo-IDE/ There is also a Spotlight thingy there :) Ben On 30 Dec 2013, at 15:23, Sean DeNigris <sean(a)clipperadams.com> wrote: > I needed an entry completion with groups, like Mac's Spotlight. While I was at it, I figured it would also be useful as a UI for the existing Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone Morph, which is a textField + results morph, and an adaptor for EntryCompetion, SpotlightEntryCompletion, which can be passed to #entryCompletion: > > A short screencast will be available at https://vimeo.com/82953583 in about 45 minutes. > > And here's a screenshot for the impatient ;) > > <Screen Shot 2013-12-30 at 9.23.02 AM.png> > > To load (tested in Pharo 2.0 latest): > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; > package: 'Spotlight'; > load. > > Then try: > SpotlightCompletionExample open. > or > SpotlightMorphExample exampleFileSearch. > or > SpotlightMorphExample exampleSmalltalkSearch.

Dec. 30, 2013

Spotlight Demo

by Sean DeNigris

I needed an entry completion with groups, like Mac's Spotlight. While I was at it, I figured it would also be useful as a UI for the existing Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone Morph, which is a textField + results morph, and an adaptor for EntryCompetion, SpotlightEntryCompletion, which can be passed to #entryCompletion: A short screencast will be available at https://vimeo.com/82953583 in about 45 minutes. And here's a screenshot for the impatient ;) To load (tested in Pharo 2.0 latest): Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; package: 'Spotlight'; load. Then try: SpotlightCompletionExample open. or SpotlightMorphExample exampleFileSearch. or SpotlightMorphExample exampleSmalltalkSearch.

Dec. 30, 2013

Re: [Pharo-users] Is there any fundamental technical barrier to compiling to JVM byte codes?

by Marcus Denker

My take on the issue: -> it is easy to take Smalltalk and make it âless Smalltalkâ and then compile that to JVM (no become, no thisContext, with all consequences). -> What the Smalltalk community should be doing (should have been doing): Make Smalltalk "more Smalltalkâ. Marcus On 28 Dec 2013, at 11:40, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Main problems to compile Smalltalk to java bytecode: > - there's no context in java. This means our implementation of continuations and exceptions is not valid anymore. This also means we cannot have a debugger with edit-and-continue as we have now. > - there's no become:, which is used to keep the system live > > Basically you can find tricks to still have become: and a live environment/debugger but in this case the Smalltalk created would be super slow. > > So compiling smalltalk to java is not an easy problem. > > Now compiling Pharo to the gemstone VM should be possible and not as hard. The complexity depends mostly on how well the gemstome contexts are implemented. > > > 2013/12/27 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On 27 Dec 2013, at 18:21, Andy Burnett <andy.burnett(a)knowinnovation.com> wrote: > >> >> <<<From: St?phane Ducasse <stephane.ducasse(a)inria.fr> >> >> The fun is important. >> What we want is well designed and powerful libraries that enabled people. >> For the JVM question: it is a question of resources + the fact that jvm do not really support well some key smalltalk operations. >> Now I do not understand why people develop their own vm instead of joining forces. >> Doing in the long term something and finishing a task are the most difficult things. >> Stef >> á§ >> >>> >> >> Thank you to everyone for your comments. I am replying to Stephane's email, just as a catch all. >> >> I am curious to know more about the limitations in the JVM. My thinking was sparked - in part - by Mark Roos's work on RTalk. > > I was not aware of that one :) > So this means that we have gravel, redline and Rtalk. > > http://i.cmpnet.com/ddj/images/mediacenter/jvmlanguagesummit/2011_Roos_Rtal… > I understand the motivation behind Rtalk and this is cool that they succeeded. > > Now what people often forget is that behind the technical challenges you have the libraries and the boring but important work > of building greta frameworks. > >> I realised, after my post, that he had actually worked the other way around, i.e. I think he built a Digitalk bytecode layer on top of the JVM, rather than compiling to JVM bytecodes. >> >> Either way, what I was vaguely wondering about was how difficult it would be to have a 'compile to JVM' option in Pharo. I could probably live - quite happily - developing in 'real' Pharo, and then deploying an app to e.g. Google App Engine, as a compiled Jar. Obviously, it would be much better to retain all the dynamism of a true Smalltalk environment even when the app has been deployed, but it it gave simple hosting, and scaling, it might be a reasonable trade off. > > I do not know because the problem is that on such topics the devil are in the details. > Now what is important is having a bootstrap and clean test covered code base because we could also see how to deploy > a gemstone vm or other platform in the future. > >> I agree with Stephane, it would be great for people to join forces around a vm. Would make like so much easier. >> >> Cheers >> Andy >> >> > >

Dec. 30, 2013

Re: [Pharo-users] Pharo code formatting

by Marcus Denker

Hi, The code formatter did not change. *BUT* In Pharo2 there are *three* formatters: -> The one of the old AST (no visitor, just implemented on all nodes) -> the original RB pretty printer -> the configurable RB Pretty Printer. In Pharo3, there is only one Pretty Printer left: the configurable RB one. See RBConfigurableFormatter (the old pretty printer as part of the old compiler is still there but not used, it will be removed in Pharo4). Marcus On 28 Dec 2013, at 23:56, Ihor Mykhalevych <ihor.mykhalevych(a)unikernel.net> wrote: > Thanks. I thought what version will be better to use to play with this formatter. > > > On 28.12.13 12:32, StÃ©phane Ducasse wrote: >> Not much as far as I know. >> >> >> >>> Hello everyone! >>> >>> Does anyone know if there were some changes to the Pharo code formatter after Pharo version 2.0? >>> >>> Best regards, >>> Ihor Mykhalevych >>> >> > >

Dec. 30, 2013

Re: [Pharo-users] have a question for morphic Designer in pharo.

by Marcus Denker

On 28 Dec 2013, at 14:25, Tobias Pape <Das.Linux(a)gmx.de> wrote: > > On 28.12.2013, at 10:07, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> I guess that >> >> #: should be #â:â > > That is one way. > In this particular case, > self property asMutator > was the better version, tho. > > Best > -Tobias > PS: Just curious, what was the reason to no longer allow #: ? > Or, where can I find the respective discussion, just want to lern. Pharo3 uses the new compiler infrastructure by default. This means that instead of the old (hand-written) parser, we now use RBParser (hand written, too). It seems that RBParser does not implement it. The question is who was wrong: the old parser or the new? I have no idea. But the good news is that we now just have two Parsers, not threeâ¦ (syntax highlighting implements itâs own parser, too). What we need is a real grammarâ¦ that can solve these differences which come from the implementation. Another example is #9 â> both RB and the old compile it as an integer, there is special code in the Parser for that even. But do we want that? If we would have a definition of our grammar, we could look there and say âyes, itâs part of the definitionâ. Even better would be an executable grammarâ¦ we should explore of we can use PetitParser in the future, but there are some open questions (error handling, speedâ¦). The most beautiful would be to have just *one* parser that has a high level model of itâs grammar that is reusable everywhere. Marcus

Dec. 30, 2013