This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Currently data shadows (links) are indicated visually by means of a display name based on the link filename plus "->" after a space. Depending on what font you are using etc., this can be somewhat clumsy-looking. Suggest instead that the icon (base taken from the original object) be badged with something like a "shortcut symbol" (see Windows UI for an example). As links are used more and more for projects, the difference will become more and more visible.
Target milestone -> 3.3.1.
Jirka, could you ship an icon, please. It may need some discussion where the icon should appear, because lots of nodes already use badges and we shouldn't make conflicts.
Created attachment 3666 [details] DataShadow
How much is it urgent? Do we plan to fix it into 3.3(.1)? Second question, I attached an example, is it what we are talking about? Thanks.
Definitely we aren't going to fix it for 3.3.x, yes your example hits the problem. We would like to get rid of the arrow (->) appended to the link's name and introduce some badge for the icon. Do you have Windows? Shortcuts on the Win desktop are composed from the icon and small arrow badge in the bottom-left corner.
I have Linux, but know the thing in Windows ;-) I'm going to talk with Bruce today and ask for the icon.
I don't think I fully understand this request. What it looks like is that the (->) indicates that the file system actually represents an alias. Is this true? Is it exactly an alias, or is it slightly different? Is the idea that this is a badge? or a modified icon for FileSystems? Is it possible for any file or directory to be an alias, or only FileSystems? What about class file level? Also, finally, do you think this will change when new Projects becomes active? I understand the idea of FileSystems will change. When Projects is implemented, will that change this icon? Whew! That's it. Lot's of questions, but the summary entry is pretty short.
1. symbol (->) marks links (aliases), you can create such link for almost every object in the IDE, just copy and paste/create link it 2. thus, single class files can have aliases, as well as folders and filesystems 3. concept of links (aliases, aka DataShadows) is general without direct connection to the projects (you can create links even if the projects module is uninstalled) and it shouldn't change with 4.0 projects 4. the node of link behaves the same way as the node of object which link points to, it has the same icon, badges, properties and usually the name, all the actions performed on the link node are delegated to the linked object, all the changes made on the linked object and visible on its node are propagated to the link's node 5. projects are heavily using concept of links and if the project view is supposed to be the main view which user will use in the future, we try to find better representation of the link than we actaully have (->) This is the motivation we have, hopefully it helps to understand this request.
Created attachment 3704 [details] examples of possible solutions
Hi all, Attached are some possible solutions to the alias/data shadow problem. Inherent problem here is that the Data Shadow is/can be ubiquitous. since it could appear anywhere and everywhere, there is a great possibility that it will cover up important icon badges if it is located in any of the existing badge areas on the icon. Therefore, all of the solutions do not cover any of the existing badge areas. Several involve an icon in the title area, in the same location as the current DataShadow. This is, I think, the most elegant solution. The Mac indicates Aliases by simply making the text italic. I think that is a good solution, too, and one of the samples has just italic text to show that. Other solutions that are possible are the link (chain) image around different parts of the icon, and in the title. However, I believe this is an important enough issue to go on to NBUI. It's an important issue that's hidden here in Issuezilla. If no one else wants to post it, I will. This change needs to be telegraphed ahead, and even if no one disagrees with it, I think it's courteous to let them know it's coming. best, b.
Thanks Bruce, it definitely needs to be dicussed on @nbui, please bring it there. I have some comments to proposed icons, but will wait for @nbui ...
Tech notes: 1. Adding an icon to the end of a node name would require an API change (unless HTML were used, see #2) so this should be avoided if possible. 2. Italicizing a node name is technically possible by writing it as HTML in Swing. However: 2a. There may be a performance loss when displaying the node. Probably insignificant for one or two links, but if there are dozens of them visible in a project this could be a problem. 2b. Currently in Swing, node labels rendered in HTML ignore the global UI defaults for font. Since NB sets a nondefault font size for tree node labels, a different font would be used in the tree view for italicized names, which would look rather ugly (I've tried in the past setting color this way; it is no good). I filed a JDK bug about it; perhaps it is fixed in 1.4, I am not sure. 2c. Perhaps an optimization (hack) would be possible in Explorer code for the specific case of a node named "<html><i>X</i>" where "X" is the actual name--pull out "X" (unescaping HTML char refs) and display as a plain text label after setting the font style to render in. I am not sure if this is feasible. This would probably solve 2a. and 2b. above. 3. Overlaying a link icon on top of the regular icon should work (assuming it is a transparent GIF), so long as the normal icon is not obscured beyond recognition. UI call. Is there no predefined place in the icon badging scheme for things like a link badge?
And what about to create badge (arrow similar to an icon on the end of a node in an example) instead of the chain in other examples? I agree with moving to nbui@, we can confine to changes that we are able to implement to 3.3.1 only. Thanks.
Set target milestone to TBD
I am not working on this anymore, reassigning to default owner.
Assigning to Tim
Will probably never bother to fix this. DataShadow's are no longer really used in the UI.
Wontfix, that is what I think as well.