Thanks for the kind words, Kilon. Please feel free to ask questions.
Cheers, Doru On Tue, Dec 2, 2014 at 11:29 AM, kilon alios <kilon.al...@gmail.com> wrote: > "In my image, I have 144 such extensions taking on average 9 lines of > code." > > Impressive then apparently GT tools goes exactly the direction I wanted. I > was aware of Glamour but to be frank I have not seen anyone else use it but > you guys so I was kinda sceptical about it and did not took it very > seriously. I was not aware that GT tools were built on top of Glamour and > this certainly gives it more credit, I thought it was merely for making > custom browsers looks like its a lot more than that. Thank you Tudor you > gave me a lot of to read. > > I definetly when to develop my tools and libraries in sync to the > direction Pharo is going so I can take advantage of the existing code and > not reinvent the wheel. So now I will sit down and study all these > technologies and see how I can utilise them better in my workflow. Thank > you for you hard work and taking the time explaining. > > On Tue, Dec 2, 2014 at 12:29 AM, Sven Van Caekenberghe <s...@stfx.eu> > wrote: > >> >> > On 01 Dec 2014, at 23:06, Tudor Girba <tu...@tudorgirba.com> wrote: >> > >> > Glamour is an engine by itself, but for the inspector you mainly need >> the presentations, which are essentially widgets that can be parameterized >> through blocks. A custom presentation like this typically requires one >> method. If you want to get examples of how to apply it for the inspector, >> you can use the inspector to answer that question, as described here: >> > http://www.humane-assessment.com/blog/managing-gtinspector-extensions/ >> >> Yes, yes, very nice. >> > > -- www.tudorgirba.com "Every thing has its own flow"
