Changes:

 - New HTML form interface generator similar to the REST interface
   generator that simplifies web front end development:
   http://vibed.org/api/vibe.http.form/registerFormInterface
   (thanks to Robert Klotzner aka eskimor)

 - Diet HTML templates now support includes and recursive
   blocks/extensions

 - The REST interface generator has got a new method to reference types
   in the generated string mixin, which makes it more robust to user
   defined types (thanks to Mihail Strašun aka mist)

 - Now includes API docs for offline viewing

 - A lot of small fixes and improvements


Full change log: http://vibed.org/blog/posts/vibe-release-0.7.9

Download: http://vibed.org/download?file=vibed-0.7.9.zip

cool, keep up the good work!

Al 31/10/12 07:59, En/na Sönke Ludwig ha escrit:
> Changes:
> 
>  - New HTML form interface generator similar to the REST interface
>    generator that simplifies web front end development:
>    http://vibed.org/api/vibe.http.form/registerFormInterface
>    (thanks to Robert Klotzner aka eskimor)
> 
>  - Diet HTML templates now support includes and recursive
>    blocks/extensions
> 
>  - The REST interface generator has got a new method to reference types
>    in the generated string mixin, which makes it more robust to user
>    defined types (thanks to Mihail Strašun aka mist)
> 
>  - Now includes API docs for offline viewing
> 
>  - A lot of small fixes and improvements
> 
> 
> Full change log: http://vibed.org/blog/posts/vibe-release-0.7.9
> 
> Download: http://vibed.org/download?file=vibed-0.7.9.zip
> 

Congratulations for this new release!

New deb packages for vibe v0.7.9 available at https://code.google.com/p/d-apt/

-- 
Jordi Sayol

AUR package updated:
https://aur.archlinux.org/packages.php?ID=61679

On Wednesday, 31 October 2012 at 06:59:45 UTC, Sönke Ludwig wrote:
> Changes:
>
>  - New HTML form interface generator similar to the REST interface
>    generator that simplifies web front end development:
>    http://vibed.org/api/vibe.http.form/registerFormInterface
>    (thanks to Robert Klotzner aka eskimor)
>
>  - Diet HTML templates now support includes and recursive
>    blocks/extensions
>
>  - The REST interface generator has got a new method to reference types
>    in the generated string mixin, which makes it more robust to user
>    defined types (thanks to Mihail Strašun aka mist)
>
>  - Now includes API docs for offline viewing
>
>  - A lot of small fixes and improvements
>
>
> Full change log: http://vibed.org/blog/posts/vibe-release-0.7.9
>
> Download: http://vibed.org/download?file=vibed-0.7.9.zip

To build Vibe.d you are using DMD 2.060 as released here? I'm just wondering what you found to be the best DMD version, or if you are using a newer pre-released version found in git? Thanks.

--rt

Am 31.10.2012 17:11, schrieb Rob T:
> On Wednesday, 31 October 2012 at 06:59:45 UTC, Sönke Ludwig wrote:
>> Changes:
>>
>>  - New HTML form interface generator similar to the REST interface
>>    generator that simplifies web front end development:
>>    http://vibed.org/api/vibe.http.form/registerFormInterface
>>    (thanks to Robert Klotzner aka eskimor)
>>
>>  - Diet HTML templates now support includes and recursive
>>    blocks/extensions
>>
>>  - The REST interface generator has got a new method to reference types
>>    in the generated string mixin, which makes it more robust to user
>>    defined types (thanks to Mihail Strašun aka mist)
>>
>>  - Now includes API docs for offline viewing
>>
>>  - A lot of small fixes and improvements
>>
>>
>> Full change log: http://vibed.org/blog/posts/vibe-release-0.7.9
>>
>> Download: http://vibed.org/download?file=vibed-0.7.9.zip
> 
> To build Vibe.d you are using DMD 2.060 as released here? I'm just wondering what you found to be the best DMD version, or if you are using a newer pre-released version found in git? Thanks.
> 
> --rt
> 

I'm using the standard 2.060 release. But I know that several people also use it with the git master version.

