Using PlantUML and blockdiag with asciidoctor

classic Classic list List threaded Threaded
56 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Using PlantUML and blockdiag with asciidoctor

wimalopaan
Hi all,

are there any activities to provide the same functionality as with the
plantuml and blockdiag plugins in asciidoc?

Regards,
 Wilhelm
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

asotobu
Hello and welcome,

currently I am working in developing asciidoctorj extensions but for JBehave. Help will be welcomed, you can write extensions in Ruby or in JVM language so if you want to start an extension for ditaa or planetUML don't hesitate to contact us here.

BTW let me tell you that these integrations are on my list too.
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

wimalopaan
Hi,

Am 18.12.2013 15:39, schrieb asotobu [via Asciidoctor :: Discussion]:
> Hello and welcome,
>
> currently I am working in developing asciidoctorj extensions but for
> JBehave. Help will be welcomed, you can write extensions in Ruby or in
> JVM language so if you want to start an extension for ditaa or planetUML
> don't hesitate to contact us here.
>
> BTW let me tell you that these integrations are on my list too.

this is very good news to me - do you have a timeline for this?


--
Wilhelm
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

asotobu
Sadly there is no timeline :( it is something that I had in my "backlog" but not prioritized, because now I am focused on releasing new version of asciidoctorj and integrating it with jbehave and cucumber.  Are you using Asciidoctor or AsciidoctorJ?


2013/12/23 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]>
Hi,

Am 18.12.2013 15:39, schrieb asotobu [via Asciidoctor :: Discussion]:
> Hello and welcome,
>
> currently I am working in developing asciidoctorj extensions but for
> JBehave. Help will be welcomed, you can write extensions in Ruby or in
> JVM language so if you want to start an extension for ditaa or planetUML
> don't hesitate to contact us here.
>
> BTW let me tell you that these integrations are on my list too.

this is very good news to me - do you have a timeline for this?


--
Wilhelm
[hidden email]



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1223.html
To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML



--
+----------------------------------------------------------+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+----------------------------------------------------------+
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

wimalopaan
Hi,

Am 23.12.2013 11:00, schrieb asotobu [via Asciidoctor :: Discussion]:
> Sadly there is no timeline :( it is something that I had in my "backlog"
> but not prioritized, because now I am focused on releasing new version
> of asciidoctorj and integrating it with jbehave and cucumber.  Are you
> using Asciidoctor or AsciidoctorJ?

sorry for my ignorance: I'm trying to use asciidoctor as an in-place
replacement for my asciidoc usage (mainly because the indferior
performance ...). What ist the difference between asciidoctor and
asciidoctorJ ?

Merry Christmas,
 Wilhelm

>
>
> 2013/12/23 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
> </user/SendEmail.jtp?type=node&node=1224&i=0>>
>
>     Hi,
>
>     Am 18.12.2013 15:39, schrieb asotobu [via Asciidoctor :: Discussion]:
>     > Hello and welcome,
>     >
>     > currently I am working in developing asciidoctorj extensions but for
>     > JBehave. Help will be welcomed, you can write extensions in Ruby
>     or in
>     > JVM language so if you want to start an extension for ditaa or
>     planetUML
>     > don't hesitate to contact us here.
>     >
>     > BTW let me tell you that these integrations are on my list too.
>
>     this is very good news to me - do you have a timeline for this?
>
>     >
>     >
>     ------------------------------------------------------------------------
>
>     > If you reply to this email, your message will be added to the
>     discussion
>     > below:
>     >
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1209.html
>     >
>     > To start a new topic under Asciidoctor :: Discussion, email
>     > [hidden email] <http://user/SendEmail.jtp?type=node&node=1223&i=0>
>     > To unsubscribe from Asciidoctor :: Discussion, click here
>     > <
>     > NAML
>     >
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>
>
>     --
>     Wilhelm
>     [hidden email] <http://user/SendEmail.jtp?type=node&node=1223&i=1>
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1223.html
>
>     To unsubscribe from Using PlantUML and blockdiag with asciidoctor,
>     click here.
>     NAML
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
>
> --
> +----------------------------------------------------------+
>   Alex Soto Bueno - Computer Engineer
>   www.lordofthejars.com <http://www.lordofthejars.com>
> +----------------------------------------------------------+
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1224.html
>
> To start a new topic under Asciidoctor :: Discussion, email
> [hidden email]
> To unsubscribe from Asciidoctor :: Discussion, click here
> <
> NAML
> <
http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>


--
Wilhelm
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

asotobu
Merry Christmas!!!

There is nothing to forgive. Asciidoctor is the Ruby implementation for rendering AsciiDoc documents. AsciidoctorJ is an implementation in Java (in fact inside it is using Ruby implementation) for rendering AsciiDoc inside Java (for example using Maven, Gradle, Servlets, ...) I think you are using the Ruby one right?


2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]>
Hi,

