Overview
|
The Fusker Collection View is the largest portion of the Image Surfer Pro application window, the portion between the Image Surfer Pro Toolbar and the Image Surfer Pro Statusbar. It is a graphical tree representation of your fusker collection. It should feel similar to a directory tree structure from Windows File Explorer. With some minor differences:
The scrollbars shown here will only be present if needed to see the entire fusker collection. The icons shown in the fusker collection view tree represent the various portions of the image references stored in the fusker collection. The fusker collection shown here is called Hot Mustangs! and it contains links to various types of files stored on the World Wide Web. It uses both the standard HTTP connections and secure HTTPS connections to access those files. The visible portion in the diagram shows it contains links to Frame, MP4 Video, Page, and Image files. You interact with your fusker collection by selecting a segment of the fusker collection tree and using the tree menu or toolbar buttons to perform actions on that segment. You select a segment by left clicking any of the icons or text in the fusker collection view. The tree menu pops up when you right click anywhere in the fusker collection view portion of the application but right clicking does not change the segment selection.
|
Fusker Collection Icon
|
The top level icon on the tree represents your fusker collection. The fusker collection holds a set of file references. The path to each file can be seen in the structure of the remaining segments. The text shown next to the icon is the Name of your fusker collection. |
| You may modify the name of your fusker collection via the tree menu Modify option. The collection segment can not be fusked and you can not roll up path segments into the collection segment. The collection name held by the segment is not used in the generation of URL references in any way. | |
Access Domain Icons
| Immediately below the fusker collection, the next layer of tree segments represents the access protocol used to reference the files of the fusker collection. There are three different icons used to represent the relative access zones. It is possible to have a fusker collection which contains files from all three domain types. Because the fusker collection stores a reference to the file and not the actual file data itself, it is important to understand that you may not be able to view the files in a fusker collection unless you have an internet connection or a connection to the local area network where the actual file data is stored. | |
|
The hard drive icon represents files which are located on the local computer. If you have mapped network hard drives, files on these drives will also be represented by this icon. Starting with Windows Vista and Windows7 you may need to turn off User Access Control, Protected Mode, and Enhanced Protected Mode to access local files through generated webpages. |
|
The network drive icon represents files which are stored on the local network but not the local computer. Files can be referenced on a trusted network through generated webpages with both User Access Control and Protected Mode turned on. However, you will need to set the security parameters for this Intranet zone to match those you use in the Internet zone. In Windows 10 and IE 11 you will also need to disable Enhanced Protected Mode to access intranet files through generated webpages. |
|
The globe icon represents the various protocols used to access files on the world wide web. For most users this will be the most common and possibly the only Path Icon they ever have in their fusker collections. The most common protocol represented by the icon is http though any protocol through which IE can connect to Internet content can be used. |
| When merging fusker collections the path segments never combine information. They will match merging path segments which have both the same access protocol and text. You can not combine references across differing paths into the same tree branch, fusk a path segment, nor roll up a directory structure into the path segment. | |
Directory Branch Icons
| Below the access type segment come the directory segments. Each of these segments can be fusked to create iterated segments. There are two types of directory segments which provide you the flexibility to create virtually any type of fusked path. Fusked segments can be identified by the + in the top right corner of the icon. | ||
|
|
The standard directory segment represents the familiar directory object in most file systems. These segments are terminated by '/'. Directories are used to organize the storage of files on servers and as such are often "logically" named based on the files they contain. Directories may be fusked with both list and numeric fusks. |
|
|
In some cases you may wish to fusk more than one set of characters in a directory or a file however each fusker collection segment can have only one fusk - the solution is to split the directory or file into two segments. The top segment of the split will always appear as a split directory with either a file or directory child segment depending upon which type of segment was split. Split directory segments may be split multiple times and may also be fusked with either list or numeric fusker data. |
| You may manually split or roll up directory and split directory segments. Merging directory segments is directional and the "level of roll up" in the existing fusker tree will be forced onto merging segments. If a file segment is rolled up into a directory or split directory segment the resulting segment will be a file. | ||
File Segment Icons
The final segment in most references is a file segment. File segments represent the end of a fusker tree branch. The icon used in the tree represents the type of data the URL accesses - or more precisely, how Image Surfer Pro will attempt to access the URL information. The type of file access used will be determined when the URL is added to the fusker collection and can not be changed.
Image Surfer Pro threats all files as one of four different types: Images, Videos, Frames, and Pages. The difference in how Image Surfer Pro deals with these different file types is partially related to how they can be displayed on a webpage as well as the relative security risk of interacting with the URL content.
Images
Images are static data files which can be embedded on a webpage in the same way regardless of the details of the different file formats. Because of this, Image Surfer Pro treates all images in the same way and uses a single icon to represent all image file formats.
These file extensions will be recognized as images: .jpg .jpe .jpeg .gif .bmp .tif .tiff .pic .pct .pict .pcx .pxr .png
|
|
Image files are represented by our traditional BLUE icon. URLs which end with an image segment will be encoded in <img> tags on the Image Surfer Pro generated pages. Image Surfer Pro was originally built for the single purpose of accessing image files in a better way. |
Videos
Like images, there are a number of static data file formats for storing video content. However, unlike images, not all videos may be encoded in HTML the same way. Image Surfer Pro uses three distinct sub-types to handle static video file references.
|
|
The GREEN icons with the film strip on the left represent MP4 video segments. URLs which end with a MP4 video segment will be encoded in <video> tags on the Image Surfer Pro generated pages. IE can only recognize files encoded in the MPEG4 format encoded in this way. |
|
|
The familiar Flash icons are used to represent Flash Video file references (.flv). IE does not recognize this popular video file format when encoded into an <video> HTML5 tag. However Image Surfer Pro has provided a generic flash player which can be reliably used to access these videos. Because of this specific encoding they are given their own sub-type and icon. |
|
|
The Windows Media Player icon is used to represent the remaining supported static video file formats. These files are encoded in HTML to utilize the built-in Windows Media Player application installed with all versions of windows. This player is used by Image Surfer Pro to display files with these file extensions: .wmv .mov .mpg .mpeg .avi .asf |
Frames
Active content added to the fusker collection can be generically called Frame data. This includes both Shockwave Flash content and other types of active content. While this type of content represents a High Risk, they are also some of the most common ways video content is delivered on the Internet. Tube sites (such as YouTube) deliver video content in this way. The difference in how Shockwave Flash and other embedded frame content is encoded on a webpage has lead Image Surfer Pro to use two icons and sub-types to represent the different frame data.
|
|
Shockwave Flash (.swf) files are not uncommon. The Image Surfer Pro flash video player is a shockwave file. This file format can be used to embed both the player and the video information and is still fairly common, though support is being phased out of most browsers. The standard Shockwave icons have been adapted into segment icons to represent URLs referencing these files. |
|
|
Active content will be found in <iframe>, <embed>, and <object> tags. Often the data source referenced by these constructs will not have a recognizable file extension. These types of active content references can be added to your fusker collection as Raw Frames represented by the Framed F icon in the fusker tree. This type of content is most often associated with the embed code captured from tube sites such as (YouTube). |
Pages
The concept of a frame in HTML was originally designed to allow multiple HTML files to be shown on a single combined webpage. This means nearly any webpage which would render in your browser can be encoded as the source of a frame on a generated webpage and fully display.
|
|
Webpages themselves can also be shown in <iframe> tags, in which case the frames become almost smaller browser windows within IE display window. |
File segments of any type never have child segments. Because of this files in the same branch can easily be combined into a single list fusked file segment. However, the differences in the way the file types are treated means they can not be grouped across file types and sub-types. "Roll Up" is disabled when a file segment is selected - however they can be split and form a split directory segment with a file segment child to allow you to fusk more than one set of characters within the file name. During mergers file segments will combine based on the setting of the {Auto combine individual files into fusked files} configuration for each file type, however sub-types will remain distinct. For example, if {Auto combine individual videos into fusked videos} is enabled, MP4 files will merge with other MP4 files in the same tree branch, but will still not merge with flash files.