cppcms-users — Disussions of users of CppCMS

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[mawan s. <ma...@gm...>]

Thankyou Artyom


I will try it.




On 7/23/17, Artyom Beilis <art...@gm...> wrote:
> First of all clearly as I suspected there are different iconv libs in
> the process
>
> $ diff -u CMakeCache_1.1.0.txt CMakeCache_1.0.5.txt
> --- CMakeCache_1.1.0.txt        2017-07-22 22:16:37.166633497 +0300
> +++ CMakeCache_1.0.5.txt        2017-07-22 22:16:34.966608893 +0300
> [snip]
> //Path to a file.
> -ICONV_INCLUDE_DIR:PATH=/usr/include
> +ICONV_INCLUDE_DIR:PATH=/opt/local/include
>
> //Path to a library.
> -ICONV_LIB:FILEPATH=/usr/lib/libiconv.dylib
> +ICONV_LIB:FILEPATH=/opt/local/lib/libiconv.dylib
>
> What I don't understand is how it was found. Probably when you run the
> 1.0.5 build you have gave an option to
> search in /opt/local/(include|lib) while for 1.1.0 you didn't maybe
> you forget to rebuild the configuration for
> 1.0.5 or something else.
>
> I suggest may 100% clean build for 1.0.5 and 1.1.0 i.e. create new
> directory test_build and run CMake only
> to see to which iconv points.
>
> The error you see is caused by using incompatible header and dynlib
> and having more than one iconv header/library installed.
> I probably need to add some additional tests that validate
> header/library compatibility.
>
> Artyom
>
>
> On Fri, Jul 21, 2017 at 5:44 AM, mawan sugiyanto <ma...@gm...> wrote:
>> Dear
>> Artyom
>>
>>
>> please see attached file.
>>
>>
>>
>> thankyou.
>>
>> On Jul 20, 2017 20:32, "Artyom Beilis" <art...@gm...> wrote:
>>>
>>> On Thu, Jul 20, 2017 at 2:17 PM, mawan sugiyanto <ma...@gm...>
>>> wrote:
>>> > Dear Artyom
>>> >
>>> > for version 1.0.5 can compile normally ..
>>> > for version 1.1.1 on mac still error libiconv
>>> >
>>> >
>>> > Thankyou
>>> >
>>>
>>> You mean you do two builds one after other on Mac OS X and 1.0.5 ok
>>> while 1.1.0 fails? Interesting...
>>> Can you please attach CMakeCache.txt from each of the builds. It is
>>> really strange.
>>>
>>> Artyom
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Cppcms-users mailing list
>>> Cpp...@li...
>>> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Cppcms-users mailing list
>> Cpp...@li...
>> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>

Re: [Cppcms-users] Simple user account login / password

[Nazım C. B. <naz...@ne...>]

Hi,

As far as I know, no there is not. Just for reference, even in Django, 
it requires several other libraries but these dependencies are hidden 
behind the Django and they are getting installed while installing Django.

My personal preference is, using Argon2 library 
(https://github.com/P-H-C/phc-winner-argon2) to securely store 
passwords. Dependencies: 1) CppDB for accessing database, 2) Argon2 to 
compute and verify password hashes.

Regards,
Nazim Can.


On 23.07.2017 14:24, jupiter wrote:
> Hi,
>
> In Django that user and admin login / password was very easy in the 
> framework. Is there a simple user and admin login / password example 
> source code available in cppcms? I was looking it from the wikipp 
> source code, but it is to completed, requires several other libraries 
> to build it.
>
> Thank you.
>
> Kind regards,
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users

Re: [Cppcms-users] CSS example

[CN <cn...@fa...>]

On Sun, Jul 23, 2017, at 07:11 PM, jupiter wrote:
> Thanks for the response. I know I need to add the external css in the template file, I built it, the  ran the css -c config.js and http://localust:8080/css, but that did not show the background color defined in style.css. I copied the first.tmpl to index.html and I could see the background color from file:///tmp/index.html. That is why I was asking what was the difference between an html file and cppcms template file??
Then I would check whether or not the HTTP server can find and read file "style.css".
Regards,
CN


-- 
http://www.fastmail.com - Send your email first class

[Cppcms-users] Simple user account login / password

[jupiter <jup...@gm...>]

Hi,

In Django that user and admin login / password was very easy in the
framework. Is there a simple user and admin login / password example source
code available in cppcms? I was looking it from the wikipp source code, but
it is to completed, requires several other libraries to build it.

Thank you.

Kind regards,

Re: [Cppcms-users] CSS example

[jupiter <jup...@gm...>]

Thanks for the response. I know I need to add the external css in the
template file, I built it, the  ran the css -c config.js and
http://localust:8080/css, but that did not show the background color
defined in style.css. I copied the first.tmpl to index.html and I could see
the background color from file:///tmp/index.html. That is why I was asking
what was the difference between an html file and cppcms template file??

$ cat first.tmpl
<% c++ #include "content.h" %>
<% skin my_skin %>
<% view message uses content::message %>
<% template render() %>
<html>
<head>
<link href="style.css" rel="stylesheet" type="text/css" />
</head>

<body>
<h1>Title: <%= title %></h1>
<p>Content detail: <%= text %>, value = <%= value %></p>
</body>
<html>
<% end template %>
<% end view %>
<% end skin %>


$ cat style.css
body {
    background-color: #abc123;
}

