-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Navigator folder view with generated HTML files #52
Comments
In newest Eclipse there is option
So if the file is really in folder I should see it after F5 or sometime, but in my experience it was not. Just confirm that no other folders are used. |
The HTML files are only visible in the Navigator view (by default) because the Project Explorer and similar views filter out files with a leading ".". The only other alternative is that you had the Use Temp folder option enabled, in which case the HTML files would never be visible under any circumstances. BTW the point I mentioned about project rebuild overhead on refresh is very important. |
By default I have all files shown, and I encourage everyone to disable filters on project files. Please reopen #51 that is user oriented. And see if more people ask for that. |
I think our opinions on the HTML files are not the same! To me, they are simply by-products of the display process and what Eclipse does to hide them is quite right. So I think I'll wait for any further comments. I will review the IFile options again when time permits. |
The plugin typically writes
.filename.md.html
files alongside the originalfilename.md
files. However since it does not use the Eclipse Workspace API to write the HTML files, these files not appear in the Navigator folder view immediately after creation. The user needs to press F5 (or context menu Refresh) on the parent folder to see them. See also: http://wiki.eclipse.org/FAQ_When_should_I_use_refreshLocal%3FTherefore, there are several possible approaches to this issue;
IFile.create()
API to write the fileIFile.refreshLocal()
API to refresh the parent folderThere are two major complications to a solution:
refreshLocal
API was that calling it seemed to force a complete rebuild of the whole parent project: with a large Java or Scala project this can take a long time and would be very intrusive to the user. So creation and updating of these files should not force a rebuild if possible.The text was updated successfully, but these errors were encountered: