Hi Jeffery,

I am Matthew Sherborne, the author of the half finished and abandoned
witty-plus library: https://github.com/matiu2/witty-plus

The reason I started writing it was so that I could have a nice library to
get websites pushed out quickly like lucky (in some ways) rails devs.

It could be used in CMS's as the example app in there has a 'page' object
which is database driven.

The reasons I stopped working on it are:

 1. There was no interest from anyone in helping on it (probably my fault
as I never really asked)
 2. A major part of it was a login system, which Wt now has (a much more
flexibile and secure one) built in
 3. I was (re) learning c++ when I wrote it and a lot of the code is not
the best

You might be able to get some ideas from it for your project.

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

These are some of my thoughts after reading your grand CMS design.

1. QT gui for design - Awesome idea, I'm thought about doing something like
that myself. I don't think you'd be able to make it 100% wsiwg in QT
because QT doesn't have the exact same widget set as WT. Perhaps a WT
wysiwyg designer ? For an app manager, QT would be pretty good.
2. A DB record for every widget - I went down that path with witty-plus. It
means a lot of DB records to show one page. I found a different approach to
be better:

  1. There are higher level widgets, I called them content-types. So a
content type might be for example a generic Page object, or a Book that you
sell. For example:
https://github.com/matiu2/witty-plus/tree/master/wittyPlus/extensions/page
  2. The Page has some fields like, title, header, body, parent. It has
some HTML templates and classes that can render a page, list pages, show an
edit screen, and handle authorization for editing it.
  3. So you have a bunch of people that know c++ making these high level
objects.
  4. Then the CMS user, just puts some together on the same page, perhaps
with another html template or some automagic layout system in built to the
smart high level widgets.

3. CDN style - So I'm understanding from this, that you have a bunch of
witty apps all over the place serving the same thing ? I think this would
be a separate project. As my use of Wt is to write web apps, or web pages
for the public to use, I put all the static stuff in a real CDN (I use
Amakai, which is built in to Rackspace cloud files). As most of my website
viewers are in Australia or New Zealand, this gives them like 13 to 80 msec
ping times when downloading static content, but as I host in USA we still
see 200-400 msec ping times to the actual witty app :(
4. Deployment Architecture - I think the best deployment architecture is
either nginx or ha-proxy in the front, then as many Wt threaded app servers
behind as needed, then your DB, clustered/replicated as needed. You can
deploy in cheap as low spec VPSs and many of them, and with floating IPs so
that if one goes down another takes over the IP.
4. Replace cPanel - You'd need a lot of mojo to do that. Personally, I'm
not a fan of panels; I know it's probably a good market though for selling,
as there are billions of wanna-be web moguls out there :). All the open
source replacements for cPanel fall majorly short. Perhaps you're thinking
just to have a configuration page for the witty server itself ?
5. p2p push out - I think most likely your whole app will come from the DB
and maybe a few templates. I think for serving video files, the best
solution is to use a real CDN service, and one that does streaming well,
allowing restart of download mid way and whatnot. Then you don't need to
worry about how it's pushed out, as you only push it out once. I think the
p2p thing would probably require some sort of system admin guy and not be
super easy for the target audience you seem to be aiming at.

*Overall advice:*

I'd break the project down into small parts and get each part working one
by one. I'd get some kind of mega plan on how to make things work first.

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

*What I'd like to work on with other Wters if anyone's interested:*

So I started a re-write of witty-plus, called wp2:
https://github.com/matiu2/wp2

It's pretty empty right now.

My aim is:

1. A library that is less flexible than Wt, it'll only do things one way.
For example, layout will be all templates, or layout will be all WtLayout
controls. (Maybe it'll support drop in layout libraries).
2. The advantage of it having only one way to do things is, it's easier to
learn and easier to get things done. It's at a higher level than Wt.
3. For example there's that widget template that gives you a label and a
FormWidget stuck together. When I'm making an editing interface, I always
end up making one of these.
4. It'll likely have some client side validators, similar to what WittyPlus
has. For example the 'your second password has to match your first password
when you try to change it validator':
https://github.com/matiu2/witty-plus/blob/master/wittyPlus/base/MatchValidator.hpp
it
does a lot less talking to the server than most Witty vaildators.
5. There will be a command line app, we'll call it wp2-manage. It will
generate you a tonne of template code, eg.

     wp2-manage new myProject --with-db --with-password-auth
--with-google-auth

will generate you a nice source tree with CMakeFiles and whatnot. Maybe in
the future, it'd be smart enough to edit source trees.

I know it's a little less of a grandious plan than Jeffery's but, that's
what I'd like to see.

Perhaps other Wters could add their grand designs in, and perhaps we could
agree on one big plan, and perhaps we could work together, along with the
original Wt authors to add this layer on top of Wt. It seems to be the way
that Wt has been going this last year or so anyway :)

I'd also like to see some more use of C++11 :)

Thanks for reading,
Matthew Sherborne

On Wed, Jun 27, 2012 at 11:41 AM, Jeffrey Scott Flesher Gmail <
[email protected]> wrote:

> **
>
> I'm starting an Open Source CMS Project called Flesh; I've decided that Wt
> should work well for this project; and now its time to start work; and I
> thought I'd check to see if there is already a CMS project out there, I did
> not find any doing a search; so I thought I would ask.
>
> If you have any ideas on how to start a project like this, let me know; I
> know that is a vague question; but I'm starting from scratch if I can not
> find a project out there, and even if I do, I doubt it will do what I'm
> trying to do, so I'm really just looking for ideas.
>
> My idea right now is to make it database driven; the main function will
> check the command line, sterilize it, parse it out, pull a database query
> for the page, check cache, clean it if data has changed, create the page if
> needed, then sever the page.
>
> It will have a db record for each item or widget I need to use for a page,
> that contains all the information I need for that widget; then use a case
> statement to execute the statement; a little over simplified, but basically
> that's it, then add the back end, which is a drag and drop widget editor,
> based on a Property sheet for each widget in advanced mode, and also a
> WYSIWYG for basic editing, which I'm leaning toward a Qt app for that, one
> for the desktop and one for devices, but have a web back end as well, but
> make it an option.
>
> I will have a theme designer to go with it; its Open Source, but I doubt
> it will get any interest till its out of beta, but the market is to replace
> all CMS's out there, so I will make the interface easy to use, with
> advanced controls and scripting capabilities, so security is a must to have
> that functionality; but I want it to replace cPanel, so it will also
> control the web server, if you are the Server Admin, with more control then
> cPanel currently has; this way all you need is a VPS account, no Panel and
> can add multiple Domain Portals, have email, ftp and other features, each
> with there own database and folder space, so they are separate; but allow
> an administrator to maintain multiple web portals using one application,
> and still giving each web master total control over their own portal.
>
> Its based on CDN, and my idea is to just push changes with the Qt app,
> such that it replicates the data to all CDN's; this way I can firewall out
> all ports, other than 80 and 443, and then only allow incoming ports based
> on the IP addresses for all the CDN's, with a master IP controller; so you
> can update the CDN IP addresses and monitor them for security, so you can
> take them off line if they become compromised, and rebuild them with new
> credentials; but at the same time, I want to use P2P update capability and
> content delivery service to cut back on bandwidth usage, so I'm talking
> about some serious code here; but I make video's and its one of the reasons
> I want to write this; so I can have a CMS that is designed for fast content
> delivery for on demand video, so it will need to interface with a Kaltura
> Server also, plus I want it to run my Email server as well, so that this
> application has enough power to run any Corporation from, and secure enough
> for the Government to use, but really aimed at the normal end user who just
> wants a web site, which opens up the Portal Market potential this project
> will have.
>
> Its geared for E-Commerce, and will be PCI Complaint; which is the main
> reason I'm doing this project.
>
> I'm not soliciting for help with this project; just asking about ideas;
> links to code that might do a few things I'm looking at doing, and to find
> out if any one has already done this; since I couldn't find a project like
> this, and don't know where to go or who to ask; I figured this was a good
> place to start, so please let me know.
>
> I've written a few CMS's in different languages over the years, the first
> one back in 1999, never happy with any of them; so I thought I'd do this
> one right, and I'm an old C programmer, but mainly did Assembly and Machine
> Language,
> back in the 80's C was a treat, and C++ was a Dream; after being retired
> from the Air Force I became a Computer Programmer for the EPA and then the
> BLM, till I retired due to worsening health issues from the War, and I like
> Qt and find Wt doesn't look much different in its style; so I shouldn't
> have much difficulty there; but I'll find out soon enough; this is just my
> introduction to this Community and first question.
>
> Thanks.
>
> Jeffrey Scott Flesher
> Retired Disabled Gulf War Vet
> Air Force Computer Programmer - Electronic Engineer and Helicopter Crew
> Chief, Special Ops and Air Rescue.
> http://LightWizzard.com
> http://VetsHelpCenter.com
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
------------------------------------------------------------------------------
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