Am <a href="tel:23.12.2013%2011" value="+12312201311" target="_blank">23.12.2013 11:00, schrieb asotobu [via Asciidoctor :: Discussion]:
> Sadly there is no timeline :( it is something that I had in my "backlog"
> but not prioritized, because now I am focused on releasing new version
> of asciidoctorj and integrating it with jbehave and cucumber.  Are you
> using Asciidoctor or AsciidoctorJ?

sorry for my ignorance: I'm trying to use asciidoctor as an in-place
replacement for my asciidoc usage (mainly because the indferior
performance ...). What ist the difference between asciidoctor and
asciidoctorJ ?

Merry Christmas,
 Wilhelm

>
>
> 2013/12/23 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
> </user/SendEmail.jtp?type=node&node=1224&i=0>>
>
>     Hi,
>
>     Am 18.12.2013 15:39, schrieb asotobu [via Asciidoctor :: Discussion]:
>     > Hello and welcome,
>     >
>     > currently I am working in developing asciidoctorj extensions but for
>     > JBehave. Help will be welcomed, you can write extensions in Ruby
>     or in
>     > JVM language so if you want to start an extension for ditaa or
>     planetUML
>     > don't hesitate to contact us here.
>     >
>     > BTW let me tell you that these integrations are on my list too.
>
>     this is very good news to me - do you have a timeline for this?
>
>     >
>     >
>     ------------------------------------------------------------------------
>
>     > If you reply to this email, your message will be added to the
>     discussion
>     > below:
>     >
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1209.html
>     >

>     > To start a new topic under Asciidoctor :: Discussion, email
>     > [hidden email] <http://user/SendEmail.jtp?type=node&node=1223&i=0>
>     > To unsubscribe from Asciidoctor :: Discussion, click here
>     > <
>     > NAML
>     >
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>
>
>     --
>     Wilhelm
>     [hidden email] <http://user/SendEmail.jtp?type=node&node=1223&i=1>
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1223.html
>

>     To unsubscribe from Using PlantUML and blockdiag with asciidoctor,
>     click here.
>     NAML
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
>
> --
> +----------------------------------------------------------+
>   Alex Soto Bueno - Computer Engineer
>   www.lordofthejars.com <http://www.lordofthejars.com>
> +----------------------------------------------------------+
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1224.html
>
> To start a new topic under Asciidoctor :: Discussion, email
> [hidden email]
> To unsubscribe from Asciidoctor :: Discussion, click here
> <
> NAML
> <
http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>


--
Wilhelm
[hidden email]



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1227.html
To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML



--
+----------------------------------------------------------+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+----------------------------------------------------------+
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

wimalopaan
Am 24.12.2013 12:35, schrieb asotobu [via Asciidoctor :: Discussion]:
> Merry Christmas!!!
>
> There is nothing to forgive. Asciidoctor is the Ruby implementation for
> rendering AsciiDoc documents. AsciidoctorJ is an implementation in Java
> (in fact inside it is using Ruby implementation) for rendering AsciiDoc
> inside Java (for example using Maven, Gradle, Servlets, ...) I think you
> are using the Ruby one right?

Yes, indeed.

>
>
> 2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
> </user/SendEmail.jtp?type=node&node=1228&i=0>>
>
>     Hi,
>
>     Am <a href="tel:23.12.2013%2011" value="+12312201311"
>     target="_blank">23.12.2013 11:00, schrieb asotobu [via Asciidoctor
>     :: Discussion]:
>     > Sadly there is no timeline :( it is something that I had in my
>     "backlog"
>     > but not prioritized, because now I am focused on releasing new
>     version
>     > of asciidoctorj and integrating it with jbehave and cucumber.  Are
>     you
>     > using Asciidoctor or AsciidoctorJ?
>
>     sorry for my ignorance: I'm trying to use asciidoctor as an in-place
>     replacement for my asciidoc usage (mainly because the indferior
>     performance ...). What ist the difference between asciidoctor and
>     asciidoctorJ ?
>
>     Merry Christmas,
>      Wilhelm
>
>     >
>     >
>     > 2013/12/23 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
>     > </user/SendEmail.jtp?type=node&node=1224&i=0>>
>     >
>     >     Hi,
>     >
>     >     Am 18.12.2013 15:39, schrieb asotobu [via Asciidoctor ::
>     Discussion]:
>     >     > Hello and welcome,
>     >     >
>     >     > currently I am working in developing asciidoctorj extensions
>     but for
>     >     > JBehave. Help will be welcomed, you can write extensions in
>     Ruby
>     >     or in
>     >     > JVM language so if you want to start an extension for ditaa or
>     >     planetUML
>     >     > don't hesitate to contact us here.
>     >     >
>     >     > BTW let me tell you that these integrations are on my list too.
>     >
>     >     this is very good news to me - do you have a timeline for this?
>     >
>     >     >
>     >     >
>     >    
>     ------------------------------------------------------------------------
>
>     >
>     >     > If you reply to this email, your message will be added to the
>     >     discussion
>     >     > below:
>     >     >
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1209.html
>     >     >
>
>     >     > To start a new topic under Asciidoctor :: Discussion, email
>     >     > [hidden email]
>     <http://user/SendEmail.jtp?type=node&node=1223&i=0>
>     >     > To unsubscribe from Asciidoctor :: Discussion, click here
>     >     > <
>     >     > NAML
>     >     >
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >     >
>     >
>     >
>     >     --
>     >     Wilhelm
>     >     [hidden email]
>     <http://user/SendEmail.jtp?type=node&node=1223&i=1>
>     >
>     >
>     >    
>     ------------------------------------------------------------------------
>
>     >     If you reply to this email, your message will be added to the
>     >     discussion below:
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1223.html
>     >
>
>     >     To unsubscribe from Using PlantUML and blockdiag with
>     asciidoctor,
>     >     click here.
>     >     NAML
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >
>     >
>     >
>     >
>     > --
>     > +----------------------------------------------------------+
>     >   Alex Soto Bueno - Computer Engineer
>     >   www.lordofthejars.com <http://www.lordofthejars.com>
>     <http://www.lordofthejars.com>
>     > +----------------------------------------------------------+
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>
>     > If you reply to this email, your message will be added to the
>     discussion
>     > below:
>     >
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1224.html
>     >
>     > To start a new topic under Asciidoctor :: Discussion, email
>     > [hidden email] <http://user/SendEmail.jtp?type=node&node=1227&i=0>
>     > To unsubscribe from Asciidoctor :: Discussion, click here
>     > <
>     > NAML
>     >
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>
>
>     --
>     Wilhelm
>     [hidden email] <http://user/SendEmail.jtp?type=node&node=1227&i=1>
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1227.html
>
>     To unsubscribe from Using PlantUML and blockdiag with asciidoctor,
>     click here.
>     NAML
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
>
> --
> +----------------------------------------------------------+
>   Alex Soto Bueno - Computer Engineer
>   www.lordofthejars.com <http://www.lordofthejars.com>
> +----------------------------------------------------------+
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1228.html
>
> To start a new topic under Asciidoctor :: Discussion, email
> [hidden email]
> To unsubscribe from Asciidoctor :: Discussion, click here
> <
> NAML
> <
http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>


--
Wilhelm
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

asotobu
Ok then I will implement first in Ruby language, or if you know Ruby feel free to create the extension we can create a repo to store it.


2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]>
Am 24.12.2013 12:35, schrieb asotobu [via Asciidoctor :: Discussion]:
> Merry Christmas!!!
>
> There is nothing to forgive. Asciidoctor is the Ruby implementation for
> rendering AsciiDoc documents. AsciidoctorJ is an implementation in Java
> (in fact inside it is using Ruby implementation) for rendering AsciiDoc
> inside Java (for example using Maven, Gradle, Servlets, ...) I think you
> are using the Ruby one right?

Yes, indeed.

>
>
> 2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
> </user/SendEmail.jtp?type=node&node=1228&i=0>>
>
>     Hi,
>
>     Am <a href="tel:23.12.2013%2011" value="<a href="tel:%2B12312201311" value="+12312201311" target="_blank">+12312201311"
>     target="_blank"><a href="tel:23.12.2013%2011" value="+12312201311" target="_blank">23.12.2013 11:00, schrieb asotobu [via Asciidoctor
>     :: Discussion]:

>     > Sadly there is no timeline :( it is something that I had in my
>     "backlog"
>     > but not prioritized, because now I am focused on releasing new
>     version
>     > of asciidoctorj and integrating it with jbehave and cucumber.  Are
>     you
>     > using Asciidoctor or AsciidoctorJ?
>
>     sorry for my ignorance: I'm trying to use asciidoctor as an in-place
>     replacement for my asciidoc usage (mainly because the indferior
>     performance ...). What ist the difference between asciidoctor and
>     asciidoctorJ ?
>
>     Merry Christmas,
>      Wilhelm
>
>     >
>     >
>     > 2013/12/23 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
>     > </user/SendEmail.jtp?type=node&node=1224&i=0>>
>     >
>     >     Hi,
>     >
>     >     Am 18.12.2013 15:39, schrieb asotobu [via Asciidoctor ::
>     Discussion]:
>     >     > Hello and welcome,
>     >     >
>     >     > currently I am working in developing asciidoctorj extensions
>     but for
>     >     > JBehave. Help will be welcomed, you can write extensions in
>     Ruby
>     >     or in
>     >     > JVM language so if you want to start an extension for ditaa or
>     >     planetUML
>     >     > don't hesitate to contact us here.
>     >     >
>     >     > BTW let me tell you that these integrations are on my list too.
>     >
>     >     this is very good news to me - do you have a timeline for this?
>     >
>     >     >
>     >     >
>     >    
>     ------------------------------------------------------------------------
>
>     >
>     >     > If you reply to this email, your message will be added to the
>     >     discussion
>     >     > below:
>     >     >
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1209.html
>     >     >

>
>     >     > To start a new topic under Asciidoctor :: Discussion, email
>     >     > [hidden email]
>     <http://user/SendEmail.jtp?type=node&node=1223&i=0>
>     >     > To unsubscribe from Asciidoctor :: Discussion, click here
>     >     > <
>     >     > NAML
>     >     >
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >     >
>     >
>     >
>     >     --
>     >     Wilhelm
>     >     [hidden email]
>     <http://user/SendEmail.jtp?type=node&node=1223&i=1>
>     >
>     >
>     >    
>     ------------------------------------------------------------------------
>
>     >     If you reply to this email, your message will be added to the
>     >     discussion below:
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1223.html
>     >

>
>     >     To unsubscribe from Using PlantUML and blockdiag with
>     asciidoctor,
>     >     click here.
>     >     NAML
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >
>     >
>     >
>     >
>     > --
>     > +----------------------------------------------------------+
>     >   Alex Soto Bueno - Computer Engineer
>     >   www.lordofthejars.com <http://www.lordofthejars.com>
>     <http://www.lordofthejars.com>
>     > +----------------------------------------------------------+
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>
>     > If you reply to this email, your message will be added to the
>     discussion
>     > below:
>     >
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1224.html
>     >
>     > To start a new topic under Asciidoctor :: Discussion, email
>     > [hidden email] <http://user/SendEmail.jtp?type=node&node=1227&i=0>
>     [hidden email] <http://user/SendEmail.jtp?type=node&node=1227&i=1>
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1227.html
>
>     To unsubscribe from Using PlantUML and blockdiag with asciidoctor,
>     click here.
>     NAML
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

>
>
>
>
>
> --
> +----------------------------------------------------------+
>   Alex Soto Bueno - Computer Engineer
>   www.lordofthejars.com <http://www.lordofthejars.com>
> +----------------------------------------------------------+
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1228.html


--
Wilhelm
[hidden email]



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1229.html
To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML



--
+----------------------------------------------------------+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+----------------------------------------------------------+
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

wimalopaan
Am 24.12.2013 12:51, schrieb asotobu [via Asciidoctor :: Discussion]:
> Ok then I will implement first in Ruby language,

great!

> or if you know Ruby
> feel free to create the extension we can create a repo to store it.

impossible, I'm ruby-agnostic ;-)

>
>
> 2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
> </user/SendEmail.jtp?type=node&node=1230&i=0>>
>
>     Am 24.12.2013 12:35, schrieb asotobu [via Asciidoctor :: Discussion]:
>     > Merry Christmas!!!
>     >
>     > There is nothing to forgive. Asciidoctor is the Ruby
>     implementation for
>     > rendering AsciiDoc documents. AsciidoctorJ is an implementation in
>     Java
>     > (in fact inside it is using Ruby implementation) for rendering
>     AsciiDoc
>     > inside Java (for example using Maven, Gradle, Servlets, ...) I
>     think you
>     > are using the Ruby one right?
>
>     Yes, indeed.
>
>     >
>     >
>     > 2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
>     > </user/SendEmail.jtp?type=node&node=1228&i=0>>
>     >
>     >     Hi,
>     >
>     >     Am <a href="tel:23.12.2013%2011" value="<a
>     href="tel:%2B12312201311" value="+12312201311"
>     target="_blank">+12312201311"
>     >     target="_blank"><a href="tel:23.12.2013%2011"
>     value="+12312201311" target="_blank">23.12.2013 11:00, schrieb
>     asotobu [via Asciidoctor
>     >     :: Discussion]:
>
>     >     > Sadly there is no timeline :( it is something that I had in my
>     >     "backlog"
>     >     > but not prioritized, because now I am focused on releasing new
>     >     version
>     >     > of asciidoctorj and integrating it with jbehave and
>     cucumber.  Are
>     >     you
>     >     > using Asciidoctor or AsciidoctorJ?
>     >
>     >     sorry for my ignorance: I'm trying to use asciidoctor as an
>     in-place
>     >     replacement for my asciidoc usage (mainly because the indferior
>     >     performance ...). What ist the difference between asciidoctor and
>     >     asciidoctorJ ?
>     >
>     >     Merry Christmas,
>     >      Wilhelm
>     >
>     >     >
>     >     >
>     >     > 2013/12/23 wimalopaan [via Asciidoctor :: Discussion]
>     <[hidden email]
>     >     > </user/SendEmail.jtp?type=node&node=1224&i=0>>
>     >     >
>     >     >     Hi,
>     >     >
>     >     >     Am 18.12.2013 15:39, schrieb asotobu [via Asciidoctor ::
>     >     Discussion]:
>     >     >     > Hello and welcome,
>     >     >     >
>     >     >     > currently I am working in developing asciidoctorj
>     extensions
>     >     but for
>     >     >     > JBehave. Help will be welcomed, you can write
>     extensions in
>     >     Ruby
>     >     >     or in
>     >     >     > JVM language so if you want to start an extension for
>     ditaa or
>     >     >     planetUML
>     >     >     > don't hesitate to contact us here.
>     >     >     >
>     >     >     > BTW let me tell you that these integrations are on my
>     list too.
>     >     >
>     >     >     this is very good news to me - do you have a timeline
>     for this?
>     >     >
>     >     >     >
>     >     >     >
>     >     >    
>     >    
>     ------------------------------------------------------------------------
>
>     >
>     >     >
>     >     >     > If you reply to this email, your message will be added
>     to the
>     >     >     discussion
>     >     >     > below:
>     >     >     >
>     >     >    
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1209.html
>     >     >     >
>
>     >
>     >     >     > To start a new topic under Asciidoctor :: Discussion,
>     email
>     >     >     > [hidden email]
>     >     <http://user/SendEmail.jtp?type=node&node=1223&i=0>
>     >     >     > To unsubscribe from Asciidoctor :: Discussion, click here
>     >     >     > <
>     >     >     > NAML
>     >     >     >
>     >     >    
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >     >
>     >     >     >
>     >     >
>     >     >
>     >     >     --
>     >     >     Wilhelm
>     >     >     [hidden email]
>     >     <http://user/SendEmail.jtp?type=node&node=1223&i=1>
>     >     >
>     >     >
>     >     >    
>     >    
>     ------------------------------------------------------------------------
>
>     >
>     >     >     If you reply to this email, your message will be added
>     to the
>     >     >     discussion below:
>     >     >    
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1223.html
>     >     >
>
>     >
>     >     >     To unsubscribe from Using PlantUML and blockdiag with
>     >     asciidoctor,
>     >     >     click here.
>     >     >     NAML
>     >     >    
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     > --
>     >     > +----------------------------------------------------------+
>     >     >   Alex Soto Bueno - Computer Engineer
>     >     >   www.lordofthejars.com <http://www.lordofthejars.com>
>     <http://www.lordofthejars.com>
>     >     <http://www.lordofthejars.com>
>     >     > +----------------------------------------------------------+
>     >     >
>     >     >
>     >     >
>     >    
>     ------------------------------------------------------------------------
>
>     >
>     >     > If you reply to this email, your message will be added to the
>     >     discussion
>     >     > below:
>     >     >
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1224.html
>     >     >
>     >     > To start a new topic under Asciidoctor :: Discussion, email
>     >     > [hidden email]
>     <http://user/SendEmail.jtp?type=node&node=1227&i=0>
>     >     > To unsubscribe from Asciidoctor :: Discussion, click here
>
>     >     > <
>     >     > NAML
>     >     >
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >     >
>     >
>     >
>     >     --
>     >     Wilhelm
>     >     [hidden email]
>     <http://user/SendEmail.jtp?type=node&node=1227&i=1>
>     >
>     >
>     >    
>     ------------------------------------------------------------------------
>
>     >     If you reply to this email, your message will be added to the
>     >     discussion below:
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1227.html
>     >
>     >     To unsubscribe from Using PlantUML and blockdiag with
>     asciidoctor,
>     >     click here.
>     >     NAML
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>     >
>     >
>     >
>     >
>     >
>     > --
>     > +----------------------------------------------------------+
>     >   Alex Soto Bueno - Computer Engineer
>     >   www.lordofthejars.com <http://www.lordofthejars.com>
>     <http://www.lordofthejars.com>
>     > +----------------------------------------------------------+
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>
>     > If you reply to this email, your message will be added to the
>     discussion
>     > below:
>     >
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1228.html
>
>     >
>     > To start a new topic under Asciidoctor :: Discussion, email
>     > [hidden email] <http://user/SendEmail.jtp?type=node&node=1229&i=0>
>     > To unsubscribe from Asciidoctor :: Discussion, click here
>     > <
>     > NAML
>     >
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>
>
>     --
>     Wilhelm
>     [hidden email] <http://user/SendEmail.jtp?type=node&node=1229&i=1>
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1229.html
>
>     To unsubscribe from Using PlantUML and blockdiag with asciidoctor,
>     click here.
>     NAML
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
>
> --
> +----------------------------------------------------------+
>   Alex Soto Bueno - Computer Engineer
>   www.lordofthejars.com <http://www.lordofthejars.com>
> +----------------------------------------------------------+
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1230.html
>
> To start a new topic under Asciidoctor :: Discussion, email
> [hidden email]
> To unsubscribe from Asciidoctor :: Discussion, click here
> <
> NAML
> <
http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>


--
Wilhelm
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

asotobu
And Java agnostic too? :) you can even write extensions in Java. :)


2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]>
Am 24.12.2013 12:51, schrieb asotobu [via Asciidoctor :: Discussion]:
> Ok then I will implement first in Ruby language,