h1 {
    color: white;
    text-align: center;
}

p {
    font-family: verdana;
    font-size: 20px;
}


On Sun, Jul 23, 2017 at 3:39 AM, CN <cn...@fa...> wrote:

> On Sat, Jul 22, 2017, at 04:01 PM, jupiter wrote:
>
> I am learning CPPCMS, but could not find an example for css in the source
> /example, is there any example code for css?
>
>
> Just embed <link> tags
>
> <link href="my_style.css" rel="stylesheet" type="text/css" />
>
> in your output as you  would embed them in your usual static html file.
>
> For example, a template with <link> tag might look like this:
>
> <% c++ #include "my_file.h" %>
> <% xhtml %>
> <% skin view %>
> <% view my_view uses content::my_content %>
> <% template render() %>
> <html xmlns="http://www.w3.org/1999/xhtml">
> <head>
> <title><% gt "This is my first page." %></title>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
> <link href="my_style.css" rel="stylesheet" type="text/css" />
> </head>
> <body>
> <h1><% gt "CppCMS Rocks" %></h1>
> </body>
> </html>
>
> Best Regards,
> CN
>
> -- http://www.fastmail.com - Accessible with your email software
>                           or over the web
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>
>

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[Artyom B. <art...@gm...>]

First of all clearly as I suspected there are different iconv libs in
the process

$ diff -u CMakeCache_1.1.0.txt CMakeCache_1.0.5.txt
--- CMakeCache_1.1.0.txt        2017-07-22 22:16:37.166633497 +0300
+++ CMakeCache_1.0.5.txt        2017-07-22 22:16:34.966608893 +0300
[snip]
//Path to a file.
-ICONV_INCLUDE_DIR:PATH=/usr/include
+ICONV_INCLUDE_DIR:PATH=/opt/local/include

//Path to a library.
-ICONV_LIB:FILEPATH=/usr/lib/libiconv.dylib
+ICONV_LIB:FILEPATH=/opt/local/lib/libiconv.dylib

What I don't understand is how it was found. Probably when you run the
1.0.5 build you have gave an option to
search in /opt/local/(include|lib) while for 1.1.0 you didn't maybe
you forget to rebuild the configuration for
1.0.5 or something else.

I suggest may 100% clean build for 1.0.5 and 1.1.0 i.e. create new
directory test_build and run CMake only
to see to which iconv points.

The error you see is caused by using incompatible header and dynlib
and having more than one iconv header/library installed.
I probably need to add some additional tests that validate
header/library compatibility.

Artyom


On Fri, Jul 21, 2017 at 5:44 AM, mawan sugiyanto <ma...@gm...> wrote:
> Dear
> Artyom
>
>
> please see attached file.
>
>
>
> thankyou.
>
> On Jul 20, 2017 20:32, "Artyom Beilis" <art...@gm...> wrote:
>>
>> On Thu, Jul 20, 2017 at 2:17 PM, mawan sugiyanto <ma...@gm...> wrote:
>> > Dear Artyom
>> >
>> > for version 1.0.5 can compile normally ..
>> > for version 1.1.1 on mac still error libiconv
>> >
>> >
>> > Thankyou
>> >
>>
>> You mean you do two builds one after other on Mac OS X and 1.0.5 ok
>> while 1.1.0 fails? Interesting...
>> Can you please attach CMakeCache.txt from each of the builds. It is
>> really strange.
>>
>> Artyom
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Cppcms-users mailing list
>> Cpp...@li...
>> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>

Re: [Cppcms-users] CSS example

[CN <cn...@fa...>]

On Sat, Jul 22, 2017, at 04:01 PM, jupiter wrote:
> I am learning CPPCMS, but could not find an example for css in the source /example, is there any example code for css?
Just embed <link> tags

<link href="my_style.css" rel="stylesheet" type="text/css" />

in your output as you  would embed them in your usual static html file.
For example, a template with <link> tag might look like this:

<% c++ #include "my_file.h" %>
<% xhtml %>
<% skin view %>
<% view my_view uses content::my_content %>
<% template render() %>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title><% gt "This is my first page." %></title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link href="my_style.css" rel="stylesheet" type="text/css" />
</head>
<body>
<h1><% gt "CppCMS Rocks" %></h1>
</body>
</html>

Best Regards,
CN

-- 
http://www.fastmail.com - Accessible with your email software
                          or over the web

[Cppcms-users] CSS example

[jupiter <jup...@gm...>]

Hi,

I am learning CPPCMS, but could not find an example for css in the source
/example, is there any example code for css?

Appreciate your help.

Thank you.

Kind regards,

- j

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[mawan s. <ma...@gm...>]

Dear
Artyom


please see attached file.



thankyou.

On Jul 20, 2017 20:32, "Artyom Beilis" <art...@gm...> wrote:
>
> On Thu, Jul 20, 2017 at 2:17 PM, mawan sugiyanto <ma...@gm...> wrote:
> > Dear Artyom
> >
> > for version 1.0.5 can compile normally ..
> > for version 1.1.1 on mac still error libiconv
> >
> >
> > Thankyou
> >
>
> You mean you do two builds one after other on Mac OS X and 1.0.5 ok
> while 1.1.0 fails? Interesting...
> Can you please attach CMakeCache.txt from each of the builds. It is
> really strange.
>
> Artyom
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[Artyom B. <art...@gm...>]