On Wednesday, 31 October 2012 at 16:19:01 UTC, Sönke Ludwig wrote:
> Am 31.10.2012 17:11, schrieb Rob T:
>> On Wednesday, 31 October 2012 at 06:59:45 UTC, Sönke Ludwig wrote:
>>> Changes:
>>>
>>>  - New HTML form interface generator similar to the REST interface
>>>    generator that simplifies web front end development:
>>>    http://vibed.org/api/vibe.http.form/registerFormInterface
>>>    (thanks to Robert Klotzner aka eskimor)
>>>
>>>  - Diet HTML templates now support includes and recursive
>>>    blocks/extensions
>>>
>>>  - The REST interface generator has got a new method to reference types
>>>    in the generated string mixin, which makes it more robust to user
>>>    defined types (thanks to Mihail Strašun aka mist)
>>>
>>>  - Now includes API docs for offline viewing
>>>
>>>  - A lot of small fixes and improvements
>>>
>>>
>>> Full change log: http://vibed.org/blog/posts/vibe-release-0.7.9
>>>
>>> Download: http://vibed.org/download?file=vibed-0.7.9.zip
>> 
>> To build Vibe.d you are using DMD 2.060 as released here? I'm just
>> wondering what you found to be the best DMD version, or if you are using
>> a newer pre-released version found in git? Thanks.
>> 
>> --rt
>> 
>
> I'm using the standard 2.060 release. But I know that several people
> also use it with the git master version.

I'm relatively new to D but making good progress with it after a very slow start (it is a very complex language). Some of what I am working on shares similarities with what vibe.d is doing, so I'm very interested in how vibe.d is progressing.

vibe.d looks like a rather complex project, so I am wondering if you've made use of any shared libs with D (i.e., .so and/or .a compiled for PIC)?

I know that the druntime will not link as-is without a rebuild to enable PIC, so have you found this to be a problem, not using shared libs, or have you rebuilt druntime to allow for it?

I'm also wondering how the co-routines are working out with vibe? I thought of using them, but my current design will be using message passing instead, where the code is broken up into small parts to perform the co-processing. When messages are received at a location, the code fragment executes. I've done this before in C++ and it worked great, but with D I now have an alternative using fibers, but I have no exerience with using them.

Thanks for any input you can provide.

--rt

On 2012-11-01 19:53, Rob T wrote:

> I know that the druntime will not link as-is without a rebuild to enable
> PIC, so have you found this to be a problem, not using shared libs, or
> have you rebuilt druntime to allow for it?

It's not enough to just recompile druntime. It's missing functionality to allow true dynamic linking (i.e. dlopen).

-- 
/Jacob Carlborg

On Thursday, 1 November 2012 at 19:23:49 UTC, Jacob Carlborg wrote:
> On 2012-11-01 19:53, Rob T wrote:
>
>> I know that the druntime will not link as-is without a rebuild to enable
>> PIC, so have you found this to be a problem, not using shared libs, or
>> have you rebuilt druntime to allow for it?
>
> It's not enough to just recompile druntime. It's missing functionality to allow true dynamic linking (i.e. dlopen).

I understand what you are saying, however I was told that you can still use shared libs in a limited way. The tricky part is knowing what will work and what will not, and why.

I'm used to coding apps that use shared libs, and loadable plugins are rather essential to have for some apps, so this is an area of interest that maybe I can work on resolving down the road. I'm also interested in understanding how people are managing without shared libs. It's nice to be able to upgrade code by compiling one shared lib and installing it, as opposed to rebuilding an entire set of apps that statically link the lib.

--rt

On Thu, 01 Nov 2012 21:29:25 +0100
"Rob T" <rob@ucora.com> wrote:

> On Thursday, 1 November 2012 at 19:23:49 UTC, Jacob Carlborg wrote:
> > On 2012-11-01 19:53, Rob T wrote:
> >
> >> I know that the druntime will not link as-is without a rebuild
> >> to enable
> >> PIC, so have you found this to be a problem, not using shared
> >> libs, or
> >> have you rebuilt druntime to allow for it?
> >
> > It's not enough to just recompile druntime. It's missing functionality to allow true dynamic linking (i.e. dlopen).
> 
> I understand what you are saying, however I was told that you can still use shared libs in a limited way. The tricky part is knowing what will work and what will not, and why.
> 

This was discussed fairly recently over on 'digitalmars.D'. Although I'm afraid I don't remember the subject line offhand or have a link.