Hi,
Thanks. I guess it is probably what I need. I will look at it more closely.
I want to be able to map an XML structure on objects and support read/write
at the object level.
Cheers,
Doru
On Wed, Aug 6, 2014 at 11:28 AM, Norbert Hartl norb...@hartl.name wrote:
There is Magritte-XML. Or
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 3dc9768a72d80e8e5bb5cfa3346dee3879acecf5
https://github.com/pharo-project/pharo-core/commit/3dc9768a72d80e8e5bb5cfa3346dee3879acecf5
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/40153
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: dc3a940516ddca4f28ac8bdd5992a00da0d1a4c2
https://github.com/pharo-project/pharo-core/commit/dc3a940516ddca4f28ac8bdd5992a00da0d1a4c2
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/40154
Home: https://github.com/pharo-project/pharo-core
Branch: refs/tags/40155
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 16959331cd19e06bd5e2eed73d68b213ef119be0
https://github.com/pharo-project/pharo-core/commit/16959331cd19e06bd5e2eed73d68b213ef119be0
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Hi,
Pharo4 #155 now contains a Pointer explorer build with the Eye Tree Inspector
framework:
EyePointerExplorer openOn: #zot
EyePointerExplorer openStrongOn: #zot
Why is this needed?
—
Currently we still use a sub lass of ObjectExplorer for the PointerExplorer,
which means that we
Good step! :)
Doru
On Thu, Aug 7, 2014 at 11:21 AM, Marcus Denker marcus.den...@inria.fr
wrote:
Hi,
i added a simple AST tree view (inspired by the GT inspector) to the base
image.
see class EyeSyntaxTreeInspector
to get it, inspect
(Object#halt) ast
and select the syntax
Nice and well done (the AST inspector too) !
On 07 Aug 2014, at 11:17, Marcus Denker marcus.den...@inria.fr wrote:
Hi,
Pharo4 #155 now contains a Pointer explorer build with the Eye Tree Inspector
framework:
EyePointerExplorer openOn: #zot
EyePointerExplorer openStrongOn: #zot
Hi,
RecentSubmissions implements a UI that actually is too powerful (and thus
complex).
Therefore update #156 simplifies it radically:
RecentSubmissions can be simplified by using the Spec based MessageBrowser
instead of the included UI.
RecentMessageList package linesOfCode
Before:
1026
I created some fogbugz entries for morphs drawing with athens api.
And a parent case 13790 Port what is needed for Athens (drawing morphs)
We can test the Athens based drawing by putting the morphs into an
AthensWrapMorph.
But this is difficult for Morph like Dialog, Menus and SystemWindows.
So
Very nice! This deserves a blog post :)
Doru
On Thu, Aug 7, 2014 at 12:14 PM, Nicolai Hess nicolaih...@web.de wrote:
I created some fogbugz entries for morphs drawing with athens api.
And a parent case 13790 Port what is needed for Athens (drawing morphs)
We can test the Athens based
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 96ff8619011491137f1ee6ddc3aae0bc2bb99262
https://github.com/pharo-project/pharo-core/commit/96ff8619011491137f1ee6ddc3aae0bc2bb99262
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/40156
Home: https://github.com/pharo-project/pharo-core
On 07 Aug 2014, at 11:17, Marcus Denker marcus.den...@inria.fr wrote:
Hi,
Pharo4 #155 now contains a Pointer explorer build with the Eye Tree Inspector
framework:
EyePointerExplorer openOn: #zot
EyePointerExplorer openStrongOn: #zot
Why is this needed?
—
Currently we
Hi
in the debugger I think that we could double-click on a inspected items
and get a new inspector.
So could the eyeinspector open a new on doubleclick?
Stef
Branch: refs/tags/40157
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 2d54b0ad681f9595621d584703326c024f938bd1
https://github.com/pharo-project/pharo-core/commit/2d54b0ad681f9595621d584703326c024f938bd1
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Very nice! Please commit this code to Athens repository.
We will integrate it
http://smalltalkhub.com/mc/Pharo/Athens/main
This is a good way to debug stuff without killing own world :)
Just in case, i added you as Athens contributor, so you can commit.
On 7 August 2014 12:14, Nicolai Hess
Hi Igor! Nice to hear from you again :)
Doru
On Thu, Aug 7, 2014 at 1:31 PM, Igor Stasenko siguc...@gmail.com wrote:
Very nice! Please commit this code to Athens repository.
We will integrate it
http://smalltalkhub.com/mc/Pharo/Athens/main
This is a good way to debug stuff without
Hi everyone,
I noticed that browsing Object take several seconds (5s on my machine).
Evaluate Nautilus openOnClass: Object.
After profiling, I found it's because of ClassWidgetsetCachedHierarchyClass:
that calls SortHierarchically classbuildHierarchyForClasses: with a big
collection of
Without testing it more, I can’t tell you,
but your code seems to make sense :)
Ben
On 07 Aug 2014, at 13:47, Camille Teruel camille.ter...@gmail.com wrote:
Hi everyone,
I noticed that browsing Object take several seconds (5s on my machine).
Evaluate Nautilus openOnClass: Object.
After
On 07 Aug 2014, at 13:49, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote:
Without testing it more, I can’t tell you,
but your code seems to make sense :)
+1
Ben
On 07 Aug 2014, at 13:47, Camille Teruel camille.ter...@gmail.com wrote:
Hi everyone,
I noticed that browsing
Branch: refs/tags/40158
Home: https://github.com/pharo-project/pharo-core
Yes, that are may changes.
I think I was a bit confused about
showHierarchy : show the real hierarchy of an class
and
showHierarchy : show the classes in a package sorted hierarchically.
The first one is enabled by the hierarchy/flat-Button (show packages)
The second one is enabled by a
On 7 août 2014, at 14:26, Nicolai Hess nicolaih...@web.de wrote:
Yes, that are may changes.
I think I was a bit confused about
showHierarchy : show the real hierarchy of an class
and
showHierarchy : show the classes in a package sorted hierarchically.
The first one is enabled by the
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 3a551c57ff316820df9a37567263c626742d549e
https://github.com/pharo-project/pharo-core/commit/3a551c57ff316820df9a37567263c626742d549e
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/40159
Home: https://github.com/pharo-project/pharo-core
On 07 Aug 2014, at 12:30, Marcus Denker marcus.den...@inria.fr wrote:
- remove package Tool-Explorer (ca. 700 Loc, 6 classes)
after
https://pharo.fogbugz.com/f/cases/13794/Make-Tools-Explorer-unloadable
we can just unload it.
in 4.0 #159 The old Tool-Explorer package is now
2014-08-07 14:42 GMT+02:00 Camille Teruel camille.ter...@gmail.com:
On 7 août 2014, at 14:26, Nicolai Hess nicolaih...@web.de wrote:
Yes, that are may changes.
I think I was a bit confused about
showHierarchy : show the real hierarchy of an class
and
showHierarchy : show the classes in
Hi Alexandre,
The patch doesn't seems to be commited in Roassal2 repo...
Vincent
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
Alexandre Bergel
Envoyé : mercredi 6 août 2014 21:44
À : Moose-related development
Cc : Pharo Development List
Objet : Re: [Pharo-dev]
http://pharoweekly.wordpress.com/2014/08/07/new-pointer-explorer/
Nicolai
this is great! like that we can debug athensification of current morph :)
Stef
On 7/8/14 12:14, Nicolai Hess wrote:
I created some fogbugz entries for morphs drawing with athens api.
And a parent case 13790 Port what is needed for Athens (drawing morphs)
We can test the Athens based
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 5027c9f2a7ffbe8d53a786f4ba4085747590d65a
https://github.com/pharo-project/pharo-core/commit/5027c9f2a7ffbe8d53a786f4ba4085747590d65a
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/40160
Home: https://github.com/pharo-project/pharo-core
Okay, so that’s good, but you guys /really/ need to improve the
documentation on the mechanical walkthrough of how to actually claim
and submit a bug fix.
Today, I happened to have some spare time, so I figured, what the
hell, why not see if I can’t fix some bugs blocking the Pharo 4
I added a description on the contribute page
http://pharo.org/contribute
camille teruel wrote
I hope for comments
How do you activate it? I loaded into #40160, and copied your snippets from
the post, but when I did MyClass new senderMethod, no debugger came up...
-
Cheers,
Sean
--
View this message in context:
Ok, thank you.
2014-08-07 13:31 GMT+02:00 Igor Stasenko siguc...@gmail.com:
Very nice! Please commit this code to Athens repository.
We will integrate it
http://smalltalkhub.com/mc/Pharo/Athens/main
This is a good way to debug stuff without killing own world :)
Just in case, i added
On 7 août 2014, at 16:15, Sean P. DeNigris s...@clipperadams.com wrote:
camille teruel wrote
I hope for comments
How do you activate it? I loaded into #40160, and copied your snippets from
the post, but when I did MyClass new senderMethod, no debugger came up...
Hello Sean,
Sorry, I did
Sean P. DeNigris wrote
How do you activate it?
Oh, okay. I guess from looking at the tests that the new pragma is
deprecatedIn:replaceWith:
Next problem ;)...
I see that you've omitted the RB `@ syntax. While easier to type, I don't
like that it's more magical - what is the list of string
On 7 août 2014, at 16:32, Sean P. DeNigris s...@clipperadams.com wrote:
Sean P. DeNigris wrote
How do you activate it?
Oh, okay. I guess from looking at the tests that the new pragma is
deprecatedIn:replaceWith:
Next problem ;)...
I see that you've omitted the RB `@ syntax. While
camille teruel wrote
It's because I don't want users to have to know RB pattern syntax and also
because I plan to not depend on the rewriter in future versions.
Ah I see. RB is powerful and well-known. While easy to replace for simple
cases, I wonder if you might be forced to either limit that
Branch: refs/tags/40161
Home: https://github.com/pharo-project/pharo-core
Sorry for delay, I was taken by some other business :)
I fixed the bug you reported: check new version.
On 7 août 2014, at 16:42, Sean P. DeNigris s...@clipperadams.com wrote:
camille teruel wrote
It's because I don't want users to have to know RB pattern syntax and also
because I plan to not
Thats better - I think some overview text on the website and link to the wiki
where more people can put finer details works very well.
On the http://pharo.org/contribute-propose-fix page - perhaps we could do the
same sort of thing too?
I’m thinking maybe the following text might be better?
There are two things that have bothered me about our use of Metacello, but I
couldn't explain exactly why until now. These are two guidelines that I
think are important:
1. ConfigurationOfMyProject should live at repoOfMyProject. Any
MetaRepoForXyz should only be a copy of this config
2.
Before I was contributing to Pharo core much more than now. I have the
impression the fogbugz website does not help me. Maybe because I do not find
stopper bug anymore. Or maybe because I am focussing entirely to Moose and
Roassal. But I prefer the code google
Website.
Alexandre
Le
1. Make changes to a package of a MetaC project
2. In Versionner, the Release version button is disabled. Tried everything
I could think of - in left list selected latest version, then baseline,
created new baseline, committed package - but couldn't get it un-gray
I think as soon as project
On Aug 7, 2014, at 9:47 AM, stepharo steph...@free.fr wrote:
It’s up to the community to be involved with the tools they love and to
submit patches, and you’re totally right to remind everyone that it’s up to
us to improve Pharo if we want to keep it alive, but it’s up to the core
team to
thanks tim
I took into account your feedback ;)
have a look
On 7/8/14 18:10, Tim Mackinnon wrote:
Thats better - I think some overview text on the website and link to
the wiki where more people can put finer details works very well.
On the http://pharo.org/contribute-propose-fix page -
Could you extend http://pharo.org/contribute-propose-fix a bit? And add a
screenshot of Slice Maker (I attach one). The following text would have
helped me (I paste the markdown. I also posted it on NoteHub for a better
reading experience
http://www.notehub.org/2014/8/7/how-to-propose-a-bug-fix):
Thanks martin I will have a look tomorrow.
Stef
On 7/8/14 22:11, MartinW wrote:
Could you extend http://pharo.org/contribute-propose-fix a bit? And add a
screenshot of Slice Maker (I attach one). The following text would have
helped me (I paste the markdown. I also posted it on NoteHub for a
On Thu, Aug 7, 2014 at 9:40 AM, Sean P. DeNigris s...@clipperadams.com
wrote:
There are two things that have bothered me about our use of Metacello, but
I
couldn't explain exactly why until now. These are two guidelines that I
think are important:
1. ConfigurationOfMyProject should live at
Dale Henrichs wrote:
On Thu, Aug 7, 2014 at 9:40 AM, Sean P.
DeNigris s...@clipperadams.com
wrote:
There
are two things that have bothered me about our use of Metacello, but I
couldn't explain exactly why until now. These are two guidelines that I
think are important:
1.
Ben and Sean,
After a bit more thought, I believe that it should be okay to make copies,
but there does need to be a single primary repository where the correct and
latest configuration can be found.
Putting copies of configurations into repositories to make project
discovery easier is a good
57 matches
Mail list logo