great!

> or if you know Ruby
> feel free to create the extension we can create a repo to store it.

impossible, I'm ruby-agnostic ;-)

>
>
> 2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
> </user/SendEmail.jtp?type=node&node=1230&i=0>>
>

>     Am 24.12.2013 12:35, schrieb asotobu [via Asciidoctor :: Discussion]:
>     > Merry Christmas!!!
>     >
>     > There is nothing to forgive. Asciidoctor is the Ruby
>     implementation for
>     > rendering AsciiDoc documents. AsciidoctorJ is an implementation in
>     Java
>     > (in fact inside it is using Ruby implementation) for rendering
>     AsciiDoc
>     > inside Java (for example using Maven, Gradle, Servlets, ...) I
>     think you
>     > are using the Ruby one right?
>
>     Yes, indeed.
>
>     >
>     >
>     > 2013/12/24 wimalopaan [via Asciidoctor :: Discussion] <[hidden email]
>     > </user/SendEmail.jtp?type=node&node=1228&i=0>>
>     >
>     >     Hi,
>     >
>     >     Am <a href="tel:23.12.2013%2011" value="<a
>     href="tel:%2B12312201311" value="<a href="tel:%2B12312201311" value="+12312201311" target="_blank">+12312201311"
>     target="_blank"><a href="tel:%2B12312201311" value="+12312201311" target="_blank">+12312201311"
>     >     target="_blank"><a href="tel:23.12.2013%2011"
>     value="<a href="tel:%2B12312201311" value="+12312201311" target="_blank">+12312201311" target="_blank"><a href="tel:23.12.2013%2011" value="+12312201311" target="_blank">23.12.2013 11:00, schrieb

