Thanks for the responses so far!
Am 18/05/15 um 13:51 schrieb Matthias Bohnstedt:
> Hi Basti,
> thanks for the detailed explanation about possible js build
> solutions. This is tough to answer right away. I personally would go
> with solution #2, since it's the most efficient workflow in my
Am 18.05.2015 um 13:51 schrieb Matthias Bohnstedt:
> separation of UI- and NoneUI developers with different workflows. I
> don't think we want that, or even push a separation like this.
>
@Franz: How often do people/students do changes to Saros that have
absolutely no UI effect? (I am lacking an
Hi Basti,
thanks for the detailed explanation about possible js build solutions. This
is tough to answer right away. I personally would go with solution #2,
since it's the most efficient workflow in my humble opinion. Every other
solution you described sounds like it would lead to a diffuse separa
Hi all,
as I already mentioned in my last mail [1], one of the main aspects of
the Saros HTML/JS GUI is "to establish a solid groundwork to build,
maintain, extend and test the Saros HTML GUI". Therefore, some tools for
automation are inevitable, for example to ease development and
maintenance via
