![]() How to extend generated javascript? => rather than editing generated code directly ![]() But the implemenation of the Asset management is beyond the scope of this project. Thus, an introduction of a build step for the javascript assets including handlebar templates would be great (cf. Implementation Decision: Precompilation should be discussed together with a proper Asset management approach for Flow.Consequence: Fluid not useable inside Handlebar Templates => Does not make much sense anyway!.Problem: How to precompile handlebar templates (possibly without dependencies on node, ruby or grunt).It would be great to use normal on-the fly compilation of handlebar templates in development context and precompiled templates in production context (more advanced than: ) => performance.Handlebars code should be outsourced into seperate files to allow precompilation => clean seperation and mixing TYPO3 FLUID and handlebars syntax problems avoided.Handlebar templates can be precompiled which increases performance dramatically and additionally the precompiler runtime code of the handlebar library does not have to be loaded. Handlebar code can be defined in a script-tag directly in the html code or seperatly in a file. Handlebars is the templating engine used by Ember.js.Note: Once, json-api has settled to a stable concensus, the REST API should be evolved to comply to json-api. Set a namespace in Ember's RestAdapter for RoutePart prefixing Flow RoutePart needs to conforms to embers standard RESTAdapter routes.Flow Controller + View needs to conform to embers RESTAdapter conventions. ![]() Thus, it is connected to how the route part handles/forwards requests.Īs illustrated in the architectural overview the Flow RestController communicates with the Ember RestAdapter via AJAX calls in JSON format.įlow EmberRestController + EmberDataView Ember DS.RESTAdapter Note: The naming decision also affects the names of routes to which ember tries to persist the models.Classes/TYPO3/Blog/Domain/Model/ => App.Blog. OR add a pattern-based config into the yaml file.Problem: What if there is a model with the same name from a different namespace/package?.Flow Classes/TYPO3/Blog/Domain/Model/Blog.php => Ember App.Blog Generally remove the long namespaces of the flow models.Properties and associations of a model can be looked up using the ReflectionService of Flow.If possible, providing a ignore list would be reasonable.I think there currently is no API to retrieve all domain models of a given package name.What to do if there is an association to an additional model? Probably just omit, as in explicit declaration we can assume that it was left out intentionally. ![]() yaml config (or commandline parameters).Options: All of a package or namespace OR explicit declaration of each model.How to define which model should be kickstared?.handling of namespaces, override existing files, simple merge.Some settings for the kickstart can be configurated using a Yaml file (eg.Kickstarting through command-line => extend FLOWs CommandController.below Ember Commons Package) or are part of ember-data are illustrated with a blue background. Components that are provided through a Flow package (cf. Components that are kickstarted (generated) are illustrated with a green background. In order to provide a concise overview, I have created a diagram showing the components that a kickstarted application will consist of.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |