February 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12336

by StÃ©phane Ducasse

12336 ----- Issue 3583: Shout should only be active in code panes. - FixWorkspaceAgain.1 - FixWorkspace1.2.1 - PrepareFixWorkspaceMenu.2 - FixWorkspaceMenu.2.cs Thanks Benjamin van Ryseghem. Stef (just spent one hour on that...)

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by StÃ©phane Ducasse

before complaining let them work. They told us that they missed their first milestone because they had other client work (which is good for them). We (the ESUG board and them) decided that they should get started and get something before asking for feedback else they will lose time replying to the "I want that and that and that and that". They have a list of mandatory features based on our experience using Squeaksource and we will see. After they will ask for feedback and the code will be MIT. Stef On Feb 16, 2011, at 9:33 AM, Torsten Bergmann wrote: > Anyone know something about the current state > of this project. Looks like it is not developed open > enough ... at least one is not able to follow any > progress or give feedback. > > Bye > T. > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat! http://portal.gmx.net/de/go/dsl >

Feb. 16, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #79 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 I integrate - FixWorkspaceAgain.1 - FixWorkspace1.2.1 - PrepareFixWorkspaceMenu.2 - FixWorkspaceMenu.2.cs in 1.2 Now FixSHWorkspace.1 FixSHWorkspaceToFixMenu.1 should be integrated in shout?

Feb. 16, 2011

Re: [Pharo-project] A new GUI visual designer

by Craig Latta

> > But whatever [your GUI widgetry model] is, you can transfer a > > method using it to another live system, because (at least in the > > stuff I wrote) you can transfer any method no matter what its > > literals are. > > I see, but then we have to check if a given message send may end up > in MNUs, right? No; it's still up to the author of the code to create modules which contain all the methods required for the application. There are ways to automate that, though. (For example, creating modules by noting all the methods which get run by the application's unit tests.) > I think I can see this grand vision working if some kind of > 'equivalence' of widgets could be produced so that a Morphic based > GUI design could be used in [say] wxWidgets based {Pharo,Squeak}. I'm not suggesting anything (yet) about what the GUI object model should be, just that we don't need to resort to transcribing the objects into a textual ("dead") form in order to deploy it. > > ...you're dealing with first-class objects all the time. That's > > what makes this scheme adaptable to GUI framework change. You > > can examine GUI objects, ask them to convert themselves to > > another framework's structures, etc. with familiar Smalltalk > > tools. > > I understand that in order that to be possible they would need to > answer to the become: protocol and need to have in the target image > both the frameworks, right? Not necessarily, no (on both issues). > With the caveat I may still have not understood your proposal in > full... I'm just suggesting that representing GUI structures non-programmatically can be done by using objects directly, without transcription (without viewspecs, XML, etc.). > I see that in limit, the right mapping would be to the host system GUI > primitives, so the whole issue of having to design a specific widget > hierarchy would vanish. Correct? Again, I'm not saying anything yet about what a good GUI object model would be. > regards, and keep the research in Spoon! Thanks! -C -- Craig Latta www.netjam.org/resume +31 06 2757 7177 + 1 415 287 3547

Feb. 16, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #78 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Yes, my bad, I forgot to remove a line after a copy/paste ... Now it works in a 1.2 core, and it works well when I load shout ^^ Attachments: FixWorkspaceMenu.2.cs 9.8 KB

Feb. 16, 2011

Re: [Pharo-project] Issue 3714 in pharo: CS removeSelector does not dirty packages

by pharo＠googlecode.com

Comment #1 on issue 3714 by stephane...(a)gmail.com: CS removeSelector does not dirty packages http://code.google.com/p/pharo/issues/detail?id=3714 Cyrille can you check that with RPackage?

Feb. 16, 2011

[Pharo-project] Issue 3714 in pharo: CS removeSelector does not dirty packages

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3714 by stephane...(a)gmail.com: CS removeSelector does not dirty packages http://code.google.com/p/pharo/issues/detail?id=3714 Workspace removeSelector: #embeddedInMorphicWindowLabeled:! does not make the package dirty. This can be normal because this is a low level API method. Now this expression is saved in the changeset when we remove a method. So the task to do is: - check if there is another API method that raise the correct notification of changes - change ChangeSorter to use this api

Feb. 16, 2011

[Pharo-project] Apparently removeSelector: does not dirty packages...

by StÃ©phane Ducasse

For example Workspace removeSelector: #embeddedInMorphicWindowLabeled:! does not make the package dirty. This can be normal because this is a low level API method. Now this expression is saved in the changeset when we remove a method. So the task to do is: - check if there is another API method that raise the correct notification of changes - change ChangeSorter to use this api http://code.google.com/p/pharo/issues/detail?id=3714 Stef

Feb. 16, 2011

Re: [Pharo-project] Loading Seaside into Pharo 1.2 core

by Torsten Bergmann

> I want to clarify that the 3.0.4 configuration _is_ intended to > correctly load into PharoCore1.2. Nice, thanks! Bye Torsten -- Schon gehÃ¶rt? GMX hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://www.gmx.net/de/go/toolbar

Feb. 16, 2011

[Pharo-project] New Squeaksource ...

by Torsten Bergmann

Anyone know something about the current state of this project. Looks like it is not developed open enough ... at least one is not able to follow any progress or give feedback. Bye T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Feb. 16, 2011