The Inbox: Tools-ct.881.mcz

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

The Inbox: Tools-ct.881.mcz

commits-2
A new version of Tools was added to project The Inbox:
http://source.squeak.org/inbox/Tools-ct.881.mcz

==================== Summary ====================

Name: Tools-ct.881
Author: ct
Time: 4 September 2019, 9:22:35.818698 pm
UUID: 8b3f75cd-2e4c-3649-b220-196e1d813c8b
Ancestors: Tools-ct.878

Refine behavior of #spawn: again

* Move implementation in StringHolder up to Model, in order to avoid error messages in other Models (such as MCTool, PreferenceBrowser etc.)
* Respect Workspace shouldStyle setting in SearchBar>>#spawn:
* In Workspace>>#spawn:, respect current styling mode

Thanks to mt!

=============== Diff against Tools-ct.878 ===============

Item was added:
+ ----- Method: Model>>spawn: (in category '*Tools') -----
+ spawn: contentsString
+
+ UIManager default edit: contentsString label: nil!

Item was changed:
  ----- Method: SearchBar>>spawn: (in category '*Tools') -----
  spawn: contentsString
 
+ UIManager default edit: contentsString label: nil shouldStyle: Workspace shouldStyle!
- UIManager default edit: contentsString label: nil shouldStyle: true!

Item was removed:
- ----- Method: StringHolder>>spawn: (in category '*Tools') -----
- spawn: contentsString
-
- UIManager default edit: contentsString label: 'Workspace' shouldStyle: self shouldStyle
- !

Item was added:
+ ----- Method: Workspace>>spawn: (in category '*Tools') -----
+ spawn: contentsString
+
+ UIManager default edit: contentsString label: 'Workspace' shouldStyle: self shouldStyle!


Reply | Threaded
Open this post in threaded view
|

Re: The Inbox: Tools-ct.881.mcz

Christoph Thiede

For follow-up: This should also resolve http://bugs.squeak.org/view.php?id=7873.


Btw: Are we still using this bugtracker system seriously (with the latest time stamps in mind)? Is it worth reporting any bug there instead of mailing it to the list directly? :)


Best,

Christoph


Von: Squeak-dev <[hidden email]> im Auftrag von [hidden email] <[hidden email]>
Gesendet: Mittwoch, 4. September 2019 21:22:40
An: [hidden email]
Betreff: [squeak-dev] The Inbox: Tools-ct.881.mcz
 
A new version of Tools was added to project The Inbox:
http://source.squeak.org/inbox/Tools-ct.881.mcz

==================== Summary ====================

Name: Tools-ct.881
Author: ct
Time: 4 September 2019, 9:22:35.818698 pm
UUID: 8b3f75cd-2e4c-3649-b220-196e1d813c8b
Ancestors: Tools-ct.878

Refine behavior of #spawn: again

* Move implementation in StringHolder up to Model, in order to avoid error messages in other Models (such as MCTool, PreferenceBrowser etc.)
* Respect Workspace shouldStyle setting in SearchBar>>#spawn:
* In Workspace>>#spawn:, respect current styling mode

Thanks to mt!

=============== Diff against Tools-ct.878 ===============

Item was added:
+ ----- Method: Model>>spawn: (in category '*Tools') -----
+ spawn: contentsString
+
+        UIManager default edit: contentsString label: nil!

Item was changed:
  ----- Method: SearchBar>>spawn: (in category '*Tools') -----
  spawn: contentsString
 
+        UIManager default edit: contentsString label: nil shouldStyle: Workspace shouldStyle!
-        UIManager default edit: contentsString label: nil shouldStyle: true!

Item was removed:
- ----- Method: StringHolder>>spawn: (in category '*Tools') -----
- spawn: contentsString
-
-        UIManager default edit: contentsString label: 'Workspace' shouldStyle: self shouldStyle
- !

Item was added:
+ ----- Method: Workspace>>spawn: (in category '*Tools') -----
+ spawn: contentsString
+
+        UIManager default edit: contentsString label: 'Workspace' shouldStyle: self shouldStyle!




Reply | Threaded
Open this post in threaded view
|

Re: The Inbox: Tools-ct.881.mcz

David T. Lewis
On Sun, Sep 08, 2019 at 07:21:48PM +0000, Thiede, Christoph wrote:
> For follow-up: This should also resolve http://bugs.squeak.org/view.php?id=7873.
>
>
> Btw: Are we still using this bugtracker system seriously (with the
> latest time stamps in mind)? Is it worth reporting any bug there instead
> of mailing it to the list directly? :)