On Thu, Jul 20, 2017 at 2:17 PM, mawan sugiyanto <ma...@gm...> wrote:
> Dear Artyom
>
> for version 1.0.5 can compile normally ..
> for version 1.1.1 on mac still error libiconv
>
>
> Thankyou
>

You mean you do two builds one after other on Mac OS X and 1.0.5 ok
while 1.1.0 fails? Interesting...
Can you please attach CMakeCache.txt from each of the builds. It is
really strange.

Artyom

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[mawan s. <ma...@gm...>]

Dear Artyom

for version 1.0.5 can compile normally ..
for version 1.1.1 on mac still error libiconv


Thankyou





On 7/20/17, Artyom Beilis <art...@gm...> wrote:
> Can you please check if it is case of :
> http://cppcms.com/wikipp/en/page/cppcms_1x_build_troubleshooting#The.iconv.library.is.not.found.on.Mac.OS.X
>
> Check that header and library do not come from different sources.
>
> On Thu, Jul 20, 2017 at 11:02 AM, mawan sugiyanto <ma...@gm...>
> wrote:
>> successfully build on centos 7
>>
>> On 7/20/17, mawan sugiyanto <ma...@gm...> wrote:
>>> I compile with mac os x
>>>
>>> [ 13%] Linking CXX shared library libbooster.dylib
>>> Undefined symbols for architecture x86_64:
>>>   "_libiconv", referenced from:
>>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>>> std::__1::allocator<char> >
>>> booster::locale::conv::impl::iconverter_base::real_convert<char,
>>> char>(char const*, char const*) in codepage.cpp.o
>>>       std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>,
>>> std::__1::allocator<wchar_t> >
>>> booster::locale::conv::impl::iconverter_base::real_convert<wchar_t,
>>> char>(char const*, char const*) in codepage.cpp.o
>>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>>> std::__1::allocator<char> >
>>> booster::locale::conv::impl::iconverter_base::real_convert<char,
>>> wchar_t>(wchar_t const*, wchar_t const*) in codepage.cpp.o
>>>
>>> booster::locale::impl_posix::mb2_iconv_converter::mb2_iconv_converter(std::__1::basic_string<char,
>>> std::__1::char_traits<char>, std::__1::allocator<char> > const&) in
>>> codecvt.cpp.o
>>>       booster::locale::impl_posix::mb2_iconv_converter::to_unicode(char
>>> const*&, char const*) in codecvt.cpp.o
>>>
>>> booster::locale::impl_posix::mb2_iconv_converter::from_unicode(unsigned
>>> int, char*, char const*) in codecvt.cpp.o
>>>   "_libiconv_close", referenced from:
>>>       booster::locale::conv::impl::iconv_between::~iconv_between() in
>>> codepage.cpp.o
>>>       booster::locale::conv::impl::iconv_between::~iconv_between() in
>>> codepage.cpp.o
>>>       booster::locale::conv::impl::iconv_between::open(char const*,
>>> char const*, booster::locale::conv::method_type) in codepage.cpp.o
>>>       non-virtual thunk to
>>> booster::locale::conv::impl::iconv_between::open(char const*, char
>>> const*, booster::locale::conv::method_type) in codepage.cpp.o
>>>       non-virtual thunk to
>>> booster::locale::conv::impl::iconv_between::~iconv_between() in
>>> codepage.cpp.o
>>>       non-virtual thunk to
>>> booster::locale::conv::impl::iconv_between::~iconv_between() in
>>> codepage.cpp.o
>>>       booster::locale::conv::impl::iconverter_base::~iconverter_base()
>>> in codepage.cpp.o
>>>       ...
>>>   "_libiconv_open", referenced from:
>>>       booster::locale::conv::impl::convert_between(char const*, char
>>> const*, char const*, char const*, booster::locale::conv::method_type)
>>> in codepage.cpp.o
>>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>>> std::__1::allocator<char> >
>>> booster::locale::conv::impl::convert_to<char>(char const*, char
>>> const*, char const*, booster::locale::conv::method_type) in
>>> codepage.cpp.o
>>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>>> std::__1::allocator<char> >
>>> booster::locale::conv::impl::convert_from<char>(char const*, char
>>> const*, char const*, booster::locale::conv::method_type) in
>>> codepage.cpp.o
>>>       std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>,
>>> std::__1::allocator<wchar_t> >
>>> booster::locale::conv::impl::convert_to<wchar_t>(char const*, char
>>> const*, char const*, booster::locale::conv::method_type) in
>>> codepage.cpp.o
>>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>>> std::__1::allocator<char> >
>>> booster::locale::conv::impl::convert_from<wchar_t>(wchar_t const*,
>>> wchar_t const*, char const*, booster::locale::conv::method_type) in
>>> codepage.cpp.o
>>>       booster::locale::conv::impl::iconv_between::open(char const*,
>>> char const*, booster::locale::conv::method_type) in codepage.cpp.o
>>>       non-virtual thunk to
>>> booster::locale::conv::impl::iconv_between::open(char const*, char
>>> const*, booster::locale::conv::method_type) in codepage.cpp.o
>>>       ...
>>> ld: symbol(s) not found for architecture x86_64
>>> clang: error: linker command failed with exit code 1 (use -v to see
>>> invocation)
>>> make[2]: *** [booster/libbooster.1.1.0.dylib] Error 1
>>> make[1]: *** [booster/CMakeFiles/booster.dir/all] Error 2
>>> make: *** [all] Error 2
>>>
>>>
>>> On 7/12/17, Shiv Shankar Dayal <shi...@gm...> wrote:
>>>> Here is the attached log.
>>>>
>>>> On Wed, Jul 12, 2017 at 11:21 AM, Artyom Beilis
>>>> <art...@gm...>
>>>> wrote:
>>>>
>>>>> > Tested with Ubuntu 16.04, GCC 7.0.1(experimental). Compiles and all
>>>>> > tests
>>>>> > are successful but I see some warnings about implicit-fallthrough
>>>>> > during
>>>>> > compilation phase. Would you want to look at them?
>>>>>
>>>>> Yes, thanks.
>>>>>
>>>>> Artyom
>>>>>
>>>>> ------------------------------------------------------------
>>>>> ------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>> _______________________________________________
>>>>> Cppcms-users mailing list
>>>>> Cpp...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Respect,
>>>> Shiv Shankar Dayal
>>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Cppcms-users mailing list
>> Cpp...@li...
>> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[Artyom B. <art...@gm...>]

