Re: [web2py] Re: static blog
Thanks. That would be great. On Saturday, September 8, 2012 8:31:16 AM UTC+12, Massimo Di Pierro wrote: Yes. I will post the script soon. I need to fix it because I changed the markmin syntax of links so my previous script broke. On Friday, 7 September 2012 14:58:06 UTC-5, Andrew W wrote: Thanks. My intention is to make , and print, a PDF of the markmin content, just like the book. For disaster recovery doco, I want a hard copy. With the new book app, are you still planning to have available a PDF from the files? --
[web2py] Re: static blog
+1
I see you used some of the book code in the book. In particular you use
MARKMIN the way it is done in the book using extra variables. That is ok
and it is done for backward compatibility with old book sources which also
need to processed in latex. If that is not important there is a batter way
to use markmin:
from gluon.contrib.autolinks import expand_one
html = MARKMIN(page.body,url=True,environment={},
autolinks=lambda link: expand_one(link,{})).xml()
Because url = True you will be able to use the @ notation to reference
any URL in the app. The book code prevents that for backward compatibility.
autolinks=lambda link: expand_one(link,{}) enables OMEBED which means if
you do not have to markup links. Web2py will automatically embed, images
video and other objects using the OEMBED protocol.
Massimo
On Friday, 7 September 2012 07:01:21 UTC-5, Martin.Mulone wrote:
http://blog.martinmulone.com.ar/post/996-static-blog-in-web2py
--
http://martinmulone.com.ar
--
Re: [web2py] Re: static blog
Yes is based on the book app. I made some changes, in the index I made a
change that read extract.markmin because abstract in info.txt is to short
in lenght, but I have to render to a file like chapters because is to
slow to read it all the time to make an index of posts. Ok I'm going to
change this on markmin. Also is not need it for this porpouse to create a
subfolder, so I create post-XXX.html and for index pages posts-X.html.
The blog is based on this.
2012/9/7 Massimo Di Pierro massimo.dipie...@gmail.com
+1
I see you used some of the book code in the book. In particular you use
MARKMIN the way it is done in the book using extra variables. That is ok
and it is done for backward compatibility with old book sources which also
need to processed in latex. If that is not important there is a batter way
to use markmin:
from gluon.contrib.autolinks import expand_one
html = MARKMIN(page.body,url=True,environment={},
autolinks=lambda link: expand_one(link,{})).xml()
Because url = True you will be able to use the @ notation to reference
any URL in the app. The book code prevents that for backward compatibility.
autolinks=lambda link: expand_one(link,{}) enables OMEBED which means if
you do not have to markup links. Web2py will automatically embed, images
video and other objects using the OEMBED protocol.
Massimo
On Friday, 7 September 2012 07:01:21 UTC-5, Martin.Mulone wrote:
http://blog.martinmulone.com.**ar/post/996-static-blog-in-**web2pyhttp://blog.martinmulone.com.ar/post/996-static-blog-in-web2py
--
http://martinmulone.com.ar
--
--
http://martinmulone.com.ar
--
Re: [web2py] Re: static blog
You are missing an administrator, or is it just me?
Ovidio Marinho Falcao Neto
Web Developer
ovidio...@gmail.com
ovidiomari...@itjp.net.br
ITJP - itjp.net.br
83 8826 9088 - Oi
83 9334 0266 - Claro
Brasil
2012/9/7 Martín Mulone mulone.mar...@gmail.com
Yes is based on the book app. I made some changes, in the index I made a
change that read extract.markmin because abstract in info.txt is to short
in lenght, but I have to render to a file like chapters because is to
slow to read it all the time to make an index of posts. Ok I'm going to
change this on markmin. Also is not need it for this porpouse to create a
subfolder, so I create post-XXX.html and for index pages posts-X.html.
The blog is based on this.
2012/9/7 Massimo Di Pierro massimo.dipie...@gmail.com
+1
I see you used some of the book code in the book. In particular you use
MARKMIN the way it is done in the book using extra variables. That is ok
and it is done for backward compatibility with old book sources which also
need to processed in latex. If that is not important there is a batter way
to use markmin:
from gluon.contrib.autolinks import expand_one
html = MARKMIN(page.body,url=True,environment={},
autolinks=lambda link: expand_one(link,{})).xml()
Because url = True you will be able to use the @ notation to
reference any URL in the app. The book code prevents that for backward
compatibility.
autolinks=lambda link: expand_one(link,{}) enables OMEBED which means if
you do not have to markup links. Web2py will automatically embed, images
video and other objects using the OEMBED protocol.
Massimo
On Friday, 7 September 2012 07:01:21 UTC-5, Martin.Mulone wrote:
http://blog.martinmulone.com.**ar/post/996-static-blog-in-**web2pyhttp://blog.martinmulone.com.ar/post/996-static-blog-in-web2py
--
http://martinmulone.com.ar
--
--
http://martinmulone.com.ar
--
--
Re: [web2py] Re: static blog
I'm not sure if I understand, there no admin, you make post copying and
pasting new folder under source_blog in the app, and editing files using
your favorite editor like gedit, ultraedit, any ide, etc.
2012/9/7 Ovidio Marinho ovidio...@gmail.com
You are missing an administrator, or is it just me?
Ovidio Marinho Falcao Neto
Web Developer
ovidio...@gmail.com
ovidiomari...@itjp.net.br
ITJP - itjp.net.br
83 8826 9088 - Oi
83 9334 0266 - Claro
Brasil
2012/9/7 Martín Mulone mulone.mar...@gmail.com
Yes is based on the book app. I made some changes, in the index I made a
change that read extract.markmin because abstract in info.txt is to short
in lenght, but I have to render to a file like chapters because is to
slow to read it all the time to make an index of posts. Ok I'm going to
change this on markmin. Also is not need it for this porpouse to create a
subfolder, so I create post-XXX.html and for index pages posts-X.html.
The blog is based on this.
2012/9/7 Massimo Di Pierro massimo.dipie...@gmail.com
+1
I see you used some of the book code in the book. In particular you use
MARKMIN the way it is done in the book using extra variables. That is ok
and it is done for backward compatibility with old book sources which also
need to processed in latex. If that is not important there is a batter way
to use markmin:
from gluon.contrib.autolinks import expand_one
html = MARKMIN(page.body,url=True,environment={},
autolinks=lambda link: expand_one(link,{})).xml()
Because url = True you will be able to use the @ notation to
reference any URL in the app. The book code prevents that for backward
compatibility.
autolinks=lambda link: expand_one(link,{}) enables OMEBED which means if
you do not have to markup links. Web2py will automatically embed, images
video and other objects using the OEMBED protocol.
Massimo
On Friday, 7 September 2012 07:01:21 UTC-5, Martin.Mulone wrote:
http://blog.martinmulone.com.**ar/post/996-static-blog-in-**web2pyhttp://blog.martinmulone.com.ar/post/996-static-blog-in-web2py
--
http://martinmulone.com.ar
--
--
http://martinmulone.com.ar
--
--
--
http://martinmulone.com.ar
--
Re: [web2py] Re: static blog
Good work Martin, I was thinking of looking at the book app for the same purpose. I want to document some Disaster Recovery procedures, so I therefore also need to create a PDF version as well. Do you think the book app vs auth.wiki() is better (easier?) for generating PDFs.? So many choices! --
Re: [web2py] Re: static blog
book app and this are static generation of the content, focus on lightweight aproach. Auth.wiki is all included is a cms, auth, edit create, delete system grid, etc. I think you can render a pdf with no problem from markmin. 2012/9/7 Andrew W awillima...@gmail.com Good work Martin, I was thinking of looking at the book app for the same purpose. I want to document some Disaster Recovery procedures, so I therefore also need to create a PDF version as well. Do you think the book app vs auth.wiki() is better (easier?) for generating PDFs.? So many choices! -- -- http://martinmulone.com.ar --
Re: [web2py] Re: static blog
If you use:
from gluon.contrib.autolinks import expand_one
html = MARKMIN(page.body,url=True,environment={},
autolinks=lambda link: expand_one(link,{})).xml()
embedding in markmin any link to a public document (pdf, doc, docx, xls,
etc.) will call google doc viewer and embed the viewer for the document.
Massimo
On Friday, 7 September 2012 14:41:05 UTC-5, Martin.Mulone wrote:
book app and this are static generation of the content, focus on
lightweight aproach. Auth.wiki is all included is a cms, auth, edit create,
delete system grid, etc. I think you can render a pdf with no problem from
markmin.
2012/9/7 Andrew W awill...@gmail.com javascript:
Good work Martin,
I was thinking of looking at the book app for the same purpose.
I want to document some Disaster Recovery procedures, so I therefore
also need to create a PDF version as well. Do you think the book app vs
auth.wiki() is better (easier?) for generating PDFs.?
So many choices!
--
--
http://martinmulone.com.ar
--
Re: [web2py] Re: static blog
Thanks. My intention is to make , and print, a PDF of the markmin content, just like the book. For disaster recovery doco, I want a hard copy. With the new book app, are you still planning to have available a PDF from the files? --
Re: [web2py] Re: static blog
Yes. I will post the script soon. I need to fix it because I changed the markmin syntax of links so my previous script broke. On Friday, 7 September 2012 14:58:06 UTC-5, Andrew W wrote: Thanks. My intention is to make , and print, a PDF of the markmin content, just like the book. For disaster recovery doco, I want a hard copy. With the new book app, are you still planning to have available a PDF from the files? --
