mantrajs / mantra-dialogue Goto Github PK

How do I delete this? My bad.

Could I use Blaze Template in this?
Because I still use any Blaze Package such as AutoForm, Account UI, Breadcrumb....
Could you example?

I get this error message when accessing the post page.

Uncaught SyntaxError: Unexpected token P

Seems like it is related with the template string. Am I missing something ?

https://github.com/samwillis/pagedown-bootstrap

I tried react-markdown-editor, but it is wonky and can't even get it to work.

Other ideas are welcome

Personally I find the Discourse interface confusing when it comes to replies.

Hey guys,

Me and @SachaG has an conversation about the Telescope re-write Nova. See: http://www.telescopeapp.org/blog/building-apps-with-nova-react-meteor/

This is about how we think about Nova:

Basically, my idea is for Telescope/Nova to become a back-end layer for React apps.

He also planning to build a front-end with Mantra. So, I just came to this project.

@vonwao How about we can join forces with Nova. Then we can do a much better job and work with Sacha. He's a pretty awesome guy to work with :)

Are the underscored names necessary for file load order? Is this something covered by Mantra naming conventions? (I looked but didn't see anything.)

We need to decide minimal feature set to make this usable. My initial list:

• User login/registration (now available thanks to meteor-matra-kickstarter). Would be nice to be able to login via github/facebook/meteor.
• Post and comments need more attributes (user, category, last comment timestamp, etc)
• Ability to edit post/comment.
• Post list needs to be loaded incrementally (infinite scrolling)
• Markdown/rich text editor

Do you have a plan to refactor all existing code to follow mantra 0.2.0 first?

Maybe @markoshust had already done some works on this but not checked into meteor-mantra-kickstarter yet.

There are some issues like issue#7 which stops us from upgrade meteor 1.3 beta to 6/7/8. But if we follow mantra 0.2.0 spec and the structure like mantra-sample-blog-app , this issue will gone.

So my suggestion is that we refactor current code first.

Which one formsy-react vs tcomb-form?
I used AutoForm.

I have mixed feelings about ODM/ORM. But on the other hand, it's nice to be able to define a data type and add some methods? What's your opinion?

The firs I am sorry, I known that mantra don't care the module structure in lib, server.
But could you advice to manage them for me?
For example I have 3 module in client A, B, C, so
1.

lib/
   A_collection1
   A_collection2
   B_collection1
...............
server/
   methods/
      A_method1
      A_method2
      B_method1
..................

lib/
   A/
      collection1
      collection2
   B/
      collection1
...............
server/
   A/
      methods/
         method1
         method1
       ..............
   B/
..................

Which one should I choose (1 or 2)?
Thanks for your advice!

I base on Collection2, SimpleSchema and AutoForm.
Could example, how to use with Simple Schema?