Can you please check if it is case of :
http://cppcms.com/wikipp/en/page/cppcms_1x_build_troubleshooting#The.iconv.library.is.not.found.on.Mac.OS.X

Check that header and library do not come from different sources.

On Thu, Jul 20, 2017 at 11:02 AM, mawan sugiyanto <ma...@gm...> wrote:
> successfully build on centos 7
>
> On 7/20/17, mawan sugiyanto <ma...@gm...> wrote:
>> I compile with mac os x
>>
>> [ 13%] Linking CXX shared library libbooster.dylib
>> Undefined symbols for architecture x86_64:
>>   "_libiconv", referenced from:
>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>> std::__1::allocator<char> >
>> booster::locale::conv::impl::iconverter_base::real_convert<char,
>> char>(char const*, char const*) in codepage.cpp.o
>>       std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>,
>> std::__1::allocator<wchar_t> >
>> booster::locale::conv::impl::iconverter_base::real_convert<wchar_t,
>> char>(char const*, char const*) in codepage.cpp.o
>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>> std::__1::allocator<char> >
>> booster::locale::conv::impl::iconverter_base::real_convert<char,
>> wchar_t>(wchar_t const*, wchar_t const*) in codepage.cpp.o
>>
>> booster::locale::impl_posix::mb2_iconv_converter::mb2_iconv_converter(std::__1::basic_string<char,
>> std::__1::char_traits<char>, std::__1::allocator<char> > const&) in
>> codecvt.cpp.o
>>       booster::locale::impl_posix::mb2_iconv_converter::to_unicode(char
>> const*&, char const*) in codecvt.cpp.o
>>
>> booster::locale::impl_posix::mb2_iconv_converter::from_unicode(unsigned
>> int, char*, char const*) in codecvt.cpp.o
>>   "_libiconv_close", referenced from:
>>       booster::locale::conv::impl::iconv_between::~iconv_between() in
>> codepage.cpp.o
>>       booster::locale::conv::impl::iconv_between::~iconv_between() in
>> codepage.cpp.o
>>       booster::locale::conv::impl::iconv_between::open(char const*,
>> char const*, booster::locale::conv::method_type) in codepage.cpp.o
>>       non-virtual thunk to
>> booster::locale::conv::impl::iconv_between::open(char const*, char
>> const*, booster::locale::conv::method_type) in codepage.cpp.o
>>       non-virtual thunk to
>> booster::locale::conv::impl::iconv_between::~iconv_between() in
>> codepage.cpp.o
>>       non-virtual thunk to
>> booster::locale::conv::impl::iconv_between::~iconv_between() in
>> codepage.cpp.o
>>       booster::locale::conv::impl::iconverter_base::~iconverter_base()
>> in codepage.cpp.o
>>       ...
>>   "_libiconv_open", referenced from:
>>       booster::locale::conv::impl::convert_between(char const*, char
>> const*, char const*, char const*, booster::locale::conv::method_type)
>> in codepage.cpp.o
>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>> std::__1::allocator<char> >
>> booster::locale::conv::impl::convert_to<char>(char const*, char
>> const*, char const*, booster::locale::conv::method_type) in
>> codepage.cpp.o
>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>> std::__1::allocator<char> >
>> booster::locale::conv::impl::convert_from<char>(char const*, char
>> const*, char const*, booster::locale::conv::method_type) in
>> codepage.cpp.o
>>       std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>,
>> std::__1::allocator<wchar_t> >
>> booster::locale::conv::impl::convert_to<wchar_t>(char const*, char
>> const*, char const*, booster::locale::conv::method_type) in
>> codepage.cpp.o
>>       std::__1::basic_string<char, std::__1::char_traits<char>,
>> std::__1::allocator<char> >
>> booster::locale::conv::impl::convert_from<wchar_t>(wchar_t const*,
>> wchar_t const*, char const*, booster::locale::conv::method_type) in
>> codepage.cpp.o
>>       booster::locale::conv::impl::iconv_between::open(char const*,
>> char const*, booster::locale::conv::method_type) in codepage.cpp.o
>>       non-virtual thunk to
>> booster::locale::conv::impl::iconv_between::open(char const*, char
>> const*, booster::locale::conv::method_type) in codepage.cpp.o
>>       ...
>> ld: symbol(s) not found for architecture x86_64
>> clang: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>> make[2]: *** [booster/libbooster.1.1.0.dylib] Error 1
>> make[1]: *** [booster/CMakeFiles/booster.dir/all] Error 2
>> make: *** [all] Error 2
>>
>>
>> On 7/12/17, Shiv Shankar Dayal <shi...@gm...> wrote:
>>> Here is the attached log.
>>>
>>> On Wed, Jul 12, 2017 at 11:21 AM, Artyom Beilis <art...@gm...>
>>> wrote:
>>>
>>>> > Tested with Ubuntu 16.04, GCC 7.0.1(experimental). Compiles and all
>>>> > tests
>>>> > are successful but I see some warnings about implicit-fallthrough
>>>> > during
>>>> > compilation phase. Would you want to look at them?
>>>>
>>>> Yes, thanks.
>>>>
>>>> Artyom
>>>>
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Cppcms-users mailing list
>>>> Cpp...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>>>>
>>>
>>>
>>>
>>> --
>>> Respect,
>>> Shiv Shankar Dayal
>>>
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[mawan s. <ma...@gm...>]

