So from what I understand so far is that WtDesktop was an abandon, but
lead to WtHttpd?
I am looking for more background so I can get a grasp on what needs to
get done for WtHttpd to be able work similar to Atom Electron.
As it is WtHttpd can run as a desktop app in Qt by boxing its Webapp,
not the same as a desktop app, and I have actually never tired this,
read about it, but for my needs it works pretty good as it is, I can
run it from my desktop, and use an browser to access it, even Qt
Creator works great, its what I use, but to have access to the Menu of
a app, would require a lot more work, and Atom proved it can be done,
they based it on Node.js, but I don't see C++ being a problem, but I
have never written a app like that, and would have to start from
scratch, and maybe that is not a bad idea.
It seems that I just need to write a Qt that can run WtHttpd and
interact with it on some level, even if it means I have to write my own
menu system, and push urls to interact with WtHttpd, I know that can be
done now, I would like to know if any projects exist that do this, it
seems like a cheat for what I really want, which is what you described
and maybe a little more, it seems what I would like to do is just have
a directive to define desktop or web, and be done, it seems like that
is possible, but it would require all output to use native controls and
not web based calls, looking at the code I know another library could
be written to compile it against, it would have to convert all the Wt
calls to Qt, and even then there is a lot of logic and database stuff
that would require a lot of work, but it would be great if it was that
easy, but real life means what can we do now, and what can we plan on
for the future.
It seems to me that the Future is going to be about projects like Atom
Electron, because that is where Web Development is going, and Wt should
look for a path that leads to Desktop Apps, and maybe a Qt Wrapper will
do the Job, its easier and I will do more Research on it, and get a
working prototype to see what Interest it will generate, but I need a
Plugin Manager, and that is not an Option, it needs to work like
Node.js in that its all Modular, and I would like to know what Plugin
Manager people at Wt doing development would like to use, I have only
found a few that sound promising, role your own in Dr. DobbsÂ
http://www.drdobbs.com/cpp/building-your-own-plugin-framework-part/2042
02899
Or Pluga by Sourcy
http://sourcey.com/building-a-simple-cpp-cross-platform-plugin-system/
My concept is simple, the Plugin Manager is for Wt Apps, so if I want
to use lets say Wt's Blog app, I can just plug it in and access it, I
do not see a problem with running a Qt Wrapper for a Desktop version,
its main advantage is that I can add Desktop capability to a deployed
web app, so the web app that is framed by Qt can be local or deployed,
my main goal is a CMS, so I can push my Local app to my Public one, so
the Menus would allow me to do that, and I am sure a lot of Wt
Developers would like that kind of Control.
Everyone that builds web apps with Wt have different needs, but the
Need for a Plugin Manager and Need for a Qt Wrapper App, should be
something that everyone can agree on, we can all use one in our
project, so is anyone interested in giving an opinion on which Plugin
Manager would be better suited for Wt and all your needs, and if anyone
has written a Qt Wrapper that works with wthttpd?
Â
Looking at old threads
http://redmine.webtoolkit.eu/boards/1/topics/1266
I found this, but links are dead:Â https://gitorious.org/wtdesktop
https://sourceforge.net/p/witty/mailman/message/26137596/
https://www.openhub.net/p/WtDesktop
Thanks
wtdesktop but I never had the time to do it. If you google the
mailing list archive, or look in the wiki (in the Summer of Code
ideas), you'll find some.
Electron is meant to develop desktop apps in the first place (that's
"easy"), my plans for wtdesktop were a bit more ambitous: develop a
webapp with Wt, then "declare" your "channels": some features that
would be available only when working inside a browser, and some
feature that would be available only when working in desktop mode (e.
g. File, Edit, etc menus).
Post by Pau Garcia i QuilesPost by Wim DumonHey Jeffrey,
The wthttp source code is part of Wt, and can be found in src/http.
don't think that project is still supported, but you may find
inspiration there.Â
Post by Pau Garcia i QuilesPost by Wim DumonBest regards,
Wim.
Post by Jeffrey Scott Flesher GmailPost by Pau Garcia i QuilesOn 30 September 2016 at 22:17, Jeffrey Scott Flesher Gmail <jeffrey
Post by Wim DumonIs wthttp maintained as a separate project, or is it just part of Wt?
Post by Pau Garcia i QuilesPost by Jeffrey Scott Flesher GmailDo you have a link to the development of it, I am interested in
knowing more about it, I want to know if it can be adapted to
work like Atom Electron?
Post by Pau Garcia i QuilesPost by Wim Dumon-------------------------------------------------------------------
-----------
Post by Pau Garcia i QuilesCheck out the vibrant tech community on one of the world's mostÂ
Post by Wim Dumonengaging tech sites, SlashDot.org! http://sdm.link/slashdot__________
_____________________________________
Post by Pau Garcia i Quileswitty-interest mailing list
https://lists.sourceforge.net/lists/listinfo/witty-interest