It would be great to have a default view.
If I open a playground, and type: | v s | v := RTView new. s := String newFrom: ($A to: $Z), ($a to: $z), ($0 to: $9). v add: (RTLabel elementOn: s). v Cmd-o, then I have the tab ‘State’ selected. Obviously, I want to have ‘View’ How can tab be added? I would like to have an ‘Example’ tab Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
And please, adding the automatic line selection if nothing is selected :-)
Alexandre On Feb 24, 2014, at 6:42 PM, Alexandre Bergel <[hidden email]> wrote: > It would be great to have a default view. > If I open a playground, and type: > > | v s | > v := RTView new. > s := String newFrom: ($A to: $Z), ($a to: $z), ($0 to: $9). > v add: (RTLabel elementOn: s). > v > > Cmd-o, then I have the tab ‘State’ selected. Obviously, I want to have ‘View’ > > How can tab be added? I would like to have an ‘Example’ tab > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Yes, this is on the roadmap, too. Doru On Mon, Feb 24, 2014 at 10:52 PM, Alexandre Bergel <[hidden email]> wrote: And please, adding the automatic line selection if nothing is selected :-) "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by abergel
Where do you want the Example tab? There exist a raw support for examples for each class, but it is not announced yet because it is still a work in progress. About the view presentation: Keep in mind that we are talking about the inspector which is the most basic of all tools (I know it's hard to believe it is a basic tool :)). That is why defaults have to be handled carefully because the tool is supposed to handle a large amount of use cases.
However, now you have two mechanisms that can help with your problem: 1. a. You execute your script once. b. Switch to the View presentation c. Modify and execute again
d. You will get the View presentation So, in the end, we get only one extra click (step b.). I think this is a good compromise for now. 2. Actually, the View presentation is an extension that you can define yourself.
gtInspectorViewIn: composite <gtInspectorPresentationOrder: 30> composite roassal2
title: 'View'; initializeView: [ self ] The order of the tabs is defined by the number from the pragma. You can try adding it first, but then it would not be as in the default case for all other objects. We need to experiment with this for a while to figure out the best approach.
For example, when debugging a faulty view, you precisely do not want to view, but might want a presentation that shows the structure of elements without rendering the view. That is why at the moment, the default is the State of the object and the idea is to make mechanism 1 a bit more powerful so that you can mold the environment to the actual context.
Doru Cheers, Doru
On Mon, Feb 24, 2014 at 10:42 PM, Alexandre Bergel <[hidden email]> wrote: It would be great to have a default view. "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |