A good one that I use is a Windows program called Exifer. It allows you to save Exif data in CSV format, and also allows you to extract any embedded thumbnails in your fullsize images. It's pretty neat.
Re:OK, how do I use this with Adobe Premiere?
on
XVID 1.0 Released
·
· Score: 1
I'm going from memory here because I'm at work, but it should be close to the following:
Go File, Export Timeline, Movie...
You should see a dialog where you're able to select the export settings. From the dropdown at the top, select "Video"
You should now see a list of video compressors. choose "Microsoft AVI" (this will contain your XViD stream)
Press the "Configure" button next to the dropdown to configure the AVI stream. You should then get another box that lets you select the XViD codec.
If your priority is for Video that you can share with friends and family, my experience is that DVD-R is the more compatible format. That doesn't mean it's without flaws, though. At least in this part of the world (Australia), both formats seem to be equally available, but a lot of the -R media is still 1x speed. At least with +R you'll get a minimum of 2.4x write times.
The advantage of the +R format is allegedly better support in future versions of Windows, and packet writing ability for the +RW formats.
Given that there are quite a few drives that can write both media, I'd say get one of those. Also, if you havea DVD-ROM drive in your computer, it's worth checking the compatibility of that as well.
But the concept of a "template engine" as you understand it, doesn't specifically require Java, and could be done in say C?
Absolutely. Having said that, one thing that Java gives you is nice introspection capabilities, that is, a template engine is able to look at a set of arbitrary business objects and map them directly into a model that the templates can use.
FreeMarker does it slightly differently, by defining a set of simple interfaces that business objects should either implement directly, or use adapter classes that adapt your business object model to the FreeMarker one. This is probably the approach you'd want to use if you were implementing something similar in C.
I see I didn't explain myself very well in my earlier post. Sorry, I was at work. In terms of the layers between your web server and a template engine, they work as follows:
At the base, your web server, probably Apache HTTPd, or similar
Tomcat, which is a servlet container, providing Java's "hook" into processing web requests and responses
Your template engine, such as Velocity, etc. Technically, JSPs belong at this level as well, though by convention a JSP container is usually bundled with the servlet container. Tomcat is no exception here.
Finally, your templates and business objects, providing the behaviour for your web site
A good introduction to the concepts behind template engines can be found at Servlets.com,
along with its followup article.
None of the template engines (to my knowledge) use XML to define the template -- a template consists mostly of your presentation output, be it HTML, XML, whatever. The template control structures vary in their formats, from XML-like syntax to something that might resemble Perl or shell script constructs. You'd have to see an example or two to understand what I mean.
Why can't I have content (be it HTML or XML) and logic (be it in Java or C or any other language) as separate but cooperative entities, such as with tags in the content to describe to the logic where output pieces go?
You're thinking of templating engines, and there are many around. Probably more by co-incidence than anything else, the ones I've come across have all been written in Java, and co-operate nicely with Servlets (this is where Tomcat fits in).
Have a look around at Velocity, Webmacro, FreeMarker or Tea (see my earlier post above, or Google for them), and have fun!
Let's not forget that there are alternatives to JSP which might be even better to work with. I would strongly encourage you to check out Velocity.
As long as we're talking about templating engines, you might also want to have a look at the alternatives as well.
As mentioned below, Velocity is one of the possibilities, but there are others, including Webmacro, FreeMarker, and Tea. Each of these have thier own advantages and disadvantages, but all primarily focus on have a Model-View-Controller architecture, and try and enfoce separation between templates and the data the populates them. This is usually where JSP and ASP sites tend to fall down in practise.
Slashdot Mirror
Amazingly it won't stop idiotic local councils from ripping them up, even today. Here's a good example - http://www.stuff.co.nz/national/10202967/Wellingtons-trolley-buses-to-go
KDE 3.3.1 had just made the Sarge mirrors. I doubt they'd pull it out and go back to 3.2.3 for release.
A good one that I use is a Windows program called Exifer. It allows you to save Exif data in CSV format, and also allows you to extract any embedded thumbnails in your fullsize images. It's pretty neat.
I'm going from memory here because I'm at work, but it should be close to the following:
Hope this helps,
Nicholas.I can confirm that the 172t allows you to switch between the two, if that helps.
Of course, just like the way the W3C did for stylesheets?
If your priority is for Video that you can share with friends and family, my experience is that DVD-R is the more compatible format. That doesn't mean it's without flaws, though. At least in this part of the world (Australia), both formats seem to be equally available, but a lot of the -R media is still 1x speed. At least with +R you'll get a minimum of 2.4x write times.
The advantage of the +R format is allegedly better support in future versions of Windows, and packet writing ability for the +RW formats.
Given that there are quite a few drives that can write both media, I'd say get one of those. Also, if you havea DVD-ROM drive in your computer, it's worth checking the compatibility of that as well.
Absolutely. Having said that, one thing that Java gives you is nice introspection capabilities, that is, a template engine is able to look at a set of arbitrary business objects and map them directly into a model that the templates can use.
FreeMarker does it slightly differently, by defining a set of simple interfaces that business objects should either implement directly, or use adapter classes that adapt your business object model to the FreeMarker one. This is probably the approach you'd want to use if you were implementing something similar in C.
I see I didn't explain myself very well in my earlier post. Sorry, I was at work. In terms of the layers between your web server and a template engine, they work as follows:
A good introduction to the concepts behind template engines can be found at Servlets.com, along with its followup article.
None of the template engines (to my knowledge) use XML to define the template -- a template consists mostly of your presentation output, be it HTML, XML, whatever. The template control structures vary in their formats, from XML-like syntax to something that might resemble Perl or shell script constructs. You'd have to see an example or two to understand what I mean.
Hope this helps,
Nicholas.
You're thinking of templating engines, and there are many around. Probably more by co-incidence than anything else, the ones I've come across have all been written in Java, and co-operate nicely with Servlets (this is where Tomcat fits in).
Have a look around at Velocity, Webmacro, FreeMarker or Tea (see my earlier post above, or Google for them), and have fun!
Nicholas.
As long as we're talking about templating engines, you might also want to have a look at the alternatives as well.
As mentioned below, Velocity is one of the possibilities, but there are others, including Webmacro, FreeMarker, and Tea. Each of these have thier own advantages and disadvantages, but all primarily focus on have a Model-View-Controller architecture, and try and enfoce separation between templates and the data the populates them. This is usually where JSP and ASP sites tend to fall down in practise.
And yes, I do have a favourite ;)
Nicholas.