successfully build on centos 7

On 7/20/17, mawan sugiyanto <ma...@gm...> wrote:
> I compile with mac os x
>
> [ 13%] Linking CXX shared library libbooster.dylib
> Undefined symbols for architecture x86_64:
>   "_libiconv", referenced from:
>       std::__1::basic_string<char, std::__1::char_traits<char>,
> std::__1::allocator<char> >
> booster::locale::conv::impl::iconverter_base::real_convert<char,
> char>(char const*, char const*) in codepage.cpp.o
>       std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>,
> std::__1::allocator<wchar_t> >
> booster::locale::conv::impl::iconverter_base::real_convert<wchar_t,
> char>(char const*, char const*) in codepage.cpp.o
>       std::__1::basic_string<char, std::__1::char_traits<char>,
> std::__1::allocator<char> >
> booster::locale::conv::impl::iconverter_base::real_convert<char,
> wchar_t>(wchar_t const*, wchar_t const*) in codepage.cpp.o
>
> booster::locale::impl_posix::mb2_iconv_converter::mb2_iconv_converter(std::__1::basic_string<char,
> std::__1::char_traits<char>, std::__1::allocator<char> > const&) in
> codecvt.cpp.o
>       booster::locale::impl_posix::mb2_iconv_converter::to_unicode(char
> const*&, char const*) in codecvt.cpp.o
>
> booster::locale::impl_posix::mb2_iconv_converter::from_unicode(unsigned
> int, char*, char const*) in codecvt.cpp.o
>   "_libiconv_close", referenced from:
>       booster::locale::conv::impl::iconv_between::~iconv_between() in
> codepage.cpp.o
>       booster::locale::conv::impl::iconv_between::~iconv_between() in
> codepage.cpp.o
>       booster::locale::conv::impl::iconv_between::open(char const*,
> char const*, booster::locale::conv::method_type) in codepage.cpp.o
>       non-virtual thunk to
> booster::locale::conv::impl::iconv_between::open(char const*, char
> const*, booster::locale::conv::method_type) in codepage.cpp.o
>       non-virtual thunk to
> booster::locale::conv::impl::iconv_between::~iconv_between() in
> codepage.cpp.o
>       non-virtual thunk to
> booster::locale::conv::impl::iconv_between::~iconv_between() in
> codepage.cpp.o
>       booster::locale::conv::impl::iconverter_base::~iconverter_base()
> in codepage.cpp.o
>       ...
>   "_libiconv_open", referenced from:
>       booster::locale::conv::impl::convert_between(char const*, char
> const*, char const*, char const*, booster::locale::conv::method_type)
> in codepage.cpp.o
>       std::__1::basic_string<char, std::__1::char_traits<char>,
> std::__1::allocator<char> >
> booster::locale::conv::impl::convert_to<char>(char const*, char
> const*, char const*, booster::locale::conv::method_type) in
> codepage.cpp.o
>       std::__1::basic_string<char, std::__1::char_traits<char>,
> std::__1::allocator<char> >
> booster::locale::conv::impl::convert_from<char>(char const*, char
> const*, char const*, booster::locale::conv::method_type) in
> codepage.cpp.o
>       std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>,
> std::__1::allocator<wchar_t> >
> booster::locale::conv::impl::convert_to<wchar_t>(char const*, char
> const*, char const*, booster::locale::conv::method_type) in
> codepage.cpp.o
>       std::__1::basic_string<char, std::__1::char_traits<char>,
> std::__1::allocator<char> >
> booster::locale::conv::impl::convert_from<wchar_t>(wchar_t const*,
> wchar_t const*, char const*, booster::locale::conv::method_type) in
> codepage.cpp.o
>       booster::locale::conv::impl::iconv_between::open(char const*,
> char const*, booster::locale::conv::method_type) in codepage.cpp.o
>       non-virtual thunk to
> booster::locale::conv::impl::iconv_between::open(char const*, char
> const*, booster::locale::conv::method_type) in codepage.cpp.o
>       ...
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> make[2]: *** [booster/libbooster.1.1.0.dylib] Error 1
> make[1]: *** [booster/CMakeFiles/booster.dir/all] Error 2
> make: *** [all] Error 2
>
>
> On 7/12/17, Shiv Shankar Dayal <shi...@gm...> wrote:
>> Here is the attached log.
>>
>> On Wed, Jul 12, 2017 at 11:21 AM, Artyom Beilis <art...@gm...>
>> wrote:
>>
>>> > Tested with Ubuntu 16.04, GCC 7.0.1(experimental). Compiles and all
>>> > tests
>>> > are successful but I see some warnings about implicit-fallthrough
>>> > during
>>> > compilation phase. Would you want to look at them?
>>>
>>> Yes, thanks.
>>>
>>> Artyom
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Cppcms-users mailing list
>>> Cpp...@li...
>>> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>>>
>>
>>
>>
>> --
>> Respect,
>> Shiv Shankar Dayal
>>
>

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[mawan s. <ma...@gm...>]

