I like that. Norm suggested maybe we need to use more than one word for the category names.
If we were starting from scratch, I might suggest taking an approach from Laszlo-Explorer and ordering the TOC by the way you might introduce the language: Language Basics canvas, view, text, inputtext, attribute Extending Behavior attribute, setter, method, handler Defining New Tags class, mixin, interface Basic (built-in) Tags view, text, inputtext, ... Organizing Programs import, include, library Advanced (built-in) Tags animator, context menu, splash ... Standard Extensions the components, probably broken out in more detail But perhaps that is a project with a longer-term focus. On 2010-09-28, at 10:31, Lou Iorio wrote: > I think this is simple and makes the most sense, but I'll leave the > discussion > open for another day or two... > > Structure > * <canvas> > * <import> > * <include> > * <library> > Language (some of these reference pages do not yet exist) > * <attribute> > * <class> > * <event> > * <handler> > * <interface> > * <method> > * <mixin> > * <passthrough> > * <setter> > > Move to components > * <splash> > * <splash view> > * <contextmenu> > * <contextmenuitem> > > On Fri, Sep 24, 2010 at 1:31 PM, [email protected] > <[email protected]>wrote: > >> I would look for the word "Custom" in the documentation. >> >> For example: >> >> Custom Language >> Custom Tag >> Custom Structure >> >> Just my $0.02 >> >> >> Pete >> >> >> >> >> >> On 9/24/2010 8:28 AM, P T Withington wrote: >> >>> [Adding laszlo-user: Users: what would you look for if you were looking >>> for documentation on how to add your own tag to the language?] >>> >>> I'm thinking that maybe this needs to be split into several pieces. >>> >>> The original title 'Structure' probably referred to canvas, import, >>> include, and library, which are how you organize your program structure. >>> >>> There is another set of things I call 'meta tags' that are the tags you >>> use to create your own new tags: class, mixin, interface, attribute, method >>> (missing), event, handler, setter (missing). Lisp calls these 'special >>> forms' because they are processed specially by the compiler, but I'm >>> thinking a title like "Language" is better. >>> >>> splash* and contextmenu* seem out of place in both these lists. They are >>> neither about structure nor language, they just seem like components, no >>> different than window, menu, etc. >>> >>> On 2010-09-24, at 10:17, Lou Iorio wrote: >>> >>> I'm about to add new reference pages for<class> and<passthrough>. >>>> >>>> It seems like these should go in the "Structure" category in the TOC, >>>> but that has become sort of a catch all for items that don't have a >>>> more obvious category. Right now, the Structure category looks like >>>> this: >>>> >>>> Structure >>>> *<attribute> >>>> *<handler> >>>> *<event> >>>> *<canvas> >>>> *<import> >>>> *<include> >>>> *<library> >>>> *<mixin> >>>> *<splash> >>>> *<splash view> >>>> *<contextmenu> >>>> *<contextmenuitem> >>>> >>>> You can see the entire TOC here< >>>> http://www.louiorio.com/openlaszlo/toc.html> >>>> . >>>> >>>> Items can appear in more than one category (for example,<event> is in >>>> both the Structure and Events categories). >>>> >>>> Any ideas for a better organization? Better name for Structure? >>>> >>> >>> >>> >>
