RFP: Templating #2995

Closed
chasenlehara opened this Issue Feb 2, 2017 · 8 comments

Comments

Projects
None yet
5 participants
@chasenlehara
Member

chasenlehara commented Feb 2, 2017

This is a request for proposals related to improving templating within CanJS.

@justinbmeyer started the discussion a few weeks ago when he opened two issues: can-semijs and can-stache 4.0. This was discussed in a contributors meeting (discussion starts at ~5:41) a couple weeks ago.

To say that the core team’s goal is to “improve” templating is a little nebulous, but I think it’s safe to say that can-stache (in its current incarnation) is not the pinnacle of maintainable, performant, and usable templating. We can do better and we want your help.

The core team encourages you to brainstorm ideas for improvements to can-stache or a complete replacement. Like Justin has already done in the issues he opened, it is best to create a new issue in this repo or can-stache to outline your proposal with:

  • Its goals & use cases
  • Details on how it might work
  • Pros and cons compared to can-stache and other alternatives
  • Unanswered questions that will warrant discussion

The core team will start discussing proposals as early as Friday, March 17, so to guarantee that your ideas will be considered, please submit them by Friday, March 10th (update). We may will start discussion later than that, so “late” proposals might will still be considered, but March 10th is the deadline we’re setting for now.

To submit a proposal, please leave a comment here with a link to the issue. We welcome proposals from anyone in the community, and we see this process as a way to brainstorm ideas, so please don’t be shy in sharing! These proposals are a starting point for our discussion, so we don’t expect one proposal to “win” and be selected without some changes. If you submit a proposal, we may invite you to join the contributors meetings to join the discussion.

As with other major changes to DoneJS, the core team will vote on a final decision. All members in good standing will have a vote. If you are not already a part of the core team, consider joining us.

@chasenlehara chasenlehara added the Epic label Feb 2, 2017

This was referenced Mar 2, 2017

@chasenlehara

This comment has been minimized.

Show comment
Hide comment
@chasenlehara

chasenlehara Mar 6, 2017

Member

The core team is quickly closing in on the DoneJS 1.0 release. Since that’s still our current focus this month, I’ve updated the RFP’s description to note that we are not requiring submissions by March 10. We will most likely set another date as we get closer to when we’ll start discussing this topic.

Member

chasenlehara commented Mar 6, 2017

The core team is quickly closing in on the DoneJS 1.0 release. Since that’s still our current focus this month, I’ve updated the RFP’s description to note that we are not requiring submissions by March 10. We will most likely set another date as we get closer to when we’ll start discussing this topic.

@leoj3n

This comment has been minimized.

Show comment
Hide comment
@leoj3n

leoj3n Mar 11, 2017

Contributor

Here is some research I found pertinent, and my opinions included:

#3089

Contributor

leoj3n commented Mar 11, 2017

Here is some research I found pertinent, and my opinions included:

#3089

@christopherjbaker

This comment has been minimized.

Show comment
Hide comment
@christopherjbaker

christopherjbaker Apr 19, 2017

Contributor

Bit of an extra feature, but could apply to any proposal. It might be worth trying to modularize the actual dom rendering component, in order that it can be swapped out for other renderers (native ios, native android, threejs/webgl, pdf, etc). I would think they could all use the same (or nearly the same) diffing (perhaps it might have some options set by the renderer?), and some sort of common API that they hook into (method calls, event system, etc).

Contributor

christopherjbaker commented Apr 19, 2017

Bit of an extra feature, but could apply to any proposal. It might be worth trying to modularize the actual dom rendering component, in order that it can be swapped out for other renderers (native ios, native android, threejs/webgl, pdf, etc). I would think they could all use the same (or nearly the same) diffing (perhaps it might have some options set by the renderer?), and some sort of common API that they hook into (method calls, event system, etc).

@imaustink

This comment has been minimized.

Show comment
Hide comment
@imaustink

imaustink May 3, 2017

Contributor

I've added a proposal here: #3197

Contributor

imaustink commented May 3, 2017

I've added a proposal here: #3197

@christopherjbaker

This comment has been minimized.

Show comment
Hide comment
@christopherjbaker

christopherjbaker May 12, 2017

Contributor

added a (meta) proposal at #3248

Contributor

christopherjbaker commented May 12, 2017

added a (meta) proposal at #3248

@christopherjbaker

This comment has been minimized.

Show comment
Hide comment
@christopherjbaker

christopherjbaker May 12, 2017

Contributor

added JSX proposal at #3252

Contributor

christopherjbaker commented May 12, 2017

added JSX proposal at #3252

@leoj3n

This comment has been minimized.

Show comment
Hide comment
@leoj3n

leoj3n May 25, 2017

Contributor

Semi-related:

https://github.com/jstransformers/jstransformer
https://www.npmjs.com/browse/keyword/jstransformer

Also, would be cool if we had an online educational REPL like this:

http://www.earl-grey.io/repl.html

Sorry if this isn't the right place to post this for discussion (please direct me otherwise if needed).

Contributor

leoj3n commented May 25, 2017

Semi-related:

https://github.com/jstransformers/jstransformer
https://www.npmjs.com/browse/keyword/jstransformer

Also, would be cool if we had an online educational REPL like this:

http://www.earl-grey.io/repl.html

Sorry if this isn't the right place to post this for discussion (please direct me otherwise if needed).

@matthewp

This comment has been minimized.

Show comment
Hide comment
@matthewp

matthewp Feb 26, 2018

Contributor

Can this be closed? I think we settled on incrementally improving stache and eventually doing JSX.

Contributor

matthewp commented Feb 26, 2018

Can this be closed? I think we settled on incrementally improving stache and eventually doing JSX.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment