Re: [orion-dev] Electron selfhosting questions...

[Remy Suen <remy.suen@xxxxxxxxx>]

Hi again, Silenio.

On Sat, Nov 5, 2016 at 1:54 AM, Silenio Quarti
<Silenio_Quarti@xxxxxxxxxx> wrote:
> The electron browser is caching the client code. The dev flag was supposed
> to work around that. I am not sure why it is no longer taking effect. I will
> investigate it.

I did some investigating today and have just posted my findings on the
bug below. But again, since I'm new to web technologies I may be doing
something wrong but that is what I am seeing.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=507097

Regards,
Remy

On Sat, Nov 5, 2016 at 1:54 AM, Silenio Quarti
<Silenio_Quarti@xxxxxxxxxx> wrote:
> Hi Remy, long time!!!
>
> The electron browser is caching the client code. The dev flag was supposed
> to work around that. I am not sure why it is no longer taking effect. I will
> investigate it. In the mean time, you can open the dev tools in the electron
> app, disable caching and refresh the page.
>
> We are working on getting the binaries available. We might get something out
> by the end of the month.
>
> The version of electron matters because of nodegit since it contains a
> native library.  Nodegit library is built specially depending whether you
> are planing to run nodejs or electron.  This probably explains why nodegit
> is not working for you.  You need an .npmrc file with the following content
> in the same directory of package.json before running npm install.
>
> silenios-mbp:orionode squarti$ cat .npmrc
> runtime = electron
> target = 1.2.7
> target_arch = x64
> dist_url = https://atom.io/download/atom-shell
>
>
> Silenio
>
>
> ----- Original message -----
> From: Remy Suen <remy.suen@xxxxxxxxx>
> Sent by: orion-dev-bounces@xxxxxxxxxxx
> To: orion-dev@xxxxxxxxxxx
> Cc:
> Subject: [orion-dev] Electron selfhosting questions...
> Date: Fri, Nov 4, 2016 7:56 AM
>
> Hi everyone,
>
> I've been playing with the Electron app yesterday and today. For
> reference, I used OrionHub only very briefly about a year ago for some
> very, very small JavaScript projects. Thus, my experience with Orion
> is actually extremely limited.
>
> With that in mind, getting Electron to open wasn't all too difficult.
> I installed electron via npm and then proceeded to run Orion directly
> from the command line via a clone from GitHub.
>
>> electron server.js
>
> It's fine save for the fact that I still haven't gotten nodegit to
> work but that's not why I'm sending this email.
>
> Now, when I make changes to the Electron code (such as to server.js or
> main.js), my changes are reflected when I shutdown Electron and boot
> it up again. However, when I make changes to stuff in the bundles/
> folder, I am not seeing the changes when I restart Electron. I thought
> using the -dev argument would help but it didn't do anything.
>
> 1. What am I doing wrong? After I make modifications to the contents
> of the bundles/ folder, what do I need to do before restarting
> Electron again from the command line?
>
> 2. Where do I download prebuilt Electron Orion binaries (assuming
> those exist)? Though honestly, I kind of like what I've got going
> right now where I'm running my Electron instance using the code I'm
> developing on.
>
> 3. On the topic of dogfooding though, I would like to know what
> version of Electron is the Orion team targeting for 13.0? I see 1.2.7
> mentioned in the modules/orionode/package.json but my Electron from
> npm is 1.4.5. How much should I care about this discrepancy?
>
> Thanks in advance.
>
> Regards,
> Remy
> _______________________________________________
> orion-dev mailing list
> orion-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/orion-dev
>
>
>
>
>
> _______________________________________________
> orion-dev mailing list
> orion-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/orion-dev