|
|
| Line 1: |
Line 1: |
| A list of possible enhancements for XUL 2.0 or APIs that would be used by XUL applications. Some are based on features found in other UI toolkits, and some are based on questions people have had on forums, newsgroups and bug reports. The items are prioritized in the order I think they should be done. I haven't yet explained why I think they should be in this order, but in general, the priority is based on the amount of requests for a feature, how much of a problem development would be if the feature didn't exist, as well as the complexity of implementing a feature. | | A list of possible enhancements for XUL 2.0 or APIs that would be used by XUL applications. Some are based on features found in other UI toolkits, and some are based on questions people have had on forums, newsgroups and bug reports. The items are prioritized in the order I think they should be done. I haven't yet explained why I think they should be in this order, but in general, the priority is based on the amount of requests for a feature, how much of a problem development would be if the feature didn't exist, as well as the complexity of implementing a feature. |
|
| |
|
| Note that I don't list issues with remote XUL. Current issues with remote XUL are listed on the RemovePrivilege page. It is assumed that all of the items below should work in remote content as well, unless there is some valid security reason for them not to. | | Note that I don't list issues with remote XUL. Current issues with remote XUL are listed on [[XUL:Remove_Privilege|another page]]. It is assumed that all of the items below should work in remote content as well, unless there is some valid security reason for them not to. |
|
| |
|
| '''Priority 1''' | | '''Priority 1''' |
| Line 129: |
Line 129: |
| #get non-rectangular windows working on every platform and not just on some configurations of Linux. Often used for audio players, or Apple Dashboard like applications. | | #get non-rectangular windows working on every platform and not just on some configurations of Linux. Often used for audio players, or Apple Dashboard like applications. |
| #custom cursors as in CSS2 might be useful for some applications. (MinhNguyen) This is [https://bugzilla.mozilla.org/show_bug.cgi?id=38447 bug 38447]. | | #custom cursors as in CSS2 might be useful for some applications. (MinhNguyen) This is [https://bugzilla.mozilla.org/show_bug.cgi?id=38447 bug 38447]. |
|
| |
| '''Some comments:'''
| |
|
| |
| *(a specialized form of grid which looks like a spreadsheet view) would be very nice, but it would have to be extensible and customizable. There are many flavors of grid-like objects in fat client applications, from spreadsheets like Excel to database-centric windows like the ones in Access... it's going to be a challenge to provide a grid control that is flexible enough that developers will use it and not resort to "rolling their own". We're prototyping something right now that is horrendously complicated already, and it's not even anywhere close to being functional yet... it would be very nice to have a built-in widget that could at least give us a leg up.
| |
| *spreadsheet view. This is an awesome idea. the spreadsheet got pcs where they are today. XUL is well suited to business applications. a spreadsheet view is an extremely logical step.
| |
| *resizing handles. I can't see it being too hard to implement, but it would be a dream come true. It would make it trivial to develop graphics apps, and a xul ide. a onresize handler would be great too if there isn't one already.
| |
| *making notification popup alerts. Yes! this would be great. Also somewhat attached to this is I'd love the ability to minimise an app to the system tray area (on windows). This functionality would make it a lot more like konfabulator in that you could write small quick apps that can be accessed easily.
| |
| *floating palettes. This would be to bonus of the year! fixed palettes are so < 1995. we're a decade older!
| |
| *make xul work properly in xml is another great one.
| |
| *If I could vote (which might be an interesting concept for the moz dev team to determine what developers want), there's the top 3 from my particular business perspective:
| |
| *spreadsheet-like control (like a StringGrid in Delphi/C++ or a data grid in C#)
| |
| **printing, absolutely!
| |
| **extend the template-thing much, much further, beyond the concept of RDF-controlled content generation. Dynamic, editable forms with plain-XML datasources would be great - maybe a bit like InfoPath. All the basics are there, it can be done!
| |
| **A easy way to do confirmation boxes, and other simple dialog boxes without lots of workarounds due to security restrictions would be _very_ helpful. In my last project using XUL a lot of effort was needed to workaround what would have easily been accomplished in small, simple dialog boxes on a local fat client.
| |
| *Spreadsheet-like grids and more versatile (ie editable) treecells would be very useful.
| |
|
| |
| Toiletduck> A good test of functionality is we need to be able to implement an iTunes clone in XUL. I'm not talking about the backend playing(decoding) of songs but everything else. We especially need a tree where you can double (or single) click in a cell to edit the content. An event should be triggered at _least_ when you hit enter/tab. I want to make a scripting language editor. When i click on the class, I want an attributes editor like visual c/basic. when i click on the value of the attribute I should be able to edit it! at the moment there are no editboxes allowed in treeviews. Neil (www.xulplanet.com) provided a hack but it makes the cursor disappear! This is 1995 functionality. about:config would be so much nicer with this functionality. IMHO it should be in priority 1.
| |