I compile with mac os x

[ 13%] Linking CXX shared library libbooster.dylib
Undefined symbols for architecture x86_64:
  "_libiconv", referenced from:
      std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >
booster::locale::conv::impl::iconverter_base::real_convert<char,
char>(char const*, char const*) in codepage.cpp.o
      std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>,
std::__1::allocator<wchar_t> >
booster::locale::conv::impl::iconverter_base::real_convert<wchar_t,
char>(char const*, char const*) in codepage.cpp.o
      std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >
booster::locale::conv::impl::iconverter_base::real_convert<char,
wchar_t>(wchar_t const*, wchar_t const*) in codepage.cpp.o
      booster::locale::impl_posix::mb2_iconv_converter::mb2_iconv_converter(std::__1::basic_string<char,
std::__1::char_traits<char>, std::__1::allocator<char> > const&) in
codecvt.cpp.o
      booster::locale::impl_posix::mb2_iconv_converter::to_unicode(char
const*&, char const*) in codecvt.cpp.o
      booster::locale::impl_posix::mb2_iconv_converter::from_unicode(unsigned
int, char*, char const*) in codecvt.cpp.o
  "_libiconv_close", referenced from:
      booster::locale::conv::impl::iconv_between::~iconv_between() in
codepage.cpp.o
      booster::locale::conv::impl::iconv_between::~iconv_between() in
codepage.cpp.o
      booster::locale::conv::impl::iconv_between::open(char const*,
char const*, booster::locale::conv::method_type) in codepage.cpp.o
      non-virtual thunk to
booster::locale::conv::impl::iconv_between::open(char const*, char
const*, booster::locale::conv::method_type) in codepage.cpp.o
      non-virtual thunk to
booster::locale::conv::impl::iconv_between::~iconv_between() in
codepage.cpp.o
      non-virtual thunk to
booster::locale::conv::impl::iconv_between::~iconv_between() in
codepage.cpp.o
      booster::locale::conv::impl::iconverter_base::~iconverter_base()
in codepage.cpp.o
      ...
  "_libiconv_open", referenced from:
      booster::locale::conv::impl::convert_between(char const*, char
const*, char const*, char const*, booster::locale::conv::method_type)
in codepage.cpp.o
      std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >
booster::locale::conv::impl::convert_to<char>(char const*, char
const*, char const*, booster::locale::conv::method_type) in
codepage.cpp.o
      std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >
booster::locale::conv::impl::convert_from<char>(char const*, char
const*, char const*, booster::locale::conv::method_type) in
codepage.cpp.o
      std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>,
std::__1::allocator<wchar_t> >
booster::locale::conv::impl::convert_to<wchar_t>(char const*, char
const*, char const*, booster::locale::conv::method_type) in
codepage.cpp.o
      std::__1::basic_string<char, std::__1::char_traits<char>,
std::__1::allocator<char> >
booster::locale::conv::impl::convert_from<wchar_t>(wchar_t const*,
wchar_t const*, char const*, booster::locale::conv::method_type) in
codepage.cpp.o
      booster::locale::conv::impl::iconv_between::open(char const*,
char const*, booster::locale::conv::method_type) in codepage.cpp.o
      non-virtual thunk to
booster::locale::conv::impl::iconv_between::open(char const*, char
const*, booster::locale::conv::method_type) in codepage.cpp.o
      ...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [booster/libbooster.1.1.0.dylib] Error 1
make[1]: *** [booster/CMakeFiles/booster.dir/all] Error 2
make: *** [all] Error 2


On 7/12/17, Shiv Shankar Dayal <shi...@gm...> wrote:
> Here is the attached log.
>
> On Wed, Jul 12, 2017 at 11:21 AM, Artyom Beilis <art...@gm...>
> wrote:
>
>> > Tested with Ubuntu 16.04, GCC 7.0.1(experimental). Compiles and all
>> > tests
>> > are successful but I see some warnings about implicit-fallthrough
>> > during
>> > compilation phase. Would you want to look at them?
>>
>> Yes, thanks.
>>
>> Artyom
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Cppcms-users mailing list
>> Cpp...@li...
>> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>>
>
>
>
> --
> Respect,
> Shiv Shankar Dayal
>

Re: [Cppcms-users] Interface with javascript

[jupiter <jup...@gm...>]

Thanks Nazim for the kind advice, appreciate your helps.

Kind regards,

- j



On Sat, Jul 15, 2017 at 10:36 PM, Nazım Can Bedir <
naz...@ne...> wrote:

