Comments on:  FDT and ANT | A User’s Guide – Part II http://blog.alanklement.com/2009/08/19/fdt-ant-part-two/ Web Developer Mon, 26 Jul 2010 12:56:14 +0000 hourly 1 http://wordpress.org/?v=3.0 By: FDT and ANT – part 1 | [mck] http://blog.alanklement.com/2009/08/19/fdt-ant-part-two/comment-page-1/#comment-1268 FDT and ANT – part 1 | [mck] Wed, 07 Jul 2010 10:17:47 +0000 http://blog.alanklement.com/?p=177#comment-1268 [...] haven’t seen the second part of this tutorial: FDT and ANT | A User’s Guide – Part II but I will. It seems to be focused on the use of the templates and [...] [...] haven’t seen the second part of this tutorial: FDT and ANT | A User’s Guide – Part II but I will. It seems to be focused on the use of the templates and [...]

]]> By: Top 20 Things every Senior Flash Developer should know – Confessions of an Flash Addict http://blog.alanklement.com/2009/08/19/fdt-ant-part-two/comment-page-1/#comment-1146 Top 20 Things every Senior Flash Developer should know – Confessions of an Flash Addict Sun, 06 Jun 2010 16:03:06 +0000 http://blog.alanklement.com/?p=177#comment-1146 [...] 12. ANT If you start working with an industry standard IDE like Eclipse or FlashDevelop, there will be a day when you need to automate the build- or other processes with ANT. Its fun, its easy and you should learn it http://blog.alanklement.com/2009/08/10/fdt-and-ant-a-users-guide-part-i/ http://blog.alanklement.com/2009/08/19/fdt-ant-part-two/ [...] [...] 12. ANT If you start working with an industry standard IDE like Eclipse or FlashDevelop, there will be a day when you need to automate the build- or other processes with ANT. Its fun, its easy and you should learn it http://blog.alanklement.com/2009/08/10/fdt-and-ant-a-users-guide-part-i/ http://blog.alanklement.com/2009/08/19/fdt-ant-part-two/ [...]

]]> By: Alan http://blog.alanklement.com/2009/08/19/fdt-ant-part-two/comment-page-1/#comment-627 Alan Mon, 08 Feb 2010 15:34:21 +0000 http://blog.alanklement.com/?p=177#comment-627 I use the FDT tasks b/c the documentation is more accessible than flex ant tasks - FDT has ant documentation within Eclipse. Honestly, I am not very familiar with flex ant tasks. I never had a need to explore them. I can't speak on what is better. At this point tho, I mostly use ANT tasks that are IDE independent such as FTP, SVN, SSH, moving files, renaming directories... Perhaps break up your tasks into IDE specific tasks and then IDE agnostic tasks. Then someone can just write in their own IDE tasks, which probably would be just compiling. I use the FDT tasks b/c the documentation is more accessible than flex ant tasks – FDT has ant documentation within Eclipse.

Honestly, I am not very familiar with flex ant tasks. I never had a need to explore them. I can’t speak on what is better.

At this point tho, I mostly use ANT tasks that are IDE independent such as FTP, SVN, SSH, moving files, renaming directories…

Perhaps break up your tasks into IDE specific tasks and then IDE agnostic tasks. Then someone can just write in their own IDE tasks, which probably would be just compiling.

]]> By: Daniel http://blog.alanklement.com/2009/08/19/fdt-ant-part-two/comment-page-1/#comment-626 Daniel Mon, 08 Feb 2010 12:18:25 +0000 http://blog.alanklement.com/?p=177#comment-626 Great tutorials! Really helpful :) I had some thoughts though: Are there any significant gains to using FDT:s ant tasks as opposed to the ordinary flex ant tasks provided with the SDK? I'm also thinking about portability. Wouldn't it be better for me to go with the generic approach instead of the FDT approach if I for example had some open source project that I wanted others to take part in? Then I'd have build script that "anyone" could use no matter what platform/IDE they where developing on. I'm not trying to come down on the FDT approach or anything. I use FDT myself and think the stuff you outline here looks great! But I'm thinking "what if I change IDE?" or "what if I need some other developer to work with the project and that person has another environment?". So I'm trying to decide which way to go :) What do you think? Great tutorials! Really helpful :)
I had some thoughts though: Are there any significant gains to using FDT:s ant tasks as opposed to the ordinary flex ant tasks provided with the SDK? I’m also thinking about portability. Wouldn’t it be better for me to go with the generic approach instead of the FDT approach if I for example had some open source project that I wanted others to take part in? Then I’d have build script that “anyone” could use no matter what platform/IDE they where developing on.

I’m not trying to come down on the FDT approach or anything. I use FDT myself and think the stuff you outline here looks great! But I’m thinking “what if I change IDE?” or “what if I need some other developer to work with the project and that person has another environment?”. So I’m trying to decide which way to go :)

What do you think?

]]> By: blog.wie-gand.de » Blog Archi » Flash / ActionScript / Ant http://blog.alanklement.com/2009/08/19/fdt-ant-part-two/comment-page-1/#comment-548 blog.wie-gand.de » Blog Archi » Flash / ActionScript / Ant Sun, 17 Jan 2010 23:56:05 +0000 http://blog.alanklement.com/?p=177#comment-548 [...] blog.alanklement // FDT and ANT | A User’s Guide – Part I FDT and ANT | A User’s Guide – Part II [...] [...] blog.alanklement // FDT and ANT | A User’s Guide – Part I FDT and ANT | A User’s Guide – Part II [...]

]]>