https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&ixPersonOpenedBy=194&sColumns=Category-Favorite-Case-TitleComment-Status-Priority-LastUpdated&sSearchFor=nautilus&sView=grid-flat
Le 29/11/2014 08:53, stepharo a écrit : > where? > > Le 28/11/14 21:30, Hilaire a écrit : >> Le 28/11/2014 08:07, Marcus Denker a écrit : >>>> It is unstable with me. It is really feature complete, it is nice, >>>> but I >>>>> may use wrongly. >>>>> May be with a simpler one I will do less mistake. >>>>> >>> If nobody reports and fixes problems, they will stay forever. >> Reported, they are. >> >> Hilaire >> > > > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu |
Le 29/11/2014 10:06, Hilaire a écrit :
> https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&ixPersonOpenedBy=194&sColumns=Category-Favorite-Case-TitleComment-Status-Priority-LastUpdated&sSearchFor=nautilus&sView=grid-flat Is that just me or is your filter/link not working? Don't hesitate to voice your feelings even if they don't fit within bug reports. The fact you're writing this is a kind of report ;) Making powerfull things simple is complex Thierry > Le 29/11/2014 08:53, stepharo a écrit : >> where? >> >> Le 28/11/14 21:30, Hilaire a écrit : >>> Le 28/11/2014 08:07, Marcus Denker a écrit : >>>>> It is unstable with me. It is really feature complete, it is nice, >>>>> but I >>>>>> may use wrongly. >>>>>> May be with a simpler one I will do less mistake. >>>>>> >>>> If nobody reports and fixes problems, they will stay forever. >>> Reported, they are. >>> >>> Hilaire >>> >> >> >> > > |
I have been using AltBrowser for a test. Some feedback - I like to see doc with my code so having to click back and forth is annoying and not conductive to writing class comments. - I got a couple freezes - I wonder how to get back to Nautilus. It would be nice to be able to use both. Phil Le 29 nov. 2014 10:40, "Thierry Goubier" <[hidden email]> a écrit :
Le 29/11/2014 10:06, Hilaire a écrit : |
"- I wonder how to get back to Nautilus. It would be nice to be able to use both." thats an annoyance for me too, I would like to be given the option to choose what browser I want to use depending on the situation. Also your comment on the comments is a valid one, I think we need a more dynamic browser in general which currently Pharo lacks, that does not try to choose for us how to do coding and instead gives us the choices . Of course dynamic browsers are more effort. |
In reply to this post by philippeback
Le 29/11/2014 11:29, [hidden email] a écrit :
> I have been using AltBrowser for a test. > > Some feedback > > - I like to see doc with my code so having to click back and forth is > annoying and not conductive to writing class comments. Good point. I wondered about having multiple text panes on the right (linked to multi-selection in the tree, such as selecting a comment + a method) but I decided against it on pure lazyness excuses (fear of code complexity / unable to see a simple way of doing it / able to get along without it). Given the size of the text pane on the right, it seems we could do a lot with it. But I have a feeling that having the start of a method allways at the same place (in the window) is significant. A "auto-appearing" comment pane at the bottom? > - I got a couple freezes Interesting. If you find a way to reproduce them, I'll be happy. > - I wonder how to get back to Nautilus. It would be nice to be able to > use both. Nautilus is still there. You can open one (PackageTreeNautilus open), but, yes, it could be nice to unregister AltBrowser. Wait, I think there is a settings option... Thierry > > Phil > > Le 29 nov. 2014 10:40, "Thierry Goubier" <[hidden email] > <mailto:[hidden email]>> a écrit : > > Le 29/11/2014 10:06, Hilaire a écrit : > > https://pharo.fogbugz.com/f/__filters/?fClosedBugs=true&__ixPersonOpenedBy=194&sColumns=__Category-Favorite-Case-__TitleComment-Status-Priority-__LastUpdated&sSearchFor=__nautilus&sView=grid-flat > <https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&ixPersonOpenedBy=194&sColumns=Category-Favorite-Case-TitleComment-Status-Priority-LastUpdated&sSearchFor=nautilus&sView=grid-flat> > > > Is that just me or is your filter/link not working? > > Don't hesitate to voice your feelings even if they don't fit within > bug reports. The fact you're writing this is a kind of report ;) > > Making powerfull things simple is complex > > Thierry > > Le 29/11/2014 08:53, stepharo a écrit : > > where? > > Le 28/11/14 21:30, Hilaire a écrit : > > Le 28/11/2014 08:07, Marcus Denker a écrit : > > It is unstable with me. It is really feature > complete, it is nice, > but I > > may use wrongly. > May be with a simpler one I will do less > mistake. > > If nobody reports and fixes problems, they will stay > forever. > > Reported, they are. > > Hilaire > > > > > > > > > |
In reply to this post by HilaireFernandes
Merci
Le 29/11/14 10:06, Hilaire a écrit : > https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&ixPersonOpenedBy=194&sColumns=Category-Favorite-Case-TitleComment-Status-Priority-LastUpdated&sSearchFor=nautilus&sView=grid-flat > > Le 29/11/2014 08:53, stepharo a écrit : >> where? >> >> Le 28/11/14 21:30, Hilaire a écrit : >>> Le 28/11/2014 08:07, Marcus Denker a écrit : >>>>> It is unstable with me. It is really feature complete, it is nice, >>>>> but I >>>>>> may use wrongly. >>>>>> May be with a simpler one I will do less mistake. >>>>>> >>>> If nobody reports and fixes problems, they will stay forever. >>> Reported, they are. >>> >>> Hilaire >>> >> >> > |
In reply to this post by Thierry Goubier
Doc at the bottom of the right pane would be nice. Phil Le 29 nov. 2014 11:43, "Thierry Goubier" <[hidden email]> a écrit :
Le 29/11/2014 11:29, [hidden email] a écrit : |
In reply to this post by kilon.alios
Le 29/11/2014 11:39, kilon alios a écrit :
> > "- I wonder how to get back to Nautilus. It would be nice to be able to > use both." > > thats an annoyance for me too, I would like to be given the option to > choose what browser I want to use depending on the situation. Doing that is just triggering a nice bug in Pharo 3. There is apparently no real API for unregistering a tool... > Also your comment on the comments is a valid one, I think we need a more > dynamic browser in general which currently Pharo lacks, that does not > try to choose for us how to do coding and instead gives us the choices . > Of course dynamic browsers are more effort. A Moldable system browser? The old system browser is dynamic, in a way: class / hierarchy / full. Changes based on what was your focus. The message list as well, the finder UI as well. But... complex, not that convincing. Thierry |
In reply to this post by philippeback
Le 29/11/2014 16:28, [hidden email] a écrit :
> Doc at the bottom of the right pane would be nice. Done for the pharo3 version, along with the ability to properly unregister AltBrowser from the settings (AltBrowser->make default browser). There is now a menu command toggling the comment pane(*). Comment is read-only even if one can type things in it(**). If we could add comments to protocols or packages, it would display those when appropriate. Oh, and for the fun :) It also works in the "message browser" mode as well as the "finder" results (which is something I wrote 0 lines for :)). Now some polishing is needed; you know better how you would like it to be, so its yours :) Thierry (*) Would that be better as a kind of setting? Making the menu longer for something you rarely switch on or off... (**) I'm lazy ;) It could be nice to have it as a more "floating" / or different color read-only pane to mark it as documentation, or even make it rw if you feel like it. > Phil > > Le 29 nov. 2014 11:43, "Thierry Goubier" <[hidden email] > <mailto:[hidden email]>> a écrit : > > Le 29/11/2014 11:29, [hidden email] <mailto:[hidden email]> > a écrit : > > I have been using AltBrowser for a test. > > Some feedback > > - I like to see doc with my code so having to click back and > forth is > annoying and not conductive to writing class comments. > > > Good point. I wondered about having multiple text panes on the right > (linked to multi-selection in the tree, such as selecting a comment > + a method) but I decided against it on pure lazyness excuses (fear > of code complexity / unable to see a simple way of doing it / able > to get along without it). > > Given the size of the text pane on the right, it seems we could do a > lot with it. > > But I have a feeling that having the start of a method allways at > the same place (in the window) is significant. > > A "auto-appearing" comment pane at the bottom? > > - I got a couple freezes > > > Interesting. If you find a way to reproduce them, I'll be happy. > > - I wonder how to get back to Nautilus. It would be nice to be > able to > use both. > > > Nautilus is still there. You can open one (PackageTreeNautilus > open), but, yes, it could be nice to unregister AltBrowser. Wait, I > think there is a settings option... > > Thierry > > > Phil > > Le 29 nov. 2014 10:40, "Thierry Goubier" > <[hidden email] <mailto:[hidden email]> > <mailto:thierry.goubier@gmail.__com > <mailto:[hidden email]>>> a écrit : > > Le 29/11/2014 10:06, Hilaire a écrit : > > https://pharo.fogbugz.com/f/____filters/?fClosedBugs=true&____ixPersonOpenedBy=194&sColumns=____Category-Favorite-Case-____TitleComment-Status-Priority-____LastUpdated&sSearchFor=____nautilus&sView=grid-flat > <https://pharo.fogbugz.com/f/__filters/?fClosedBugs=true&__ixPersonOpenedBy=194&sColumns=__Category-Favorite-Case-__TitleComment-Status-Priority-__LastUpdated&sSearchFor=__nautilus&sView=grid-flat> > > <https://pharo.fogbugz.com/f/__filters/?fClosedBugs=true&__ixPersonOpenedBy=194&sColumns=__Category-Favorite-Case-__TitleComment-Status-Priority-__LastUpdated&sSearchFor=__nautilus&sView=grid-flat > <https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&ixPersonOpenedBy=194&sColumns=Category-Favorite-Case-TitleComment-Status-Priority-LastUpdated&sSearchFor=nautilus&sView=grid-flat>> > > > Is that just me or is your filter/link not working? > > Don't hesitate to voice your feelings even if they don't > fit within > bug reports. The fact you're writing this is a kind of > report ;) > > Making powerfull things simple is complex > > Thierry > > Le 29/11/2014 08:53, stepharo a écrit : > > where? > > Le 28/11/14 21:30, Hilaire a écrit : > > Le 28/11/2014 08:07, Marcus Denker a écrit : > > It is unstable with me. It is really > feature > complete, it is nice, > but I > > may use wrongly. > May be with a simpler one I will do > less > mistake. > > If nobody reports and fixes problems, they > will stay > forever. > > Reported, they are. > > Hilaire > > > > > > > > > > > > |
In reply to this post by kilon.alios
In general we should enhance the ToolRegistry to not just register one tool, but instead keep all and have a UI in the settings where people can the change the tool used. There is of course an issue entry for that at https://pharo.fogbugz.com/f/cases/10529/ToolRegistry-need-to-support-multiple-registrations-per-tool (this would not be a solution to “different tool per context”, but nevertheless we need it) Marcus |
2014-12-01 9:52 GMT+01:00 Marcus Denker <[hidden email]>:
It would be convenient, yes. At the same time, it's not much for additional tools to handle a set-as-default setting by themselves, except for the part where the API for unregistering a tool seems broken (I easily managed to throw my image into a DNU each time some tool wanted a browser, for example). Thierry
|
The mechanism is very simple… if you remove a tool and then use it, there will be a DNU. (it should open instead window and tell that no tool is installed) Marcus
|
2014-12-01 10:19 GMT+01:00 Marcus Denker <[hidden email]>:
In fact, it's worse: it DNUs even if you still have some tools installed, just because you unregistered one of them. i.e. With AltBrowser installed, you have four browsers in your image: SystemBrowser, Nautilus, PackageTreeNautilus, and AltBrowser. If you unregister AltBrowser, you have a DNU, even if you have the three others still available. There is apparently some magic in the world menu to trigger a user-driven choice among existing tools, but I don't know how to trigger that. Thierry
|
Yes, as they are there but not registered. ToolRegistry just knows about the *last* tool registered. If you unregister that, there is none (this is why ToolRegistry needs to be extended to remember all and just have the last be the default)
No, the only thing it does is to execute all the methods (in a some un-defined order). The last tool’s #registerToolsOn: then will be the one that ToolRegistry knows about. Marcus |
2014-12-01 10:32 GMT+01:00 Marcus Denker <[hidden email]>:
I disagree. Just force an interactive choice feels a lot better to me (and far simpler). Otherwise you'll see people jokeying for order for their tool, and anyway you have to provide a user setting. A cool one: open the settings browser at the right place, instead of creating an ad-hoc dialog. Reuse code + GUI familiarity + less lines of code.
There is somewhere a user-query that you can trigger under some circumstances. But I could not find it. I'll have a look. I noticed that unloading AltBrowser was a very nice way to end up with a dead Pharo image :( Remember, AltBrowser is clearly the best, so I won't provide a way back to the old ways :):):) Thierry
|
> On 01 Dec 2014, at 10:50, Thierry Goubier <[hidden email]> wrote: > > Remember, AltBrowser is clearly the best, so I won't provide a way back to the old ways :):):) That's the spirit ! |
In reply to this post by Thierry Goubier
"A Moldable system browser? The old system browser is dynamic, in a way: class / hierarchy / full. Changes based on what was your focus. The message list as well, the finder UI as well. But... complex, not that convincing." yes exactly . Why bother making a system browser that can do tons of things when you can build a browser that is easy to customise gui wise and features wise ? Users will come and extend it far beyond that what a few developers can do. Same as games really, you have something like Skyrim and then you have like tons of mods for it that some are even better than the game itself. I think generally what Pharo lacks is an ADDONS API like Blender. An API that would make it easy for users to customise Pharo on the fly. Of course its really good that we have such direct and live access to the source code of Pharo but sometimes you dont want to learn a ton of stuff to change just a few bits. On Sat, Nov 29, 2014 at 6:21 PM, Thierry Goubier <[hidden email]> wrote: Le 29/11/2014 11:39, kilon alios a écrit : |
Hi, This is precisely the direction that the IDE of Pharo is taking. Take the inspector for example. It is a tiny piece of code that can be extended in many ways and in doing so, it can support various workflows. The same is actually available already for the debugger (GTDebugger) although this is not yet integrated. And more is coming. Eventually, we will also get to the code browser :). Doru On Mon, Dec 1, 2014 at 12:54 PM, kilon alios <[hidden email]> wrote:
|
"Take the inspector for example. It is a tiny piece of code that can be extended in many ways and in doing so, it can support various workflows."
What is its API and where is documented ? |
Interesting that you are asking that question. This basically means that the whole philosophy of the GTInspector did not get communicated well. We have to work on this because I think GTInspector is the most significant step in object inspection since the introduction of the original inspector. So, here is the main page: Here is the introduction: Some examples: How to manage the extensions: And a more thorough list: Cheers, Doru On Mon, Dec 1, 2014 at 1:21 PM, kilon alios <[hidden email]> wrote:
|
Free forum by Nabble | Edit this page |