Request for Recursive Warnings as Message DUB Flag
I really think DUB lacks an important flag/option namely a variant of allowWarnings that *recursively* affects all the sub packages of a dub.json project description. Otherwise developers who want to try out D will think its is broken because of warnings such as deprecated use of C-style arrays hinders them from building and trying out all the cool software currently packaged with DUB. I don't think D's deprecation system was meant to have this affect on the developer. Comments on that, please.
Re: crate.d a draft for a mvc library
On Sunday, 30 November 2014 at 00:20:57 UTC, Dylan Knutson wrote: On Thursday, 27 November 2014 at 19:16:24 UTC, gedaiu wrote: Hi, In the last weeks I tried to make a draft for a mvc library. I tried to take advantage of templates, uda and ctfe to make the interaction with the database and the routing easier. There is still a lot of work to do for making it ready to work in production... but anyway.. what do you think? https://github.com/gedaiu/crate.d Thanks, Bogdan Hi, I noticed you had your own templating library to parse the .dh files, so I thought I'd mention my project Temple which does something similar: https://github.com/dymk/temple It's perhaps a bit more feature complete, and can handle stuff like capturing blocks of code, render to arbitrary output ranges, etc. That being said, your solution is very nice; it's amazing what you can do in so few lines of code in D :) MongoModel in the model part of crate.d is interesting, and I'm glad to see there's a more structured way of interacting with MongoDB than just poking at untyped objects. I think D is still missing a really good ORM (Rikki's dvorm is a start), but there's nothing out there that conforms to the activerecord pattern as far as I can tell. Hi, I seen the Temple library and I was thinking to use it, but I did not had time to look in more details on it. It looks very nice and I will use it for sure. The solution that I found with the dh files is just a temporary and it should be rewritten as soon as I will find a good solution for the models. Regarding the models I tried to implement something that comforms with activerecord in the past, but I failed big time... I intend to do a similar interface for relational databases too, but I don't know right now how I should treat the joins... @Rikki nice job with your projects. I did not know about them and I will take a look on them these days. Thanks, Bogdan
Re: Coedit alpha 8 released
On Friday, 28 November 2014 at 16:39:38 UTC, Basile Burg wrote: Hello, a new release of Coedit[MainPage], the small open-source D IDE for Windows and Linux, is released. Here is a paste of the release log. Messages: = - redesigned the widget: a toolbar at the top allows to filter the messages according to a category, either all, editor (focused editor messages), project, misc (messages from the custom tools) or application (Coedit warnings or exceptions). - custom tools messages are redirected if poUsePipes is defined in the tool options. - errors messages are not split anymore (e.g: instantiated from here...) thus less confusing. Miscellaneous: == - non D files syntax highlighter: txt, md, etc. Automatically set when opening a file. - the project inspector displays the items from the project Path options (-I, -J, additional sources). - Zoom in,out editor with Ctrl++, Ctrl+-, restore with Ctrl+. - The static explorer widget scans in background, refresh on change, refresh on focus does not freeze the GUI anymore. - various bug fixed and small improvements. - pre-build binaries include an up-to-date DCD build. - refer to the wiki[WikiPage] for more information about the changes and the new features. Pre-build binaries are available from the [ReleasePage]. - [MainPage]: https://github.com/BBasile/Coedit [ReleasePage]: https://github.com/BBasile/Coedit/releases [WikiPage]:https://github.com/BBasile/Coedit/wiki - Baz. Looks pretty cool but why not support DUB projects directly instead of your own format?
Re: Coedit alpha 8 released
On Sunday, 30 November 2014 at 17:59:06 UTC, ponce wrote: On Friday, 28 November 2014 at 16:39:38 UTC, Basile Burg wrote: Hello, a new release of Coedit[MainPage], the small open-source D IDE for Windows and Linux, is released. Here is a paste of the release log. Messages: = - redesigned the widget: a toolbar at the top allows to filter the messages according to a category, either all, editor (focused editor messages), project, misc (messages from the custom tools) or application (Coedit warnings or exceptions). - custom tools messages are redirected if poUsePipes is defined in the tool options. - errors messages are not split anymore (e.g: instantiated from here...) thus less confusing. Miscellaneous: == - non D files syntax highlighter: txt, md, etc. Automatically set when opening a file. - the project inspector displays the items from the project Path options (-I, -J, additional sources). - Zoom in,out editor with Ctrl++, Ctrl+-, restore with Ctrl+. - The static explorer widget scans in background, refresh on change, refresh on focus does not freeze the GUI anymore. - various bug fixed and small improvements. - pre-build binaries include an up-to-date DCD build. - refer to the wiki[WikiPage] for more information about the changes and the new features. Pre-build binaries are available from the [ReleasePage]. - [MainPage]: https://github.com/BBasile/Coedit [ReleasePage]: https://github.com/BBasile/Coedit/releases [WikiPage]:https://github.com/BBasile/Coedit/wiki - Baz. Looks pretty cool but why not support DUB projects directly instead of your own format? Mostly because when I started dmd_wrap.pas (June) I had never used DUB at all. A bit as a matter of style too since the project things are done the way I like to program in Pascal (properties, component streaming, and now the RTTI grid). Later (end of August) I've changed the code to allow the pre-compilation process to be set on DUB (see wiki, tutos, [Build with DUB]). Maybe you've noticed it's possible since you've written 'why not...directly'. Now I just wait for the right idea to pop up but just as a hint I would say that LoadProjectFromDubFile() and SaveProjectToDubFile() is quite faisable. -- [Build with DUB]: https://github.com/BBasile/Coedit/wiki#using-dub-in-coedit-as-a-project-pre-build-process --
Re: Coedit alpha 8 released
Hello Basile, I want to create new Coedit deb packages for d-apt http://d-apt.sourceforge.net/. If you're interested too, please contact me on g.sayol at yahoo dot es Regards, Jordi
Re: Programming in D book, draft of the first print edition and eBook formats
Cool!
undeaD - zombie phobos modules back from the grave
http://code.dlang.org/packages/undead https://github.com/DigitalMars/undeaD In upgrading old D code, one time consuming aspect is reworking code that depends on old Phobos modules that have been taken out behind the woodshed and shot. Sometimes, there's significantly more work involved than just renaming things. Just to get things working, it's convenient to be able to use the old modules until one has time to redo the code. I've done this myself, and then noticed that Dmitry Olshansky had also done it when updating DMDScript to D2. Rather than having people keep duplicating others' efforts, I created the undeaD library of zombie Phobos modules. I'm new to dub, so if I botched that up, please do a pull request! Also, if there are any other dead Phobos modules you'd like exhumed, PR's are welcome.
O'Reilly conference needs D presentations!
You guys are working on a lot of great stuff that'll make for very interesting talks. http://softwarearchitecturecon.com/sa2015 Proposals are due Dec. 2. I'm submitting mine - see you there!
Re: undeaD - zombie phobos modules back from the grave
On 2014-12-01 05:07, Walter Bright wrote: http://code.dlang.org/packages/undead https://github.com/DigitalMars/undeaD In upgrading old D code, one time consuming aspect is reworking code that depends on old Phobos modules that have been taken out behind the woodshed and shot. Sometimes, there's significantly more work involved than just renaming things. Just to get things working, it's convenient to be able to use the old modules until one has time to redo the code. There wasn't significant work to get these modules up to date with the latest compiler? I'm new to dub, so if I botched that up, please do a pull request! Also, if there are any other dead Phobos modules you'd like exhumed, PR's are welcome. Just a minor note, seems a bit odd to start with version 1.0.1. But you might already have versions that haven't been released. -- /Jacob Carlborg
Re: undeaD - zombie phobos modules back from the grave
On 11/30/2014 11:43 PM, Jacob Carlborg wrote: On 2014-12-01 05:07, Walter Bright wrote: There wasn't significant work to get these modules up to date with the latest compiler? No, not much. bitarray took a bit longer, as it was a D1 module. I'm new to dub, so if I botched that up, please do a pull request! Also, if there are any other dead Phobos modules you'd like exhumed, PR's are welcome. Just a minor note, seems a bit odd to start with version 1.0.1. But you might already have versions that haven't been released. Well, I had tagged 1.0.0, then fixed a problem :-)