The bugs.squeak.org Mantis tracker does not get much use any more,
mainly because we do try to resolve things when possible directly
through inbox/trunk. But this does (too often) lead to good improvements
that rot in the inbox.

In my opinion, the Mantis tracker remains useful for:

1) Issues that require input or review from several people who may
not all be paying attention to the mailing list at the same time.

2) Issues that are being overlooked or ignored on the mailing list.

3) Historical record of old issues.

I think it is great that you linked back to Patrick's issue #7833
that he entered almost a year ago. And as soon as the fix that you
provided in Tools-ct.881.mcz is merged in trunk we should close
Mantis #7833.

:-)

Dave


Reply | Threaded
Open this post in threaded view
|

Re: The Inbox: Tools-ct.881.mcz

Christoph Thiede

Hi David,


thank you for clarification. I have collected a list of miscellaneous minor bugs in Squeak. So when I am going to report them, I will send them to squeak-dev, and if no one reacts on it, I will enter them into Mantis? :)


Btw, do bugs refering to SqueakMap packages (such as RefactoringTools) also belong into this mailing list/bugs.squeak.org?


Best,

Christoph


Von: Squeak-dev <[hidden email]> im Auftrag von David T. Lewis <[hidden email]>
Gesendet: Sonntag, 8. September 2019 23:48:38
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] The Inbox: Tools-ct.881.mcz
 
On Sun, Sep 08, 2019 at 07:21:48PM +0000, Thiede, Christoph wrote:
> For follow-up: This should also resolve http://bugs.squeak.org/view.php?id=7873.
>
>
> Btw: Are we still using this bugtracker system seriously (with the
> latest time stamps in mind)? Is it worth reporting any bug there instead
> of mailing it to the list directly? :)

The bugs.squeak.org Mantis tracker does not get much use any more,
mainly because we do try to resolve things when possible directly
through inbox/trunk. But this does (too often) lead to good improvements
that rot in the inbox.

In my opinion, the Mantis tracker remains useful for:

1) Issues that require input or review from several people who may
not all be paying attention to the mailing list at the same time.

2) Issues that are being overlooked or ignored on the mailing list.

3) Historical record of old issues.

I think it is great that you linked back to Patrick's issue #7833
that he entered almost a year ago. And as soon as the fix that you
provided in Tools-ct.881.mcz is merged in trunk we should close
Mantis #7833.

:-)

Dave




Reply | Threaded
Open this post in threaded view
|

Re: The Inbox: Tools-ct.881.mcz

Nicola Mingotti

I am in the same position of Christoph,

I found some little bugs here and there. I see that that dev mailing list just in a few hours produced a lot of traffic. I doubt I can keep it under control.

If Mantis is not used anymore I will post here but I will loose trace of them.

extra note. I used Bugzilla (Mantis equivalent I guess) to report bugs in for different parts of FreeBSD software and/or documentation. It works well. It enables the user (non dev) to give his contribution into spotting bugs. It warns the bugs is there for other users to be aware of, till it gets solved.

bye
Nicola







On 9/9/19 2:08 AM, Thiede, Christoph wrote:

Hi David,


thank you for clarification. I have collected a list of miscellaneous minor bugs in Squeak. So when I am going to report them, I will send them to squeak-dev, and if no one reacts on it, I will enter them into Mantis? :)


Btw, do bugs refering to SqueakMap packages (such as RefactoringTools) also belong into this mailing list/bugs.squeak.org?


Best,

Christoph


Von: Squeak-dev [hidden email] im Auftrag von David T. Lewis [hidden email]
Gesendet: Sonntag, 8. September 2019 23:48:38
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] The Inbox: Tools-ct.881.mcz
 
On Sun, Sep 08, 2019 at 07:21:48PM +0000, Thiede, Christoph wrote:
> For follow-up: This should also resolve http://bugs.squeak.org/view.php?id=7873.
>
>
> Btw: Are we still using this bugtracker system seriously (with the
> latest time stamps in mind)? Is it worth reporting any bug there instead
> of mailing it to the list directly? :)

The bugs.squeak.org Mantis tracker does not get much use any more,
mainly because we do try to resolve things when possible directly
through inbox/trunk. But this does (too often) lead to good improvements
that rot in the inbox.

In my opinion, the Mantis tracker remains useful for:

1) Issues that require input or review from several people who may
not all be paying attention to the mailing list at the same time.

2) Issues that are being overlooked or ignored on the mailing list.

3) Historical record of old issues.

I think it is great that you linked back to Patrick's issue #7833
that he entered almost a year ago. And as soon as the fix that you
provided in Tools-ct.881.mcz is merged in trunk we should close
Mantis #7833.

:-)

Dave