Hi Sebastian, Thanks for the feedback.
On Sun, Jan 25, 2015 at 6:24 PM, Sebastian Sastre < sebast...@flowingconcept.com> wrote: > It’s really nice to see innovation in this area. I feel grateful for this > work. > > Here comes my UX notes > > *Things I like:* > > - Publish to the cloud > - Able to copy-paste the content of the box with feedback > - Encourages inspect of that very instance (this one was really good!) > - transforms the printed result to comment. > - clicking in the workspace makes the result disappear (good!) > - full selects the comment after enter so a second enter can clean it > - the shared snipped page has syntax highlight > > *Things that I see can be improved:* > > - the shared snippet page has a terrible design, the contrast issue is > probably the most severe, being unclean the second one > - the printed result transformed to comment gets injected at the cursor > position and that functionality doesn’t really make much sense (having it > printed always at the end of the line you make more sense for example). > This is still under work. The current behavior is the same as the previous print-it. We are considering all this input and we'll come back with a proposal. - the inspect button doesn’t look like a button and doesn’t change the > cursor on hover > - No undo on cmd-z (this one feels like a deal-breaker) > What do you mean? Undo should work as expected (even after I insert the code in the editor). Could you give me a way to reproduce the problem? - The tab for me is a redundant feature with an unclean title (we have how > to recall different workspaces from the bottom bar already) > This is a work in progress. > - The icon to publish to the cloud looks like download from the cloud > (arrow points down instead of up) > Good point. I changed it. > - The inspector is surprisingly complex and abuses the use of tabs > What is complex? What do you mean by abuses the use of tabs? Could you give examples of what you saw and what you expected? In case you did not see it before, the GTInspector wants to be more than a classic inspector, so perhaps that is why the implementation does not seem to align with expectations. Here is a post that describes in some details the concept behind: http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructed > - The inspector for Dictionary by default hides a naive observation of the > object and assumes that a “smart” object aware presentation hiding behind a > click the tree-like observation of instvars. > I am not sure what you are saying here, but If I understand correctly, you would prefer to see the raw tally and array of associations instead of a table as the first view for a dictionary. Is that is so, why do you find it a better representation? - Also in inspector the icon for browse looks like a document, doesn’t feel > like a match > I am not happy with that one either, but I could not figure out a better one. Do you have a suggestion? > good work! > Thanks. Doru > > > > On Jan 19, 2015, at 5:33 AM, Tudor Girba <tu...@tudorgirba.com> wrote: > > Hi, > > I worked with Andrei to find a solution for improving the print-it > support. You can take a look here: > > http://www.humane-assessment.com/blog/improving-print-it-support-in-gtplayground > > The current solution can be found in the latest Pharo image. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"
