I have looked, but am unable to find anything which makes me think I'm approaching this the wrong way.
When I update the content in a template, or display a new template, I want to animate the transition. Currently the content switches but I'd like to be able to use Greensock or similar to perform the change. I have Greensock working on elements fine, but not on templates.
I'd show code but I'm not sure where to begin. I'll update when I've at least made a start.
Cheers.
You can google about undocumented Meteor _uihooks used for example here:
https://atmospherejs.com/percolate/momentum
https://atmospherejs.com/percolate/momentum-iron-router
Related
I have a template in my template gallery that I have been working on and have hit something of a snag with what I am wanting to do. Basically, I want to have my invoice numbers increment when I click on the graphic button in Column H. I have a script tied to the drawing and it works exactly how I want it to--at least locally.
So, here is my question: I would like to have this script update the data sheet on my template--either in addition to or instead of--I don't really care either way on that.
EtA: I neglected to include a link to an example sheet. Here is that:
https://docs.google.com/spreadsheets/d/17zOSkM2yYSMOKobgKkkhQNHHRR901gBiK0BdeempZwo/edit?usp=sharing
Honestly, I haven't really attempted anything. The sum total of my looking into this has been looking via Google and in the forums, but everything I'm finding talks about being able to pull data from an external spreadsheet, but nothing about pushing data there. Given that this is a template. An alternative (in my mind) would be to have the invoice number automatically increment/set each time the template is used, but I have no idea where to even start on something like that.
Any advice--even telling me that I am out of my gourd and nothing like this is possible using Google Sheets--is appreciated.
I have created a custom form in a custom module but No matter what I do, the form is still is using core/themes/classy/templates/form/form.html.twig as the template. i've tried everything (that I can find) on the web but still no way to have own template applied. Please help!
Tried everything google can find me.
Just need my custom template to be applied instead of the default one.
My only requirement is for the module to contain its own theme templates and not rely on a specific theme.
Having tried everything I could find, I resulted to overwriting the template in a new theme rather than in the module. I wanted something else, but better than continuing to waste time. I hope this helps someone else.
i'm new in cakephp and I have started with version 3. I want to build a beautifull app and because I'm not good in design, I would really like to use a free template or buy one that I can use within cakephp.
So, I would really appreciate all your propositions and ideas or best practises. The easy way will be the best because I don't have a lot of time with this project. Thank you in advance.
If you don't have a lot of time like you mentioned, the easiest way to go ahead and get started is to paste a lot of the code in your default.ctp layout inside of src/Template/Layout/default.ctp.
You'll notice there are some lines of PHP already in there that are relevant to fetching blocks of css, meta tags, and other bits of code that could potentially exist throughout your project.
Find the main layout of the theme your trying to use - the one that will be consistent across most of the pages. That's the one you'll use for default.ctp. Compare what's already in default.ctp and make the comparable adjustments around the HTML in that document while keeping the important lines of PHP there as well.
For other important pages like a login or registration page, just create a new document for those, like 'login.ctp', then inside the function that loads the page (maybe 'login' inside of UsersController'), change the default layout with this line of code:
$this->viewBuilder()->layout('login'); // without the .ctp ending
This way you can create one-off layouts that don't really match any other page.
As a user experience requirement, I need to create a dynamic dashlet.
According to what I need, a dynamic dashlet would be a special dashlet that can load inside "almost every content". I say almost every content because of course this kind of dashlet would have its own limits of course. At the same time, it would be nice that the dynamic dashlet has the ability of being maximized, what in fact would show the real content (for example, an Alfresco page).
Perhaps my question is ambiguous, but the intention to give the user the chance of check execute common functionality inside that special dashlet, this way the user doesn't have to leave the dashboard improving the user experience as a consequence.
Did anybody have had such requirement or similar before? Would that be possible to do?
I would like to know some tips and suggestions in order to find out the right approach.
Thanks in advance.
You could try re-using the webview Dashlet which can also show another page.
The only problem is that not every part which is visible in Share can be accessed via url. Sure the template gets build up by regions of *.ftl's but that doesn't mean you can 'just' view the *.ftl.
The only 'dynamic' thing I see is making a custom page template which shows one or couple of regions which are dynamically build by the url.
e.g. pointing to share/page/customPage?region1=documentlibrary should insert the documentlibrary template within that page and thus it can be shown within the iFrame of the webview Dashlet.
Actually the documentlibrary is a bad example, because there is already a portletMode available for Liferay. But hopefully you'll get my point.
Why is the Ember Snippet i have linked not working? I am setting up a simple ArrayController and fill it with contents upon initialization. Then i want to display the contents of this controller with the help of {{#each}}, but this is not working.
In tutorials i have read through, the following structure is always used:
{{#each AppNamespace.myModelController}}
...
{{each}}
But to make my example work i had to use:
{{#each AppNamespace.myModelController.content}}
...
{{/each}}
Could you have a look at the provided fiddle and tell me what is wrong with it? I assume that i must have done something wrong since i have seen this pattern so often in tutorials.
Note: I am a Javascript beginner coming from Java Server Development. So it maybe easy JS basics that i am struggling with.
I would have posted the complete code here, but the formatting was not working properly.
Link to my JS Fiddle showing my problem
Add a call to this._super() inside your init method.
https://github.com/emberjs/ember.js/pull/1251
Also, not directly related to your question, but it looks like you would benefit from reading #6 here: http://codebrief.com/2012/03/eight-ember-dot-js-gotchas-with-workarounds/
Tried your fiddle with http://cloud.github.com/downloads/emberjs/ember.js/ember-0.9.6.min.js instead of 1.0 pre it is working fine in both the cases.
I'm starting to look at Ember myself and I'm concerned about the process you're using.
As far as I'm aware you shouldn't really be retrieving data directly from the controller like that. The pattern you use should be based upon models, controllers, views and the router.
http://trek.github.com/ is a resource which I have found useful while learning about Ember.
Based upon that example, this would be my take on a small ember test application:
http://jsfiddle.net/zDfBv/
Hopefully that will be of some use to you as a starting point.
If you pass 1 argument to the #each helper it needs to be a Ember.Array compatible object-- in your first example you pass the controller when your data is in the content property.. your second example works because you pass the content property.. and there is nothing wrong with doing it that way if you feel like it.
There is however an alternate syntax for the #each helper which you may see more often, it uses element naming {{#each model in myModelController}} ... {{/each}}. When you do it this way Ember takes care of looking for the content property for you because it's the default rendering context for the view.
Assuming you're using the latest version from Github you'll find it takes care of looking for content in both cases so the point becomes moot once that is released as stable.