3
edits
(remove vandalism) |
No edit summary |
||
(One intermediate revision by one other user not shown) | |||
Line 3: | Line 3: | ||
to solve. | to solve. | ||
== Comments NeilDeakin == | |||
=== Chrome === | |||
==== The term ==== | |||
People have difficult time understanding chrome. For instance, it is common to | People have difficult time understanding chrome. For instance, it is common to | ||
assume that files placed in the chrome directory have added privileges. Or, | assume that files placed in the chrome directory have added privileges. Or, | ||
Line 22: | Line 22: | ||
deprecated. | deprecated. | ||
==== Chrome registration ==== | |||
In addition, there's the fact that there is no way of knowing whether your | In addition, there's the fact that there is no way of knowing whether your | ||
newly created chrome application is set up right and you haven't messed up | newly created chrome application is set up right and you haven't messed up | ||
Line 29: | Line 30: | ||
thing developers need to do. If this is too hard, they become discouraged. | thing developers need to do. If this is too hard, they become discouraged. | ||
: This has become much better after bsmedberg's changes to chrome registration, and for example getting started with writing extensions should be quite easy because there are quick-start guides and downloads: [http://kb.mozillazine.org/Getting_started_with_extension_development#Resources]. We should provide such stubs for xulrunner apps too. --[[User:Asqueella|Nickolay]] 11:09, 11 Feb 2006 (PST) | |||
=== Trees === | |||
Some common issues about trees: | Some common issues about trees: | ||
Line 52: | Line 55: | ||
creating a more specialized widget for this. | creating a more specialized widget for this. | ||
=== List Boxes === | |||
Some Common Issues about List Boxes: | |||
* List box headers should have the same functionality as Tree (Column controls, sortability). | |||
* After a list box is loaded, users should have the ability to sort any column (asc/desc) and hide columns. This would be similar to the functionality of Trees. | |||
* Code wise, attributes should be settable to allow these types of functionality. This should be generic - regardless of the datasource (i.e. RDF, Javascript, XML etc...) | |||
=== Templates === | |||
[[XUL:Xul Templates]] are difficult to understand, but I think everyone knows that | [[XUL:Xul Templates]] are difficult to understand, but I think everyone knows that | ||
Line 65: | Line 75: | ||
How Templates Work guide I've been meaning to write for a while now. | How Templates Work guide I've been meaning to write for a while now. | ||
: -> http://developer.mozilla.org/en/docs/XUL:Template_Guide | |||
=== Element Interfaces === | |||
One issue I had when creating the element reference was that a number of | One issue I had when creating the element reference was that a number of |
edits