Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 04 2018 12:19

    catmando on noreset

    initial commit refactoring now (compare)

  • Oct 01 2018 13:19

    barriehadfield on edge

    Hyperloop point to master for JS (compare)

  • Oct 01 2018 13:08

    barriehadfield on edge

    Hyperloop 0.99.1 (compare)

  • Sep 08 2018 00:40

    catmando on edge

    got tests passing again Gemfiles point to released gems (compare)

  • Sep 07 2018 23:03
    catmando closed #20
  • Sep 07 2018 23:03
    catmando closed #19
  • Sep 07 2018 23:03

    catmando on edge

    closes #19 closes #20 Merge branch 'edge' of github.c… resolved gemspec merge conflict (compare)

  • Sep 07 2018 22:49
    catmando opened #20
  • Sep 02 2018 08:34

    barriehadfield on edge

    Update README.md (compare)

  • Sep 02 2018 08:33

    barriehadfield on edge

    Update README.md (compare)

  • Aug 31 2018 09:31
    mpantel commented #12
  • Aug 28 2018 07:15
    mpantel commented #12
  • Aug 22 2018 08:00
    mpantel commented #12
  • Aug 19 2018 21:12

    johansmitsnl on edge

    Move the libv8 to running depen… Remove webdriver Remove empty helper (compare)

  • Aug 19 2018 21:06

    johansmitsnl on edge

    (compare)

  • Aug 19 2018 21:02

    johansmitsnl on edge

    Download and install the chrome… (compare)

  • Aug 19 2018 20:51

    johansmitsnl on edge

    Remove the find for the webdriv… (compare)

  • Aug 19 2018 20:51

    johansmitsnl on edge

    Include the database schema (compare)

  • Aug 19 2018 20:46

    johansmitsnl on edge

    Use find to locate the webdriver Don't set the path directly (compare)

  • Aug 19 2018 20:42

    johansmitsnl on edge

    Update the gemfile.lock (compare)

Mitch VanDuyn
@catmando
part IX -> learn to be a pilot like catmando
Barrie Hadfield
@barriehadfield
Mitch VanDuyn
@catmando
part X -> buy a yacht
part XI -> find true love
wow all this because you use hyperstack!
Barrie Hadfield
@barriehadfield
:-)
Mitch VanDuyn
@catmando
you can start on part IV now (code will not change) the repo assumes there will be a branch for each part (i.e part-4) so you can build it out now, as the test code wont change.
Barrie Hadfield
@barriehadfield
am in Kiev today
Mitch VanDuyn
@catmando
and perhaps as the cleaning up the UI won't actually change the tests we can flip the order
cool
I am figuring a post a week is about right
Barrie Hadfield
@barriehadfield
I have been thinking quite a bit about Devise and client-side (secure) routing
was goign to update the Devise tutorial I wrote last year
Paul Richardson
@iamprich
@ScottDuke Hey! I dockerized a decent sized Hyperstack app a few weeks ago. It was similar to dockerizing a standard Rails app from what I remember.
Barrie Hadfield
@barriehadfield

@catmando re Devise, what I have been wondering about is if there is a way to keep the Admin JS completely separate from the User JS app. In the past I have done:

Rails.application.routes.draw do
    authenticate :member do
      mount Hyperstack::Engine => '/hyperstack'
      get '/(*other)', to: 'hyperstack#main_frame'
    end
  end

So, a not-logged in user does not even get to the Hyperstack API or the JS app (they stay in HTML pages with normal Rails routes). I have been thinking that depending on the user (admin/normal) they get a different main component which has its own client side routing - just thinking...

