Community
Participate
Working Groups
This bug is used to discuss a potential contribution from Kalle Launiala. See http://dev.eclipse.org/mhonarc/lists/orion-dev/msg00369.html for his email. The email links to the project pages as follows: "The example documentation and video can be found under Documentation at http://abstraction.codeplex.com" I found the mentioned video at: http://www.youtube.com/watch?v=rXuX0sIY3Ls
Hi Kalle, Your email didn't make any sense to me at all, so I invested an additional five minutes to watch your screencast on Youtube. What you have is a trivial subset of EMF and EEF. See: http://www.eclipse.org/modeling/emf/ http://wiki.eclipse.org/EEF You might also be interested in "Naked Objects" - see: http://www.nakedobjects.org/ I see no direct value for Orion in what you have developed. Good luck!
This can probably be closed right away, but feel free to add comments on this bug for further questions and comments.
Please allow me to provide more detail; as in this technology the devil is in the details. It is much more than modeling per-se, although there are a lot of similarities - because it takes strict control of the software architecture. No existing modeling technology provides absolute simplification, because they cannot provide flexible enough detailed control for the actual software logic. This technology however does not sacrifice any details or programmer control, even when the software is initially made of trivialization. If you watched the screencast, what you effectively saw was a full-scale enterprise-grade architecture software built from the minimal absolute information. Now that's nothing new in DSL/modeling scheme of itself. However the trick is, that the trivialization requires no more than 35 lines of functional code - consisting solely of XML transformation. The trivialization layer is built on top of existing full-software-stack: http://abstraction.codeplex.com/wikipage?title=Example%20for%20Mobile%20End%20User%20Making%20His%20or%20Her%20Own%20Application&referringTitle=Documentation There are several key-differentiators that allow this to happen and are also listed in the documentation. This effectively means, that anyone who can "write text" can make full-scale software. Of course functionality still requires normal code written, but architectural ceremony code for client-server and alike interaction can be constrained to minimal. However because the stack can rely on each individual component, the Orion could for example start with the absolute trivialization and allow more detailed control by providing the lower level abstractions as well. For each Orion developer to his/her own skill level, all producing perfect-quality software as the end result.
