Hi Nagaev,

Thanks so much for your feedback.

My comments are below:

On Mon, Jul 30, 2012 at 2:06 AM, Nagaev Boris <[email protected]> wrote:

> Hi Matthew,
>
> 1. I think wt-config.xml should not be a part of generated project. I
> mean, code generated should not depend on specific settings in
> wt-config.xml. If it does depend on wt-config.xml, then freedom to
> change wt-config.xml would be taken away from developer of project.
>

Yeah, I was thinking to have it generate a template for wt-config that
cmake uses to generate the real file depending on cmake variables entered.
For example if you're building in debug mode, then the Wt debug flag would
be turned on.

I was thinking to have it generate just a development version, so just
using the Wt internal web server, and for other deployments, you'd have to
custamize it.

It wouldn't take away freedom from the developer, as it just generates it
once when you're starting your new project and won't override any of your
changes. It might be good to have it be filled with useful comments on
configuration options.


> 2. I am not sure, that Wt's standard images, css and JS should be
> placed into project's dir. IMHO, Project dir should not include files,
> that must not be changed by user. Wt's files must not be changed by
> user. So it is better to use system-wide Wt's filed. For example, in
> Debian and Ubuntu they can be found in /usr/share/Wt. CMake magic can
> be used to find them in cross-platform manner. (This does not mean,
> that Wt's standard files can not be copied by cmake in build dir.)
>

Thanks that's a good idea. I might make it an option to copy them, or just
have the run.sh script, or wt-config if possible tell Wt to look in the
system location.


> 3. I think, cmake/FindWt.cmake may be useful
>

Yeah, definitely. One thing it should have should be variables to look for
the debug Wt libraries plus the non debug versions. You know how when you
compile Wt, it can build wtd.so for the debug version and wt.so for the
release one.


> 4. CSS/Wt Layout should an option.
>

Yeah, I use 'compass' in my projects to generate the CSS. I'm not sure if
adding a compass source dir and a 'make css' command would be popular as
that kind of adds to the learning curve, but it does provide a lot of
power. I think I'll add CSS last, and decide then how best to do it.

5. Wt version. For example, Wt::Auth 3.2.0 and 3.2.1 are not
> compatible (because of RegistrationModel and AuthModel, introduced in
> Wt 3.2.1). So desired Wt's version (or version range) should an option
> of witty-codegen.
>

I was planning to only make it work with the latest and future versions. My
thinking being, it's for writing new projects, and most new projects would
use the latest available.

6. C++ version. Let it be old c++ (c++98 which is the same for
> programmers as c++03). Many of c++11 features (like for=foreach) are
> already in boost. Since Wt is using boost, it would be wise to use it
> as well. I think, moving to c++11 will happen, when Wt itself moves to
> c++11. By the way, "Support both" can be done not only by compiler
> pre-processing, but also by pre-processing in witty-codegen itself.
>

Good idea for the witty-codegen processing.. My thinking at the moment is
to just support c++11 as by the time this script gets to maturity, Ubuntu
Precise will be out with gcc4.7, which will mean it's pretty mainstream by
then, and again it's for new projects, so I expect most people will want to
be working with the latest available.

>
> Boris Nagaev
>

Many Thanks
Matthew Sherborne
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to