Hi Looking at the way pivot starts applications up (desktop applications in particular, not web applications), I have some comments
(1) Not being able to have my own main method is not great. In general, IDE's don't know about Pivot special way of starting applications. This approach is probably fine for applets, which need special handling anyway, but for desktop applications it is really annoying. Also, I frequently need to exercise quite fine control over the order of starting stuff up. For example, one of my apps runs in console or UI mode, depending on the availability of a windowing system, and it has to be quite careful not to touch anything that could cause AWT classes to get loaded, before it knows for sure what it is going to do. (2) Similarly, having the format of my command-line arguments predefined for me is also not ideal. I frequently have to be compatible with other argument passing conventions that may not match the one Pivot uses. (3) ApplicationContext - setInterval, clearInterval, setTimeout, clearTimeout are not great names. addIntervalTask(), removeIntervalTask(), addTimeoutTask(), removeTimeoutTask() would be much better. (4) DesktopApplicationContext has lots of static stuff. This is going to cause problems with those occasional desktop applications that need to construct more than one top-level window. >From looking at the code, I can't even see any compelling reason why this stuff needs to be static. Regards, Noel Grandin
