Re: Continuous integration

[raman]

address@hidden (Phillip Lord) writes:
I'd phrase the  requirement slightly differently from what Phillip says
below.

"Functional" is really in the eye of the beholder -- most of the
JS-based browser  environments   lack good APIs that keep the UI
front-end separate from the app-logic back-end.


So asking "does it work in EWW" itself may be a red-herring -- a
well-designed system would let you implement a clean UI from the emacs
end, eeither with or without EWW.

For a good example of such API separation, see Ipython notebooks and how
package ein in Emacs leverages that separation. 
> Chad Brown <address@hidden> writes:
>
>>> On 23Mar, 2017, at 14:29, Toon Claes <address@hidden> wrote:
>>> 
>>> If you aware of tools that won't require the initial review through the
>>> web interface, I really am interested to see how they work.
>>
>> Would someone with a functional setup for such a system (GitLab,
>> etc.) be willing to check and see how functional it is in eww, please?
>> (The only one I have easy access to is github, which is problematic
>> for other reasons).
>
>
> Both of them have online versions either as service or a demo. As far as
> I can tell, neither of them are functional within eww.
>
> Ultimately, if our main criteria for a CI and code review system is
> "does it work with EWW" or "can we have an emacs interface", then I
> think that it's likely we are going to end up with something that is
> poorly functional. Picking a good system and then making Emacs work with
> it seems a better way forward.
>
> Phil
>
>

--