Closed mark-hahn closed 10 years ago
For anyone curious I've started a github project (https://github.com/mark-hahn/oolong) called Oolong. It assumes a totally new codebase instead of forking teacup as I originally planned. As I thought it through it morphed into a beast somewhat different from teacup. I hope to keep them compatible in the sense that teacup templates will work unchanged in Oolong. I apologize for referencing a different project in this one.
Sounds awesome @mark-hahn thanks for the heads up! I'm curious to see where you take this.
We've had some fun using Teacup with Rivets.
Rivets look pretty nice. It's the closest thing I've seen to a simple binding solution without all the other bloat.
I probably shouldn't try to do the zillionth binding library but I've gotten it in my head that adding binding to teacup will make things even simpler than rivets. It will let the code in the template do half the work.
On Thu, Mar 20, 2014 at 6:26 PM, Adam Hull notifications@github.com wrote:
Sounds awesome @mark-hahn https://github.com/mark-hahn thanks for the heads up! I'm curious to see where you take this.
We've had some fun using Teacup with Rivets http://www.rivetsjs.com/.
Reply to this email directly or view it on GitHubhttps://github.com/goodeggs/teacup/issues/35#issuecomment-38239942 .
I hope you don't mind but I forked teacup and changed the name to oolong. I'm going to be butchering your code enough that our separate code shouldn't exist in the same repo.
I've got the oolong architecture designed on paper and I'll start coding asap. I'll have to rewrite the README because it has changed so much in the past week. Take a peak at the new version when you get a chance. I respect your opinion greatly.
Well, it's been a year and I obviously never did what I claimed I was going to do.
We've had some fun using Teacup with Rivets.
What are you using now? I'm back in the market for a simple binding solution.
Hey @mark-hahn, we're still using Rivets for most of our binding. We like what we've seen with React and cjsx. Might give that a try next time we're in the market for a new stack.
space-pen is another interesting alternative.
Thanks.
I've been working on the GItHub Atom editor which used space-pen
as the
default until recently when they switched to native components. Space-pen
doesn't have bindings. There is a new space-pen in the works.
I've been considering some lighter react alternatives.
On Mon, Apr 20, 2015 at 2:57 PM, Adam Hull notifications@github.com wrote:
space-pen https://github.com/atom/space-pen is another interesting alternative.
— Reply to this email directly or view it on GitHub https://github.com/goodeggs/teacup/issues/35#issuecomment-94578904.
Have you looked at riotjs? I'm trying to come up with a react-like solution that not only uses coffescript for code but also teacup for the template. I might be able to fork riotjs to use teacup. It already supports coffeescript.
Like many others I've been paying great attention to data-binding frameworks like angular, react, and knockout.
I just discovered mithril (http://lhorie.github.io/mithril), which is a very lightweight mvc data-binding framework. What is the most interesting thing to me about mithril is that the templates are implemented as a DSL in plain javascript which are conceptually like teacup. The DSL is quite inferior to teacup of course.
I want to combine mithril with teacup somehow. I have a side-project waiting to use it. Here are some random ideas ...
1) Issue a pull request to mithril that enables coffeescript and teacup to be used with as little change as needed to mithril and teacup.
2) Add mithril capabilities to teacup and copy everything that makes sense as literally as possible.
3) Steal the lightweight nature and philosophy of mithril but create an entirely new tool.
I never care about popularity of a module (my drykup is proof), I just want to do something worthwhile, useful, and fun. For the fun part I'd like to do #3.
Anyone interested in helping? I would use teacup as the base for the new product. Any long-term connection to teacup would be left as a decision for the future.