Re: Refactory Browser help
Locked
Re: Refactory Browser help
 
|
Re: Refactory Browser help
|
|
Re: Refactory Browser help
|
|
Boris:
Sorry, I got confused. I thought you meant ADvance tools. You are just referring to the old doc generator i.e. which yes was always just plain text. A much nicer documenter would be the one provided with ADvance. It generates nice html docs and I do believe that there are free html to acrobat converters although I don't recall a name off hand. The StarBrowser ADvance integration does one the favor of setting a particular package as an ADvanc e subject which is what is required to use the ADvance documenter on it. However, it is not a big deal to set a subject manually if one does not want to load StarBrowser. I have attached a screen shot of an example of what it could generate. I also have attached a zipped folder with the html docs and images it generates. I don't share your trust in the usefulness of comments in the system, or let's say that they are at best just "somewhat useful", also I'm not sure that class comments would generally be sufficient to help developers handle some of the IDE tweak issues that come up on this list from time to time, especially if one considers that there is quite a decent level of variability in user level of experience with VW. To be fair to Cincom I don't believe that it is warranted that they have to provide tutorials on how to muck with the IDE. After all, its Smalltalk, all one really needs is a debugger and a way to get under the hood :) -Charles On Thu, 12 Jan 2006 12:24:59 -0500, Boris Popov <[hidden email]> wrote: > Charles A. Monteiro wrote: >> Boris: >> >> thanks, hopefully SmalltalkDoc will also fill this gap. BTW, are the >> Advanced tools now generating pdfs. I vaguely recall them generating >> html. > > You can either generate plain text or send the output to the printer, > which could very well be any kind of PDF printer, such as Acrobat, > pdf995 etc. > > Cheers! > > -Boris > >> >> -Charles >> >> >> On Wed, 11 Jan 2006 10:41:50 -0800, Boris Popov >> <[hidden email]> wrote: >> >>> Charles A. Monteiro wrote: >>>> There are no docs that I know of into the internals such as the >>>> RBCommand and its "editor" UI, it is a pretty pluggable framework but >>>> the docs are not there. >>> >>> Fortunately for RB (and any other framework with at least half-decent >>> class comments) you could easily use Advanced Tools to generate >>> somewhat >>> useful class reference document as the next best thing. With a bit of >>> luck at picking the right keywords, you can use Acrobat to either study >>> the framework in detail or find solutions to specific problems rather >>> quickly. >>> >>> I'm attaching a PDF with class comments from all Refactory.Browser.* >>> for >>> your reference. >>> >>> Cheers! >>> >>> -Boris >>> >>>> >>>> -Charles >>>> >>>> On Wed, 11 Jan 2006 12:26:22 -0500, Charles Adams >>>> <[hidden email]> wrote: >>>> >>>>> >>>>> Charles, >>>>> >>>>> Yes, I follow you completely. Before I asked for help, I poked around >>>>> the >>>>> RB but quickly got off into the weeds. >>>>> >>>>> In prior generations of VW, I spent a respectable amount of time >>>>> tweaking >>>>> tools. I will no doubt be tempted to do the same in 7.x. So, I will >>>>> keep >>>>> your example in mind and attempt to "unravel the mysteries" again. >>>>> (We, here at Adventa, are late coming to the new VW. Most of our >>>>> customers are still using VW 2.5.) >>>>> >>>>> But, that does beg the question: why should RB and Store be so >>>>> mysterious? Am I missing some documentation? -- beyond user docs that >>>>> is. >>>>> >>>>> Thanks for the pointers. >>>>> >>>>> Charlie >>>>> >>>>> On 1/11/2006, "Charles A. Monteiro" <[hidden email]> wrote: >>>>> >>>>>> Charlie: >>>>>> >>>>>> Do you know how to break into the tools in VW? >>>>>> >>>>>> For example, you seem to have wanted to do basically want "Finds >>>>>> package" >>>>>> does on the opening of the browser i.e. open and select. So an >>>>>> approach to >>>>>> understand how to do this would be to find out what the action for >>>>>> the >>>>>> menu item "Finds Package" does. In case you don't know you can do >>>>>> the >>>>>> following: >>>>>> >>>>>> 1. Pop mouse, highlight entry >>>>>> 2. Control Y >>>>>> 3. Walk down the stack until in this case you find e.g. >>>>>> Win95MenuAsPopUpController >>>>>> 4. Look at its model -- its a menu, dive >>>>>> 5. Look at the "items" of the menu, dive >>>>>> 6. Find the menu in question , dive >>>>>> 7. Look at its "value" -- a blockClosure , dive >>>>>> 8. debugIt - "self value" >>>>>> 9. send into "self action: newItem" >>>>>> 10. send into "self performAction: aMenuItem nameKey asString" - go >>>>>> into >>>>>> #performAction: >>>>>> 11. send into "action performWith: self dispatcher" btw, note that >>>>>> RBCommand's action is: #findPundle >>>>>> 12. send into "self perform: action on: (self receiverFor: >>>>>> anObject)" >>>>>> 13. send into "anObject perform: aSymbol", -- no surprise the >>>>>> symbol is >>>>>> #findPundle >>>>>> 14. voila , you are home in #findPundle , now you find the little >>>>>> tresures >>>>>> you need to do what you want to do :) >>>>>> >>>>>> As good as Boris is , once you go through the above a couple of >>>>>> times, >>>>>> which I made it long-winded and safe in order to get the process >>>>>> across, I >>>>>> think you will find yourself doing more tweaks to the environment >>>>>> since >>>>>> they will come much easier to you i.e. given you can unlock its >>>>>> mysteries >>>>>> faster. >>>>>> >>>>>> BTW, on the same thread a nice package to load is the >>>>>> ProgrammingExtensions package, particularly since it contains this >>>>>> nice >>>>>> capability of popping an inspector on the widget you point to. Once >>>>>> you do >>>>>> this you can for example more quickly find what an action button >>>>>> does i.e. >>>>>> >>>>>> 1. Inspect widget via ProgrammingExtension added menu item to the >>>>>> blueButtonMenu >>>>>> 2. debugIt -- "self model value: generallyAnything" >>>>>> >>>>>> well, I'll spare you the details but you will soon find out what the >>>>>> button does. >>>>>> >>>>>> hth, >>>>>> >>>>>> >>>>>> -Charles >>>>>> >>>>>> On Tue, 10 Jan 2006 20:15:54 -0500, Charles Adams >>>>>> <[hidden email]> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> Yes, I understand that now. >>>>>>> >>>>>>> There are customizations I'd like to make to the tools but I >>>>>>> struggle >>>>>>> with their complexity. I also have other things to do :) which >>>>>>> doesn't >>>>>>> allow me much time to ponder tool customization. >>>>>>> >>>>>>> That's why its nice to have someone like Boris that can crank out >>>>>>> an >>>>>>> elegant solution so quickly. Thanks again, Boris. >>>>>>> >>>>>>> On 1/10/2006, "Isaac Gouy" <[hidden email]> wrote: >>>>>>> >>>>>>>> Well the remark did seem bitter, but not particularly >>>>>>>> wounding - a few decades ago there was a shift away >>>>>>>> from including arbitrary file content and towards >>>>>>>> importing modules (and having development tools that >>>>>>>> could figure out where to get the modules). >>>>>>>> >>>>>>>> >>>>>>>> --- Charles Adams <[hidden email]> wrote: >>>>>>>> >>>>>>>>> sarcasm? >>>>>>>>> >>>>>>>>> On 1/10/2006, "Travis Griggs" <[hidden email]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> > >>>>>>>>> >On Jan 10, 2006, at 10:26, Charles Adams wrote: >>>>>>>>> > >>>>>>>>> >> That's getting close. I probably should not have >>>>>>>>> been so terse. >>>>>>>>> >> >>>>>>>>> >> The button on the launcher with the ST balloon >>>>>>>>> opens the RB. The >>>>>>>>> >> view I >>>>>>>>> >> get is the Package view, because of my selection >>>>>>>>> in the settings tool. >>>>>>>>> >> The list of packages (well, pundles really) is in >>>>>>>>> a small box at >>>>>>>>> >> the top >>>>>>>>> >> left hand corner. >>>>>>>>> >> >>>>>>>>> >> Whenever I hit the balloon I invariably want to >>>>>>>>> go to a particular >>>>>>>>> >> package. That package is invariably buried within >>>>>>>>> nested bundles way >>>>>>>>> >> down the list. >>>>>>>>> >> >>>>>>>>> >> There is the notion of "current package" so I >>>>>>>>> thought: why not try to >>>>>>>>> >> get the RB to open on it? >>>>>>>>> >> >>>>>>>>> >> I did the same thing with the Envy >>>>>>>>> ApplicationManager, but this new >>>>>>>>> >> RB is >>>>>>>>> >> beyond me. >>>>>>>>> > >>>>>>>>> >Sounds like you just want a Package list? That >>>>>>>>> would be cool. Just >>>>>>>>> >packages in the RB. But for those that do rely on >>>>>>>>> bundles... having >>>>>>>>> >them somewhere is handy for organizing bundles. The >>>>>>>>> RB tries to do it >>>>>>>>> >all at once. Maybe a separate tool? But wait, as >>>>>>>>> you said, I'm just >>>>>>>>> >reinventing the split between Envy's >>>>>>>>> ApplicationManager and the >>>>>>>>> >Browser. One problem with doing so would be that >>>>>>>>> we'd by consigning >>>>>>>>> >Bundles to a specific role. Some people like using >>>>>>>>> them as Packages >>>>>>>>> >and Packages as Categories while others struggle >>>>>>>>> trying to turn them >>>>>>>>> >into Applications. I think it'd just be easier if >>>>>>>>> we put everything >>>>>>>>> >in files and wired them together with twisty mazes >>>>>>>>> of include >>>>>>>>> >directives. >>>>>>>>> > >>>>>>>>> >Anyway, it's just a tools issue (deposit Nickel in >>>>>>>>> Vassili's >>>>>>>>> >collection box). >>>>>>>>> > >>>>>>>>> >-- >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _ >>> >>> >>> -Boris >>> >> >> >> > > > -Boris > -- Charles A. Monteiro |
RBAdvanceDocs.jpg (52K)
Re: Refactory Browser help
|
|
| Free forum by Nabble | Edit this page |