- Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20224

by Marcus Denker

20224 ----- Issue 6398: MCPackageManager class >> methodMoved: uses old SystemChangeNotifier http://code.google.com/p/pharo/issues/detail?id=6398& Issue 6390: Spotlight throws "TextMorphForFieldView DNU #lostFocusBlock:" http://code.google.com/p/pharo/issues/detail?id=6390 Issue 6362: Failing test: KMDispatcherTestCase.testBuffering http://code.google.com/p/pharo/issues/detail?id=6362 Issue 5993: Change in Scrollbar behavior http://code.google.com/p/pharo/issues/detail?id=5993 -- Marcus Denker -- http://marcusdenker.de

July 18, 2012

[Pharo-project] [update 1.4] #14455

by Esteban Lorenzano

14455 ----- Issue 6386: [BUG]: [1.4]: New ProcessSpecificVariables & Running Processes http://code.google.com/p/pharo/issues/detail?id=6386

July 18, 2012

Re: [Pharo-project] [update 2.0] #20223

by Pavel Krivanek

On Wed, Jul 18, 2012 at 11:11 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 20223 > ----- > > Issue 6408: inputWidgetForFileOrDirectoryWithAction: for Dummies > http://code.google.com/p/pharo/issues/detail?id=6408 > > Issue 6406: [BUG]: FileDialogWindow: Open on Absolute Path > http://code.google.com/p/pharo/issues/detail?id=6406 The test is failing on Mac -- Pavel > > Issue 6403: handle obsolete classes in MessageSend >> value and value: > http://code.google.com/p/pharo/issues/detail?id=6403 > > Issue 6401: package System-PragmaCollector > http://code.google.com/p/pharo/issues/detail?id=6401 > > > > -- > Marcus Denker -- http://marcusdenker.de > >

July 18, 2012

[Pharo-project] [update 2.0] #20223

by Marcus Denker

20223 ----- Issue 6408: inputWidgetForFileOrDirectoryWithAction: for Dummies http://code.google.com/p/pharo/issues/detail?id=6408 Issue 6406: [BUG]: FileDialogWindow: Open on Absolute Path http://code.google.com/p/pharo/issues/detail?id=6406 Issue 6403: handle obsolete classes in MessageSend >> value and value: http://code.google.com/p/pharo/issues/detail?id=6403 Issue 6401: package System-PragmaCollector http://code.google.com/p/pharo/issues/detail?id=6401 -- Marcus Denker -- http://marcusdenker.de

July 18, 2012

Re: [Pharo-project] New VMs at http://www.mirandabanda.org/files/Cog/VM/VM.r2559/

by Camillo Bruni

I assume they don't include the FilePlugin changes? Because then they will only work under Pharo 1.4 and before! On 2012-07-18, at 04:21, Sean P. DeNigris wrote: > Eliot Miranda-2 wrote >> >> Add -blockonerror flag to Unix & Mac VMs to allow attaching gdb on >> error/segv. >> > > Cool!! Thanks, Eliot > > -- > View this message in context: http://forum.world.st/New-VMs-at-http-www-mirandabanda-org-files-Cog-VM-VM-… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 18, 2012

[Pharo-project] [OT] Sharelatex

by Torsten Bergmann

Maybe this is usefull for collaborative writing on PBE2 https://www.sharelatex.com/

July 18, 2012

Re: [Pharo-project] [ANN] Alternative view of a system browser

by StÃ©phane Ducasse

I do not have a connection to look at it. But I LOVE the idea. I love the idea that we can prototype fast new tools and rethink how processesâ¦. Spec is one way to enable that. For example I love the GlamourInspector and it would be great to rewrite it with Spec. Thanks a lot. Stef On Jul 17, 2012, at 3:12 PM, Goubier Thierry wrote: > I believe that the traditional SystemBrowser of Smalltalk of old has been made unusable by the amount of code (and structure) you find in today's Smalltalk images. > > So this is to show you an alternative, a different way to browse through packages / classes and methods and code. This is Spec-based. > > https://picasaweb.google.com/lh/photo/ic_fRnBXXdyqbiJ5NRP9YtMTjNZETYmyPJy0l… > > What is missing / targeted ? > * Drag and drop reorganisation of the tree as preferred / or as package / category reuse. > * A good search facility in the tree. It is already keyboard navigation friendly (since the tree view is). > * Most / All menu methods of a complete System Browser. I'm planning on reusing the OmniBrowser command structure as much as possible (to make it faster). > * Funny ideas on how to use the tree structure : group / selection display, queries, metrics ... > ** There is probably a lot more to be done here, but it would probably require Mondrian or other graph visualisation tools. > > Expect the code sometime by the end of the week, in a Pharo 2.0 / Pharo 1.4 version. > > 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 > >

July 18, 2012

Re: [Pharo-project] Spec Enhancement Request

by StÃ©phane Ducasse

On Jul 17, 2012, at 9:46 AM, Goubier Thierry wrote: > Hi, > > could Spec gives access to drag and drop on morphs ? yes it should. A spec should capture all the description of the underlying widget. Many of the behavior/presentation are not captured right just because we wanted to make sure that the idea work and we took a breadth first approach. Because adding new meta-data is simple. > I'm trying to get TreeModel to do things by drag and drop, and I haven't found another way than subclassing it. > > 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 > >

July 18, 2012

Re: [Pharo-project] Customizing the Caret of a PluggableTextMorph

by StÃ©phane Ducasse