So I am thinking that the whole Admin section can be in one JS package and the rest of the app in another and rails view templates will only bring in the admin section if the user is Admin
This would get past the problem of Admin type code being a part of the client code.
Mitch VanDuyn
@catmando
that is a couple of different ideas.
Barrie Hadfield
@barriehadfield
yes, I am thinking aloud
Mitch VanDuyn
@catmando
having two different SPAs for user vs admin is perfectly reasonable
not 100% sure but you would just do something like this:
get '/admin/(*other)', to: 'hyperstack#admin'
get '/(*other)', to: 'hyperstack#app'
(cause rails runs the first route it hits)
catprint actually has a bunch of smaller SPAs
the possible problem with a static login page, is just user experience.
Barrie Hadfield
@barriehadfield
I like the idea of the public parts of a site being in simple HTML so they load fast, get indexed, etc. The SPA(s) then hide behind the authentication (ie mount Hyperstack::Engine => '/hyperstack’ never even happens for a public user)
the possible problem with a static login page, is just user experience.
Same style sheet and bits of JS niceness will overcome that
Mitch VanDuyn
@catmando
I know the easiest way to get into devise (for example) is take that route (no pun intended) but it certainly can be done to get things wired up to use hyperstack ControllerOps (or even tweak a rails controller to deliver some JS) in the long run its going to give a better experience.
Same style sheet and bits of JS niceness will overcome that
of course, but you still have this reload going on.
which is unnecessary
from hyperstacks standpoint all that happens when you login, is that new channels are created.
Of course if you are adapting an existing site then keep you current login strategy, at least until you have more important pieces working.
IMHO of course
we lived with a pretty gross strategy for years at Catprint
Barrie Hadfield
@barriehadfield
:thumbsup: will think on it
Forrest Chang
@fkchang
@catmando call scheduling app could be a good example app number of angles
  • Non trivial app w/an actual use - that's always the problem with example apps, their either too simple to give a feel of the power, or too much to digest
  • dogfooding gives the best apps - since we should use it for our calls in the future, we'll be more investing in making it good, and refining over time
  • We should document it via blog and video as we're building. Blogs are good for the "follow the book part", video should highlight cool dev things like hot reloading in a situation where the data setup is significant, so a hot reload doesn't require you to re setup
  • and of course, an open source repo, coz working code is always the best documentation
  • who knows maybe if successful, it could become a real product
@barriehadfield I think a call to action as well as a blog posts section is good, we'll headline the latest hot post, and reference all the other collected posts
@catmando re: the Ruby is fast enough post, I think that's good reason to keep going with Rails, I presently think that's the best bet for adoption - a "batteries included on front and back end" solution which would lean on everything that Rails brings to the table
Mitch VanDuyn
@catmando
@fkchang between you and me, I agree, but if its a minority opinion I'm not going to fight it. I do think the cost of changing to a Rack app is pretty low, and it would mean that the request-broadcast cycle would be handled at a lower level, and therefore more efficiently. I think this is the main reason you might want to use sinatra anyway (i.e. you don't need a complex router, controllers, etc clogging things up.) So if you had rails, but all the hyperstack requests are handled by the rack layer, you get the best of both worlds.
I put some notes at the end of the readme here along these lines: https://github.com/hyperstack-org/todo-compare#hey-why-rails
Forrest Chang
@fkchang
@catmando best of both worlds is good for ruby backends, making it viable for crystal a higher hanging fruit
I like the readme addition, I think that kind of underrates what Rails gives though as someone who has often rewritten parts of Rails in non Rails apps
Mitch VanDuyn
@catmando
@barriehadfield @peterlamber could we add a link (or badge) to stack-overflow on the header (git, chat, stack-overflow) the link is https://stackoverflow.com/questions/ask?tags=hyperstack
Barrie Hadfield
@barriehadfield
Sure - excellent idea. I think this is the right combo of tags as we want it exposed to as many commuinities as possible: https://stackoverflow.com/questions/ask?tags=hyperstack+ruby-on-rails+reactjs+ruby+isomorphic
Barrie Hadfield
@barriehadfield
@catmando I have added that to the header and also the footer https://hyperstack.org/ as well as updating the tutorial pages with a blogs and questions sections.
@/all please remember that writing a tutorial or blog (even while you are learning) is a fantastic way of perfecting your knowledge and helping others as they progress. We would love to include your tutorials and blogs - no matter how big or small. All you need to do is issue a PR on the Community page https://hyperstack.org/edge/docs/tutorials/community (which you can do from the website) to have your links included.
Tim Blokdijk
@Tim-Blokdijk
I can confirm this, I followed Mitch's ToDo tutorial and fixed and improved it at the same time.
peterlamber
@peterlamber
Screenshot from 2019-03-29 23-37-00.png