Navigation

• Main Page

• Application recipes
• SoftGrid FAQ
• Tweaks & tricks
• Tools & Utilities
• Websites
• News on SoftGrid
• Free-falling

Account settings

• Login/Logout

• Create Account
• Language Selection
• Your Profile

Wiki tools

• Create a new Page
• All Pages
• Categories
• File Management

• Administration

Quick Search

Advanced Search »

Edit

How SoftGrid items should be named

In an SoftGrid environment, there are several things that are given names. Not only that Softgriders use strange items (like a Package Root, a Content Folder or a Suite) but they also give these items names that follow strange convetions. Some suggestions about how to name certain things around SoftGrid are:

Generaly, file names should be as descriptive as possible. Note that most files are deployed based on URLs or UNC paths, so avoid special character. You should restrict yourself to the basic Latin (or english) letters, Arabic Digits, the Hyphen "-" and the Underscore "_"

Edit

OSD,ICO,SFT and SPRJ file names

For the current (Version 4) Sequencer, there is no easy way to change ICO file names and the "[SomeName] Icons" folder name. If you still use a Version 3 Sequencer, you might have the chance to change, so don't care about the ICO file and folder names directly. The OSD file name is defined during Sequencer's "Application" phase, when the list of determined applications is displayed. You actively have to "Edit" each of these or you'll get OSD filenames that contain spaces, several dots and sometimes even commass.

If you use a Content subfolder on the SoftGrid Virtual Application Server for each package, it is enough to name OSD files like


If you intend to have several packages inside on (sub) folder of Content, you should name the OSD files more expressive:


You should include the Vendor, the Application Family Name and Version here and have the Single Application name as one of the lasst parts (you see, if you have an "Office" subfolder, you still can quite fast see what belongs to Office 2000, 2003 and so on (and not having all these "Excels" clustered)

The Softricity File (.SFT) and Softricity Project File (.SPRJ) should be named like in the above recommendation for Content subfolders: You enter this name, when you "Save" your package in the sequencer and replace the "softapp" value. The SFT gets the same name and also the icon folder uses this name





Edit

SoftGrid Sequencer Suite Name

The Suite Name for a package has to be unique. It was for instance used to build sub folders for the user’s personal application settings.
Best practices for Suite Names include

SuiteName_Vendor_Version_SequencingMethod


Vendor_SuiteNameWithVersion_SequencingMethod


Another example might be


Note: You should maintain a database / excel sheet to record this settings



Edit

SoftGrid Sequencer Asset or Package Root directory

This is the only one directory that strictly should follow 8.3 conventions. Also this folder has to be unique. Typically this directory is created on the Q: drive of the Sequencer before sequencing starts. Best practices for Asset or Package root contain




Note: You should maintain a database / excel sheet to record this settings

It is also recommended to create a sub directory below the Package Root directory and to install the application into this sub folder. This makes it easier to add new components to the package without mixing them with the original stuff. An example might be


- Office2k.en for the Package Root directory


- Office2k.en\Microsoft Office 2000 en SP1 for the directory where Office is installed to


Another example to explain this could be FireFox.


The Asset directory could be FireFox.030 (indicating this is the 3rd major version of a FireFox package)

Of course all application files for Firefox and Java could be placed in the Package Root, but then it would be difficult to sort out what belongs where.



Edit

SoftGrid Virtual Application Server - Content directory

Since the Suite Name (explained above) has to be unique across the SoftGrid platform it’s a good practice (but not mandatory) to use it for Content-subfolders as well
Examples:



SoftGrid Virtual Application Server’s Content directory allows usage of sub directories, like




There are more information about SoftGrid Item Naming at www.kirx.org


Back to the FAQ main page