Re: emeralD - Command-line tool for template files
On Sunday, 17 June 2018 at 23:04:59 UTC, bauss wrote: emeralD is a command-line tool for template files that can be used to generate code files, configurations etc. It's a very useful tool for generating files that you'd normally have to create by hand. The idea for emeralD was not actually by me, but by Moogly (I don't know what he goes by in the forums, if he uses them.) who wanted something to generate files for ex. vibe.d and Diamond. Also additionally thanks to 0xEAB for a few ideas. emeralD is generic and not tied to D files only, but can be used for any type of file within any programming language. For more information see the Github repository and for examples see the read me. Github: https://github.com/DiamondMVC/emeralD Thank you! Sounds interesting. But the readme is missing a basic thing: a complete working example command for the impatient.
Re: Aalborg D meetup
On Friday, 15 June 2018 at 08:45:29 UTC, Bienlein wrote: On Friday, 15 June 2018 at 07:34:07 UTC, biocyberman wrote: On Friday, 15 June 2018 at 07:20:04 UTC, Bienlein wrote: On Wednesday, 13 June 2018 at 12:37:26 UTC, bauss wrote: On Wednesday, 13 June 2018 at 12:12:11 UTC, bauss wrote: I'll be there since I live there and would be nice to see monthly meetups! :) I forgot to ask. Is it free entry? :) Yeah, and the Aalborg Akvavit is also free ? ;-) Depending on the volume you can take and how you transport to and from the meetup :) But I am taking some beer, soft drinks (saft vand?), fruit and chips. It's good for discussing socializing parts It is called soda vand, I think. Unhappily I'm about 1000 km away from Aalborg :-( I will explore further the possibility to make an online meetup after our first on-site one. If we do streaming on Youtube for example, everyone can join.
Re: emeralD - Command-line tool for template files
On Monday, 18 June 2018 at 13:31:40 UTC, bauss wrote: The files will be created / copied to the current working directory. In the next version you'll be able to specify folders that you work in and give them a name which can be used to invoke emeralD from anywhere and still work in the directories you want.
Re: emeralD - Command-line tool for template files
On Monday, 18 June 2018 at 10:42:53 UTC, Dechcaudron wrote:
On Sunday, 17 June 2018 at 23:04:59 UTC, bauss wrote:
For more information see the Github repository and for
examples see the read me.
Could we get a complete, simple usage example? Like target
directory structure and how to invoke the program to get to it.
Simple template example for ex. a class:
```
emerald d class myclass myclass MyClass
...
emerald [root] [template] [$1] [$2] [$3]
```
Will generate a file called myclass.d with the following content:
```
module myclass;
class MyClass
{
public:
this()
{
}
}
```
An example on scaffolding ex. an empty project with a dub.json
would be:
```
-sc dub myproject -ex
```
Which will basically create a Hello World! example with a minimal
dub.json
It's possible to fetch scaffolding archives remote, as well fetch
templates online.
See the --remote / -r commands for that.
https://github.com/DiamondMVC/emeralD#--remote-root-template-url---rm-root-template-url
https://github.com/DiamondMVC/emeralD#--remote--scaffold-name-url---rm--sc-name-url
For examples on templates just see the the folders "templates"
and "scaffold" in the repository.
Re: emeralD - Command-line tool for template files
On Sunday, 17 June 2018 at 23:04:59 UTC, bauss wrote: Github: https://github.com/DiamondMVC/emeralD Thank you! Scaffolding has now been added, along with shell command passing. This makes it possible to use emeralD for like project shells, build tool combination and multiple file generation.
Re: emeralD - Command-line tool for template files
On Sunday, 17 June 2018 at 23:04:59 UTC, bauss wrote: For more information see the Github repository and for examples see the read me. Could we get a complete, simple usage example? Like target directory structure and how to invoke the program to get to it.
Re: detectcycles: A source code dependency cycle checker
On Sunday, 17 June 2018 at 20:20:48 UTC, Mario Kröplin wrote: I did not mention it in the README, but the tred filter used in https://code.dlang.org/packages/depend complains about cyclic dependencies. I am currently working on a branch, where the transitive reduction and the corresponding warnings are built in. While this tool is for D only, it also allows to visualize and to check dependencies. Very nice project. The PlantUML output is a brilliant idea. In my case, I am mostly analyzing projects that are NOT in D, so I need a general purpose tool. I'm putting it through practical runs this morning and discovering areas of improvement. For example, in Java, one need not import dependencies within the same package, so I need to take a list of "uses" regex patterns instead of just having a single one, so that things like "@Autowired" from Spring can be detected as well.
Re: iopipe v0.1.0 - now with Windows support!
On Sunday, 17 June 2018 at 04:52:07 UTC, Martin Nowak wrote: On 06/10/2018 10:10 PM, Steven Schveighoffer wrote: Note that the new io library also supports sockets, which IODev did not have support for, AND has a pluggable driver system, so you could potentially use fiber-based async io without rebuilding. It just makes a lot of sense for D to have a standard low-level io library that everything can use without having to kludge together multiple types of io libraries. Note that the WIP std.io library is fully @nogc @safe, so it's a bit edgy on using latest features. Soon want to move to use DIP10008 instead of preallocated exceptions. This is very encouraging. I’d like to see it working well with Photon (though my time is very limited atm). Any thoughts on what set of syscalls I need to support? Maybe I could just provide my own “native” driver that fits your concept of I/O driver in io library. With that and @nogc in the Driver interface¹ it's still to be seen whether we can adapt this well with vibe.d or need to adjust the low-level design. -Martin ¹: https://martinnowak.github.io/io/std/io/driver/Driver.html
