# UnifiedFiler v1.9.4-fix2 Notes

v1.9.4-fix2 aligns the source tree naming with the Control architecture terminology.

## View directory rename

The former internal UI component directory was renamed:

```text
scripts/plugins/  ->  scripts/views/
```

These modules are still implemented as jQuery plugin based View/Controller components, but their architectural position is View. Host-facing code should treat them as internal view modules owned by Controls.

## View module file rename

The old file names included the implementation technology. They now use architectural names:

```text
scripts/views/FileExplorerView.js
scripts/views/FilePickerDialogView.js
scripts/views/FileSaverDialogView.js
```

The jQuery plugin APIs remain registered for compatibility:

```javascript
$('#explorer').fileExplorer(options);
$('#host').filePickerDialog(options);
$('#host').fileSaverDialog(options);
```

New Control-based integrations should continue to use:

```javascript
new UnifiedFiler.controls.FileExplorerControl('#explorer', options);
new UnifiedFiler.controls.FilePickerControl(options);
new UnifiedFiler.controls.FileSaverControl(options);
```

## Public package export

`scripts/main.js` now exposes these modules under `UnifiedFiler.views`:

```javascript
UnifiedFiler.views.FileExplorerView
UnifiedFiler.views.FilePickerDialogView
UnifiedFiler.views.FileSaverDialogView
```

This keeps the package names parallel with `models`, `services`, `commands`, and `controls`.