Re: [science-iwg] web Re: e3 or e4

[<Matt.Gerring@xxxxxxxxxxxxx>]

Hello,

So I think my strategy should be to continue to base things on e3 for some API's and e4 for others, allowing but not forcing e4. If faced later by a rewrite to web applications, I have the option to float the idea of migrating to Scout with complete e4 migration(medium task) and removal of static data(medium task). This could be good and potentially cheaper than making a new front end for data acquisition. Thanks for the ideas ;)

Regards,

Matt

-----Original Message-----
From: science-iwg-bounces@xxxxxxxxxxx [mailto:science-iwg-bounces@xxxxxxxxxxx] On Behalf Of Kasemir, Kay
Sent: 12 September 2016 14:17
To: science-iwg@xxxxxxxxxxx
Subject: Re: [science-iwg] web Re: e3 or e4

Hi:

> Date: Mon, 12 Sep 2016 09:10:06 +0000
> From: <Matt.Gerring@xxxxxxxxxxxxx>
> ..I made a RAP version of DAWN a few years back and the plotting in 
> draw2d mostly worked, as did many of the tools but we hit the static 
> data problem
Many key pieces of CS-Studio alternatively compile and run with RAP instead of plain SWT.
That’s very convenient from the implementation point of view. Single-source RCP code magically appears on the web.
But it has not been practical for our operational setups. Our displays work fine with RCP, where a GC.draw* operation directly draws on the screen. With RAP, that turns into JavaScript polling for updates, server then sending JSON with drawing operations like [ "call", "gc55", "draw", { "operations": [ [ "beginPath" ], [ "rect", 0.0, 0.0, 1470.0, 441.0 ], [ "fill" ], [ "strokeStyle", [ 0, 0, 0, 255 ] ], [ "font", [ [ “Verdana” ..

So basically a lot of text is sent over the network, to be interpreted by Javascript on the client side.
The end result is slow, it can’t compete with a smarter setup where you only send the data, like “xyz=3.14” and the Javascript code then knows how to update some section of the HTML to reflect that value.
That can be done, but then you’re fully into regular web development, doing a lot of custom Javascript, which is what I’d like to avoid because we’re not Amazon/Google.

> From: Jay Jay Billings
> Sent: 11 September 2016 01:38
> ..I'm strongly leaning towards Eclipse Scout…
If you learn more about that, please consider keeping the mailing list updated, maybe do a google hangout with a demo of what works well, and what doesn’t.

Thanks,
Kay
_______________________________________________
science-iwg mailing list
science-iwg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/science-iwg

-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom