[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/476/ 2 regressions found. KernelTests.Processes.ProcessTest.testHighPriorityOverridesWaitTime Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion
Re: [Pharo-dev] [smaltalk-gsoc-students] Some news of the UIPainter project
2013/9/8 b...@openinworld.com
**
Thanks Erwan. Really sweet tool. That video did the trick to stimulate my
interest to try it out, so I've got some feedback. Don't take them as
criticisms. They cover some things that probably have not been a priority
so far.
feedbacks good or not is always needed :)
Video:
V1. Nice structure, short and simple. Easy to follow, except the text you
type in is hard to read. There is a lot of irrelevant space around the
tool. It would be better is you could zoom in, so the tool takes the
entire frame. You might also consider shrinking the size of the tool a bit
from its default size. The clearer the video the more people will be drawn
in to try it out.
Yeah, maybe i should add subtitles ... I will apply your tips for the
next videos.
Application:
A1. It would be good to have a 'Duplicate' icon with the widget halos.
Once you have sized a button, the easiest way to get another the same size
is to copy. Also in some cases, the code would be very similar.
Ok, my mentor suggested me to create it :)
Added to todo list
A2. With 'GenerateUI Provide following information...' it is awkward
that Category defaults to a system category. As well, having all system
categories listed in the pulldown is awkward, since most of these will
never be a target. However offhand I can't think of a good solution. Some
way to sort probable targets near the top. Maybe a tree list where the
top-level items provide a filter for the second level items. For example,
top-level items / filters might be:
* Recent - in particularly, the category just created would appear here
* Categories ending in '-UI'
* Categories containing classes that inherit from a particular object
(like ComposableModel)
* Categories that contain classes that contain a certain method (like
#generatedFromUIPainter)
* 'All categories' would be the last as the last top-level items .
Yeah. ComposableModel allsubclasses packagesList shoud be more efficient,
like you suggested.
Added to todo list
A3. In the same Category field, the hash(#) and the quotes('') seem
redundant. Indeed, when I click the add category + button and type
MyCounter then click Add, it shows in the list without quotes e.g.
#MyCounter instead of #'MyCounter' like the rest of them. If I try to
create 'MyCounter2' then I get #''MyCounter2''.
Smalltalk environment organization categories sorted asArray inspect
...holds #MyCounter and #'''MyCounter2''' instead of #'MyCounter' and
#'MyCounter2' like the rest of the entries,
so the problem would seem to be in UIPainterSpecGenerationCategoryAddUI
button
line: SystemOrganizer default addCategory: self input getText asString.
For comparison, I looked at how Nautilus adds packages (by putting a halt
at the top of AbstractNautilusUIaddPackage), which uses [self
browsedEnvironment packageOrganizer createPackageNamed: name] in
#addPackageBasedOn: . For one thing, this uses [self browsedEnvironment
packageOrganizer] evaluates to RPackageOrganiser. I don't know how that
differs from SystemOrganizer, but maybe consider doing it the same of
Nautilus.
I know there is bugs here, my latest commit was to fix some bugs with it,
but it's not enough. I also have the problem of the refresh.
Thanks for the Nautilus tip, i will have a look on it
Added to todo list
A4. It would be nice if there was an Open or Test button at the top,
that generates and opens the form, rather than having to do it manually
from a Workspace.
Yeah, maybe a window open or not after the generation process
Added to todo list
A5. Rather than provide the Class Name, Category and Title every time you
generate, these would be better as project properties that remain
consistent every time you generate.
Hum ... many changes for that i guess.
I don't promise anything but i will have a look on it :)
Added to todo list
A6. The tooltip of the 'paperclip' halo icon is 'unknown tooltip'. Btw,
what is its purpose. Clicking makes it turn red but otherwise seems to have
no effect.
The effect is sticky morph when you move/resize it, the morph will stick
to the closest point of the grid. When the button is red this option is
disable.
Are you sure than it does not work ? It works for me :s
I also added to my todo list the ability to change the grid size.
cheers -ben
Thanks for feedbacks :)
Erwan Douaille wrote:
Here is a video about how to build a counter with
UIPainter:https://www.youtube.com/watch?v=S4IfW0TQhSc
2013/9/7 Erwan Douaille douailleer...@gmail.com douailleer...@gmail.com
Hi :)
Yes i will. I'm writting a documentation about how to install it, use it,
... add new widgets ...
As a part of the GSoC i have to write doc, tests
I will do some screencasts. A counter is a nice idea.
Tonight i will upload a screencast for the counter :)
2013/9/6 Alexandre Bergel alexandre.ber...@me.com alexandre.ber...@me.com
Hi!
I've just tried and it
Re: [Pharo-dev] [smaltalk-gsoc-students] Some news of the UIPainter project
On Sep 8, 2013, at 10:33 AM, Erwan Douaille douailleer...@gmail.com wrote:
2013/9/8 b...@openinworld.com
Thanks Erwan. Really sweet tool. That video did the trick to stimulate my
interest to try it out, so I've got some feedback. Don't take them as
criticisms. They cover some things that probably have not been a priority so
far.
feedbacks good or not is always needed :)
Video:
V1. Nice structure, short and simple. Easy to follow, except the text you
type in is hard to read. There is a lot of irrelevant space around the tool.
It would be better is you could zoom in, so the tool takes the entire frame.
You might also consider shrinking the size of the tool a bit from its default
size. The clearer the video the more people will be drawn in to try it out.
Yeah, maybe i should add subtitles ... I will apply your tips for the next
videos.
Application:
A1. It would be good to have a 'Duplicate' icon with the widget halos. Once
you have sized a button, the easiest way to get another the same size is to
copy. Also in some cases, the code would be very similar.
Ok, my mentor suggested me to create it :)
Added to todo list
A2. With 'GenerateUI Provide following information...' it is awkward that
Category defaults to a system category. As well, having all system categories
listed in the pulldown is awkward, since most of these will never be a
target. However offhand I can't think of a good solution. Some way to sort
probable targets near the top. Maybe a tree list where the top-level items
provide a filter for the second level items. For example, top-level items /
filters might be:
* Recent - in particularly, the category just created would appear here
* Categories ending in '-UI'
* Categories containing classes that inherit from a particular object (like
ComposableModel)
* Categories that contain classes that contain a certain method (like
#generatedFromUIPainter)
* 'All categories' would be the last as the last top-level items .
Yeah. ComposableModel allsubclasses packagesList shoud be more efficient,
like you suggested.
Added to todo list
A3. In the same Category field, the hash(#) and the quotes('') seem
redundant. Indeed, when I click the add category + button and type
MyCounter then click Add, it shows in the list without quotes e.g.
#MyCounter instead of #'MyCounter' like the rest of them. If I try to create
'MyCounter2' then I get #''MyCounter2''.
Smalltalk environment organization categories sorted asArray inspect
...holds #MyCounter and #'''MyCounter2''' instead of #'MyCounter' and
#'MyCounter2' like the rest of the entries,
so the problem would seem to be in UIPainterSpecGenerationCategoryAddUI
button
line: SystemOrganizer default addCategory: self input getText asString.
For comparison, I looked at how Nautilus adds packages (by putting a halt at
the top of AbstractNautilusUIaddPackage), which uses [self
browsedEnvironment packageOrganizer createPackageNamed: name] in
#addPackageBasedOn: . For one thing, this uses [self browsedEnvironment
packageOrganizer] evaluates to RPackageOrganiser. I don't know how that
differs from SystemOrganizer, but maybe consider doing it the same of
Nautilus.
I know there is bugs here, my latest commit was to fix some bugs with it, but
it's not enough. I also have the problem of the refresh.
Thanks for the Nautilus tip, i will have a look on it
Added to todo list
I think this behaviour is managed in AbstractTool.
Maybe you could consider having an instance of AbstractTool as an inst var and
delegate this job to it :)
I just figured out that you will maybe need a way to specify the
browsedEnvironment
Ben
A4. It would be nice if there was an Open or Test button at the top, that
generates and opens the form, rather than having to do it manually from a
Workspace.
Yeah, maybe a window open or not after the generation process
Added to todo list
A5. Rather than provide the Class Name, Category and Title every time you
generate, these would be better as project properties that remain consistent
every time you generate.
Hum ... many changes for that i guess.
I don't promise anything but i will have a look on it :)
Added to todo list
A6. The tooltip of the 'paperclip' halo icon is 'unknown tooltip'. Btw, what
is its purpose. Clicking makes it turn red but otherwise seems to have no
effect.
The effect is sticky morph when you move/resize it, the morph will stick to
the closest point of the grid. When the button is red this option is disable.
Are you sure than it does not work ? It works for me :s
I also added to my todo list the ability to change the grid size.
cheers -ben
Thanks for feedbacks :)
Erwan Douaille wrote:
Here is a video about how to build a counter with UIPainter:
https://www.youtube.com/watch?v=S4IfW0TQhSc
2013/9/7 Erwan Douaille douailleer...@gmail.com
[Pharo-dev] [update 3.0] #30377
30377 - 11520 Give Job its own announcer, no longer use the SystemAnnouncer https://pharo.fogbugz.com/f/cases/11520 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.89.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1596.diff signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/477/ 1 regressions found. Tests.Release.ReleaseTest.testInstanceSideMethodsWithNilKeyInLastLiteral
[Pharo-dev] Begone TranslucentColor
Hi, I'm happy to announce that I finished working on the Issue 1551 [1], to finally remove the redundant TranslucentColor class from the Pharo. You can to read more about it here: http://fernandoolivero.wordpress.com/2013/09/08/begone-translucentcolor/. Stay tuned, more cleanups are on the way. Fernando pd: Have a nice ESUG @ beautiful Annecy! [1] https://pharo.fogbugz.com/f/cases/11519/Merge-Color-and-Translucent-Color
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/477/ 1 regressions found. Tests.Release.ReleaseTest.testInstanceSideMethodsWithNilKeyInLastLiteral
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/478/ 1 regressions found. Graphics.Tests.Primitives.RectangleTest.testInsettingByPointPairShouldNotProduceNegativeRectangle
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/478/ 1 regressions found. Graphics.Tests.Primitives.RectangleTest.testInsettingByPointPairShouldNotProduceNegativeRectangle
Re: [Pharo-dev] The Moldable Debugger Framework
Hi, Great job, Andrei! Just a couple of complementary remarks: - Moldable tools offer a significant departure from the original Smalltalk environment. Just think about it: we pride ourselves on our live environment, yet the default tools are utterly static. In contrast, the moldable debugger lets you switch change your debugging tools while debugging. Another example from the same family is the GTInspector: there too you can switch the inspection workflow and presentation while inspecting. Live should describe everything in our environment, not just the code model. - The Moldable Debugger also brings enhanced presentations into the debugger. For example, in the Glamour-specific debugger instead of only textual presentations of your objects, you get a visualization that shows the schematics of your browser. - But, the Moldable Debugger is not just a debugger or a collection of debuggers, it's an engine for building your own debuggers. And the great thing about it is that it makes it cheap. A couple of hundred lines of code cheap. This was made possible through to a complete rewrite of the debugger model that is essentially integrated in Pharo 3.0. - By making it cheap, a moldable tool opens another door: if you spend your energy building a framework, you should spend a little fraction of the overall effort and ship dedicated tools to handle that framework, too. This can increase the value of your framework significantly. For example, in Moose, we now have a browser dedicated for developing and analyzing parsers, we have debuggers for PetitParser and Glamour, we have dedicated editors for building interactive tools like Roassal or Glamour, and we have enhancements to the GTInspector for various object types we work often with. This makes Moose much more than a library: it makes it a versatile environment with which you can craft your own analyses cheaply. Yet, the cost of these additional tools is tiny compared with the overall cost of building the engines. All in all, please take a bit of time and look into this work. Moose offers examples of how it looks in practice, but the moldable tools should be used for any Pharo project. Yes, having worked on this I am biased, but I believe if we go on this route we can redefine what the IDE means. And this can be a huge opportunity both for Pharo and for Moose. Cheers, Doru On Sun, Sep 8, 2013 at 12:31 AM, Andrei Vasile Chis chisvasileand...@gmail.com wrote: Hi, I'd like to announce the first version of the Moldable Debugger. It is a framework for creating and working with domain specific debuggers. It's integrated into Moose and it currently comes with three debuggers: one for announcements, one for PetitParser and one for Glamour. More information can be found here: * http://scg.unibe.ch/research/moldabledebugger* A video introducing the framework is here: *https://vimeo.com/73980431* (more are on the way) Cheers, Andrei -- www.tudorgirba.com Every thing has its own flow
[Pharo-dev] [update 3.0] #30379
30379 - 11540 Monticello unique names should be calculated in destination repository, not all https://pharo.fogbugz.com/f/cases/11540 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-EstebanLorenzano.625.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-EstebanLorenzano.902.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-EstebanLorenzano.534.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/MonticelloGUI-EstebanLorenzano.256.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-EstebanLorenzano.859.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Metacello-MC-EstebanLorenzano.675.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-EstebanLorenzano.1599.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Gofer-Core-EstebanLorenzano.204.diff
Re: [Pharo-dev] [update 3.0] #30379
yes! :) On 2013-09-08, at 09:42, Esteban Lorenzano esteba...@gmail.com wrote: 30379 - 11540 Monticello unique names should be calculated in destination repository, not all https://pharo.fogbugz.com/f/cases/11540 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-EstebanLorenzano.625.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-EstebanLorenzano.902.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-EstebanLorenzano.534.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/MonticelloGUI-EstebanLorenzano.256.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-EstebanLorenzano.859.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Metacello-MC-EstebanLorenzano.675.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-EstebanLorenzano.1599.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Gofer-Core-EstebanLorenzano.204.diff signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] [update 3.0] #30381
30381 - 11542 Load FileTree in the image core https://pharo.fogbugz.com/f/cases/11542
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/481/ 3 regressions found. KernelTests.Classes.BehaviorTest.testHasAbstractMethods Refactoring.Tests.Core.RBClassTest.testObjectIsNotAbstract Refactoring.Tests.Core.RBPullUpMethodTest.testPullUpWithMethodThatCannotBePushedDown
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/481/ 3 regressions found. KernelTests.Classes.BehaviorTest.testHasAbstractMethods Refactoring.Tests.Core.RBClassTest.testObjectIsNotAbstract Refactoring.Tests.Core.RBPullUpMethodTest.testPullUpWithMethodThatCannotBePushedDown
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/481/ 3 regressions found. KernelTests.Classes.BehaviorTest.testHasAbstractMethods Refactoring.Tests.Core.RBClassTest.testObjectIsNotAbstract Refactoring.Tests.Core.RBPullUpMethodTest.testPullUpWithMethodThatCannotBePushedDown
[Pharo-dev] Nautilus Newlist
Is there anything besides manpower that prevents us form using NewList in Nautilus? signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] What is the replacement for CMD-F to find a class in nautilus? [EOM]
[subject said it all]. Best -Tobias
Re: [Pharo-dev] What is the replacement for CMD-F to find a class in nautilus? [EOM]
cmd f c 2013/9/8 Tobias Pape das.li...@gmx.de [subject said it all]. Best -Tobias -- Best regards, Douaille Erwan douaille.er...@gmail.com
Re: [Pharo-dev] [Moose-dev] The Moldable Debugger Framework
Looks like great! We will have great discussions at ESUG :) Alexandre Le 07-09-2013 à 18:31, Andrei Vasile Chis chisvasileand...@gmail.com a écrit : Hi, I'd like to announce the first version of the Moldable Debugger. It is a framework for creating and working with domain specific debuggers. It's integrated into Moose and it currently comes with three debuggers: one for announcements, one for PetitParser and one for Glamour. More information can be found here: http://scg.unibe.ch/research/moldabledebugger A video introducing the framework is here: https://vimeo.com/73980431 (more are on the way) Cheers, Andrei ___ Moose-dev mailing list moose-...@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Re: [Pharo-dev] The Moldable Debugger Framework
excellent. BTW do you have some news about the object centric debugger for Pharo30? Stef On Sep 8, 2013, at 12:31 AM, Andrei Vasile Chis chisvasileand...@gmail.com wrote: Hi, I'd like to announce the first version of the Moldable Debugger. It is a framework for creating and working with domain specific debuggers. It's integrated into Moose and it currently comes with three debuggers: one for announcements, one for PetitParser and one for Glamour. More information can be found here: http://scg.unibe.ch/research/moldabledebugger A video introducing the framework is here: https://vimeo.com/73980431 (more are on the way) Cheers, Andrei
Re: [Pharo-dev] The Moldable Debugger Framework
I'm afraid that's going to take a while :( We are having trouble migrating Bifröst to Pharo 3.0 due to some dependencies issues with Opal compiler... but I was writing another email with that and some other updates :) Congrats Andrei! I'm really honored to have you as my mentor, I have learnt a lot from you in these months :) On 8 September 2013 15:47, Stéphane Ducasse stephane.duca...@inria.frwrote: excellent. BTW do you have some news about the object centric debugger for Pharo30? Stef On Sep 8, 2013, at 12:31 AM, Andrei Vasile Chis chisvasileand...@gmail.com wrote: Hi, I'd like to announce the first version of the Moldable Debugger. It is a framework for creating and working with domain specific debuggers. It's integrated into Moose and it currently comes with three debuggers: one for announcements, one for PetitParser and one for Glamour. More information can be found here: * http://scg.unibe.ch/research/moldabledebugger* A video introducing the framework is here: *https://vimeo.com/73980431* (more are on the way) Cheers, Andrei
Re: [Pharo-dev] Nautilus Newlist
Is there something beside manpower which prevent you from anything ? :P But to answer your question, no, nothing. The thing is since the initialisation is a bit different with the NewList, it's tricky in some situation Ben On Sep 8, 2013, at 6:54 PM, Camillo Bruni camillobr...@gmail.com wrote: Is there anything besides manpower that prevents us form using NewList in Nautilus?