> Hi,
>
> In such cases, I usually prefer to use technique which is also central to
> Apache's Tapestry project. Basic structure is follows:
>
>    - Boilerplate web page is generated by CppCMS as usual.
>    - Boilerplate web page is using require.js.
>    - On page load, require.js is loading web application's entry point.
>    - From the entry point, my own Javascript module do following:
>       - Make an Ajax requests to web app via JSON-RPC.
>       - On the server side, application is responding to requests with
>       cppcms::rpc::json_rpc_server.
>       - Javascript handles the server's response and apply changes.
>       - In my case, changes are either loading additional require.js
>       modules, or changing already existing DOM elements and their content on the
>       page.
>    - For things like user notification, I prefer to employ Server-Side
>    Events; where initial registration for the events are performed from the
>    Javascript module loaded by require.js.
>
> For JSON-RPC, please see http://cppcms.com/wikipp/en/
> page/cppcms_1x_chat_json_rpc. For Server-Side Events, please see
> http://blog.cppcms.com/post/107.
>
> Out of box, CppCMS doesn't provide any way to glue browser events and DOM
> to C++ objects. If you do not already know about, I highly suggest to take
> a quick look at tapestry.apache.org for getting an idea about how deep
> the rabbit hole may be :)
>
> Hope helps.
>
> Regards,
> Nazim Can.
>
> On 15/07/17 15:23, jupiter wrote:
>
> Hi,
>
> I am still learning the structure of the cppcms, most of examples and
> tutorials are calling cppcms generate html page. One thing I am not clear
> is how to make an interface between C++ and javascript with AJAX
> capability, the C++ feeds json to javascript which renders ajax style web
> page. Appreciate any advice.
>
> Thank you,
>
> Kind regards,
>
> - j
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Cppcms-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/cppcms-users
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>
>

Re: [Cppcms-users] Interface with javascript

[Nazım C. B. <naz...@ne...>]

Hi,

In such cases, I usually prefer to use technique which is also central 
to Apache's Tapestry project. Basic structure is follows:

  * Boilerplate web page is generated by CppCMS as usual.
  * Boilerplate web page is using require.js.
  * On page load, require.js is loading web application's entry point.
  *  From the entry point, my own Javascript module do following:
      o Make an Ajax requests to web app via JSON-RPC.
      o On the server side, application is responding to requests with
        |cppcms::rpc::json_rpc_server.|
      o Javascript handles the server's response and apply changes.
      o In my case, changes are either loading additional require.js
        modules, or changing already existing DOM elements and their
        content on the page.
  * For things like user notification, I prefer to employ Server-Side
    Events; where initial registration for the events are performed from
    the Javascript module loaded by require.js.

For JSON-RPC, please see 
http://cppcms.com/wikipp/en/page/cppcms_1x_chat_json_rpc. For 
Server-Side Events, please see http://blog.cppcms.com/post/107.

Out of box, CppCMS doesn't provide any way to glue browser events and 
DOM to C++ objects. If you do not already know about, I highly suggest 
to take a quick look at tapestry.apache.org for getting an idea about 
how deep the rabbit hole may be :)

Hope helps.

Regards,
Nazim Can.


On 15/07/17 15:23, jupiter wrote:
> Hi,
>
> I am still learning the structure of the cppcms, most of examples and 
> tutorials are calling cppcms generate html page. One thing I am not 
> clear is how to make an interface between C++ and javascript with AJAX 
> capability, the C++ feeds json to javascript which renders ajax style 
> web page. Appreciate any advice.
>
> Thank you,
>
> Kind regards,
>
> - j
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users

[Cppcms-users] Interface with javascript

[jupiter <jup...@gm...>]

 Hi,

I am still learning the structure of the cppcms, most of examples and
tutorials are calling cppcms generate html page. One thing I am not clear
is how to make an interface between C++ and javascript with AJAX
capability, the C++ feeds json to javascript which renders ajax style web
page. Appreciate any advice.

Thank you,

Kind regards,

- j

Re: [Cppcms-users] Need a help for dependencies instalation on windows

[Artyom B. <art...@gm...>]

It looks like  http://cppcms.com/wikipp/en/page/cppcms_1x_build_troubleshooting#Lots.of.tests.fails
On Mon, Jun 19, 2017 at 12:57 AM, kodjo amedome mn-dianey via
Cppcms-users <cpp...@li...> wrote:
>
>
> thank you for your reply.
> I'm ussing mingw and my os is Windows 10. I left  the icu and openssl
> libraries because they are not mandatory requirements.
>
> I started the building but as shown in the result below, 47% of my make test
> failed. what may be the causes of these failures? what will be the
> consequence if i ignore this result and continue with the installation?
>

Re: [Cppcms-users] New plugin API for your review

[Hery M. <hma...@gm...>]

Hi,

Very good news, I will test it and I will do feed back if there is any
issues.

Congratulation and Thank you.

Maminirina.


2017-07-11 16:18 GMT+03:00 Artyom Beilis <art...@gm...>:

> Hello,
>
> I completed the documentation of new plugin API:
>
>     http://cppcms.com/wikipp/en/page/cppcms_1_2_plugin_api
>
> Please review it. Comments are welcome.
>
> Artyom
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[Shiv S. D. <shi...@gm...>]

Here is the attached log.

On Wed, Jul 12, 2017 at 11:21 AM, Artyom Beilis <art...@gm...>
wrote:

> > Tested with Ubuntu 16.04, GCC 7.0.1(experimental). Compiles and all tests
> > are successful but I see some warnings about implicit-fallthrough during
> > compilation phase. Would you want to look at them?
>
> Yes, thanks.
>
> Artyom
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>



