Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

focus discuss; alpha-2.0+0010 #200

Closed
ruby0x1 opened this issue Dec 5, 2014 · 2 comments
Closed

focus discuss; alpha-2.0+0010 #200

ruby0x1 opened this issue Dec 5, 2014 · 2 comments

Comments

@ruby0x1
Copy link
Member

ruby0x1 commented Dec 5, 2014

luxe alpha-2.0 is about:

Assets/Resources/Windowing

Please read these posts before commenting below :


See the issues on the milestone.

Remember: discussion here is about assets, resources and windowing. If you have questions, bugs, suggestions, ideas about those specifically this is the place to bring it up.

#184

@ruby0x1 ruby0x1 added this to the alpha-2.0 milestone Dec 5, 2014
@anissen
Copy link
Contributor

anissen commented Dec 5, 2014

I would love to see some live reloading improvements for the web target. Specifically:

  • Building luxe to the web platform should refresh the existing luxe tab (if any) rather than opening a new
  • Live reloading of changed resources on web platform (it appears to be desktop only according to assets; expose underlying reload api #189)
  • Being able to reload the page (that is, I would prefer to have the server keep running as default without having to pass additional arguments -- it's a matter of opinion but this is a discussion after all)

For inspiration, see Flambé. Flambé also has a node.js-based build-system and has all the above features on the web target. I believe it uses catapult for handling all the reloading functionality.

@ruby0x1 ruby0x1 self-assigned this Jan 12, 2015
@ruby0x1 ruby0x1 changed the title focus discuss; alpha-2.0 focus discuss; alpha-2.0+0010 Jan 24, 2015
@ruby0x1
Copy link
Member Author

ruby0x1 commented Jan 26, 2015

I linked this elsewhere, but I'll add it here for history:

  • auto reload tab is best solved by tools specific to the job right now
  • the live asset reloading isn't desktop specific, it will depend how long it would take to do on web if it makes alpha 2.0, but it will be definitely covered on web at some point
  • This will remain with the timeout by default. errors about port being in use or random ports or ghost servers left dangling by IDE's is not an option. Passing options to the commands from sublime will be added in the near future as well.

Thanks for the catapult link, I will see if it fits what I am after with regards to the reloading, but adding this feature to the flow build pipeline itself may be beneficial in the long run. It's something that requires testing so I will tackle it when it comes up.

Thanks for the replies, excuse my delay (waiting for the alpha sheet :P)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants