raw nabble email content

current_raw_nabble_email_content.txt

Return-path: <[email protected]>
Envelope-to: [email protected]
Delivery-date: Thu, 07 Mar 2013 08:55:34 -0800
Received: from mail-la0-f42.google.com ([209.85.215.42])
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <[email protected]>)
	id 1UDe6P-00048w-Mq
	for [email protected]; Thu, 07 Mar 2013 08:55:34 -0800
Received: by mail-la0-f42.google.com with SMTP id fe20so736444lab.1
        for <[email protected]>; Thu, 07 Mar 2013 08:55:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:mime-version:in-reply-to:references:from:date:message-id
         :subject:to:content-type;
        bh=plXDiW8WBNBimWfpXHCIPb2EXGQ9gfT8LlaMIKvdLyk=;
        b=TUnlW/lwvHDmqNhvBBnyC7lJqS6DF+0jx/4dznAO3p1GDmRaGpTDrATXdRnfybo6HI
         tuhEIZFpztC08uRYl+WF5sou63rGcvayrwRrQIMmZRdbL0kdjnL6zOuvdVTNK2h2n1x6
         q1AB17cx1PHxz3D8smilPGCskW15qYsZELLD9XeNAYNqj6Q4GiAc2G/fgSiOnFoHdJu2
         r4Zmi9J55ZURsQA7ZVqnkiwN1u1JRL/c/n4rMJzUOFbB/b0t+/dP6X7bRdebgTvUywJX
         RWFA5iSH/Wa/dSSv6NASKN67G9ILcD8qAPdzPlmOs5Mor88KY40RbqUTiMiHxUY6Gl4I
         Bwhw==
X-Received: by 10.112.99.5 with SMTP id em5mr9000025lbb.1.1362675327459; Thu,
 07 Mar 2013 08:55:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.98.170 with HTTP; Thu, 7 Mar 2013 08:55:07 -0800 (PST)
In-Reply-To: <[email protected]>
References: <[email protected]> <[email protected]>
 <[email protected]>
From: Jason Porter <[email protected]>
Date: Thu, 7 Mar 2013 09:55:07 -0700
Message-ID: <CAF9TksOqsVTVLOGbz9f_ZdBMFLm15MGAcH6tag4xYR8iuDbBpg@mail.gmail.com>
Subject: Re: Asciidoctor backends
To: ""asotobu [via Asciidoctor :: Discussion]"" <[email protected]>
Content-Type: multipart/alternative; boundary=f46d0401f775d66dda04d758929f
X-SA-Exim-Connect-IP: 209.85.215.42
X-SA-Exim-Mail-From: [email protected]
X-SA-Exim-Scanned: No (on sam.nabble.com); SAEximRunCond expanded to false

--f46d0401f775d66dda04d758929f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I was just thinking about this in context of the maven and gradle plugins.
With these being a different gem, it

1. becomes difficult to add different backends for your build
2. knowing the exact location of the backends, will Ruby explode the jar?

I think we may need to readdress this idea of having the backends be
different gems.


On Thu, Mar 7, 2013 at 7:04 AM, asotobu [via Asciidoctor :: Discussion] <
[email protected]> wrote:

> Hi Paul,
> well first of all let me tell you that I am only developing backends
> (mainly because I have no idea of Ruby ), so some of questions you asking
> should be answered by Dan I guess . Well let's start with what I can
> answering you:
>
> - You do not require -b option, only -T pointing to backend directory, in
> https://github.com/asciidoctor/asciidoctor-backends#deckjs-backend you
> can see an instellation example.
>
> - I completely agree with you that we need some way to install backends i=
n
> a fashionable way, something like gem install and then the <backend> / or
> gem install extra-backends with all backends.
>
> - In case of documentation, for now we are using the README.md where we
> are documenting all supported backends. So if backends are treat as
> ""external"", I think it should be a link from official asciidoctor
> documentation to get backends repo.
>
> - About what you have noticed about ""official"" backends, I think that Dan
> would give you a better answer. By default asciidoc (and asciidoctor) com=
es
> with these two backends, and I think that in case of asciidoctor are not
> implemented as HAML or SLIM template, but as native ruby file (Tilt is no=
t
> used). So asciidoctor extension is implemented using Tilt gem, so if you
> want to provide an extension it should be done using this second approach=
.
> Keep in mind that in case of asciidoc, it is the way how it works.
>
> Of course feel free to ask me as many questions as you had, and I will tr=
y
> to answer it as better as possible, also keep in mind that Dan and all
> people of asciidoctor are improving it every week, so we should stay aler=
t
> about possible changes.
>
> And again for any question do not hesitate to contact me.
>
> Alex.
>
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
> http://discuss.asciidoctor.org/Asciidoctor-backends-tp16p24.html
>  To start a new topic under Asciidoctor :: Discussion, email
> [email protected]
> To unsubscribe from Asciidoctor :: Discussion, click here<http://discuss.=
asciidoctor.org/template/NamlServlet.jtp?macro=3Dunsubscribe_by_code&node=
=3D1&code=3DbGlnaHRndWFyZC5qcEBnbWFpbC5jb218MXw3NzU3OTU3MTg=3D>
> .
> NAML<http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=3Dmacr=
o_viewer&id=3Dinstant_html%21nabble%3Aemail.naml&base=3Dnabble.naml.namespa=
ces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web=
.template.NodeNamespace&breadcrumbs=3Dnotify_subscribers%21nabble%3Aemail.n=
aml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemai=
l.naml>
>



--=20
Jason Porter
http://en.gravatar.com/lightguardjp

--f46d0401f775d66dda04d758929f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D""ltr"">I was just thinking about this in context of the maven and=
 gradle plugins. With these being a different gem, it=C2=A0<div><br></div><=
div style>1. becomes difficult to add different backends for your build</di=
v><div style>

2. knowing the exact location of the backends, will Ruby explode the jar?</=
div><div style><br></div><div style>I think we may need to readdress this i=
dea of having the backends be different gems.</div></div><div class=3D""gmai=
l_extra"">

<br><br><div class=3D""gmail_quote"">On Thu, Mar 7, 2013 at 7:04 AM, asotobu =
[via Asciidoctor :: Discussion] <span dir=3D""ltr"">&lt;<a href=3D""mailto:ml-=
[email protected]"" target=3D""_blank"">ml-node+s49171n24h50@n6.=
nabble.com</a>&gt;</span> wrote:<br>

<blockquote class=3D""gmail_quote"" style=3D""margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"">

	Hi Paul,=20
<br>well first of all let me tell you that I am only developing backends (m=
ainly because I have no idea of Ruby <img>), so some of questions you askin=
g should be answered by Dan I guess <img>. Well let&#39;s start with what I=
 can answering you:
<br><br>- You do not require -b option, only -T pointing to backend directo=
ry, in <a href=3D""https://github.com/asciidoctor/asciidoctor-backends#deckj=
s-backend"" rel=3D""nofollow"" link=3D""external"" target=3D""_blank"">https://git=
hub.com/asciidoctor/asciidoctor-backends#deckjs-backend</a>=C2=A0you can se=
e an instellation example.
<br><br>- I completely agree with you that we need some way to install back=
ends in a fashionable way, something like gem install and then the &lt;back=
end&gt;=C2=A0/ or gem install extra-backends with all backends.
<br><br>- In case of documentation, for now we are using the README.md wher=
e we are documenting all supported backends. So if backends are treat as &q=
uot;external&quot;, I think it should be a link from official asciidoctor d=
ocumentation to get backends repo.
<br><br>- About what you have noticed about &quot;official&quot; backends, =
I think that Dan would give you a better answer. By default asciidoc (and a=
sciidoctor) comes with these two backends, and I think that in case of asci=
idoctor are not implemented as HAML or SLIM template, but as native ruby fi=
le (Tilt is not used). So asciidoctor extension is implemented using Tilt g=
em, so if you want to provide an extension it should be done using this sec=
ond approach. Keep in mind that in case of asciidoc, it is the way how it w=
orks.
<br><br>Of course feel free to ask me as many questions as you had, and I w=
ill try to answer it as better as possible, also keep in mind that Dan and =
all people of asciidoctor are improving it every week, so we should stay al=
ert about possible changes.
<br><br>And again for any question do not hesitate to contact me.
<br><br>Alex.
<br><br>
=09
	<br>
	<br>
	<hr noshade size=3D""1"" color=3D""#cccccc"">
	<div style=3D""color:#444;font:12px tahoma,geneva,helvetica,arial,sans-seri=
