This is really beautiful :)
Doru
On Wed, Jan 1, 2014 at 12:29 AM, Alexandre Bergel
wrote:
> Happy new year!!
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> | view txt x y el shape size offset |
> txt :=
> '
> x x xxx x
> x x x xx x x
>x x x x xx x
>
Happy New Year, everyone!
Doru
On Tue, Dec 31, 2013 at 7:53 PM, Stéphane Ducasse wrote:
> Hi pharoers
>
> Sometimes I think that we are crazy to build this system but this is really
> important to have dreams and make them becoming true. :)
> I really like what we are doing: we are building a
Sounds like a great New Year gift :). I will review the code today.
Cheers,
Doru
On Wed, Jan 1, 2014 at 3:20 AM, DeNigris Sean wrote:
> Thanks for the feedback everyone!
>
> A few enhancements:
> - Close on escape
> - Select next on down arrow when open
> - Show all on down arrow when closed
>
Thanks for the feedback everyone!
A few enhancements:
- Close on escape
- Select next on down arrow when open
- Show all on down arrow when closed
- Select previous on up arrow
- Accept on enter - requires an override in PluggableTextFieldMorph, but I
think the change can be integrated in Core
-
wow!
2014/1/1 Alexandre Bergel :
> Happy new year!!
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> | view txt x y el shape size offset |
> txt :=
> '
> x x xxx x
> x x x xx x x
>x x x x xx x
> xx x xx
> x x x x x
>
Happy new year!!
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| view txt x y el shape size offset |
txt :=
'
x x xxx x
x x x xx x x
x x x x xx x
xx x xx
x x x x x
x x x x
'.
view := ROView new.
x :
Happy New Year to all
Light Guardians . I wish you to be healthy and full with passion to
explore. I am so curious to see what kind of surprises you have in store
for me for 2014.
Στις 31 Δεκ 2013 11:38 μ.μ., ο χρήστης "Yuriy Tymchuk"
έγραψε:
> Happy new year all!
>
> And thank you Stef, for bein
Happy new year all!
And thank you Stef, for being the centre of our galaxy and keeping us together.
Uko
On 31 Dec 2013, at 20:53, Stéphane Ducasse wrote:
> Hi pharoers
>
> Sometimes I think that we are crazy to build this system but this is really
> important to have dreams and make them be
>> I'm not sure what you mean. Sounds like a "maybe" ;)
>
> no just that it is pending for integration.
No. The code was globally correct, but with some strange things.
I asked for more details about the implementation, never got an answer.
So basically, there is a code base for this. But it wi
On 31 Dec 2013, at 20:51, Stephan Eggermont wrote:
> Hi Doru,
>
> I like very much how easy it is to modify and adapt these tools.
> The higher abstraction level provided by Glamour really pays off here.
> In the past week I also looked at Nautilus, MCWorkingCopyBrowser and
> the UiDesigner and
On 31 Dec 2013, at 18:13, Sean P. DeNigris wrote:
> Benjamin Van Ryseghem-2 wrote
>> On 30 Dec 2013, at 01:55, Sean P. DeNigris <
>
>> sean@
>
>> > wrote:
>>> Will that be used for Nautilus eventually?
>>
>> There is a bug entry. With a slice.
>
> I'm not sure what you mean. Sounds like a "m
Sean wrote:
>I would've fixed it already, but since someone went through the trouble to add
>a setting, I figured maybe there was a use case I was missing...
Please go ahead, I won't have any more time to do it today or tomorrow. Design,
no choice!
Stephan
Hi Doru,
I like very much how easy it is to modify and adapt these tools.
The higher abstraction level provided by Glamour really pays off here.
In the past week I also looked at Nautilus, MCWorkingCopyBrowser and
the UiDesigner and the difference is shocking.
Stephan
On Tue, Dec 31, 2013 at 8:35 PM, kilon alios wrote:
> I really like the idea of having debugger adjust to the workflow of the
> coder, I think the same should apply to Browser too, though AFAIK already
> Nautilus is very flexible.
>
> Congratulations on the videos by the way, they really show the
Thanks for spotting this problem. I renamed a few classes recently.
Should be GTGenericStackDebugger instead of GTDebugger
The following script should work:
Gofer new
url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main';
configuration;
load.
(Smalltalk globals at: #Configurati
Hi pharoers
Sometimes I think that we are crazy to build this system but this is really
important to have dreams and make them becoming true. :)
I really like what we are doing: we are building a strong community and a
really great system.
Of course it could be better but it is going in the righ
I really like the idea of having debugger adjust to the workflow of the
coder, I think the same should apply to Browser too, though AFAIK already
Nautilus is very flexible.
Congratulations on the videos by the way, they really show the potential of
the debugger.
I think , and correct me if that i
How does it load in Pharo 3?
As far as I can see the instructions are
Gofer new
url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main';
configuration;
load.
(Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment.
(Smalltalk globals at: #GTInspector) registerToolsOn: Sm
This only works in Pharo 3.0.
Doru
On Tue, Dec 31, 2013 at 6:57 PM, Hernán Morales Durand <
hernan.mora...@gmail.com> wrote:
> Really impressive and useful.
> Thanks for sharing.
>
> Can you point how to install it in a common Pharo 2.0 image?
>
> Hernán
>
>
>
> 2013/12/31 Andrei Chis
>
>> Hi,
Really impressive and useful.
Thanks for sharing.
Can you point how to install it in a common Pharo 2.0 image?
Hernán
2013/12/31 Andrei Chis
> Hi,
>
> I made two new screencasts showing a small domain-specific debugger for
> SUnit and one for PetitParser.
>
> https://vimeo.com/83017763 - SUn
just Nautilus with 3 plugins.
Nautilus
pluginClasses:
{{FinderPlugin. #top}.
{AnnotationFieldPlugin. #middle}.
{PackageTasksPlugin. #bottom}} asOrderedCollection
PackageTasksPlugin: patched
AnnotationFieldPlugin: my work
FinderPlugin: as is
2013/1
EstebanLM wrote
> looks cool… but it does not works in 3.0 :(
Yes :)
>> To load (tested in Pharo 2.0 latest):
But I'd be surprised if it took much to port. In fact, I'm surprised it
doesn't work. It's pretty much pure Morphic / Announcements. I wasn't going
to port it because I need it on 2.0 and
Benjamin Van Ryseghem-2 wrote
> Did you had a look at:
> https://ci.inria.fr/pharo-contribution/job/New-Pharo-IDE/
> There is also a Spotlight thingy there :)
No, I didn't know about that. How do I view the "Spotlight thingy" ;)? The
Spotlight that come up with the shortcut looks the same to me...
Benjamin Van Ryseghem-2 wrote
> On 30 Dec 2013, at 01:55, Sean P. DeNigris <
> sean@
> > wrote:
>> Will that be used for Nautilus eventually?
>
> There is a bug entry. With a slice.
I'm not sure what you mean. Sounds like a "maybe" ;) is the bug/slice
related to using NewList for Nautilus? Will
Sean P. DeNigris wrote
> and here is that person
I would've fixed it already, but since someone went through the trouble to
add a setting, I figured maybe there was a use case I was missing...
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Pharo3-issues-tp4733048p473
Stéphane Ducasse wrote
> So if somebody thinks that something that is not in our critical path
> should be changed he should submit code.
+1... and here is that person. The question in my post was: "will anyone
speak up for this 'feature'?" If not, I will be happy to revert to the old
behavior. Wh
Doru
The point of marcus is that we cannot take into account all wishes of
everybody: else we would not do anything else.
So if somebody thinks that something that is not in our critical path should be
changed he should submit code.
I have tons of ideas that could be implemented now since we do
2013/12/16
> Hi! We're sending this automatic email twice a month, to give the
> community an opportunity to easily know what's happening and to coordinate
> efforts. Just answer informally, and feel free to spawn discussions
> thereafter!
>
> ### Here's what I've been up to since the last Whats
Marcus wrote:
>On 31 Dec 2013, at 11:58, Tudor Girba <[hidden email]> wrote:
>
> >I think this should not be a global preference at all. Most of the time, you
> >actually want to commit in the same repository where >you always do. Only
> >from time to time do you need to switch and copy to anothe
Hey!
What is the browser you are using?
Looks really cool!
Alexandre
On Dec 31, 2013, at 10:55 AM, NISHIHARA Satoshi wrote:
> now, i am trying to use it for personal experimental project.
>
>
> 2013/12/31 Tudor Girba :
>> Thank you, Alex.
>>
>> Doru
>>
>>
>> On Mon, Dec 30, 2013 at 11:4
Thanks, Andrei.
These are really cool demos! :)
Doru
On Tue, Dec 31, 2013 at 2:50 PM, Andrei Chis wrote:
> Hi,
>
> I made two new screencasts showing a small domain-specific debugger for
> SUnit and one for PetitParser.
>
> https://vimeo.com/83017763 - SUnit
> https://vimeo.com/83017762 - Peti
Hi,
I made two new screencasts showing a small domain-specific debugger for
SUnit and one for PetitParser.
https://vimeo.com/83017763 - SUnit
https://vimeo.com/83017762 - PetitParser
There is also an older one for announcements (https://vimeo.com/83020584).
The debuggers were created using the
Thank you, Alex.
Doru
On Mon, Dec 30, 2013 at 11:40 PM, Alexandre Bergel
wrote:
> I am quasi exclusively using the Moose image, which includes GTDebugger
> and GTInspector.
> These are two great tools. I use the standard Pharo 3.0 for particular
> needs only. When I do this, it is like using Na
I do not understand this reaction :(
Doru
On Tue, Dec 31, 2013 at 12:01 PM, Marcus Denker wrote:
>
> On 31 Dec 2013, at 11:58, Tudor Girba wrote:
>
> I think this should not be a global preference at all. Most of the time,
> you actually want to commit in the same repository where you always d
Jannik wrote
>- In a browser, when I did a change in the source code of a method,
> then I select another method, the changes are lost, without asking if I want
> to save changes.
Thanks Nicolai, for the fast results. I retested.
Resolved, Fix to Include
Stephan
On 31 Dec 2013, at 11:58, Tudor Girba wrote:
> I think this should not be a global preference at all. Most of the time, you
> actually want to commit in the same repository where you always do. Only from
> time to time do you need to switch and copy to another repo. So, the
> preference shoul
I think this should not be a global preference at all. Most of the time,
you actually want to commit in the same repository where you always do.
Only from time to time do you need to switch and copy to another repo. So,
the preference should be per browser, not global.
Cheers,
Doru
On Tue, Dec 3
On 30 Dec 2013, at 13:54, Sven Van Caekenberghe wrote:
> Hi Nicolai,
>
> On 30 Dec 2013, at 13:26, Nicolai Hess wrote:
>
>> for issue 12223
>>
>> please revert the changes done for editing history in Nautilus.
>> It makes more trouble than it helps.
>> It is a nice feature, but it is impleme
On 30 Dec 2013, at 14:42, Sean P. DeNigris wrote:
> Marcus Denker-4 wrote
>>> - In monticello browser: when I select my project, all the repositories
>>> available in Pharo are shown. As in Pharo 2.0, it should show only the
>>> concerned repositories (2 or 3 max).
>>>
>> Yes, this was made on
On 31 Dec 2013, at 11:10, Norbert Hartl wrote:
>
> Am 30.12.2013 um 19:41 schrieb Stéphane Ducasse :
>
>>
>>> If Linus Torvald is your model, then I quit Pharo :P
>>
>> I will tell you stories where democracy in open-source does not work in feb.
>>
> Between Linus Torvalds and a democrazy v
On 31 Dec 2013, at 11:10, Norbert Hartl wrote:
>
> Am 30.12.2013 um 19:41 schrieb Stéphane Ducasse :
>
>>
>>> If Linus Torvald is your model, then I quit Pharo :P
>>
>> I will tell you stories where democracy in open-source does not work in feb.
>>
> Between Linus Torvalds and a democrazy v
Am 30.12.2013 um 19:41 schrieb Stéphane Ducasse :
>
>> If Linus Torvald is your model, then I quit Pharo :P
>
> I will tell you stories where democracy in open-source does not work in feb.
>
Between Linus Torvalds and a democrazy variant that leads only to stagnation is
plenty of room for a m
Let’s promote Pharo by tweeting: “Pharo #code2013”
Cheers!
Happy new year.
Uko
43 matches
Mail list logo