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

Re: [Pharo-project] Issue 2786 in pharo: Mixed concerns on Object>>saveOnFile

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 2786 by marcus.d...(a)gmail.com: Mixed concerns on Object>>saveOnFile http://code.google.com/p/pharo/issues/detail?id=2786 in 13107

March 24, 2011

Re: [Pharo-project] Issue 2240 in pharo: CondenseChange Trait Tests

by pharo＠googlecode.com

Updates: Status: Closed Comment #5 on issue 2240 by marcus.d...(a)gmail.com: CondenseChange Trait Tests http://code.google.com/p/pharo/issues/detail?id=2240 in 13107

March 24, 2011

Re: [Pharo-project] Issue 1765 in pharo: JPEGReadWriter>>#decompressionTest should be made into a Sunit Test

by pharo＠googlecode.com

Updates: Status: Closed Comment #7 on issue 1765 by marcus.d...(a)gmail.com: JPEGReadWriter>>#decompressionTest should be made into a Sunit Test http://code.google.com/p/pharo/issues/detail?id=1765 in 13107

March 24, 2011

Re: [Pharo-project] Issue 3768 in pharo: Deprecate String >> get/putInteger32:

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3768 by marcus.d...(a)gmail.com: Deprecate String >> get/putInteger32: http://code.google.com/p/pharo/issues/detail?id=3768 in 13107

March 24, 2011

Re: [Pharo-project] Issue 3858 in pharo: On windows, Error when dropping an image in the vm

by pharo＠googlecode.com

Comment #3 on issue 3858 by Torsten....(a)astares.de: On windows, Error when dropping an image in the vm http://code.google.com/p/pharo/issues/detail?id=3858 If you want others to reproduce it you should at least point to the image: - Is it an image from http://www.moosetechnology.org/download - if so which moose version 4.0, 4.1., 4.2, 4.3 or 4.4.? - or is it one from the Hudson used for Moose? http://hudson.moosetechnology.org ? A description of the problem/error message would also help to see if it is a pharo or moose problem

March 24, 2011

Re: [Pharo-project] Issue 2240 in pharo: CondenseChange Trait Tests

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #4 on issue 2240 by marcus.d...(a)gmail.com: CondenseChange Trait Tests http://code.google.com/p/pharo/issues/detail?id=2240 code with the test attached. Test is green. The changeset adds some methods to MethodReference that where missed when removing LocatedMethod. Attachments: TraitsFileOutTest.2.cs 2.7 KB

March 24, 2011

Re: [Pharo-project] Issue 2254 in pharo: sorted and sorted: should be moved to TSortable

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #3 on issue 2254 by marcus.d...(a)gmail.com: sorted and sorted: should be moved to TSortable http://code.google.com/p/pharo/issues/detail?id=2254 (No comment was entered for this change.)

March 24, 2011

Re: [Pharo-project] What is the future of GUI in Pharo?

by Janko MivÅ¡ek

Let me think a bit towards very far vision, don't be angry on me .. :) Here it is: - a common UI for both Pharo and the web, by extending Morphic ideas to the web while things like CSS back to Morphic. - Morphic on top Jtalk for the web? The same API level one for Pharo too? - Isn't this like an extension, or better, towards the idea behind Lively? Janko On 24. 03. 2011 09:17, StÃ©phane Ducasse wrote: > Here is the vision: we need it better and simpler with better widgets, better UIBuilder and better tools. > if you give me some engineers I can build something clear, now this is not the case so we are exploring and multiple paths > Now if you want to see the system moving faster just join and help > > So here is a list > > Frameworks > ---------- > First step > - Integrate polymorph (move class to the right packages, remove overrides) > - Reduce complexity of morphic when possible > > In parallel > - Clean SimpleMorphic (remove preferences, PopUpChoiceMenu) > - Based on SimpleMorphic, clean also Morphic > > Alain told me that he want to take simpleMorphic and create a kernel that can be run and debugged on the side > or morphic. Then he wants to add list and tree and see if he can add a better version of polymorph. > Now he can fail too. so this is why the incremental points are important. > > Fixing and improving announcements is important > - It was done during the last sprint > - We were discussing how to make anonucement faster to avoid to climbing their parent tree - but no success so far. > - We evaluated signals (as used in HPI frameworks) and we do not really like it. The use of thisContext is probably a problem among others. > > Widgets > ------- > We need better widgets > - accordion > - better text > - grid > We should evaluate your widgets to integrate them. But first we should clean what is there. > Stacking on top of bad foundation just make the system more complex and difficult to maintain. > > > Low level: a new Canvas and clean event > ----------------------------------- > Igor started to design a new canvas called Athens and we will see where it will go > Again if people want to see this coming faster, they should help. > The idea is to have a canvas for > - opengl > - cairo > - bitbl > > We are evaluating the event hierarchy designed by Mickael Rueger and we would like > to integrate it: eliminate the floating of arrays btween eventfetcher and HandMorph > the idea is that event should be emitted by eventSensor not raw array > > I'm starting to clean Sensor references that are using the polling behavior because we should not have polling anymore > the Windows virtual machine should be fixed and get the enhancement that Igor sent more than a year ago for the input semaphore > and so that all the vm are aligned. > > > Tools > ----- > We are rewriting from scratch the basic tools > - Browser (Nautilus soon to be announced - with groups, package browsers, refactorings, may be plugin architecture) > - Finder > - TestRunner (soon) > - MCBrowser > - Debugger (waiting for a debugger model) > The idea is that we want to kill the StringHolder hierarchy alltogther so in a first phase we will probably have to keep it > for the debugger but only for it. > > We will remove toolBuilder (we are waiting to finish the TestRunner rewriting). > > Glamour will probably be used as a default super IDE of the future but it depends on people > We are currently working on the fall back (the tools when you have nothing). > > So I hope it clarifies the picture and you are welcome to help. Now an important point > This is not because something is under preparation that the other should not get clean and improve. > We have no problem throwing away our effort if something better come up but we should be prepared that nothing come up or is delayed > this is why we have this parallel strategy. > > > Stef > > > > > > > > >> Many new things is happens this days on Pharo, and I donÂ´t understand the >> status of all. >> >> What is the future of GUI in Pharo? what changes will happen? which is the >> roadmap? Now I see SimpleMorphic. Pharo will work with it? Pharo will works >> with another way of draw/render the morphs? >> We will reduce the number of morph classes and hierarchy? The Morphic UI >> designer will be incorporated in dev image? >> >> Thanks for your answers. > > > -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

March 24, 2011

Re: [Pharo-project] Issue 3853 in pharo: Integrate image-side changes to use new primitive to disable module loading

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3859 Comment #1 on issue 3853 by marcus.d...(a)gmail.com: Integrate image-side changes to use new primitive to disable module loading http://code.google.com/p/pharo/issues/detail?id=3853 (No comment was entered for this change.)

March 24, 2011

Re: [Pharo-project] Issue 3859 in pharo: Pluggin control

by pharo＠googlecode.com

Comment #1 on issue 3859 by marcus.d...(a)gmail.com: Pluggin control http://code.google.com/p/pharo/issues/detail?id=3859 Issue 3853 has been merged into this issue.

March 24, 2011