>     asotobu [via Asciidoctor
>     >     :: Discussion]:
>
>     >     > Sadly there is no timeline :( it is something that I had in my
>     >     "backlog"
>     >     > but not prioritized, because now I am focused on releasing new
>     >     version
>     >     > of asciidoctorj and integrating it with jbehave and
>     cucumber.  Are
>     >     you
>     >     > using Asciidoctor or AsciidoctorJ?
>     >
>     >     sorry for my ignorance: I'm trying to use asciidoctor as an
>     in-place
>     >     replacement for my asciidoc usage (mainly because the indferior
>     >     performance ...). What ist the difference between asciidoctor and
>     >     asciidoctorJ ?
>     >
>     >     Merry Christmas,
>     >      Wilhelm
>     >
>     >     >
>     >     >
>     >     > 2013/12/23 wimalopaan [via Asciidoctor :: Discussion]
>     <[hidden email]
>     >     > </user/SendEmail.jtp?type=node&node=1224&i=0>>
>     >     >
>     >     >     Hi,
>     >     >
>     >     >     Am 18.12.2013 15:39, schrieb asotobu [via Asciidoctor ::
>     >     Discussion]:
>     >     >     > Hello and welcome,
>     >     >     >
>     >     >     > currently I am working in developing asciidoctorj
>     extensions
>     >     but for
>     >     >     > JBehave. Help will be welcomed, you can write
>     extensions in
>     >     Ruby
>     >     >     or in
>     >     >     > JVM language so if you want to start an extension for
>     ditaa or
>     >     >     planetUML
>     >     >     > don't hesitate to contact us here.
>     >     >     >
>     >     >     > BTW let me tell you that these integrations are on my
>     list too.
>     >     >
>     >     >     this is very good news to me - do you have a timeline
>     for this?
>     >     >
>     >     >     >
>     >     >     >
>     >     >    
>     >    
>     ------------------------------------------------------------------------
>
>     >
>     >     >
>     >     >     > If you reply to this email, your message will be added
>     to the
>     >     >     discussion
>     >     >     > below:
>     >     >     >
>     >     >    
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1209.html
>     >     >     >

>
>     >
>     >     >     > To start a new topic under Asciidoctor :: Discussion,
>     email
>     >     >     > [hidden email]
>     >     <http://user/SendEmail.jtp?type=node&node=1223&i=0>
>     >     >     > To unsubscribe from Asciidoctor :: Discussion, click here
>     >     >     > <
>     >     >     > NAML
>     >     >     >
>     >     >    
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >     >
>     >     >     >
>     >     >
>     >     >
>     >     >     --
>     >     >     Wilhelm
>     >     >     [hidden email]
>     >     <http://user/SendEmail.jtp?type=node&node=1223&i=1>
>     >     >
>     >     >
>     >     >    
>     >    
>     ------------------------------------------------------------------------
>
>     >
>     >     >     If you reply to this email, your message will be added
>     to the
>     >     >     discussion below:
>     >     >    
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1223.html
>     >     >

>
>     >
>     >     >     To unsubscribe from Using PlantUML and blockdiag with
>     >     asciidoctor,
>     >     >     click here.
>     >     >     NAML
>     >     >    
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     > --
>     >     > +----------------------------------------------------------+
>     >     >   Alex Soto Bueno - Computer Engineer
>     >     >   www.lordofthejars.com <http://www.lordofthejars.com>
>     <http://www.lordofthejars.com>
>     >     <http://www.lordofthejars.com>
>     >     > +----------------------------------------------------------+
>     >     >
>     >     >
>     >     >
>     >    
>     ------------------------------------------------------------------------
>
>     >
>     >     > If you reply to this email, your message will be added to the
>     >     discussion
>     >     > below:
>     >     >
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1224.html
>     >     >

>     >     > To start a new topic under Asciidoctor :: Discussion, email
>     >     > [hidden email]
>     <http://user/SendEmail.jtp?type=node&node=1227&i=0>
>     >     > To unsubscribe from Asciidoctor :: Discussion, click here
>
>     >     > <
>     >     > NAML
>     >     >
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>     >
>     >     >
>     >
>     >
>     >     --
>     >     Wilhelm
>     >     [hidden email]
>     <http://user/SendEmail.jtp?type=node&node=1227&i=1>
>     >
>     >
>     >    
>     ------------------------------------------------------------------------
>
>     >     If you reply to this email, your message will be added to the
>     >     discussion below:
>     >    
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1227.html
>     >

>     >     To unsubscribe from Using PlantUML and blockdiag with
>     asciidoctor,
>     >     click here.
>     >     NAML
>     >    
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>     >
>     >
>     >
>     >
>     >
>     > --
>     > +----------------------------------------------------------+
>     >   Alex Soto Bueno - Computer Engineer
>     >   www.lordofthejars.com <http://www.lordofthejars.com>
>     <http://www.lordofthejars.com>
>     > +----------------------------------------------------------+
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>
>     > If you reply to this email, your message will be added to the
>     discussion
>     > below:
>     >
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1228.html
>
>     >
>     > To start a new topic under Asciidoctor :: Discussion, email
>     > [hidden email] <http://user/SendEmail.jtp?type=node&node=1229&i=0>
>     [hidden email] <http://user/SendEmail.jtp?type=node&node=1229&i=1>
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1229.html
>
>     To unsubscribe from Using PlantUML and blockdiag with asciidoctor,
>     click here.
>     NAML
>     <http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

>
>
>
>
>
> --
> +----------------------------------------------------------+
>   Alex Soto Bueno - Computer Engineer
>   www.lordofthejars.com <http://www.lordofthejars.com>
> +----------------------------------------------------------+
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1230.html


--
Wilhelm
[hidden email]



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1231.html
To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML



--
+----------------------------------------------------------+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+----------------------------------------------------------+
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

pepijnve
Hi all,

Just wanted to let you guys know I started work on an asciidoc-plantuml work-alike for asciidoctor. Work-in-progress code is available at https://github.com/pepijnve/asciidoctor-plantuml.

Regards,

Pepijn
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

mojavelinux
Administrator

Super cool! I look forward to trying out what you have so far and helping where I can.

Hopefully you find the extension capability in Asciidoctor much more powerful than the filters in AsciiDoc Python. If not, I'm interested to know what power you need and we'll give it a boost!

-Dan

On Feb 5, 2014 2:22 PM, "pepijnve [via Asciidoctor :: Discussion]" <[hidden email]> wrote:
Hi all,

Just wanted to let you guys know I started work on an asciidoc-plantuml work-alike for asciidoctor. Work-in-progress code is available at https://github.com/pepijnve/asciidoctor-plantuml.

Regards,

Pepijn


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1354.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

asotobu
In reply to this post by pepijnve
Yes I love the idea!!! In parallel some day I will start of integration with DITAA.
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

pepijnve
In reply to this post by mojavelinux
Hi Dan,

Thanks for the enthousiastic response :) The extension api has been great so far. Adding the block processor and configuring the positional attrbutes was trivial. Great work there! I'll be sure to let you know if I run into any limitations.

