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
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
that's it for this week (my wife doesn't let me work on the weekend ^^) please give me your feedback (or you can even check out the mui-migration branch in the website repo) because this time would be good to incorporate your wishes
not sure why the icons don't appear btw
Mitch VanDuyn
@catmando
@peterlamber - wow that looks really nice!
can't wait to see it live
Mitch VanDuyn
@catmando
@/all just put this comment in ycombinator... please add your likes so it sits near the top!
Mitch VanDuyn
@catmando
search for mvanduyn to find my comment
upvote is the tiny triangle on the left of the comment header
I think replies also increase the points as well.
@/all also please make sure to "start" the github if you have not done so already : https://github.com/hyperstack-org/hyperstack
Adrian Madrid
@aemadrid
are we close to having an udpated https://www.npmjs.com/package/hyperstack-client ?
I’d like to try writing a simple todo tutorial with just FE HS
Adrian Madrid
@aemadrid
@peterlamber looks great
the top menu items kinda dissappear on the darker menu though
Barrie Hadfield
@barriehadfield
@aemadrid I will setup the call for next week; there is quite a bit to think about here, or perhaps I am overthinking it!
@peterlamber fantastic work! Cant wait to see the final design, I know right now you are more focused on the mechanics of moving to Material UI from Semantic UI
Mitch VanDuyn
@catmando
@/all new question on Stack Overflow... I spot the problem, but it would be great if somebody else wants to answer (hint just a little typo in the create_new_todo_item method)
Mohamed Ziata
@WaKeMaTTa

Hi there!
I have a question. Why do you use this ugly syntax:

class HelloWorld < HyperComponent
  render(DIV) do
    # try changing 'world' to your own name
    H1 { 'Hello world' }
    P(class: 'green-text') { "Let's gets started!" }
  end
end

instead of:

class HelloWorld < HyperComponent
  render(div) do
    # try changing 'world' to your own name
    h1 { 'Hello world' }
    p(class: 'green-text') { "Let's gets started!" }
  end
end
Mitch VanDuyn
@catmando
@WaKeMaTTa because everything in Ruby is a method call, its nice to be able to quickly see the difference between builtin html/svg tags, application defined components, and other method calls.
actually you example sort of shows the point. In the top example DIV/H1/P are all colored blue so they standout.
But of course the nice thing about Ruby (and Hyperstack) is we are not too opioniated. If you really want to change it, its not too hard. Actually I think there is a module you can include in your application Hyperstack Class that changes it :-)
But one of things a lot of us hyperstackers really dislike about the JSX world is that when you read code there are very few syntactic hints to help make the code quickly understandable. Everything is a function call, and a bunch of curly brackets.
All that said, its a good question you raise!
Mohamed Ziata
@WaKeMaTTa
I see, but as a ruby developer when I see UPCASE words I know that are CONSTANTS and it feels strange, very strange because CONSTANTS they are made to be always the same. But in Hyperstack it has a method. If the only things that maters here is the color to see quickly what is what, you can install a plugin in your editor to recognize the framework/language you use and change the color in that context.
Mitch VanDuyn
@catmando
yeah but I don't think most editors right now would be smart enough to tell the difference. But you are correct it is a bit of a deviation from ruby syntax.
If it makes you feel better in fact each component (whether its a builtin tag, or an application defined component) is in fact a class (i.e. constant), and saying MyComponent(...) is shorthand for MyComponent.insert(...)
Mohamed Ziata
@WaKeMaTTa

And the second question I have is why you are passing a DIV to render?

class HelloWorld < HyperComponent
  render(DIV) do
    # try changing 'world' to your own name
    H1 { 'Hello world' }
    P(class: 'green-text') { "Let's gets started!" }
  end
end

maybe it would be better:

class HelloWorld < HyperComponent
  render do
    div do
      # try changing 'world' to your own name
      h1 { 'Hello world' }
      p(class: 'green-text') { "Let's gets started!" }
    end
  end
end
Mitch VanDuyn
@catmando
its funny we wanted to be able to say MyComponent[...] which is very normal Ruby, buttttt guess what there is a known bug in ruby where you can't pass a block to the [] method! So we had to drop that idea :-(
You can say the latter