Thread: [A-a-p-user] Learning and using aap in website project
Brought to you by:
vimboss
From: Fredrik <aa...@st...> - 2004-06-28 21:09:06
|
Hi, I'm maintaining a website for an non-profit org and all the articles that get submitted is written in asciidoc[1] and I have been using simple shell scripts for generating and uploading the site and has worked pretty okay until I stumbled on a-a-p via asciidoc's homepage and found an example how to build and maintain a site with asciidoc and aap, beautiful! Here is how my tree looks like: / /style /html /source/ /source/conf /source/articles /source/articles/conf Where: style - is where some images and css files are located html - where the generated site should be placed source - where the site is index.asc, contact.asc and so on source/articles - where the submitted articles are located conf - is the asciidoc configuration for templating. I would like to generate html from ascidoc sources and from the asciidoc website example[2] the "rule" looks like this: ---------- cut ROOT = index aboutsite about tutorials ASCIIDOC_FILES = $*(ROOT).asc HTML_FILES = $*(ROOT).html # AsciiDoc options to generate web pages. ASCIIDOC_OPTS = -b css -f conf/asciidoc.conf -g revision=$VERS # File translation rules. :rule %.html : %.asc conf/asciidoc.conf @if target == 'index.html': # Index has description and keywords meta tags. ASCIIDOC_OPTS += -g index-only -o $target :sys $ASCIIDOC $ASCIIDOC_OPTS -o $target $(source[0]) all: build build: $HTML_FILES ----------- cut This works very well when you have the main.aap *.asc files in the same directory. So my question is how I should do when using subdirs for generating the site? I have checked the documentation and tried but with no luck. I couldn't find any good examples either so I thought I would try my luck here. [1] : http://www.methods.co.nz/asciidoc/index.html [2] : http://www.methods.co.nz/asciidoc/examples/website/index.html -- .Fredrik |
From: Bram M. <Br...@mo...> - 2004-06-29 09:28:54
|
Fredrik wrote: > I'm maintaining a website for an non-profit org and all the articles > that get submitted is written in asciidoc[1] and I have been using > simple shell scripts for generating and uploading the site and has > worked pretty okay until I stumbled on a-a-p via asciidoc's homepage > and found an example how to build and maintain a site with asciidoc > and aap, beautiful! > > Here is how my tree looks like: > > / > /style > /html > /source/ > /source/conf > /source/articles > /source/articles/conf > > Where: > style - is where some images and css files are located > html - where the generated site should be placed > source - where the site is index.asc, contact.asc and so on > source/articles - where the submitted articles are located > conf - is the asciidoc configuration for templating. > > I would like to generate html from ascidoc sources and from the asciidoc > website example[2] the "rule" looks like this: [...] > This works very well when you have the main.aap *.asc files in the > same directory. So my question is how I should do when using subdirs > for generating the site? > > I have checked the documentation and tried but with no luck. I > couldn't find any good examples either so I thought I would try my > luck here. There are several ways to do this, of course. Let's assume you want to separate generating the html files from uploading them. This means you can try them out locally first. Create a main.aap in the toplevel directory that contains something like this: # Include the list of files to be generated. :include filelist.aap HTML_FILES = html/$*(ROOT).html # Where to upload the HTML files to. :attr {publish = scp://myhost/path/%file%} $HTML_FILES # Rules for building the HTML files :child source/main.aap # Default target: build the HTML files all: $HTML_FILES # Publish target: upload the HTML files (build them too) publish: $HTML_FILES :publishall One thing to watch out for: The HTML files have "html" in their name, thus %file% also has that. You might want to use %basename% instead. filelist.aap: ROOT = index aboutsite about tutorials In the source/main.aap recipe you place the stuff to build the HTML files (so that you can run "aap" there to check your .asc files): :include ../filelist.aap HTML_FILES = ../html/$*(ROOT).html all: $HTML_FILES # AsciiDoc options to generate web pages. ASCIIDOC_OPTS = -b css -f conf/asciidoc.conf -g revision=$VERS # File translation rules. :rule %.html : %.asc conf/asciidoc.conf @if target == 'index.html': # Index has description and keywords meta tags. ASCIIDOC_OPTS += -g index-only -o $target :sys $ASCIIDOC $ASCIIDOC_OPTS -o $target $(source[0]) Note that $HTML_FILES files exists both in the toplevel recipe and the child recipe in the source directory, but have different values. That is because file names in a recipe are relative to that recipe. I don't know what you want to do with the source/articles directory. Hopefully the above provides enough ideas to figure this out. You could put the rule in a separate recipe and include that where you need it. Avoids that you have to copy it around. I didn't test any of this! -- Vim is like Emacs without all the typing. (John "Johann" Spetz) /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html /// |
From: Fredrik <aa...@st...> - 2004-06-29 12:32:23
|
On [040629 11:30] Bram Moolenaar <Br...@mo...> wrote: > > Fredrik wrote: > > > I'm maintaining a website for an non-profit org and all the articles > > that get submitted is written in asciidoc[1] and I have been using > > simple shell scripts for generating and uploading the site and has > > worked pretty okay until I stumbled on a-a-p via asciidoc's homepage > > and found an example how to build and maintain a site with asciidoc > > and aap, beautiful! [...] > > [...] > > > This works very well when you have the main.aap *.asc files in the > > same directory. So my question is how I should do when using subdirs > > for generating the site? > > > > I have checked the documentation and tried but with no luck. I > > couldn't find any good examples either so I thought I would try my > > luck here. > > There are several ways to do this, of course. Let's assume you want to > separate generating the html files from uploading them. This means you > can try them out locally first. > > Create a main.aap in the toplevel directory that contains something like > this: [...] Thanx for the quick reply. When following your instructions I get the following message: $ aap Aap: Do not know how to build "../html/index.asc" $ aap -v Options: verbose: 1 Values: Targets: Aap: Reading recipe "/usr/lib/aap/default.aap" Aap: Finished reading recipe "/usr/lib/aap/default.aap" Aap: Reading recipe "main.aap" Aap: Reading recipe "filelist.aap" Aap: Finished reading recipe "filelist.aap" Aap: Entering directory `/home/stone/new-site/source' Aap: Reading recipe "main.aap" Aap: Reading recipe "../filelist.aap" Aap: Finished reading recipe "../filelist.aap" Aap: Finished reading recipe "main.aap" Aap: Adding default dependency for "clean" Aap: Adding default dependency for "cleanmore" Aap: Entering directory `/home/stone/new-site' Aap: Finished reading recipe "main.aap" Aap: Adding default dependency for "clean" Aap: Adding default dependency for "cleanmore" Aap: Building the "all" target Aap: 1 - updating target "all" Aap: 2 - Using dependency "all : ../html/index.html ../html/aboutsite.html ../html/about.html" Aap: Entering directory `/home/stone/new-site/source' Aap: 3 - updating target "../html/index.html" Aap: 4 - Using build rule "%.html : %.asc conf/asciidoc.conf" for target "../html/index.html" Aap: 5 - updating target "../html/index.asc" Aap: 5 - Do not know how to build "../html/index.asc" Aap: 5 - updating target "html/index.asc" Aap: 5 - Do not know how to build "html/index.asc" Aap: Do not know how to build "../html/index.asc" Here is my setup: main.aap # Include the list of files to be generated :include filelist.aap HTML_FILES = html/$*(ROOT).html # where to upload the HTML files to :attr {publish = scp://web/%file%} $HTML_FILES :child source/main.aap # Rules for building the HTML files all: $HTML_FILES # publish target: upload the HTML files (build them too) publish: $HTML_FILES :publishall filelist.aap ROOT = index aboutsite about source/main.aap :include ../filelist.aap HTML_FILES = ../html/$*(ROOT).html ASCIIDOC_FILES = $*(ROOT).asc all: $HTML_FILES # AsciiDoc options to generate web pages ASCIIDOC = '/home/stone/progs/asciidoc-5.0.8/asciidoc.py' ASCIIDOC_OPTS = -b css -f conf/asciidoc.conf -g revision=1.0 # File translation rules. :rule %.html : %.asc conf/asciidoc.conf @if target == 'index.html': # Index has description and keywords meta tags. ASCIIDOC_OPTS += -g index-only -o $target :sys $ASCIIDOC $ASCIIDOC_OPTS -o $target $(source[0]) I'm not shure what I'm missing. -- .Fredrik |
From: Bram M. <Br...@mo...> - 2004-06-29 18:31:53
|
Fredrik wrote: > When following your instructions I get the following message: > $ aap > Aap: Do not know how to build "../html/index.asc" [...] > Aap: Entering directory `/home/stone/new-site/source' > Aap: 3 - updating target "../html/index.html" > Aap: 4 - Using build rule "%.html : %.asc conf/asciidoc.conf" for target > "../html/index.html" > Aap: 5 - updating target "../html/index.asc" > Aap: 5 - Do not know how to build "../html/index.asc" [...] > # File translation rules. > :rule %.html : %.asc conf/asciidoc.conf > @if target == 'index.html': > # Index has description and keywords meta tags. > ASCIIDOC_OPTS += -g index-only -o $target > :sys $ASCIIDOC $ASCIIDOC_OPTS -o $target $(source[0]) > > > I'm not shure what I'm missing. It's not so obvious. Aap finds the rule to turn a .asc file into a .html file, but a rule does not specify where to search for the source file. It simply uses the name of the file with the path for the %. The most explicit solution is to adjust the rule to include the path: :rule ../html/%.html : %.asc conf/asciidoc.conf ... -- DENNIS: Listen -- strange women lying in ponds distributing swords is no basis for a system of government. Supreme executive power derives from a mandate from the masses, not from some farcical aquatic ceremony. The Quest for the Holy Grail (Monty Python) /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html /// |
From: Fredrik <aa...@st...> - 2004-06-30 17:43:00
|
On [040629 21:40] Bram Moolenaar <Br...@mo...> wrote: > > Fredrik wrote: > > > When following your instructions I get the following message: > > $ aap > > Aap: Do not know how to build "../html/index.asc" > > [...] > > > Aap: Entering directory `/home/stone/new-site/source' > > Aap: 3 - updating target "../html/index.html" > > Aap: 4 - Using build rule "%.html : %.asc conf/asciidoc.conf" for target > > "../html/index.html" > > Aap: 5 - updating target "../html/index.asc" > > Aap: 5 - Do not know how to build "../html/index.asc" > > [...] > > > # File translation rules. > > :rule %.html : %.asc conf/asciidoc.conf > > @if target == 'index.html': > > # Index has description and keywords meta tags. > > ASCIIDOC_OPTS += -g index-only -o $target > > :sys $ASCIIDOC $ASCIIDOC_OPTS -o $target $(source[0]) > > > > > > I'm not shure what I'm missing. > > It's not so obvious. Aap finds the rule to turn a .asc file into a > .html file, but a rule does not specify where to search for the source > file. It simply uses the name of the file with the path for the %. > > The most explicit solution is to adjust the rule to include the path: > > :rule ../html/%.html : %.asc conf/asciidoc.conf > ... Thanx! That solved it! I still cannot figure out how to solve the "articles" part (subdir). In the "source" dir I have another dir called "articles" where I put submitted articles also written in AsciiDoc but in this dir the conf/asciidoc.conf is diffrent than in the the source dir so I can't have these files in the "source" dir. I have tried a lot of combinations with ":child source/articles/main.aap" and changed the "ROOT" variable in the filelist to "ARTICLES" but I get an message about that source/articles/main.aap doesent know how to build "about.asc" which is a file in "source" not in "articles". Even after I have changed the the "HTML_FILES" variable to "ARTICLES" wich is a variable in the "filelist.aap". ( I hope you understand what I mean). Here is an exact description of what I want to do :) / /source/ /source/conf/ /source/atricles /source/articles/conf /html In the source dir the "main" site is located and in the "articles" dir submitted articles are located. In those dirs there is another dir "conf" which contans a asciidoc.conf file which holds the configuration when generating html from the ascidoc files. These need to be diffrent (that's why I need to have a seperate dir for the articles). Going to / and type "aap" would first go to "source" and build all the %.asc files using /source/conf/asciidoc.conf configuration file and then go to "/source/articles" and build all the %.asc files using "/source/articles/conf/asciidoc.conf" configuration and all build files should be palced in the /html dir. *phew* Or am I doing something very wrong here? :) -- .Fredrik |
From: Bram M. <Br...@mo...> - 2004-07-01 10:12:55
|
Fredrik wrote: > > It's not so obvious. Aap finds the rule to turn a .asc file into a > > .html file, but a rule does not specify where to search for the source > > file. It simply uses the name of the file with the path for the %. > > > > The most explicit solution is to adjust the rule to include the path: > > > > :rule ../html/%.html : %.asc conf/asciidoc.conf > > ... > > Thanx! That solved it! > > I still cannot figure out how to solve the "articles" part (subdir). > > In the "source" dir I have another dir called "articles" where I put submitted > articles also written in AsciiDoc but in this dir the conf/asciidoc.conf is > diffrent than in the the source dir so I can't have these files in the > "source" dir. I have tried a lot of combinations with ":child > source/articles/main.aap" and changed the "ROOT" variable in the filelist to > "ARTICLES" but I get an message about that source/articles/main.aap doesent > know how to build "about.asc" which is a file in "source" not in "articles". > Even after I have changed the the "HTML_FILES" variable to "ARTICLES" wich is > a variable in the "filelist.aap". ( I hope you understand what I mean). > > Here is an exact description of what I want to do :) > > / > /source/ > /source/conf/ > /source/atricles > /source/articles/conf > /html > > In the source dir the "main" site is located and in the "articles" dir > submitted articles are located. In those dirs there is another dir "conf" > which contans a asciidoc.conf file which holds the configuration when > generating html from the ascidoc files. These need to be diffrent > (that's why I need to have a seperate dir for the articles). > > Going to / and type "aap" would first go to "source" and build all the %.asc > files using /source/conf/asciidoc.conf configuration file and then go to > "/source/articles" and build all the %.asc files using > "/source/articles/conf/asciidoc.conf" configuration and all build files should > be palced in the /html dir. *phew* It looks like it gets too complicated to do this with a rule. Let's switch to explicit dependencies. This has the advantage that the file names are fixed (relative to the recipe in which the dependency is defined). Since you will use the build commands more then once, it's a good idea to put them in an action. This functions as a subroutine then. You could put this in the top directory in a "include.aap" recipe. :action asc2html default ... build commands from $source to $target ... To make sure the right conf/asciidoc.conf is used, define the dependencies in the directory where the .asc files are located. Is it OK that conf/asciidoc.conf is one of the source files? For source/main.aap: :include ../include.aap LocalFiles = one two three @for name in var2list(LocalFiles): ../html/$(name).html : $(name).asc conf/asciidoc.conf :do asc2html $source For source/articles/main.aap: :include ../../include.aap LocalFiles = hip hop hup @for name in var2list(LocalFiles): ../../html/$(name).html : $(name).asc conf/asciidoc.conf :do asc2html $source To avoid listing the files twice you can pass the html names to the parent: _top.FileList += html/$*(LocalFiles).html So that in the toplevel main.aap you can do: :child source/main.aap :child source/articles/main.aap all: $FileList Hope that gives you enough ideas. -- -rwxr-xr-x 1 root 24 Oct 29 1929 /bin/ed -rwxr-xr-t 4 root 131720 Jan 1 1970 /usr/ucb/vi -rwxr-xr-x 1 root 5.89824e37 Oct 22 1990 /usr/bin/emacs /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html /// |
From: Fredrik <aa...@st...> - 2004-07-08 21:26:46
|
On [040701 12:15] Bram Moolenaar <Br...@mo...> wrote: [...] > It looks like it gets too complicated to do this with a rule. Let's > switch to explicit dependencies. This has the advantage that the file > names are fixed (relative to the recipe in which the dependency is > defined). [...] Thank you it works, Yay! One last question (I hope :)). Now I want to upload a directory of images called "img" recursive when publishing the site. I have read in the archives[1] but the :tree thingy dosen't work as I expect. When experimenting with :tree only the files in the "img" directory is published not the actual "img" directory with files and subdirs. WEB_FILES = $HTML_FILES img :attr {publish = ...} $WEB_FILES dosent work and gives a message about: Aap: Error in recipe: Copying a directory requires -r flag How do I set a recursive attribute on "img" (if that is the right way to do it) or if someone got any pointer to examples etc? Thank you in advance. [1] http://article.gmane.org/gmane.comp.tools.aap.user/263 .Fredrik (who is lurking in #aap and no one is online when I am ;) ) |
From: Joakim R. <jr...@fo...> - 2004-07-08 21:40:09
|
On Thu, 2004-07-08 at 14:26, Fredrik wrote: [...] > > WEB_FILES = > $HTML_FILES > img > > :attr {publish = ...} $WEB_FILES > > dosent work and gives a message about: > > Aap: Error in recipe: Copying a directory requires -r flag > > How do I set a recursive attribute on "img" (if that is the right way to do > it) or if someone got any pointer to examples etc? Looks like the question I asked a while ago about recursive copying which, at the time I asked, wasn't supported... It's a shame because I think it's a _very_ common case. --Jo |
From: Bram M. <Br...@mo...> - 2004-07-09 15:30:06
|
Fredrik wrote: > One last question (I hope :)). Now I want to upload a directory of images > called "img" recursive when publishing the site. I have read in the > archives[1] but the :tree thingy dosen't work as I expect. When experimenting > with :tree only the files in the "img" directory is published not the actual > "img" directory with files and subdirs. > > WEB_FILES = > $HTML_FILES > img > > :attr {publish = ...} $WEB_FILES > > dosent work and gives a message about: > > Aap: Error in recipe: Copying a directory requires -r flag That's right, publishing a directory isn't supported yet. > How do I set a recursive attribute on "img" (if that is the right way to do > it) or if someone got any pointer to examples etc? You somehow have to find all files in the "img" directory that you want to publish. You can use the :tree command for that, it does work since version 1.063. The examples will show you how to do it. -- Computers make very fast, very accurate, mistakes. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html /// |
From: Andreas P. <a.p...@ac...> - 2006-09-06 11:45:26
|
* Bram Moolenaar <Br...@mo...> [040709 17:40]: > > :attr {publish = ...} $WEB_FILES > > > > dosent work and gives a message about: > > > > Aap: Error in recipe: Copying a directory requires -r flag > > That's right, publishing a directory isn't supported yet. Is this still true? I'm using 1.072, would it help to go for the CVS version? -- Thank you, Andi |
From: calmar <ma...@ca...> - 2006-09-06 14:35:09
|
On Wed, Sep 06, 2006 at 01:44:51PM +0200, Andreas Poisel wrote: Hi Andi, just in case, http://www.calmar.ws/aap/index.html there are some recipies I use. (see recipes :) Not that it's smart to go the same way, but maybe it can help anyway. cheers marco For me, aap is a great help - since not 'that' much users seems to use it unfortunately, I'm always a little bit concerned - since I really want want to lose that great tool... > * Bram Moolenaar <Br...@mo...> [040709 17:40]: > > > :attr {publish = ...} $WEB_FILES > > > > > > dosent work and gives a message about: > > > > > > Aap: Error in recipe: Copying a directory requires -r flag > > > > That's right, publishing a directory isn't supported yet. > > Is this still true? I'm using 1.072, would it help to go for the CVS > version? > -- > Thank you, Andi > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > A-A-P-user mailing list > A-A...@li... > https://lists.sourceforge.net/lists/listinfo/a-a-p-user -- (o_ It rocks: LINUX + Command-Line-Interface //\ V_/_ http://www.calmar.ws |
From: <ma...@ca...> - 2006-09-06 20:02:20
|
On Wed, Sep 06, 2006 at 04:35:02PM +0200, calmar wrote: > On Wed, Sep 06, 2006 at 01:44:51PM +0200, Andreas Poisel wrote: > > Hi Andi, > > just in case, > > http://www.calmar.ws/aap/index.html > > there are some recipies I use. (see recipes :) > > Not that it's smart to go the same way, but maybe it can help > anyway. > > cheers > marco > > For me, aap is a great help - since not 'that' much users seems > to use it unfortunately, I'm always a little bit concerned - > since I really want want to lose that great tool... since I really *do not* want to lose that great tool ... I meant. Cheers and Thanks, marco > > > > > > * Bram Moolenaar <Br...@mo...> [040709 17:40]: > > > > :attr {publish = ...} $WEB_FILES > > > > > > > > dosent work and gives a message about: > > > > > > > > Aap: Error in recipe: Copying a directory requires -r flag > > > > > > That's right, publishing a directory isn't supported yet. > > > > Is this still true? I'm using 1.072, would it help to go for the CVS > > version? > > > > -- > > Thank you, Andi > > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > A-A-P-user mailing list > > A-A...@li... > > https://lists.sourceforge.net/lists/listinfo/a-a-p-user > > -- > (o_ It rocks: LINUX + Command-Line-Interface > //\ > V_/_ http://www.calmar.ws > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > A-A-P-user mailing list > A-A...@li... > https://lists.sourceforge.net/lists/listinfo/a-a-p-user -- http:/www.candrian.org |
From: Andreas P. <a.p...@ac...> - 2006-09-07 11:26:04
|
Hi Marco! * ma...@ca... <ma...@ca...> [060906 22:10]: > > http://www.calmar.ws/aap/index.html > > there are some recipies I use. (see recipes :) Great site, thank you! But I think it doesn't contain an answer to my question (is it still not possible to upload directories recursively using the ":publish" attribute?). I've been using aap for years for different tasks but I think it's time to take a look at the documentation again. I'm using a fraction of aap's features only, your page with commented examples is a great starting point. > since I really *do not* want to lose that great tool ... I meant. It's there and it's open source - I think it won't disappear. But maybe Bram could comment on the status and his future plans with A-A-P (if any). AFAIK the mailing list had been offline for awhile, that wasn't beneficial for the discussion here. But the documentation is really great, it answers most questions. So I think people _are_ using aap - silently. ;-) -- Thank you, Andreas |
From: <ma...@ca...> - 2006-09-07 13:54:13
|
On Thu, Sep 07, 2006 at 01:25:21PM +0200, Andreas Poisel wrote: Hi Andreas, > * ma...@ca... <ma...@ca...> [060906 22:10]: > > > > http://www.calmar.ws/aap/index.html > > > there are some recipies I use. (see recipes :) > > Great site, thank you! But I think it doesn't contain an answer to my > question (is it still not possible to upload directories recursively > using the ":publish" attribute?). Well, I dunno really. A workaround might be something like: ,--------------------------------------------- | :tree folder | files += $name | | :attr { publish = $(ftp_url)%file% } $files | | all : $files | :publish $files `--------------------------------------------- or similar. The only idea I have actually, I don't know aap really well so. Cheers marco |
From: Bram M. <Br...@mo...> - 2006-09-07 20:12:18
|
Andreas Poisel wrote: > > since I really *do not* want to lose that great tool ... I meant. > > It's there and it's open source - I think it won't disappear. But maybe > Bram could comment on the status and his future plans with A-A-P (if > any). There is a todo list, but I haven't been able to work on the items for a long time. I do fix bugs, but there have been only few the last year. The project is open for someone who wants to make improvements. > AFAIK the mailing list had been offline for awhile, that wasn't > beneficial for the discussion here. But the documentation is really > great, it answers most questions. So I think people _are_ using aap - > silently. ;-) I use it every day. Mostly for uploading website changes and distributing Vim files. -- `When any government, or any church for that matter, undertakes to say to its subjects, "This you may not read, this you must not see, this you are forbidden to know," the end result is tyranny and oppression no matter how holy the motives' -- Robert A Heinlein, "If this goes on --" /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// |
From: P. <pi...@ir...> - 2006-09-07 21:38:01
|
[Bram Moolenar] >I use [A-A-P] every day. So do I, yet probably less frequently than Bram, and probably less=20 universally as well, but I do like A-A-P: all the Makefiles I converted=20 get smaller, cleaner, and more legible. I should probably take another=20 serious dive in the documentation, as I'm getting rusted at always using=20 the same limited set of tricks :-). The only bit that I find irritating, and this since my very first days=20 with A-A-P, is all those prominent AAPDIR everywhere. It appears I'm=20 just unable to get used at seeing them. They also pollute inter-machine=20 synchronisation as the logs get renamed all the time. Bram says he does=20 not want to hide these directories, because names that would work on=20 every platform (yet there is already an `~/.aap/'). Moreover, as I almost never go the logs in AAPDIR, I observe they are=20 rarely useful in practice in my case. Not necessary that they should be=20 ditched, Bram says they are really useful when you need them. Still,=20 I wish aap be more discrete and hide AAPDIR somehow, and maybe refrain=20 from renaming log files. --=20 Fran=E7ois Pinard http://pinard.progiciels-bpi.ca |