[Coquelicot] coquelicot contributions

[Konrad Mohrfeldt]

hi,

On 28.12.2016 12:18, Lunar wrote:
> Konrad Mohrfeldt:
>> ping?
> 
> Really sorry I haven't replied to you earlier. I'm glad you've pinged us
> again, your initial email was lost in travel and too much backlog.
> 

I’ve started to wonder if debian folks like web-developers :P. I’d
understand. Packaging the JavaScript/Node ecosystem must be hell :D.

> I've never been a good web developper, so I'm really happy to see your
> attempt to improve Coquelicot. Mobile support is especially welcome. :)
> 
> I'm not sure what kind of feedback you want on the current redesign.
> It's already quite an improvement! There's probably a few things which I
> would like to discuss, like loosing the byte counters that were
> displayed with the progress bar, but it's not clear to me how ready was
> the proposal.

The only feedback i really needed was if there’s a chance that these
changes would be merged :). I’m happy about suggestions though and the
byte counter probably just slipped through when i made my changes.

> 
> As a Debian developper, my primary deployment target is Debian. So any
> external JavaScript library needs to be packaged in Debian before
> Coquelicot can depend on it.

I’ll try to keep dependencies to a minimum and stick with vanilla
JavaScript whenever I can, but in order to do so we have to make a
decision regarding browser support. I guess we could support all browser
with EcmaScript 5 Support [1], which would include IE9 with only a
single dependency to node-es6-promise (available since stretch). That
would be everything we need to reimplement the current JavaScript code
production-dependency-wise. Are build-dependencies required to be
packaged in Debian as well?

> 
> With that in mind, I would not necessarily be opposed to using
> npm—Coquelicot is already using Bundler—but it should be as
> straightforward as possible to use, develop and deploy. As I don't have
> any real experience with it, I can't really judge how good is it.

Well… it’s everything we have right now :). As I stated before I liked
that the project just worked™ when I cloned the repository. The js build
system would introduce webpack as a build tool. Webpack receives an
entry file, recursively resolves dependencies (import/require
statements) and outputs a single js file that would be added as the only
script tag in the rendered HTML page. It also supports a watch mode, so
we could keep the original "just works™" behaviour if we spin up webpack
when starting the development server.

> 
> Please tell me if you need more help from me to enable you to improve
> Coquelicot! :)
> 

I’d like to keep my hands from the ruby codebase in order to focus on
the other tasks, so if anyone could take care of the webpack watchmode
integration once it’s ready that’d be awesome. apart from that I only
have two remarks/questions:

1. Are you fine with the separate repository where you can
   pull my changes?
2. If you have any comments regarding Debian compatibility just tell me.
   I’m not familiar with most of the packaging guidelines :).

bye

konrad

[1] http://kangax.github.io/compat-table/es5/