I would love to get your advice on a couple of implementation aspects for this extension.

At the moment I mimicked asciidoc-plantuml in the sense that plantuml blocks are listing blocks. Is that ok, or should it be applicable to any kind of block? I felt a listing block was ok since the plantuml code is a kind of code.

I'm currently registering the extension in the extension itself. In other words, requiring 'asciidoc/plantuml' will enable the extension automatically. Is that the way to do this or should that be left to the extension users themselves? Auto-registering seemed the most convenient to me, but perhaps there are good reasons to not do this.

What do you think the plantuml code block should be translated to? I'm currently generating a paragraph block containing an inline image macro. Any suggestions here would be welcome. It's not clear to me how we should handle block ids, captions, etc. Are these handled automagically somehow by the lexer or do I need to do additional work in the block processor to handle this?

Finally, testing. Any ideas on how to write meaningful tests for this? I haven't looked at the asciidoctor test suite itself yet; that was going to be my main source of inspiration. If you could describe the general testing approach in a nutshell that would be great and save me some code reading time :)

Thanks,

Pepijn

On 06-02-14 03:06, mojavelinux [via Asciidoctor :: Discussion] wrote:

Super cool! I look forward to trying out what you have so far and helping where I can.

Hopefully you find the extension capability in Asciidoctor much more powerful than the filters in AsciiDoc Python. If not, I'm interested to know what power you need and we'll give it a boost!

