You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by adithyank <ad...@gmail.com> on 2018/05/17 12:07:14 UTC

New DSLs in the groovy platform itself for more script like use cases

I have always felt that groovy platform itself can have rich set of DSLs
(list given below) so that groovy will be in hands of many non-developers.
Even developers will find it much useful for quicker outputs.We can design
the DSLs in such a way that non-developers can define the work in
declarative style.Some of my ideas and an example structure for each idea is
given below.These are my proposals. We can identify lot of such use
cases.Can I start working on these if the team approves !Is it the right
channel to gain the votes, I am not sure. Pls advice
1. Database
a. Database querying, data transformation, printb. Similar Use cases can be
listed very easily
2. Text / String processing 
a. use cases for more command line text processing like `awk`b. command line
usage
3. Lot of String Extension methods
4. Simple Unit conversions
a.  938.meter.toMilesb. 9823749.bytes.toGBc. lots like this
5. Http Client DSL
a. Download / xml processing / print raw text
6. Xml to different types of 2d conversion
7. Json to different types of 2d conversion




--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: New DSLs in the groovy platform itself for more script like use cases

Posted by Paul King <pa...@asert.com.au>.
Hi, reminders are always welcome - we are all busy and sometimes leave
things hoping someone else will respond.
When I first saw your email I thought some of these looked good but perhaps
not all and I haven't had time to go through and select and suspect I won't
have time for another couple of weeks. The hardest choices with languages
is to work out what to leave out rather than what might be good to have in.

Cheers, Paul.


On Thu, May 31, 2018 at 3:09 PM, adithyank <ad...@gmail.com> wrote:

> Hi All,
>
> Sorry for the disturbance !
>
> I had proposed some of the friendly DSLs in groovy platform itself. The
> original post here
>
> http://groovy.329449.n5.nabble.com/New-DSLs-in-the-
> groovy-platform-itself-for-more-script-like-use-cases-td5750522.html
>
> As I am new the this dev group, I have couple of doubts in the protocol
>
> 1. Is this `dev` mailing list the best way to propose new language features
> 2. There has been `no reply` to this original thread. How should I
> understand now. Couple of options below
>      * Project maintainers are not interested to this proposal. So, not
> replied
>      * or People are busy in other things (new releases, etc), so no reply.
> I have to wait for more days and give reminder
>      * or what is the best way to take the proposals forward
>
> Pls advice
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>

Re: New DSLs in the groovy platform itself for more script like use cases

Posted by adithyank <ad...@gmail.com>.
Thanks Jochen Theodorou,

Thanks for the feedback. I will create new topic of each DSL and elaborate
there to enable easy discussions...!

Reg,

Adithyan K




--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: New DSLs in the groovy platform itself for more script like use cases

Posted by Jochen Theodorou <bl...@gmx.org>.

Am 31.05.2018 um 07:09 schrieb adithyank:
> Hi All,
> 
> Sorry for the disturbance !
> 
> I had proposed some of the friendly DSLs in groovy platform itself. The
> original post here
> 
> http://groovy.329449.n5.nabble.com/New-DSLs-in-the-groovy-platform-itself-for-more-script-like-use-cases-td5750522.html
> 
> As I am new the this dev group, I have couple of doubts in the protocol
> 
> 1. Is this `dev` mailing list the best way to propose new language features

dev is for the implementation, I personally think user and dev should be 
used. Depending on if I want a wider audience right away or not I 
usually go with either first

> 2. There has been `no reply` to this original thread. How should I
> understand now. Couple of options below
>       * Project maintainers are not interested to this proposal. So, not
> replied
>       * or People are busy in other things (new releases, etc), so no reply.
> I have to wait for more days and give reminder
>       * or what is the best way to take the proposals forward

reading it again your proposal was very specific without actually saying 
much ;) I think you need to chop them up one DSL at a time, maybe the 
suggestions for the extension methods in one mail on their own and then 
we can start discussing about if we want that like that or at all or 
different.

You will also have to explain why you want what you want specifically... 
for example those bw prefixed methods... I am not sure what they are 
actually for.

bye Jochen

Re: New DSLs in the groovy platform itself for more script like use cases

Posted by adithyank <ad...@gmail.com>.
Hi All,

Sorry for the disturbance !

I had proposed some of the friendly DSLs in groovy platform itself. The
original post here

http://groovy.329449.n5.nabble.com/New-DSLs-in-the-groovy-platform-itself-for-more-script-like-use-cases-td5750522.html

As I am new the this dev group, I have couple of doubts in the protocol

1. Is this `dev` mailing list the best way to propose new language features
2. There has been `no reply` to this original thread. How should I
understand now. Couple of options below
     * Project maintainers are not interested to this proposal. So, not
replied
     * or People are busy in other things (new releases, etc), so no reply.
I have to wait for more days and give reminder
     * or what is the best way to take the proposals forward

Pls advice



--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html