-- 
Respect,
Shiv Shankar Dayal

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[Artyom B. <art...@gm...>]

> Tested with Ubuntu 16.04, GCC 7.0.1(experimental). Compiles and all tests
> are successful but I see some warnings about implicit-fallthrough during
> compilation phase. Would you want to look at them?

Yes, thanks.

Artyom

[Cppcms-users] Updated Roadmap

[Artyom B. <art...@gm...>]

Hello,

Since 1.2 is almost ready and going to be released soon I've updated
the road map for future releases.

http://cppcms.com/wikipp/en/page/cppcms_1x_tasks


Note versioning:
- Odd numbers like 1.1, 1.3. 1.5 are beta,
- Even 1.2, 1.4, 2.0 etc are for stable
- 2.0 incompatible ABI

Comments are welcome

Artyom Beilis

Re: [Cppcms-users] CppCMS 1.1.0 Beta released

[Shiv S. D. <shi...@gm...>]

Tested with Ubuntu 16.04, GCC 7.0.1(experimental). Compiles and all tests
are successful but I see some warnings about implicit-fallthrough during
compilation phase. Would you want to look at them?

On Wed, Jul 12, 2017 at 2:17 AM, Artyom Beilis <art...@gm...>
wrote:

> Hello Dear CppCMS Users.
>
> After the goals for 1.2 were completed I announce official CppCMS
> 1.1.0 beta (stable will be 1.2.0)
>
> It is available on the usual place:
>
>     https://sourceforge.net/projects/cppcms/files/cppcms/
> 1.1.0-beta/cppcms-1.1.0.tar.bz2
>
> It includes many new and important features:
>
>     http://cppcms.com/wikipp/en/page/cppcms_1_2_whats_new
>
> Now I ask the community to fully participate in beta testing so 1.2
> will be released ASAP.
> --------------------------------------------------
>
> What do I need to test:
>
> (a) Framework Unit Test:
>
> 1. Download the beta version, build, run tests
> 2. Report on what platform you tested: OS, Compiler version, standard
> library (libstdc++/libc++)
> 3. Have you had any tests failed and if you had please attach
> Testing/Temporary/LastTest.log and CMakeCache.txt from your build
> directory
>
> I specially need tests on Mac OS X various versions, various ARM
> platforms like raspberry pi and Windows different compilers
>
> (b) Compatibility Test:
>
> 1. Try to build your existing applications with latest version, report
> any problems
> 2. If you have been using CppCMS 1.0.5 till now please try to build
> CppCMS 1.1.0 and run existing programs with new shared objects/dll
> WITHOUT rebuilding your applications - it must work as is!
>
> (c) Feature Test:
>
> Go to: http://cppcms.com/wikipp/en/page/cppcms_1_2_whats_new
>
> And try some of new features, report any issues with them or any
> problems with API design.
>
> -----------------------
>
> If all goes smoothly I'll release 1.2.0 - official stable version.
>
> Best Regards,
>   Artyom Beilis
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>



-- 
Respect,
Shiv Shankar Dayal

[Cppcms-users] CppCMS 1.1.0 Beta released

[Artyom B. <art...@gm...>]

Hello Dear CppCMS Users.

After the goals for 1.2 were completed I announce official CppCMS
1.1.0 beta (stable will be 1.2.0)

It is available on the usual place:

    https://sourceforge.net/projects/cppcms/files/cppcms/1.1.0-beta/cppcms-1.1.0.tar.bz2

It includes many new and important features:

    http://cppcms.com/wikipp/en/page/cppcms_1_2_whats_new

Now I ask the community to fully participate in beta testing so 1.2
will be released ASAP.
--------------------------------------------------

What do I need to test:

(a) Framework Unit Test:

1. Download the beta version, build, run tests
2. Report on what platform you tested: OS, Compiler version, standard
library (libstdc++/libc++)
3. Have you had any tests failed and if you had please attach
Testing/Temporary/LastTest.log and CMakeCache.txt from your build
directory

I specially need tests on Mac OS X various versions, various ARM
platforms like raspberry pi and Windows different compilers

(b) Compatibility Test:

1. Try to build your existing applications with latest version, report
any problems
2. If you have been using CppCMS 1.0.5 till now please try to build
CppCMS 1.1.0 and run existing programs with new shared objects/dll
WITHOUT rebuilding your applications - it must work as is!

(c) Feature Test:

Go to: http://cppcms.com/wikipp/en/page/cppcms_1_2_whats_new

And try some of new features, report any issues with them or any
problems with API design.

-----------------------

If all goes smoothly I'll release 1.2.0 - official stable version.

Best Regards,
  Artyom Beilis

Re: [Cppcms-users] New plugin API for your review

[Boutrin D. (EXTERNE) <DBo...@gr...>]

I suggest amalgation like sqlite3, developer work on modules header/source while release code should be done into a single file or 2 ( header + amalgation )

Regards
DBO

-----Message d'origine-----
De : Artyom Beilis [mailto:art...@gm...] 
Envoyé : mardi 11 juillet 2017 15:19
À : cpp...@li...
Objet : [Cppcms-users] New plugin API for your review

Hello,

I completed the documentation of new plugin API:

    http://cppcms.com/wikipp/en/page/cppcms_1_2_plugin_api

Please review it. Comments are welcome.

Artyom

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________
Cppcms-users mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppcms-users