Back to XUL: JavaScript Logic - Scripting the Menubar: Save
(Page 4 of 4 )
Next is the very similar save file dialog, which is basically a different implantation of the same underlying structure used in the open file dialog. Generating an instance of the save file dialog is almost identical to the open dialog. All that is different is the string displayed in the dialog's title bar and the interface mode:
function saveDialog() {
const CC = Components.classes, CI = Components.interfaces;
var fp = CC["@mozilla.org/filepicker;1"].createInstance(CI.nsIFilePicker);
fp.init(window, "Pick a location to save to",
CI.nsIFilePicker.modeSave);
fp.appendFilters(CI.nsIFilePicker.filterAll | CI.nsIFilePicker.filterText | CI.nsIFilePicker.filterXUL |
CI.nsIFilePicker.filterXML | CI.nsIFilePicker.filterHTML);
var rv = fp.show();
We still encase the remainder of the function in an if loop so that it is executed on the OK button click, and we still get the file from fp.file. This however is where the similarities end:
if (rv == CI.nsIFilePicker.returnOK) {
var file = fp.file;
var foStream = CC["@mozilla.org/network/file-output-
stream;1"].createInstance(CI.nsIFileOutputStream);
This time, we implement the NSIFileOutputStream interface from the ["@mozilla.org/network/fileOutputStream;1"] component. In order to save data to a file, you need to create an output stream and pass the data to be saved into it. Once we have set the interface to a variable, we call the initialize method:
foStream.init(file, 0x02 | 0x08, 0664, null);
The first parameter is what we want to initialize, in this case the file. The next parameter states that the file should be in write mode, or if it does not exist, it should be created. The third parameter deals with permissions, and the final parameter is always set to null as it is not yet supported.
Next, we want to get the content of our editor. To do this, you first need to get the editor itself, then the contents of the editor:
var text = document.getElementById('mainContent');
var text = data.contentDocument.body.textContent;
The text in your editor is actually HTML, so to get the actual words that are typed to save correctly, you need to get them from the <body> element, which the second line above will do.
All you need to do now is write the data and close the output stream:
foStream.write(text, text.length);
foStream.close();
You now have a way of opening files, displaying (and modifying) their content, and saving files. Our File menu is now completely scripted with all of the required behaviors, although there is still more work to be done. We still need to code the Edit menuitems, again using XPCOM to handle the clipboard actions, and we still need to create our help window and script the calls to open it. All of this and more will be discussed in the next article.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 3 
