My understanding is: HTML/JavaScript will continue to exist in IMatch 6. But as Mario mentioned in some other post, the object model used to access the database, the files therein and everything else, will presumably change. For example, many Basic scripts first retrieve the "current selection", then do something with these files. If I convert such a Basic script into an IMatch 5 App I would maybe use the same logic. In fact, one small JavaScript function I use for moving files to different directories, dependent on some specific file name patterns, looks like:
function _moveImportedFiles() {
// The database
var l_db = IMatchLib.database();
// Get selected files
var l_sel = IMatchLib.application().GetFileWindow(IMatchLib.FileWindowType.imfwtCurrent).SelectedFiles;
if (l_sel.Count < 1)
return;
for (i=1; i<=l_sel.Count; i++) {
var l_file = l_sel(i).Name;
for (j=0; j<FileNameMatching.length; j++){
var l_regex = new RegExp(FileNameMatching[j].pattern);
if ( l_regex.test(l_file) ){
l_destfolder = l_db.Folders(FileNameMatching[j].folder);
l_db.MoveFile(l_sel(i), l_destfolder);
// Set category
if (FileNameMatching[j].cat.length>0){
l_db.Categories(FileNameMatching[j].cat).AssignFile(l_sel(i));
}
}
}
}
}
But I am not so sure that for scripting in IMatch 6 this function will work. It depends heavily on the current object model: Get the "Application" object, get the File Windows, get the selected files...:
var l_sel = IMatchLib.application().GetFileWindow(IMatchLib.FileWindowType.imfwtCurrent).SelectedFiles;
This said, I am confident that it will be possible in IMatch 6 to achieve the same functionality. But the JavaScript code will not exactly be the same. Some rewriting will be necessary.
