Hi all! As promised my experiences:
I used CYG bash on my Win 10 machine, but It also works with
WindowsPowershell v1.0 after I installed GitHub Desktop -App, without any
further ado. (I hit checkbox that NODE should be added to the Systempath
while I installed it, so I didn’t need to adjust anything here manually).
The scripts didn’t run after upgrading from 8 to 10. I needed to run “npm
install” one time again. After this the CP command and the scripts worked
fine. (It seems that there was a CP node modules installed), I didn’t
encounter any problems after this: build, prebuild, postbuild script worked
fine.
All in all the setup to build the JS didn’t take me more than 40 minutes
(No reading time included):
• Install CYG
• Install GIT Desktop for windows
• Install NODE (4.2.4)
• Run “npm install” from ../html/ in bash (this step took quite a while
and it seems the bash was frozen, but after 5 Minutes it finished)
• “npm run build” in bash
However, I have the same problem Franz described: The HTML GUI view only
shows as a white page, as if no JavaScript is executed. I know that the
page wasn’t white with Windows 8, but became after I updated to Win 10. I
doubt that there was any changes on the JS part of the frontend during
this time. I am certain that we already encounter this problem last
summer, and I think Basti changed a JS command (or something on those
lines) to fix it. As there was a JS command that the IE just isn’t “okay”
with and refuse to execute it.
Nina and me tried to find out why this don’t occur on every Win 10
machines, as it works on her win 10 version.
We thought that one possible cause for this problem might be related to the
different node versions that builds the js bundle. Because Nina was using a
different node version then me, and that was the only visible differences
between my and her settings. But I tried NODE 0.10. and 4.2.4 and in both
cases the page remains white(the script worked in both versions).
Nina said she also had this problem but solved it “on accident”, meaning
she couldn’t recall what she changed to make it work. Maybe she or Basti
can say more about it.
Just for the records: I use Eclipse SDK 3.7.2.
Regarding the Saros/I problem: I just uploaded a new version of the fix.
Everybody feel free to review :) [1]
[1] http://saros-build.imp.fu-berlin.de/gerrit/#/c/2981/
2016-01-24 15:20 GMT+01:00 Matthias Bohnstedt <matthias.bohnst...@gmail.com>
:
> I will do this tomorrow, while I am not sure what Stefan means by saying
> "Just implement it". If I could "just" implement it, I wouldn't provide a
> empty placeholder method on intellIJ side. (His quote is referring to the
> method "getProjects()"). Holger was fine with this solution, until we are
> certain about the shape of our filesystem interfaces, I wouldn't put to
> much effort in this right now.
>
> So if someone could have a look at this patch discussion would be lovely.
> http://saros-build.imp.fu-berlin.de/gerrit/#/c/2981/
>
> 2016-01-24 13:14 GMT+01:00 Zieris, Franz <franz.zie...@fu-berlin.de>:
>
>> Hi there,
>>
>> *** the IntelliJ side ***
>>
>> I wrote:
>> > Starting Saros/I works with the Swing GUI. When I switch to the HTML GUI
>> > "-Dsaros.swtbrowser=true"), Saros/I does not even start. It crashes
>> with the
>> > stacktrace attached below.
>>
>> Christian wrote:
>> > Summary: IntelliJ HTML *mechanism* working in theory but pico container
>> won't start for anyone.
>>
>> Matthias wrote:
>> > regarding the error in IntelliJ: [...], the UI crash is caused by a
>> missing IWorkspaceRoot
>> > implementaion. There is already a fix:
>> http://saros-build.imp.fu-berlin.de/gerrit/#/c/2981/.
>> > I need to include the feedback of Stefan in this, and I am sorry that I
>> have not done it yet.
>>
>> Alright, Matthias. Do you see a realistic chance that you'll get to this
>> in the near future?
>>
>>
>> *** the Eclipse side ***
>>
>> Christian wrote:
>> > Yesterday, I also ran into the 'missing cp command' when trying to
>> execute the npm build script.
>> > After some googling, I think the excepted practice is to use git bash
>> or cygwin under Window
>> > for running npm and not the build-in command line.
>>
>> I already use the Git Bash for everything command-line-ish on a Windows
>> machine.
>> My problem with NodeJS 4.2.4 was that I was not able to execute "npm run
>> build" because 'npm'
>> wouldn't find 'node', although both were accessible through the PATH
>> variable [1].
>> I tried many NodeJS versions, but everything newer than NodeJS 0.10.41
>> resulted in the same
>> error [2].
>> In other words: I *do* have a working environment for calling 'npm
>> install' and 'npm run build',
>> and -- as far as I can tell -- it produces the right outcome:
>>
>> ----
>> ~/saros/de.fu_berlin.inf.dpp.ui.frontend/html $> rm -rf dist && npm run
>> build --silent && ls -lhR dist
>> dist:
>> total 10K
>> drwxr-xr-x 1 Franz 197121 0 Jan 24 13:09 bundle/
>> drwxr-xr-x 1 Franz 197121 0 Jan 24 13:09 css/
>> drwxr-xr-x 1 Franz 197121 0 Jan 24 13:09 fonts/
>> -rw-r--r-- 1 Franz 197121 401 Jan 24 13:09 main-page.html
>> -rw-r--r-- 1 Franz 197121 423 Jan 24 13:09 start-session-wizard.html
>>
>> dist/bundle:
>> total 1,8M
>> -rw-r--r-- 1 Franz 197121 1,8M Jan 24 13:09 bundle.js
>>
>> dist/css:
>> total 220K
>> -rw-r--r-- 1 Franz 197121 3,1K Jan 24 13:09 32px.png
>> -rw-r--r-- 1 Franz 197121 1,9K Jan 24 13:09 40px.png
>> -rw-r--r-- 1 Franz 197121 145K Jan 24 13:09 bootstrap.css
>> -rw-r--r-- 1 Franz 197121 23K Jan 24 13:09 bootstrap-theme.css
>> -rw-r--r-- 1 Franz 197121 30K Jan 24 13:09 jstree.css
>> -rw-r--r-- 1 Franz 197121 2,2K Jan 24 13:09 saros.css
>> -rw-r--r-- 1 Franz 197121 1,7K Jan 24 13:09 throbber.gif
>>
>> dist/fonts:
>> total 220K
>> -rw-r--r-- 1 Franz 197121 20K Jan 24 13:09
>> glyphicons-halflings-regular.eot
>> -rw-r--r-- 1 Franz 197121 107K Jan 24 13:09
>> glyphicons-halflings-regular.svg
>> -rw-r--r-- 1 Franz 197121 45K Jan 24 13:09
>> glyphicons-halflings-regular.ttf
>> -rw-r--r-- 1 Franz 197121 23K Jan 24 13:09
>> glyphicons-halflings-regular.woff
>> -rw-r--r-- 1 Franz 197121 18K Jan 24 13:09
>> glyphicons-halflings-regular.woff2
>> ----
>>
>> I can open the main-page.html in Firefox and Microsoft Edge, and I see
>> the rendered UI.
>> My problem is that is does not show in the Eclipse Saros HTML View --
>> there, the static
>> main-page.html is loaded (I can inspect the source code), but it's not
>> filled with any
>> content [2].
>>
>> Franz
>>
>>
>> [1] http://article.gmane.org/gmane.comp.ide.eclipse.saros.devel/1694
>> [2] http://article.gmane.org/gmane.comp.ide.eclipse.saros.devel/1707
>>
>
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
