On Wed, Sep 23, 2009 at 8:05 AM, Keith Lazuka <[email protected]> wrote:
> - $subsection now displays the definition-icon next to the link rather
> than a plain bullet symbol
>
> - If $subsection is used to display a link to a word's documentation,
> the word's stack effect is now drawn in a dark green color, making it
> easier to read the word name at a glance

Right now, only the word name is clickable. The effect is clickable
too, but this is useless because it just opens the effect in the
inspector. How about making the entire line clickable with the word's
presentation? The effect doesn't need a presentation at all.

> - Some documentation has been updated to use $subsections
> (specifically all of the "sequences" documentation).

Can you update the rest?

> - The "html.streams" vocab now knows how to create an <img> HTML
> element from the formatted streams' "image" character style. One
> caveat is that the image is *not* directly embedded in the img tag,
> instead the image must be manually copied to "/images" in your
> webserver path, preserving the nested vocabulary directory structure.
> So if your image resource is at "vocab:definitions/icons/foo.tiff",
> then you must copy it to "/images/basis/definitions/icons/foo.tiff" on
> your webserver (notice that the vocab-root is expanded).

I simplifed this logic a bit. Now it just hardcodes
vocab:definitions/icons/ and redirects that to /icons/. I also changed
webapps.help to mount this directory under /icons/.

Slava

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk

Reply via email to