These are awesome. It's not just a URL example, but an example of using a URL inside a Text instance -- something that can take a good bit of digging if you don't have an example.
-Lex
These are awesome. It's not just a URL example, but an example of using a URL inside a Text instance -- something that can take a good bit of digging if you don't have an example.
-Lex
Thanks :-)
Though it should have been [ENH] and not [Enh], that what comes of thin images, where you don't have scamper to file out automatically to the list :-/
For consistency reasons, I also think it is a good idea to name the other tag with upper case letters also: [EG]
Examples could also certainly be put in some [TEST] packages, and maybe later harvested.
This means, when you write tests, it would be _great_ if you put the fixtures in such kind of exampleFoo methods on the class-sides.
And please don't forget to put them in a category called
"*Eg-example-objects"
*Eg is for possibly use with DVS, and -objects is both for: - separating them from the usual examples where one could get user-interfaces (Uups, I didn't say that yet, please only put automatically usable things in this category) - separating them from example-methods, another concept, I am playing with. I am using both category-names in my little Eg-tool, found on SqueakMap (still very alpha, I mean it...)
Actually, for my little "modal info dialog"-hack, I did it the [TEST]-way.
So I am still on track with my much to ambitious "one example a day"-goal ;-)
Any help appreciated, now I put that on the Swiki,
Markus
On Thu, 12 Jun 2003, Markus Gaelli wrote:
And please don't forget to put them in a category called
"*Eg-example-objects"
*Eg is for possibly use with DVS,
Hm. But if you name it that, then DVS or other PackageInfo-based tools would treat it as part of the Eg package, and it *won't* get filed out along with the class you're adding the examples to.
Is that what you're intending?
Avi
Hi Avi,
And please don't forget to put them in a category called
"*Eg-example-objects"
*Eg is for possibly use with DVS,
Hm. But if you name it that, then DVS or other PackageInfo-based tools would treat it as part of the Eg package, and it *won't* get filed out along with the class you're adding the examples to.
Is that what you're intending?
You are absolutely right. No, I didn't intend that and I was wrong. :-/
What I _was_ intending, is to have a naming-convention, which allows us and the tool Eg to know which are automatic/no-user-interaction-required examples.
So it should be "your package-prefix, with or without a leading *-example-objects" or just only "example-objects"
Thanks a lot for correcting that,
Markus
"The rate at which a person can mature is directly proportional to the embarrassment he can tolerate" Doug Engelbart
superseded by changeset posted later. [closed]
< I'm a bug-fixing machine! >
This post brought to you by the BugFixArchiveViewer, a handy tool that makes it easy to comment on proposed fixes and enhancements for Squeak. For more information, check out the Web page for the BugFixArchiveViewer project: http://minnow.cc.gatech.edu/squeak/3214
< I'm a bug-fixing machine! >
squeak-dev@lists.squeakfoundation.org