f""><div class=3D""im"">
		<div style=3D""font-weight:bold"">If you reply to this email, your message =
will be added to the discussion below:</div>
		</div><a href=3D""http://discuss.asciidoctor.org/Asciidoctor-backends-tp16=
p24.html"" target=3D""_blank"">http://discuss.asciidoctor.org/Asciidoctor-back=
ends-tp16p24.html</a>
	</div><div class=3D""HOEnZb""><div class=3D""h5"">
	<div style=3D""color:#666;font:11px tahoma,geneva,helvetica,arial,sans-seri=
f;margin-top:.4em;line-height:1.5em"">
		To start a new topic under Asciidoctor :: Discussion, email <a href=3D""ma=
ilto:ml-node%[email protected]"" target=3D""_blank"">ml-node+s49171n=
[email protected]</a> <br>
		To unsubscribe from Asciidoctor :: Discussion, <a href=3D""http://discuss.=
asciidoctor.org/template/NamlServlet.jtp?macro=3Dunsubscribe_by_code&amp;no=
de=3D1&amp;code=3DbGlnaHRndWFyZC5qcEBnbWFpbC5jb218MXw3NzU3OTU3MTg=3D"" targe=
t=3D""_blank"">click here</a>.<br>


		<a href=3D""http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=
=3Dmacro_viewer&amp;id=3Dinstant_html%21nabble%3Aemail.naml&amp;base=3Dnabb=
le.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-=
nabble.view.web.template.NodeNamespace&amp;breadcrumbs=3Dnotify_subscribers=
%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_em=
ail%21nabble%3Aemail.naml"" rel=3D""nofollow"" style=3D""font:9px serif"" target=
=3D""_blank"">NAML</a>
	</div></div></div></blockquote></div><br><br clear=3D""all""><div><br></div>=
-- <br><div dir=3D""ltr"">Jason Porter<br><a href=3D""http://en.gravatar.com/l=
ightguardjp"" target=3D""_blank"">http://en.gravatar.com/lightguardjp</a><br><=
/div>


</div>

--f46d0401f775d66dda04d758929f--

expected.txt

I was just thinking about this in context of the maven and gradle plugins.
With these being a different gem, it

1. becomes difficult to add different backends for your build
2. knowing the exact location of the backends, will Ruby explode the jar?

I think we may need to readdress this idea of having the backends be
different gems.

> Hi Paul,
> well first of all let me tell you that I am only developing backends
> (mainly because I have no idea of Ruby ), so some of questions you asking
> should be answered by Dan I guess . Well let's start with what I can
> answering you:
>
> - You do not require -b option, only -T pointing to backend directory, in
> https://github.com/asciidoctor/asciidoctor-backends#deckjs-backend you
> can see an instellation example.
>
> - I completely agree with you that we need some way to install backends in
> a fashionable way, something like gem install and then the <backend> / or
> gem install extra-backends with all backends.
>
> - In case of documentation, for now we are using the README.md where we
> are documenting all supported backends. So if backends are treat as
> ""external"", I think it should be a link from official asciidoctor
> documentation to get backends repo.
>
> - About what you have noticed about ""official"" backends, I think that Dan
> would give you a better answer. By default asciidoc (and asciidoctor) comes
> with these two backends, and I think that in case of asciidoctor are not
> implemented as HAML or SLIM template, but as native ruby file (Tilt is not
> used). So asciidoctor extension is implemented using Tilt gem, so if you
> want to provide an extension it should be done using this second approach.
> Keep in mind that in case of asciidoc, it is the way how it works.
>
> Of course feel free to ask me as many questions as you had, and I will try
> to answer it as better as possible, also keep in mind that Dan and all
> people of asciidoctor are improving it every week, so we should stay alert
> about possible changes.
>
> And again for any question do not hesitate to contact me.
>
> Alex.
>

--
Jason Porter
http://en.gravatar.com/lightguardjp