-Dan

On Feb 5, 2014 2:22 PM, "pepijnve [via Asciidoctor :: Discussion]" <[hidden email]> wrote:
Hi all,

Just wanted to let you guys know I started work on an asciidoc-plantuml work-alike for asciidoctor. Work-in-progress code is available at https://github.com/pepijnve/asciidoctor-plantuml.

Regards,

Pepijn


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1354.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1355.html
To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

mojavelinux
Administrator
Pepijn,

Your plantuml extension is awesome! You nailed it. I'm psyched to see the extension system in action. So cool!

I'll start my feedback by saying it works great. I created a document with a plantuml block, pasted in some plantuml markup, add a block title, rendered the document, and voila! I see a diagram with a title just as I was expecting. *Game on!*

The code is also excellent. You're extension uses the API just as I had imagined it. Below are responses to your specific questions.

> At the moment I mimicked asciidoc-plantuml in the sense that plantuml blocks are listing blocks.
> Is that ok, or should it be applicable to any kind of block? I felt a listing block was ok since the plantuml code is a kind of code.

For sure, this is a matter of taste. To me, a listing block is definitely appropriate. If you use a listing block, then you should probably add a literal block as well to give the writer at least one other option should a conflict in syntax arise (e.g., a line with four hyphens in the data).

When thinking about which contexts to use for an extension, it's important to think about how it will look when the extension system is absent, such as on GitHub. For plantuml, that reinforces the choice of selecting the listing and literal blocks since it will render nicely as UML source on GitHub.

Generally, I think all extensions should also support the open block, unless there is some reason not to allow it. Obviously, if you use an open block with a "plantuml" style, it's not going to look right on GitHub. But, for writers that don't care about that, the open block saves a few characters of typing and it maintains the spirit of the open block (open to anything).

Long answer, short,

[source,ruby]
--
option :contexts, [:listing, :literal, :open]
--

> I'm currently registering the extension in the extension itself. In other words, requiring 'asciidoc/plantuml' will enable the extension automatically.
> Is that the way to do this or should that be left to the extension users themselves?
> Auto-registering seemed the most convenient to me, but perhaps there are good reasons to not do this.

This should definitely be one way to load it. It's simple, gets people started without extra work and it will go nicely with the "load path" feature I'm adding to the asciidoctor command in 1.5.0.

However, I think there should also be a way to load it without auto-registering. Here's how I'd structure it:

....
lib/
  asciidoctor-plantuml/
    extension.rb
    version.rb
  asciidoctor-plantuml.rb
  plantuml.jar
....

In lib/asciidoctor-plantuml.rb, you'd put:

[source,ruby]
--
# we should assume Asciidoctor is already loaded
require_relative 'asciidoctor-plantuml/extension'

Asciidoctor::Extensions.register do |document|
  block :plantuml, Asciidoctor::PlantUml::Block
end
--

That way, you can either import with auto-register:

[source,ruby]
--
require 'asciidoctor-plantuml'
--

or you can just load the extension itself:

[source,ruby]
--
require 'asciidoctor-plantuml/extension'
--

To make this refactor easier to visually, I've sent a pull request. See: https://github.com/pepijnve/asciidoctor-plantuml/pull/1

> What do you think the plantuml code block should be translated to?
> I'm currently generating a paragraph block containing an inline image macro.

You should generate an image block instead. Simply change the context from :paragraph to :image and set the `target` attribute to the file name and the `:content_model` option to `:empty`. For example:

[source,ruby]
--
attributes['target'] = file_name # unless target was provided
Asciidoctor::Block.new parent, :image, :content_model => :empty, :attributes => attributes
--

> It's not clear to me how we should handle block ids, captions, etc.
> Are these handled automagically somehow by the lexer or do I need to do additional work in the block processor to handle this?

All that is automatic. Nothing to worry about as long as you pass along the attributes map, as you are doing.

> Finally, testing. Any ideas on how to write meaningful tests for this?

I would advise against looking at the Asciidoctor test code as a model since that's a very old-fashioned way of doing tests. Instead, I recommend using rspec. You are probably best off just finding a good tutorial on the web, because even I need to read up on how to best structure tests.

Another option is cucumber tests, which are conceptually a lot easier to run in this scenario. The cucumber setup in Asciidoctor is reasonable to copy because it offers a few ways to go about the problem. See: https://github.com/asciidoctor/asciidoctor/blob/master/features/open_block.feature

Before I wrap up, I want to mention that the Extension API will be changing in 1.5.0. When 1.5.0.preview2 is released, it might be a good idea to create a branch of asciidoctor-plantuml and experiment with the changes you need to make. The changes aren't drastic, and you might even find them to clean some things up. I'll have details when I broadcast that I've pushed the 1.5.0.preview2 release. Until now, the changes are sitting in a pull request.

Again, great job!

-Dan

p.s. For other ideas about how to setup, configure and name extensions, or ideas about extensions to create, check out Middleman extensions. There are lots of them and that's the model on which Asciidoctor Extensions are primarily based. See: https://github.com/search?p=2&q=middleman&source=cc&type=Repositories

Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

mojavelinux
Administrator
In reply to this post by pepijnve
Since we're on the topic of extensions, I figured I'd share a quick little extension I hacked up today to query CSV data into an AsciiDoc table using textql.


You can imagine having a single data set and being able to generate a bunch of different reports from it inside your AsciiDoc document using this extension. Lightweight reporting!

-Dan
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

mojavelinux
Administrator
In reply to this post by pepijnve
Pepijn,

I forget the most important thing! It would be my pleasure to welcome asciidoctor-plantuml to the Asciidoctor organization on GitHub if and when you are interested.

