Username Password
Bookmark and Share


Related Pages

  • adding newsletter object to your site
    Adding a newsletter object to your site.
  • Article Asset templates
    There are currently five Article templates: Default Article Left align image Linked Image with Caption Item Article With Pagination This article describes these templates and explains which template you should use in different scenarios. All article templates now display the titles with the h3 tag. Please share your creative uses of these templates. When do I use which template? Default Article This template contains all the normal amenities: title, and the article itself, followed by a "url link" and it's "url title", followed by an attachment loop. Left align image (Article with Image) This is similar to the Default Article, except it assumes only one attachment is provided and that it is an image. The image will be embedded within the article's description. You can use CSS to align the image. By default, it's is left aligned. The description is followed by "link url" and it's title. Linked Image with Caption This allows you to display an image, followed by the article description. If the "link url" is provided, the image will be linked to it. If the "link title" is also provided, it will become the image's "caption" which will also be linked to the "link url". All this is followed by the article description content. Item If the link url is provided, the title of the article asset will be hyperlinked to the "link url". Followed by the article description, and any attachments. "link title" is ignored. This is handy for a simple store front for product categories, and such. Article With Pagination This is a paginated article. It will display the title, followed by the description. On the last "page" of the article, it will display the "link url" and "link title" if any, followed by any attachments. The size and number of pages is determined by the separator macro (
  • Aspects
    An Aspect is basically a pluggable component which can be added to any asset to give it additional functionality. An example of an aspect is the keyword attribute.
  • Assets
    Assets are the building blocks of any WebGUI site. They can be, for example, Article assets for serving static HTML content, Gallery assets for presenting multimedia content or Collaboration System assets, which are used for the realization of Fora, Weblogs, Guest Books, and many more. Even the visible pages presented to the user are assets - namely Page Layout assets. They serve as containers for other assets, determine the way they are arranged and build the hierarchical structure of the site. At the time of writing there are more than 40 assets available in WebGUI (Version 7.5) providing almost any functionality you can think of. And their number is continuosly growing. An overview of available assets is given in the following section.
  • Common Asset Settings
    AssetID - This is the unique identifier WebGUI uses to keep track of this Asset instance. Normal users should never need to be concerned with the asset id, but some advanced users may need to know it for things like SQL Reports. The asset id is not editable.
  • Composite Asset
    A Composite Asset is an asset made up of multiple assets like Wiki Master (a Wobject) + Wiki Page (an Asset).
  • Creating a new namespace
    I didn't find anything explaining this, and perhaps it's a no brainer, but I thought I'd document it anyway.  =)
  • Creative use of built in Assets to minimize the need for programming
    One of the main aspects of WebGUI is powerful templating. With templating you can make built-in assets do more than what they where intended to.
  • Find most recent versions with assetIndex
    The assetIndex table is part of WebGUI's search system, also described in some detail in JT's Black Blog. Because the primary purpose is to facilitate searching for current versions of content, each asset gets only one entry in the table, representing the current committed version of the asset. This makes the table very useful, not only for what most of us think of as "searches" on content, but also for SQL Reports. For example, finding the 3 most recent posts to a forum or a list of tomorrow's events.
  • HTTP Proxy
    The HTTP Proxy asset brings content from another site into your page. External content can be de-styled to match your style via the Display tab (Remove style?).
  • Image Asset templates
    There are currently three Image templates:
  • Lineage
    Lineage was created to allow retrieval of any or all related assets with a single, simple query to the database. This means we can retrieve all ancestors, parents, siblings, children, and descendants as well as know the ranks of all within a group of siblings.
  • magic numbers
    This is a list of the magic numbers that WebGUI uses
  • WebGUI Glossary
    Assets Everything inside of WebGUI is an Asset: files, images, forums, threads in forums, posts in threads, templates, Wobjects (like Articles, DataForms, EventsCalendars) and more. Assets come in three types, Utility, Container and Assets (for lack of a better name). Regular old Assets are those assets that are dealt with on a daily bases, such as Articles, File Piles, Data Forms and Collaboration Systems.
  • Wobject Cookbook
    The Wobject Cookbook is intended for developers as a cookbook guide to writing a custom asset. It includes miscellaneous recipes on how to do various tasks within your custom asset. 
  • Wobject Development Tutorial
    The following is a tutorial on how to build your own Wobjects. Note that the same techniques go into building regular assets. Before building a Wobject you should be familiar with WebGUI's available API's, the Wobjects that already exist and their code. If you don't familiarize yourself with all of these you'll likely spend a lot of time reinventing the wheel, and ultimately you may even fail in building your own Wobject.
  • wobject vs asset
    A Wobject is a broad type of Asset that provides additional basic functionality like style templates
Most Popular | Recent Changes | Wiki Home
© 2023 Plain Black Corporation | All Rights Reserved