On Wednesday, 29 May 2013 at 17:28:52 UTC, Martin Nowak wrote:
On 05/28/2013 11:25 PM, Flamaros wrote:
2) Integrated editor (launch with the user application in a
second Window)
a) Good :
- Preview is the final result with real data
- All application components accessible to the editor
without
complex plugin system (in this way all editors components will
be well
placed in the preview)
- Full real-time edition (can preview menus
transitions,...)
- User can customize the editor
b) Bad :
- Intrusive in the application code
- Force the user to port application on a desktop OS
(Linux, Mac or
Windows), not friendly if he target only embedded devices (can
be
bypassed with a remote system)
- Less stable editor?
I think an integrated editor has a huge benefit because of the
instant feedback.
You could use IPC and have the editor in a separate
application. That is probably more difficult to implement but
it mitigates your negative points.
https://developers.google.com/chrome-developer-tools/docs/remote-debugging
Yes that just what I think about this evening, developing the
editor with an Object reflection trough a network API. If the API
of the protocol is enough good it will certainly possible to
implement something trough USB too.
I think we'll need use more __traits :-).
It will like remote debugging on JVM too.