Cheers!

-Dan


On Fri, Feb 7, 2014 at 2:54 AM, Dan Allen <[hidden email]> wrote:
Pepijn,

Your plantuml extension is awesome! You nailed it. I'm psyched to see the extension system in action. So cool!

I'll start my feedback by saying it works great. I created a document with a plantuml block, pasted in some plantuml markup, add a block title, rendered the document, and voila! I see a diagram with a title just as I was expecting. *Game on!*

The code is also excellent. You're extension uses the API just as I had imagined it. Below are responses to your specific questions.


> At the moment I mimicked asciidoc-plantuml in the sense that plantuml blocks are listing blocks.
> Is that ok, or should it be applicable to any kind of block? I felt a listing block was ok since the plantuml code is a kind of code.

For sure, this is a matter of taste. To me, a listing block is definitely appropriate. If you use a listing block, then you should probably add a literal block as well to give the writer at least one other option should a conflict in syntax arise (e.g., a line with four hyphens in the data).

When thinking about which contexts to use for an extension, it's important to think about how it will look when the extension system is absent, such as on GitHub. For plantuml, that reinforces the choice of selecting the listing and literal blocks since it will render nicely as UML source on GitHub.

Generally, I think all extensions should also support the open block, unless there is some reason not to allow it. Obviously, if you use an open block with a "plantuml" style, it's not going to look right on GitHub. But, for writers that don't care about that, the open block saves a few characters of typing and it maintains the spirit of the open block (open to anything).

Long answer, short,

[source,ruby]
--
option :contexts, [:listing, :literal, :open]
--

> I'm currently registering the extension in the extension itself. In other words, requiring 'asciidoc/plantuml' will enable the extension automatically.
> Is that the way to do this or should that be left to the extension users themselves?
> Auto-registering seemed the most convenient to me, but perhaps there are good reasons to not do this.

This should definitely be one way to load it. It's simple, gets people started without extra work and it will go nicely with the "load path" feature I'm adding to the asciidoctor command in 1.5.0.

However, I think there should also be a way to load it without auto-registering. Here's how I'd structure it:

....
lib/
  asciidoctor-plantuml/
    extension.rb
    version.rb
  asciidoctor-plantuml.rb
  plantuml.jar
....

In lib/asciidoctor-plantuml.rb, you'd put:

[source,ruby]
--
# we should assume Asciidoctor is already loaded
require_relative 'asciidoctor-plantuml/extension'

Asciidoctor::Extensions.register do |document|
  block :plantuml, Asciidoctor::PlantUml::Block
end
--

That way, you can either import with auto-register:

[source,ruby]
--
require 'asciidoctor-plantuml'
--

or you can just load the extension itself:

[source,ruby]
--
require 'asciidoctor-plantuml/extension'
--

To make this refactor easier to visually, I've sent a pull request. See: https://github.com/pepijnve/asciidoctor-plantuml/pull/1

> What do you think the plantuml code block should be translated to?
> I'm currently generating a paragraph block containing an inline image macro.

You should generate an image block instead. Simply change the context from :paragraph to :image and set the `target` attribute to the file name and the `:content_model` option to `:empty`. For example:

[source,ruby]
--
attributes['target'] = file_name # unless target was provided
Asciidoctor::Block.new parent, :image, :content_model => :empty, :attributes => attributes
--

> It's not clear to me how we should handle block ids, captions, etc.
> Are these handled automagically somehow by the lexer or do I need to do additional work in the block processor to handle this?

All that is automatic. Nothing to worry about as long as you pass along the attributes map, as you are doing.

> Finally, testing. Any ideas on how to write meaningful tests for this?

I would advise against looking at the Asciidoctor test code as a model since that's a very old-fashioned way of doing tests. Instead, I recommend using rspec. You are probably best off just finding a good tutorial on the web, because even I need to read up on how to best structure tests.

Another option is cucumber tests, which are conceptually a lot easier to run in this scenario. The cucumber setup in Asciidoctor is reasonable to copy because it offers a few ways to go about the problem. See: https://github.com/asciidoctor/asciidoctor/blob/master/features/open_block.feature

Before I wrap up, I want to mention that the Extension API will be changing in 1.5.0. When 1.5.0.preview2 is released, it might be a good idea to create a branch of asciidoctor-plantuml and experiment with the changes you need to make. The changes aren't drastic, and you might even find them to clean some things up. I'll have details when I broadcast that I've pushed the 1.5.0.preview2 release. Until now, the changes are sitting in a pull request.

Again, great job!

-Dan

p.s. For other ideas about how to setup, configure and name extensions, or ideas about extensions to create, check out Middleman extensions. There are lots of them and that's the model on which Asciidoctor Extensions are primarily based. See: https://github.com/search?p=2&q=middleman&source=cc&type=Repositories




--
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

asotobu


2014-02-07 11:33 GMT+01:00 mojavelinux [via Asciidoctor :: Discussion] <[hidden email]>:
Pepijn,

I forget the most important thing! It would be my pleasure to welcome asciidoctor-plantuml to the Asciidoctor organization on GitHub if and when you are interested.

Cheers!

-Dan


On Fri, Feb 7, 2014 at 2:54 AM, Dan Allen <[hidden email]> wrote:
Pepijn,

Your plantuml extension is awesome! You nailed it. I'm psyched to see the extension system in action. So cool!

I'll start my feedback by saying it works great. I created a document with a plantuml block, pasted in some plantuml markup, add a block title, rendered the document, and voila! I see a diagram with a title just as I was expecting. *Game on!*

The code is also excellent. You're extension uses the API just as I had imagined it. Below are responses to your specific questions.


> At the moment I mimicked asciidoc-plantuml in the sense that plantuml blocks are listing blocks.
> Is that ok, or should it be applicable to any kind of block? I felt a listing block was ok since the plantuml code is a kind of code.

For sure, this is a matter of taste. To me, a listing block is definitely appropriate. If you use a listing block, then you should probably add a literal block as well to give the writer at least one other option should a conflict in syntax arise (e.g., a line with four hyphens in the data).

When thinking about which contexts to use for an extension, it's important to think about how it will look when the extension system is absent, such as on GitHub. For plantuml, that reinforces the choice of selecting the listing and literal blocks since it will render nicely as UML source on GitHub.

Generally, I think all extensions should also support the open block, unless there is some reason not to allow it. Obviously, if you use an open block with a "plantuml" style, it's not going to look right on GitHub. But, for writers that don't care about that, the open block saves a few characters of typing and it maintains the spirit of the open block (open to anything).

Long answer, short,

[source,ruby]
--
option :contexts, [:listing, :literal, :open]
--

