Re: [Pharo-dev] creating custom browsers out of GTInspector extensions
Le 14/10/2014 23:26, Tudor Girba a écrit : > Now, that more people are playing with the GTInspector, I would like to > raise another point that might otherwise go unnoticed: The inspector > extensions do not only work in the inspector, but can also be combined > in other browsers as well. > It really looks intersting! I can imagine some good use of it to navigate in geometric objects. Thanks Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu
Re: [Pharo-dev] creating custom browsers out of GTInspector extensions
Really Cool...! On Wed, Oct 15, 2014 at 11:52 AM, Marcus Denker wrote: > > > On 14 Oct 2014, at 23:26, Tudor Girba wrote: > > > > Hi, > > > > Now, that more people are playing with the GTInspector, I would like to > raise another point that might otherwise go unnoticed: The inspector > extensions do not only work in the inspector, but can also be combined in > other browsers as well. > > > > We could replace (most of) the FileBrowser by > > GLMPager new with: [ :pager | > pager show: [ :composite :file | > composite title: file basename. > file gtInspectorItemsIn: composite. > file gtInspectorContentsIn: composite ]; > title: 'FileBrowser' ]; > openOn: FileSystem disk workingDirectory > > > > Where it replaces > > FileList linesOfCode > > ==> 1075 > (plus three more helper classes). > > Of course this does a little bit more, but most of that is at the wrong > spot anyway. > (editor for text files, API for file selection on the class side). > > Marcus >
Re: [Pharo-dev] creating custom browsers out of GTInspector extensions
> On 14 Oct 2014, at 23:26, Tudor Girba wrote: > > Hi, > > Now, that more people are playing with the GTInspector, I would like to raise > another point that might otherwise go unnoticed: The inspector extensions do > not only work in the inspector, but can also be combined in other browsers as > well. > We could replace (most of) the FileBrowser by GLMPager new with: [ :pager | pager show: [ :composite :file | composite title: file basename. file gtInspectorItemsIn: composite. file gtInspectorContentsIn: composite ]; title: 'FileBrowser' ]; openOn: FileSystem disk workingDirectory Where it replaces FileList linesOfCode ==> 1075 (plus three more helper classes). Of course this does a little bit more, but most of that is at the wrong spot anyway. (editor for text files, API for file selection on the class side). Marcus
[Pharo-dev] creating custom browsers out of GTInspector extensions
Hi, Now, that more people are playing with the GTInspector, I would like to raise another point that might otherwise go unnoticed: The inspector extensions do not only work in the inspector, but can also be combined in other browsers as well. For example, the attached picture shows a Pillar browser that shows only the presentations relevant to editing Pillar books. And the code looks like: GLMPager new with: [ :pager | pager show: [ :composite :file | composite title: file basename. file gtInspectorItemsIn: composite. file gtInspectorPillarConfigurationIn: composite. file gtInspectorPillarIn: composite. file gtInspectorPillarProjectIn: composite. file gtInspectorPngIn: composite. file gtInspectorGifIn: composite. file gtInspectorContentsIn: composite ] ]; openOn: FileSystem disk workingDirectory [image: Inline image 1] See here some more details: http://www.humane-assessment.com/blog/creating-custom-browsers-out-of-inspector-extensions The interesting thing is that we can now easily imagine creating rather sophisticated tools with little code and that we only use for a very short time (like minutes). This has a rather high disruption potential given that no other environment I know of allows for something like this. Let us know what you think. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"