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.
[ BUILD # : 20051101_1 ] [ JDK VERSION : 1.5.0_04 ] Consider making it possible to rearrange the layout of the text and image components of a SplasScreen. I think that it would be neat to be able to place the Image close to the top of the screen, and then put some text below it. It would be nice of this could all be done by dragging the resources around in the Screen Designer.
Yes, it would be nice to have such functionality. It will require a lot of work (on both the designer and the component itself). One problem I can see in the solution is the fact the screen designer is not 100% pecent WYSIWIG tool for the actual screen to be visualized on a real device. Thus even though I have sizes of screen available for the Canvas, and I know size of the image, I don't know the size of the text being displayed (on the real device), so a screen looking good in the designer (and even some devices) might look completely differently and bad on other devices. One of the reasonable solution for implementing a workaround for this problem might be to create a contraint based arrangement -> the image could be placed in an arbitrary position on the canvas and the text could be placed above/below , perhaps with a definable space between the image and the text. What do you think? Any other suggestions for this issue?
I think that your suggestion above is quite good. That would certainly make it easier to arrange both text and image elements on the same SplashScreen. I guess there's not really much to be done about the font issue, since the IDE will never be able to know exactly what fonts are availbale for every device. This will probably have to be left for the devloper to test on the physical devices, if / when this is added to the component.
moving to mobility component
Designer 1 has been removed. Therefore reassigning to Designer 2 module. Anyway very likely this enhancement will be resolved in the future.
Very likely it will not be implemented in NB 6.0.