#27 Reloading application page breaks Helios commits

已關閉
nero8 年之前創建 · 0 條評論

Originally at 2014-09-15T22:41:34Z by Pat Maddox closed at 2014-12-06T15:25:22Z

From a similar issue on amber - which was requested that I report it here instead.

It appears that reloading the application causes the IDE's commit process to break.

Here are the steps I've taken, I'm curious to see if anyone else can replicate it:

  1. Create a new amber project w/ amber init
  2. Load localhost:4000 in the browser
  3. Click 'Helios IDE' to launch the IDE
  4. Add a method to project class. Save & commit (works)
  5. Reload localhost:4000 in the browser. Keep the IDE window open, no refresh
  6. Add a method, save. Commit fails w/ the message above
  7. If I close the IDE and launch it again, it works.

So it appears as though in order to test a change in the browser, I need to reload EVERYTHING - reload the app, close the IDE and launch it again. Is that what people are doing? That's a pretty bad workflow in my opinion - why do I need to completely close my development environment whenever I want to run the code I just wrote? It makes me wonder if this happens for everyone… I would guess not, because I can't imagine so many people being okay with that workflow.

I'm happy to provide more information as needed. For now I'm happy with the legacy IDE - it's not flashy, but at least I don't lose code / context every time I want to make a change.

Originally at 2014-09-15T22:41:34Z by Pat Maddox closed at 2014-12-06T15:25:22Z From [a similar issue on amber](https://github.com/amber-smalltalk/amber/issues/1076) - which was requested that I report it here instead. It appears that reloading the application causes the IDE's commit process to break. Here are the steps I've taken, I'm curious to see if anyone else can replicate it: 1. Create a new amber project w/ amber init 2. Load localhost:4000 in the browser 3. Click 'Helios IDE' to launch the IDE 4. Add a method to project class. Save & commit (works) 5. Reload localhost:4000 in the browser. Keep the IDE window open, no refresh 6. Add a method, save. Commit fails w/ the message above 7. If I close the IDE and launch it again, it works. So it appears as though in order to test a change in the browser, I need to reload EVERYTHING - reload the app, close the IDE and launch it again. Is that what people are doing? That's a pretty bad workflow in my opinion - why do I need to completely close my development environment whenever I want to run the code I just wrote? It makes me wonder if this happens for everyone… I would guess not, because I can't imagine so many people being okay with that workflow. I'm happy to provide more information as needed. For now I'm happy with the legacy IDE - it's not flashy, but at least I don't lose code / context every time I want to make a change.
nero7 年之前 關閉
登入 才能加入這對話。
未選擇標籤
未選擇里程碑
未指派成員
1 參與者
正在加載...
取消
保存
尚未有任何內容