Hey Guys:
IDE : VS 2008 Team Suite trial edition
OS : Windows XP (SP3)
*Wt : 2.2.4 (I thought I was using 2.99)*
Browser : IE v6
> First of all, which version of Wt are you using,
> simplechat + filetostring questions make me think you're using an older
> version of wt?
>
Yeah you were right...it is version 2.2.4 ...version 2.99 is the latest
isn't it?
> A few of your problems are due to missing Ext,
> ./examples/HINTS.txt explains what you need to do.
>
I did find HINTS.txt file in BUILD / examples and it says that if the
resource files are not found I might get a 404. But I got it only for one
example, bobsmith.
> The git view example is probably missing git,
> can you verify this?
Yeah ...I checked it up. Is it the GIT source control we are dealing with?
If yes, then I do not have that...I will get it soon
> Dragdrop, are you starting the example from the src (where the icons are
> located),
> this would also explain the ???xyz??? errors (here because the resource
> file cannot be found).
>
I do not know what you are saying. Is it the image folder u are talking
about? I only got the cannot refresh sign for icons container. Does that
mean that I need some third party javascript library from
http://yogurtearl.com as HINTS.txt says? Or do I have to copy over the image
folder to the folder where solution is?
Well, one more thing I wanted to ask in this regards is, I want to keep the
framework / library related files separate from the example projects and the
ones I create. Now, what CMake does is, it puts all the content in one
directory BUILD. I do not exactly remember the steps of how I installed Wt,
but since I am successful in building Wt examples, I would say I was right.
The BUILD directory contains all the directories like doc, examples, src,
etc. and it is located in D: \ My Documents \ My Projects \ BUILD...I myself
have no clue as to what I have done....
So, what I want to know is, if I have to separate the Wt lib specific files
from the project files and keep them in the installation folder, what shall
I do? Let us say, I want to link dynamically in future, what shall I do? I
am thinking of going for Wt 2.99 and redo all the process...what do u think
of that? What are the benefits I get by the way of Wt 2.99 and what are req?
The Boost version I am currently using is 1.40 Does it include Asio,
Spirit2.1/2.2, etc.
> MMM is the format for the 3 first chars of a month' s name (e.g.: Jan ->
> January).
>
Yeah...that was dumb.
I am more keen to build Wt samples without the slightest of error...so here
are a couple of other important Qs apart from the ones above:
- What about the functionality supporting the dragging of the popup dialogs
by clicking the title bar and holding it down to drag?
- Why do I keep getting runtime error dialogs; mostly owing to javascripts
for some of the samples mentioned above?
Thanks and regards,
Bhushan
On Tue, Oct 13, 2009 at 3:59 AM, OvermindDL1 <[email protected]> wrote:
> On Mon, Oct 12, 2009 at 7:43 AM, Wim Dumon <[email protected]> wrote:
> > Looking forward to your contribution... When did Spirit2 make its
> > intro? Currently we depend on boost >= 1.35, and I'm wondering if we
> > should support Spirit.Classic for backward compatibility reasons.
> > There's no need to put parts of boost in Wt.
>
> Boost.Spirit2.0 (missing many features over Classic, but is still
> faster in execution speed, slower in compile speed) was released with
> Boost 1.39.
> Boost.Spirit2.1 (includes all of the features and much more, faster
> execution speed, faster compile speed) will be released in Boost 1.41.
> Boost.Spirit2.2 (adds customization feature points that make writing
> grammars with very odd constructs really easy, Wt would not need that
> feature) will be released in Boost 1.42.
>
> Boost has a tool called bcp. bcp allows you to say what parts of
> boost you want to use and it will extract those parts, dependencies,
> and etc... into a directory of your choosing; it can also rename the
> boost namespace to something else; and all extracted headers are
> designed to co-exist with any installed Boost of any version as it is
> completely self-contained. Boost is designed to be split up like
> this, take the parts you want and include it in your own projects,
> where boost can still be installed on the system itself for if the
> library user wants to use other things that were not extracted by bcp.
>
> But yes, Boost.Spirit2.1+ is *tremendously* faster then Classic, and
> thus far it is tremendously faster then any other parser we have
> tested from ANTLR (ANTLR is slower then heck we found out) to
> decade-old hand-grown company parser code (where the Spirit2.1 code
> was about a hundred the length and outperformed it from between 2x to
> 8x, and was never slower) and many things in between (if you happen to
> find something that is faster, give it to us and we will make
> Spirit2.1+ faster then it as well).
>
>
> On Mon, Oct 12, 2009 at 7:47 AM, Wim Dumon <[email protected]> wrote:
> > The speed improvements are probably not worth switching to the new
> > signals, as this is not the area where the library spends a lot of
> > time. Better thread-safety would be a good thing (but the model of
> > boost.signal suits current Wt fine). I haven't looked at signals2 yet;
> > I hope it's a switch we can do under the hood without API changes.
>
> Regardless, any speed improvements are beneficial. The API is mostly
> the same, the changes are minor, and should not cause any front-end
> code changes from what I have seen thus far (except perhaps if people
> made their own signals they would need to change it to signal2 or so,
> can probably be worked around with a typedef or something).
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
