Backbone #87
Closed
Backbone #87
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| (function () { | ||
|
|
||
| Ghost.Collections.Settings = Backbone.Collection.extend({ | ||
| model: Ghost.Models.Post |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
Closed
|
Closing this as #90 has now gone in. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So as opposed to continue to debate the pros/cons, implementation, etc for Backbone... I went ahead and converted the current backend to a very simple Backbone implementation.
Obviously things need to be split into a lot smaller views, and we'll need to hook up models, etc. but I guess I just wanted to start off the conversation on this because (at least for me) the faster there's a consistent pattern for laying out the frontend the easier it is to conceptually be able to plan/develop its interaction with the API... it can be tough to know what data/relations/settings etc needs to be bootstrapped/loaded on each page and how they will relate to each other otherwise until you start doing it.
This is not intended to be merged as-is, and we don't even have to do a sweeping overhaul, we could break this up into smaller parts. I think with another few hours though the admin panel could be up and running smooth as a single page app.
Edit: made the issue a bit more concise