91
edits
m (→Priority 3) |
|||
Line 47: | Line 47: | ||
#controls for selecting dates and times. Again see WebForms 2.0 for how we should do this. | #controls for selecting dates and times. Again see WebForms 2.0 for how we should do this. | ||
#panels that can be docked on the sides on the window or in some form of container. By clicking on some button, they become floating. This would be useful for floating palettes. | #panels that can be docked on the sides on the window or in some form of container. By clicking on some button, they become floating. This would be useful for floating palettes. | ||
#ability to capture a window or parts of a window into an image. This is useful for creating thumbnails. | #ability to capture a window or parts of a window into an image. This is useful for creating thumbnails. (ChrisThomas) Is roc's drawWindow the solution to this? | ||
#need to get the ActiveX control to work well with XUL, for instance, allowing it to recognize components and display new dialogs. (NeilRashbook) Java with XUL too. (AxelHecht) Lots of the layout points look very similar and ask for some kind of non-block non-inline non-xul-box layout scheme, right? | #need to get the ActiveX control to work well with XUL, for instance, allowing it to recognize components and display new dialogs. (NeilRashbook) Java with XUL too. (AxelHecht) Lots of the layout points look very similar and ask for some kind of non-block non-inline non-xul-box layout scheme, right? | ||
#ensure that scrolling APIs for getting and changing the scroll position in elements are available and usable in remote content. Also useful would be to have a scrollToPosition type function for textboxes. | #ensure that scrolling APIs for getting and changing the scroll position in elements are available and usable in remote content. Also useful would be to have a scrollToPosition type function for textboxes. |
edits