On Jul 16, 2012, at 9:38 PM, Sean P. DeNigris wrote: > For VimPharo, I want to have a different cursor depending on whether a tool > is in insert or normal mode. > > I tried a handful of ways, but they all failed or worked > partially/inconsistently. Here's some of them: > * add the state to the paragraph, but the entire paragraph gets replaced > during the life of the tool, so the state gets lost > * add the state to the editor, but the situation is the same > * add the state to PluggableTextMorph, override and access it from > TextMorphForEditView>>updateFromParagraph. This was an extreme PITA and got > me very acquainted with the emergency evaluator. It "worked", but only after > using the arrows a bit. > > Does anyone have any idea where I might hook in? > > <rant>I find the whole text system very confusing. What the heck does a > paragraph know about insertion points?? A view has one paragraph object, > even if there are several paragraphs (as understood by the rest of humanity > as a block of text with breaks between the adjoining ones. Editors and > Paragraphs are thrown out and replaced on a whim. I'm finding it very hard > to understand and modify</rant> I got burned by that when I worked on my botanics envâ¦. it was terrible. > > Thanks, > Sean > > -- > View this message in context: http://forum.world.st/Customizing-the-Caret-of-a-PluggableTextMorph-tp46402… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 18, 2012

Re: [Pharo-project] Spec questions

by StÃ©phane Ducasse

this is a good summary Ben willcertainly comment it. > Here I come with somme feedback on Spec. > > I tried to rebuilt an example using a tree view using spec this week-end, and it went fairly well (after a few misunderstandings). > > So, if I summarize what Spec is : > > * A herarchical view of models (a model is composed of submodels, where submodels may themselves be composite), up to elementary models provided by Spec. > * A related hierarchy of views, which are created by specs. > * Each model provides a defaultSpec to create the display. > * Each model, even a composite, must implement the following methods : initializePresenter, initializeWidgets. And use instantiateModels:! > * Models are linked to one another by appropriate "trigger" blocks. > > Good points : > > * Creating a window is very easy; just call openWithSpec. > * The declarative aspect of Spec methods seems nice for a GUI painter. > * There are enough models for a good start. > > A bit confusing so far with Spec: > > * Some examples have twice the submodels initialization (ClassMethodBrowser, in initialize and initializeWidgets) > * Two syntaxes are available in xSpec methods > * Two syntaxes are available in calls to instantiateModels: this will be fixed. > * I don't know yet how an existing application would connect to a Spec-based GUI (i.e. I don't know how to do a M-MVC app with it). indeed for now not clear if we will handle that > * I haven't found a declarative way of setting up relations between models. How would it be possible? > * The spec and instantiateModels syntax isn't detailed. > * I don't know how to integrate a non-spec morph and model. > * The level of customization is frightening (TreeModel defaultSpec) but this seems to be a Morphic problem overall. > * Exploring the generated morph hierarchy doesn't help much, due to the complexity linked with each morph object. I imagine that it often depend on the base widgetry > * Why isn't there is a bit of info in the HelpBrowser ? It's easier to read the doc this way instead of toggling between a Pharo window and a pdf reader. Because there is no need to duplicate documentation for an evolving system. > > I'll show you soon my results with spec! > > Thierry > > Le 11/07/2012 16:25, Benjamin a Ã©crit : >> To participate, you can: >> - take a random tool and rewrite it using Spec :) >> - read the tech report, and tell where it's clear/unclear :) >> - write comments ^^ >> - just use it, and share your feedback. Then all together we can improve Spec >> - try to convince other people to participate :D >> >> Thank you in advance, >> Ben >> >> >> On Jul 11, 2012, at 4:22 PM, Goubier Thierry wrote: >> >>> How to participate then ? >>> >>> Will it be possible to do maybe a simple, but "live" painter ? >>> >>> My first contact with Morphic to do a few gui elements (such as rewritting the Nautilus GUI :-P) found the interface to be on the confusing side (multiple morphs doing the same thing, complex instantiation interface on average). >>> >>> Thierry >>> >>> Le 11/07/2012 14:58, StÃ©phane Ducasse a Ã©crit : >>>> The plan is the following: >>>> >>>> - focus on really added value: >>>> - dynamic spec (and ben did it already). We should be able to build mac os x like finder engine >>>> >>>> - focus on four/five items (buttons, list, trees, text area) >>>> - build a first complete UIPainter something that can be used to >>>> place widgets on the screen and wire them. >>>> - we started to look again at UIBuilder in 1.0 to get what could be reused >>>> (for now we will probably drop the event aspect) >>>> - ideally the panes for widgets settings should be generated automatically >>>> based on some kind of meta description or spec of the widgets so that we can >>>> move faster >>>> >>>> - continue to rewrite all the tools with Spec. ChangeSorter and dualChangeSorter got into >>>> production. >>>> >>>> - continue the chapter. >>>> - probably some videos. >>>> >>>> Now if people want to help, there are welcome. >>>> I think that we need more users. A typical task would be to rewrite the MC tools. >>>> >>>> >>>>> >>>>> Do we have Spec examples for >>>>> - menues >>>>> - lists with icons >>>>> - trees >>>>> >>>>> already? What is the state and overall >>>>> plan for the near future. >>>>> >>>>> Thx >>>>> T. >>>>> >>>> >>>> >>>> >>> >>> >>> -- >>> 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 >>> >>> >>> >> >> >> >> > > > -- > 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 > > >

July 18, 2012