Many websites have loading animations, slide in text and more. What language is used to trigger the animations?
A lot of various technologies can be used, but among the most widespread, there are JavaScript (and many many libraries / technologies built upon it, like jQuery, NodeJS, AngularJS, VueJS, etc.) and HTML5, which includes sets of "native" HTML tags enabling animations (and a lot more than that). Among others, one could also mention Django, which is built in Python.
I hope this helps ; please refer to these technologies' documentations for actual details.
You can, and we used to, animate stuff directly with javascript. This has largely been replaced with css transitions, which are much cleaner. So you define your animation in css with the transition rule, and you trigger it with built-in selectors :hover :active :focus etc., or by adding a class to the class list. If you use a js mvvm framework like angular or vue, you can bind your class list to your model. As such, everything is declarative, nothing is procedural. My goodness we've gotten clever :-)
Related
I'm currently working on a project that uses the routing approach (not documentation yet for Dart):
https://angular.io/docs/ts/latest/guide/router-deprecated.html
And I wonder how could I control the transition between different views. I read about the CssAnimationBuilder, but there is no much documentation about this class.
Even though the question is related to the Dart environment, TypeScript and JavaScript programmers are welcome, since Dart is still a small group.
There is a new router coming again and there is also new animation feature work in progress and it looks like it is about to be shipped (https://www.youtube.com/watch?v=Hr4IKlr9mhg) I think it's better to wait until these become available.
If you need or want a solution immediately I would create a custom <router-outlet> that adds the new component, before it removes the old one and adds/removes CSS classes as required to make it easy to apply animations.
I have used backbone boilerplate on the past
https://github.com/backbone-boilerplate/backbone-boilerplate
I want to use marionette on my next project and I have found this
https://github.com/BoilerplateMVC/Marionette-Require-Boilerplate
My question is if it's a good idea to go with the marionette boilerplate or start form scratch.
As an aside, I'd like to suggest you give Yeoman a shot for scaffolding your first Marionette app. Yeoman works via what are called "generators", and provide much more than the the above Boilerplate MVC can offer you (Chai and Sinon for testing, Bower for client-side package management, etc...). Plus, Addy Osmani, who runs backbone-boilerplates is one of the heads of the project. Check out generator-marionette here.
I haven't used BoilerPlate, but glancing through it, it certainly seems like a valid approach to writing Marionette apps. If you're just getting started it will certainly help you see how the various pieces are supposed to be used. One gripe I've got is the folder structure. I prefer to break my applications down into modules, and then add models, collections, views, etc under each module. But this will certainly get you up and running quick, and there's nothing stopping you from customizing it to suit your needs.
I agree with others here: it is a useless limitation to imitate a folder structure that follows the 'old mvc model for server-side code'. You will remain more flexible further down the road if you think of your application strictly as completely self-containing modules, i.e. they contain their own controller/router/views/collections/templates etc. You can have a separate folder structure for shared code that is not a module, although anything can be made a module :)
Regarding boilerplate code and generators: i think in the beginning you should actually NOT do it, because you won't understand what you're doing. But that's just my personal opinion.
I am looking for a javascript library that provides a comprehensive set of widgets that covers most HTML elements and also has a good grid table. The out of the box look and feel must be good. Ajax will be nice as well or else must have ability to attach event handlers.
Any ideas?
PS:
Dont say jQuery please.
Anyway jquery is suited for normal needs , i won't personally recommend you any other thing but for the question part you can either go for Mootools OR YUI
EDIT
Go for a look over here
http://javascriptlibraries.com/
Is there a reason why not jQuery? It's arguably the best one out there...but anyways, some alternatives are Prototype, MooTools and Dojo...but if you're shying away from jQuery because it's "hard" or some other similar reason, you're not going to have much more luck with any other library out there...all pretty much the same thing...
You may be familiar with IntenseDebate, Disqus, and their ilk. These tools produce wretched markup that pollutes my pages significantly and is difficult to style correctly.
I have a site which is statically generated. Are there hosted commenting options that are simple, clean, unobstrusive, and easy to style?
The solution I settled on was using hosted-commenting JSON APIs plus JS templating. You give up the social-media button widgets and you have to roll some of your own comment form, but that's ultimately a small price to pay in my book.
I am currently using the JBoss RichFaces JSF component library for the project I am working on. It works quite well in general, especially the AJAX support provided by ajax4jsf (A4J), but I find the usually very inflexible table-markup used for almost every component and all this "skin" stuff of RichFaces quite annoying. It would be nice if there were some components which just provided the functionality and only minimal markup/style. Originally I had planned to use ICEfaces, but that didn't work too well either and also brings a lot of predefined styles with it, so for now RichFaces seems to be the best option.
Now I thought it would be nice to develop a clean tag library which provides some useful components found in RichFaces, ICEfaces or Tomahawk (not all of course!), which don't use any predefined style and generate markup which can be styled easily with CSS.
I wanted to use the ajax4jsf library for AJAX support, because I think it works quite nicely, and integrates seamlessly into standard JSF with facelets. But it seems that since it has moved over to JBoss, it isn't available as a standalone library anymore. You can only download the whole RichFaces package, which I don't want.
Is the ajax4jsf (A4J) project dead? If it is, what alternatives are there?
You can find many alternatives here:
JSF AJAX Component Library Feature Matrix
If you read the ajax4jsf forum you'll see that it's been merged with Richfaces.
You don't have to use the Richfaces components on your page, so do you have an issue with having the JARs in your project?
I agree that many JSF components (not just Richfaces) are based on tables (eg. h:selectManyCheckbox). Don't forget that it's easy to write a new renderer for many of these. I've done this for the h:selectManyCheckbox so that the checkboxes are rendered inside divs instead of a table. I would think that you should be able to do the same for Richfaces components...but if that's the case, then why use them?
You may find it easier/nicer using jQuery UI elements and tie them back to your Beans with a4j:jsFunction (or similar).
Just a comment. I started using icefaces. I'm a web designer also and im very particular on look and feel of the icefaces components in relation to my web application. I was highly frustrated at the time it took me to override the look and feel of icefaces components using css. The components had a lot of nested table markup that annoyed me.
When i moved to richfaces. I discovered it was alot easier to override the look n feel because richfaces have an integrated system of overriding the look n feel in css. The css given to the components had similar and sensible class names that made it easier to predict and override.
If you are feeling adventurous, take a look at JSF 2. It features a shift in view technologies from JSP to Facelets and built in AJAX support. David Geary has been running a series of JSF 2 fu articles on developerWorks (though you'll have to wait for part 3 for the AJAX stuff). Ed Burns and Jim Driscoll have been demoing various features during the development of the new API, so you might want to check out their blogs too.