This is the home page for ideas concerning an IDE for the creation and deployment of end-user applications in the accelerator field.

  • No labels

5 Comments

  1. Unknown User (chevtsov)

    I would like to start with comments on XML UI. While this concept is generally language/framework-independent, there are some great open-source Java Swing implementations, e.g. swiXML http://www.swixml.org/

    One major disadvantage of adapting XML UI:
    We would need to redesign all available GUI applications as no framework in the community seems to incorporate the XML UI concept.

  2. Greg White

    Excellent idea to base the GUI on a XML UI framework. But I think it is dependent on whether that XML UI framework can be done within the ECLIPSE framework. Also, it wouldn't matter if other places were not using the XML UI concept as long as we developed applictions in it within the Eclipse framework.

    Relatedly, how many real, not demo, applications exist in XAL?

    1. Unknown User (chevtsov)

      About 60.
      Actually, it doesn't sound like too big a deal since we would have to change their GUIs only (providing, of course, SNS guys used proper MVC techniques to separate data processing from presenation (smile)

  3. Unknown User (chevtsov)

    Object-Relational Mapping
    There will be an overview presentation of this concept on July 21st, at 2:00pm in the Red room (part of LCLS week)

  4. Greg White

    Forward Reference to Cost Benefit Analysis for the question of using Eclipse, CSS and XAL:

    In general, my view is that the outcome of this feasibility and cost-benefit analysis, should be a short report that outlines the technologies and the issues. In particular, it should help a reader understand why the question is not "XAL or Eclipse", but rather which technologies may be used for which aspects, and what are the implications of each choice. It should also give some short forward references to a design, such as line or two about which channel access technology would be used, which graphics systems might be used, and so on. And it should outline some of the immediate design questions which will come up, such as the question of configurability, how the user switches between applications and so on. It need only be 2 or 3 pages.