> I'm currently registering the extension in the extension itself. In other words, requiring 'asciidoc/plantuml' will enable the extension automatically.
> Is that the way to do this or should that be left to the extension users themselves?
> Auto-registering seemed the most convenient to me, but perhaps there are good reasons to not do this.

This should definitely be one way to load it. It's simple, gets people started without extra work and it will go nicely with the "load path" feature I'm adding to the asciidoctor command in 1.5.0.

However, I think there should also be a way to load it without auto-registering. Here's how I'd structure it:

....
lib/
  asciidoctor-plantuml/
    extension.rb
    version.rb
  asciidoctor-plantuml.rb
  plantuml.jar
....

In lib/asciidoctor-plantuml.rb, you'd put:

[source,ruby]
--
# we should assume Asciidoctor is already loaded
require_relative 'asciidoctor-plantuml/extension'

Asciidoctor::Extensions.register do |document|
  block :plantuml, Asciidoctor::PlantUml::Block
end
--

That way, you can either import with auto-register:

[source,ruby]
--
require 'asciidoctor-plantuml'
--

or you can just load the extension itself:

[source,ruby]
--
require 'asciidoctor-plantuml/extension'
--

To make this refactor easier to visually, I've sent a pull request. See: https://github.com/pepijnve/asciidoctor-plantuml/pull/1

> What do you think the plantuml code block should be translated to?
> I'm currently generating a paragraph block containing an inline image macro.

You should generate an image block instead. Simply change the context from :paragraph to :image and set the `target` attribute to the file name and the `:content_model` option to `:empty`. For example:

[source,ruby]
--
attributes['target'] = file_name # unless target was provided
Asciidoctor::Block.new parent, :image, :content_model => :empty, :attributes => attributes
--

> It's not clear to me how we should handle block ids, captions, etc.
> Are these handled automagically somehow by the lexer or do I need to do additional work in the block processor to handle this?

All that is automatic. Nothing to worry about as long as you pass along the attributes map, as you are doing.

> Finally, testing. Any ideas on how to write meaningful tests for this?

I would advise against looking at the Asciidoctor test code as a model since that's a very old-fashioned way of doing tests. Instead, I recommend using rspec. You are probably best off just finding a good tutorial on the web, because even I need to read up on how to best structure tests.

Another option is cucumber tests, which are conceptually a lot easier to run in this scenario. The cucumber setup in Asciidoctor is reasonable to copy because it offers a few ways to go about the problem. See: https://github.com/asciidoctor/asciidoctor/blob/master/features/open_block.feature

Before I wrap up, I want to mention that the Extension API will be changing in 1.5.0. When 1.5.0.preview2 is released, it might be a good idea to create a branch of asciidoctor-plantuml and experiment with the changes you need to make. The changes aren't drastic, and you might even find them to clean some things up. I'll have details when I broadcast that I've pushed the 1.5.0.preview2 release. Until now, the changes are sitting in a pull request.

Again, great job!

-Dan

p.s. For other ideas about how to setup, configure and name extensions, or ideas about extensions to create, check out Middleman extensions. There are lots of them and that's the model on which Asciidoctor Extensions are primarily based. See: https://github.com/search?p=2&q=middleman&source=cc&type=Repositories




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Using-PlantUML-and-blockdiag-with-asciidoctor-tp1208p1362.html
To unsubscribe from Using PlantUML and blockdiag with asciidoctor, click here.
NAML



--
+----------------------------------------------------------+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+----------------------------------------------------------+
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

pepijnve
In reply to this post by mojavelinux
Thanks for all the suggestions Dan. Integrated those and fixed some errors in the test code, gem spec, etc.

I made the block type change you suggested as well. SVG and PNG formats now result in an image block.
Just for kicks I added ASCII-art support as well :). Those are turned into literal blocks to ensure they render correctly in the final document.

On the testing front I was wondering in particular how I should write the assertions. Is there an easy way to dig into the Document object? Something xpath-ish perhaps?

If you feel the code is up to snuff, I have no objection at all to adding it under the asciidoctor umbrella. Honoured in fact. There's still more testing to do (on JRuby in particular; Open3 has issues under JRuby IIRC) before I would consider it releasable though. Need to write more test cases that actually assert something as well :)

Pepijn
Reply | Threaded
Open this post in threaded view
|

Re: Using PlantUML and blockdiag with asciidoctor

mojavelinux
Administrator
Pepijn,

Glad to help! Little do you know, you (and Alex) are now the role model for extension writers :)

Your updates look great! The ASCII-art support is a nice touch.

> On the testing front I was wondering in particular how I should write the assertions.
> Is there an easy way to dig into the Document object? Something xpath-ish perhaps?

Using xpath to verify the output tends to be pretty hit or miss and the thing I dislike the most about the current Asciidoctor test suite. I think it's far better to just verify the expected output, or at least grab the most relevant fragment of HTML or XML and verify it matches what you expect.

The tricky part about matching HTML and XML is formatting. That's one of the main reasons I've removed all indentation from the output that Asciidoctor generates. Indentation is just messy and has no semantic meaning anyway. Thus, it should be easier to verify directly against the HTML and XML.

What I've done the in Cucumber tests is find a way to compare by structure using the Slim language. The slim template is rendered to HTML and I compare that against what Asciidoctor generates. That way, the assertion is kept at a higher level.

> If you feel the code is up to snuff, I have no objection at all to adding it under the asciidoctor umbrella. Honoured in fact.

Excellent! I've given you transfer permissions. When you are ready, you just go into the admin page on the repository and transfer it to the organization. That moves everything, including the issues and forks. Then, just fork it back into your personal space. I'll assign you the admin role on the repo and you remain the lead.

> There's still more testing to do (on JRuby in particular; Open3 has issues under JRuby IIRC) before I would consider it releasable though.
> Need to write more test cases that actually assert something as well :)

Keep in mind there's always room for improvement, so once you have a few tests running, I encourage you to release a 1.0.0.alpha.1 version. Personally, i think starting with 0.0.1 puts you in the situation we got in with Asciidoctor. You never seem to get to 1.0.0. Let's call a first release what it is, 1.0.0 :)

In the Ruby world, the version qualifiers seem to go something like: preview.<n>, alpha.<n>, beta.<n>, rc.<n>, and finally the unqualified version. You can see an example here: http://rubygems.org/gems/haml/versions. You typically only use preview once a project is mature and you are experimenting with a brand new major version. I recommend starting with alpha.1.

After the 1.0.0 release, you might want to consider keeping the JVM warm by using some sort of spawning approach if available. You can fall back to java -jar for platforms that can't handle it. You could also detect the JRuby environment and see if the plantuml classes are already available. Just some ideas.

Cheers!

123