On Wed, Feb 10, 2010 at 9:21 PM, Sherlock, Ric <[email protected]> wrote: > Comments regarding your template: > (I'm aware that your template is designed for gathering content rather than > as a finalized format)
Exactly. Need to bear in mind that some features are superficial, such as <<TableOfContents>> ...This can be ripped out and put back at any time, so it's purely decorative at this stage. The same goes for the big heavy bars. > I like the sub-titles - they appear to do a good job of conveying the context > (monadic/dyadic) without getting in the way. It would be good to get some > feedback from newcomers to J though. I guess you mean the == x ?? y (JName) == ...Yes, I shall populate and control these highest-level headings. Which means I can rip them out and have them different at any time. I'm expecting to change them. I can think of one subheading we could do with: Idioms. (Or should that be: Phrases?) > One disadvantage is that it will be a pain to hyperlink to directly to them, > for example to link to the section on "Larger Of" the url is: > http://www.jsoftware.com/jwiki/Vocabulary/greaterperiod#x.3E.y.28LargerOf.2CMax.29 Yup. I still don't like the fact that the page for a verb is in effect two distinct pages glued together, viz the monadic & dyadic cases. It gets us into problems like this. But I was shot down in flames when I wanted them separate. Now if we could have had them as separate pages, they could have had stable URLs like mgreaterperiod, dgreaterperiod, instead of http://www.jsoftware.com/jwiki/Vocabulary/greaterperiod#x.3E.y.28LargerOf.2CMax.29 Anyway that: x.3E.y.28LargerOf.2CMax.29 -is not set in concrete and will change. I'd expect it to incorporate rank and part-of-speech in due course. And, yes, although the existing http://www.jsoftware.com/jwiki/Vocabulary links only to a page called greaterperiod (or will do), I anticipate good task support will demand the need to link to monadic and dyadic sections separately. It's a pity if we're prevented from having the H1 title we really want, just because we need it to say Monadic or Dyadic (say) purely in order to link to it with a stable URL. My whole approach is: usability task support first, MoinMoin convenience second. Having said that, let's start with what's already there for us. > The template seems to suggest that users shouldn't add to the See Also > sections. Is this intended? No. The See Also is purely an example. But a ref to the existing Voc is IMO essential ...and I can generate that. > Other things I would like to see: > * a bigger version of the primitive at the top of the page in a monospaced > font to reinforce that I'm on the right page. So would I. I envisage it being provided as a JPG. Maybe a cute cartoon primitive? Thanks to our consistent nameset I know what it will be called: greaterperiod.JPG ...etc. Anyway I think its provision can be deferred and doesn't interfere with content-collection. Try out ideas with one of the format samples. > * Using the TableOfContents macro for navigation is nicer but I also see > some value in an at-a-glance summary of the primitive somewhere. Yeah, I just stuck it in. No opinions about that TOC, except to note that it lets you go quickly to the dyadic case :-) If that's the only task it supports, then... there are other ways to do that. But like the aforementioned JPG it's not important for my limited purpose. "at-a-glance summary of the primitive somewhere"... I guess you mean the blue box we had. Yes, my omitting that is not to deprecate it, but because I'm waiting for a stable design. I don't want content-providers to insert the data for that, else I'd have to debug it. To control it easily I need to generate it. ...Another retrofit. Ian ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
