[Wt-interest] Using Wt in a diferent context

Hello,

I am using a distributed software framework named XDAQ. This framework 
has created a wrapping of the cgicc through callbacks. When you want to 
create a new dynamic webpage you create a callback of type  
(OBJECT::*callback_)(Xgi:Input* in,Xgi:Output* out). Inside this 
callback you can use cgicc interface in this way:

 cgicc::Cgicc cgi(in);
//use cgi
*out << cgicc::html() << endl;
//..and so on..

My question is: Is it posible to use Wt in this context? How can I do 
that? For example, can I acces to the input/output stream of the Fastcgi 
framework?

Thank you very much. Regards,

______________________________
Marc Magrans de Abril
Wisconsin University, Madison, USA
http://triggersupervisor.cern.ch
______________________________

Re: [Wt-interest] Using Wt in a diferent context

Hey Marc,

> I am using a distributed software framework named XDAQ. This framework
> has created a wrapping of the cgicc through callbacks. When you want to
> create a new dynamic webpage you create a callback of type
> (OBJECT::*callback_)(Xgi:Input* in,Xgi:Output* out). Inside this
> callback you can use cgicc interface in this way:
>
>  cgicc::Cgicc cgi(in);
> //use cgi
> *out << cgicc::html() << endl;
> //..and so on..
>
> My question is: Is it posible to use Wt in this context? How can I do
> that? For example, can I acces to the input/output stream of the Fastcgi
> framework?

I do not think I fully understand what you want to do, but it does not look like
Wt can help you in generating dynamic content, given how XDAQ lets you
implement this call-back function -- the call-back assumes already many things
which Wt likes to have control of.

Conceptually, you should think of Wt as a GUI library, such as Qt.

So, if XDAQ allows you to write native GUI clients for it, then you
should be able to
use Wt (to develop web-based GUI clients for it).

Hope this helps,

[Wt-interest] can used in windows?

Re: [Wt-interest] can used in windows?

Hi

We're in the process of transitioning the signal and
slots implementation in Wt to some newer stuff. The
classes that were sputtered out by your compiler may
not be included in a future release. 
Please wait while we iron the issues out on the
current implementation. In the meantime, if your
willing to help tracking out some compiler errors on
different platforms, you may try out the next
iteration of Wt by check out the bleeding edge release
by anonymous cvs.

best regards,
abj
--- peng wang <wangpengdragon@...> wrote:

> hi:
>     we build witty in windows , there are many
> error, we fix some, but
> 
> 
> 
> wt3.lib(WObject.obj) : error LNK2001: unresolved
> external symbol "protected:
> void __thiscall WObject::buildSignalMap(class
> std::map<class
> std::basic_string<char,struct
> std::char_traits<char>,class
> std::allocator<char> >,class WSignalInstance_ *,stru
> ct std::less<class std::basic_string<char,struct
> std::char_traits<char>,class std::allocator<char> >
> >,class
> std::allocator<class WSignalInstance_ *>
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com