|
|
KNotations :: Documentation and development plans from the KnowNet development team
|
Weblog | 84 entries | 23-June-2006 | 1 authors |
|
|
Blog Entry | 0 replies | 19-June-2005 | Mike Malloch |
Steve recently added a bit of a hack to allow API posts to specify new categories. Users of knotes blogs who post through the web (TTW) will be used to adding new categories ad-hoc as they post. In the TTW form for editing posts, there is a widget for adding a new category and associating it with the post. (The new category is added to your personal categories - at some point we plan to implementt interfaces for negotiating the promotion of personal categories to blog-wide or portal-wide scoping, but that's another issue. :o) Users who post with a weblog API client like blogjet or ecto, on the other hand, have had to specify their categories in advance, or edit their entries TTW after posting. There is no provision in the API specifications for creating categories when editing or creating posts: category association is taken to be a list-choice. If a category is not already on the list of categories for that blog (and you as an editor), you have to go to the weblog through the web and add it there. Graham for one was finding this awkward; Steve has built a workaround. To associate an entry with a new category just insert it between a pair of '<cat>...</cat>' tags - anywhere at all within the body of the post. . When you submit the entry, our API implementation will scan for these 'tags', and any new categories so specified will be added to the categories for the entry. The tags themselves will be removed from the text of the entry when the server processes it. tags. Make sure of course that you are in a raw-html editing mode when you type in the <cat> and </cat> though - otherwise the tags come through encoded like '<cat>...</cat>'and are not parsed as 'tags'.
Your client probably can help with this. In ecto, for instance, there is a Custom Tags feature ( on the toolbar, HTML tags in the Window menu, or command-shift-M ). See the attached screenshot |