Hi Kilon, Thanks for the feedback.
I am interested in what makes it so confusing for you. It seems to me that there are quite a number of confusions, so, let's take it step by step. Perhaps we can discover ways to improve or to explain the interface. I will address your points and in the process I will ask a couple of questions. Even if they appear dumb, I am genuinely interested in your responses. On Thu, Oct 2, 2014 at 5:19 PM, kilon alios <[email protected]> wrote: > Is it just me or is the Playground a big step back in the usability of > Pharo ? > > For me its Gui makes no sense. Gone is the right click menu which had tons > of useful actions now you only get like a few options. The tab thing is > weird to say the least with the navigation of the tabs being in the > opposite side (bottom) of the navigation of the internal tabs(top). No more > right arrow menu for shortcuts and many features that workspace had. > I will concede that the contextual menu is incomplete. We will work on that. In the meantime, the keybindings work as in the classic workspace. But, what are the many features that the workspace had and you miss? No ability to resize the panel tabs . > That is true, but that is because it is a feature. Btw, you do not have to spawn a pane. If you treat the Playground like a classic Workspace (and just use inspect or do it), you will not see any difference. No pane will spawn to the right. > Weird terminolgy like "All ref" and "Meta". Meta tab you have to select > the first item and then the other first item and then it displays fully . > What do you find weird about "Meta"? I agree that "All ref" should be better explained. But, what do you think these tabs mean? Also how one closes a tab panel ? Is it possible ? I tried everything but i > cant get them to close. > You cannot close it for now. This feature will be added. But, if you have 5 panes open, and you select another object in the second pane, panes 3,4,5 will be deleted and replaced with a new pane. It's like the interface from Mac Finder. I click a method and instead of opening a panel on the bottom for the > source as I would expect ,make my workspace area disappear and create a new > panel that sends me to state, whatever this is. Then I have to click on the > source tab. This is one of the most annoying guis I have used in an IDE. > >From the description, I believe you inspected a class, and then you got a tab with the methods of that tab. And then you selected one method and to the right you got a tab with source. Is that correct? The State tab shows you the object state. In essence these are the instance variables. Is the name confusing, or is its presentation? In another thread we are discussing a different naming. Ironically the meta tab has got this right , name of class - method names > and source of methods . On the instance side tab there is a different kind > of thinking , why ? > It is not different thinking. It is a different use case :). The Meta tab shows the class of the object you inspect. If you inspected a class, then the inspector also provides you a list of its methods. It's not the same thing. Perhaps this confusion will go away once the "Meta" tab will be implemented using the new code widget that I demoed at ESUG. But, what do you mean by instance side tab? > Also the inspector seems to get in some kind of loop opening forever > panels when it finds a dead end in its inspection.For example clicking self. > >From your description, I believe that you are clicking on the self entry, and then you get the same object to the right. And then clicking self again spawns another object to the right. Is that correct? If so, clicking on an entry, is the correspondent of inspecting that object. In the "State" tab, we also provide self to denote the same object as the one represented in the tab. This was borrowed from the classic inspector, but maybe it is confusing in the context of the new inspector. In any case, if you continue clicking on self, you will indeed get the same object over and over. But, that does not mean that the inspector went in a loop. > It has some good ideas in it, but I dont like the execution. > Which one did you like? > The big loss for me is the inability to create windows groups, this > functionality provided a very nice solution to the windows mess of pharo. I > can name my groups but also the individual windows and so the tabs have > short names that I know what they are and names of course I can customise. > I do not understand this part. Can you explain in more details? I can disable it via settings but maybe I am missing something here, a some > kind of usefulness because I don't understand or don't know how to use it > properly. > Let's try a bit more and see afterwards :). Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"
