- Pharo-users - lists.pharo.org

Re: [Pharo-users] Process Browser: bug or feature?

by Arturo Zambrano

thanks On Tue, Feb 18, 2014 at 11:05 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > it is not a bug... you need to turn auto update on. > (right button on the left panel of the process browser... there is an option) > > On 18 Feb 2014, at 14:56, Arturo Zambrano <arturo.zambrano(a)gmail.com> > wrote: > > > I'm running the beta version of Pharo3. > > > > working with some background processes, I notice that process browser > does not update correctly. If I launch a new process it is not updated. > When process browser is relaunched the process is there. > > > > The same happens when the process is terminated... the list in process > browser is updated only when the process is terminated from the process > browser UI. If I kill the process from somewhere else, it is not updated. > > > > If it is a bug I can report it on the bug tracker, please send me the > URL. > > > > regards > > art > > >

Feb. 18, 2014

Re: [Pharo-users] Removing an obsolete class

by Esteban A. Maringolo

This is still in the image, adding "AnObsolete" prefix everytime I want to remove it... :-/ AnObsoleteAnObsoleteAnObsoleteAnObsoleteGptRouteItemRegistration How Obsolete it must be before it's gone? :) Esteban A. Maringolo

Feb. 18, 2014

Re: [Pharo-users] Process Browser: bug or feature?

by Esteban Lorenzano

it is not a bugâ¦ you need to turn auto update on. (right button on the left panel of the process browserâ¦ there is an option) On 18 Feb 2014, at 14:56, Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > I'm running the beta version of Pharo3. > > working with some background processes, I notice that process browser does not update correctly. If I launch a new process it is not updated. When process browser is relaunched the process is there. > > The same happens when the process is terminated... the list in process browser is updated only when the process is terminated from the process browser UI. If I kill the process from somewhere else, it is not updated. > > If it is a bug I can report it on the bug tracker, please send me the URL. > > regards > art

Feb. 18, 2014

Re: [Pharo-users] Spec and an application menu

by Goubier Thierry

Le 18/02/2014 14:32, Johan Fabry a Ã©crit : > > And I agree with Ben :-) > > Also, since a UI framework is something very large and complicated, with many possible uses, it's not realistic to expect a few developers to be able to do a 'big bang' release that is 100% feature complete. Spec, as is, is very complete and useful for a large variety of UIs. If the community uses it, it will become clear which features have been overlooked and hence which Spec improvements will need to be prioritized. I do agree with the very large and complicated. > So, use it and tell us about it :-) Which is exactly what's happening now :) Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 18, 2014

Process Browser: bug or feature?

by Arturo Zambrano

I'm running the beta version of Pharo3. working with some background processes, I notice that process browser does not update correctly. If I launch a new process it is not updated. When process browser is relaunched the process is there. The same happens when the process is terminated... the list in process browser is updated only when the process is terminated from the process browser UI. If I kill the process from somewhere else, it is not updated. If it is a bug I can report it on the bug tracker, please send me the URL. regards art

Feb. 18, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Johan Fabry

Thanks for your comments and questions. We will try to address them in a second version of the documentation, together with the other questions and answers that have appeared on the mailing list in the mean time. So, if anybody else has more comments and questions, do ask. They will be integrated in a second iteration of the documentation! On Feb 16, 2014, at 9:34 AM, kmo <voxkmp(a)gmail.com> wrote: > The Spec documentation is very good /as far as it goes/. As a native speaker, > I would say the English is excellent, though the tone is rather dry and > technical. Generally, I think it is well written and very helpful. That's > not the issue. > > The real problem is that this documentation is no more than an overview. It > is not written from a /How To/ perspective. The result is that it offers > little help to anyone who wants to actually create a user interface with > Spec. > > Here are some obvious questions that might occur to anyone starting to use > Spec. None of them are answered in the current documentation. > > How do use Spec to write an application that fills the pharo window? (There > is no mention of openWorldWithSpec in the document). > > How do I write an application with a main menu at the top, a toolbar under > it, and a status bar at the bottom? > > How to I create, use and close, non-modal windows in my application? > > How do I write a modal dialog, ask for complex information, and get it back? > (There is a modal dialog example in the document under Prototyping a UI but > nothing explicit). > > How do I use a SliderModel, RadioButtonModel etcetera? > > How do I use all those cool Morphs I've found - PianoKeyboardMorph, LEDMorph > etcetera - with Spec? Surely I don't have to write my own Morphic Adapter > for each one? > > How do I migrate my Morphic application to Spec? > > To my mind, this document is only the beginning. It doesn't even have a list > of the available Spec models and their APIs - even the original Spec Report > had a table of these. The approach seems to be - here's a general idea of > how it works - read the source if you actually want to do anything. Well, > even an idiot like me can perhaps work out how to use a LabelModel, but > TreeModel,say, with its TreeColumns and TreeNodes is not so obvious and it > needs trial and error to find out how it all fits together (not helped by > the complete abscebnce of helpful class comments). We don't need tail and > error. We need documentation. > > Finally, can we please stop using class browsers as examples? I know that it > is easy (and cool) to use reflection to get lists of classes, protocols and > methods but this only adds to the impression that the smalltalk community is > self-absorbed and narcissistic. If you want to attract business developers > then use examples that relate to the real world, not to the pharo > environment itself. Why not a database example or a paint application > example? No one wants to write a class browser - that's already available! > > Perhaps I should stop before this becomes filed under /Why is > smalltalk/pharo so unpopular./ > > To sum up, this documentation is a good start - but that's all it is. > > > > > > > > > > -- > View this message in context: http://forum.world.st/ANN-Spec-documentation-in-PFTE-book-finished-tp474303… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 18, 2014

Re: [Pharo-users] Spec and an application menu

by Johan Fabry

And I agree with Ben :-) Also, since a UI framework is something very large and complicated, with many possible uses, it's not realistic to expect a few developers to be able to do a 'big bang' release that is 100% feature complete. Spec, as is, is very complete and useful for a large variety of UIs. If the community uses it, it will become clear which features have been overlooked and hence which Spec improvements will need to be prioritized. So, use it and tell us about it :-) On Feb 18, 2014, at 6:53 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > I do agree with you all :) > > The things is many people ask for more things into Spec, > but at the end, I am still the only one implementing them :) > > And as you can imagine, my time is not infinite :P > > I will end up proposing a kickstarted project I think :P > > Ben > > On 18 Feb 2014, at 09:36, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > >> >> >> Le 18/02/2014 09:26, Goubier Thierry a Ã©crit : >>> >>> Now I want to try something: populate the menu bar with all possible >>> menu/shortcuts commands defined in my app (i.e. tree node contextual >>> menu, code pane contextual menu, smart-suggestions type commands) to >>> ensure discoverability, in as few lines as possible. >> >> I guess it should be a mission for Spec. >> For DrGeo, I have to hand write it and it is no a few lines. Not to >> mention I did not set up the keyboard short cut. >> >> >> -- >> Dr. Geo http://drgeo.eu >> >> > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 18, 2014

Re: [Pharo-users] TextModel and TextInputFieldModel font-size bug?

by Benjamin

I think itâs time to open a bug entry :) Ben On 18 Feb 2014, at 03:18, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > I confirm this issue using a vanilla Pharo 3. > > PluggableTextFieldMorph new openInWindow > > If you comment last line here it works > > PluggableTextFieldMorph>>initialize > > textMorphClass := TextMorphForFieldView. > super initialize. > " self beDecrypted" > > which makes me think. Why #beDecrypted? Are text morphs encrypted by default? > If not we are wasting cycles there. To me it sounds like you should decrypt when something was encrypted, not just in case. > > However that does not resolve the issue with TextInputFieldModel. > > > > > 2014-02-16 10:55 GMT-03:00 kmo <voxkmp(a)gmail.com>: > When I create an interface in Spec with TextModel or TextInputFieldModel, the > font-size is tiny. Same behaviour in both Windows and Linux. Is this a bug > or have I missed something important? > > <http://forum.world.st/file/n4744094/SmallFont.png> > > > > > > -- > View this message in context: http://forum.world.st/TextModel-and-TextInputFieldModel-font-size-bug-tp474… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Feb. 18, 2014

Re: [Pharo-users] Spec and an application menu

by Benjamin

I do agree with you all :) The things is many people ask for more things into Spec, but at the end, I am still the only one implementing them :) And as you can imagine, my time is not infinite :P I will end up proposing a kickstarted project I think :P Ben On 18 Feb 2014, at 09:36, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > > > Le 18/02/2014 09:26, Goubier Thierry a Ã©crit : >> >> Now I want to try something: populate the menu bar with all possible >> menu/shortcuts commands defined in my app (i.e. tree node contextual >> menu, code pane contextual menu, smart-suggestions type commands) to >> ensure discoverability, in as few lines as possible. > > I guess it should be a mission for Spec. > For DrGeo, I have to hand write it and it is no a few lines. Not to > mention I did not set up the keyboard short cut. > > > -- > Dr. Geo http://drgeo.eu > >

Feb. 18, 2014

Re: [Pharo-users] Spec and an application menu

by btc＠openinworld.com

Goubier Thierry wrote: > > > Le 18/02/2014 09:36, Hilaire Fernandes a Ã©crit : >> >> >> Le 18/02/2014 09:26, Goubier Thierry a Ã©crit : >>> >>> Now I want to try something: populate the menu bar with all possible >>> menu/shortcuts commands defined in my app (i.e. tree node contextual >>> menu, code pane contextual menu, smart-suggestions type commands) to >>> ensure discoverability, in as few lines as possible. >> >> I guess it should be a mission for Spec. > > Probably ;) > >> For DrGeo, I have to hand write it and it is no a few lines. Not to >> mention I did not set up the keyboard short cut. > > Well, I lifted the Command framework of the OmniBrowser for my own > needs, and building automatically the menu and the shortcuts is just a > few lines (and the shortcuts are allways in sync with the menu). > > I just have to change a bit the isActive/isEnabled for the menu bar; > it should do the trick. Longuest will probably be rebuilding the > layout of the window to accomodate the menu bar. > > Oh, and some menu commands names depend on the name of the ast node at > the cursor point in the text (such as 'create accessors on requestor' > when selecting the 'requestor' instance variable name in the > #subclass: class description), so I should have a way to handle that > (have a default name when nothing is selected?) > > Thierry Pharolauncher doesn't have a menu but it does have a an command icon toolbar at the top which is similar. It provide a very good example of a Spec application to learn from. cheers -ben

Feb. 18, 2014