[WysGUI] To Open Source or Not to Open Source [POLL]
Should I give this an open source version?
If I do, will you help development in the preserved section of ragezone?
Note that this is not team recruitment post, it's merely an opportunity for all to get involved and become a part of the Open Source CMS explosion. This might be a questionnaire as to whether or not I'll post in that section.
It's not really MMORPG server development so it doesn't really fit in all that well. I could post it on source forge or something or another.
The questions are listed.
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
Do you have any idea just how many open source CMS systems there are out there? And from the looks of it, yours is in no way special (or even looks pretty). So sure, go ahead, make a SourceForge page, open it up, but I really doubt you'll get anyone to pitch in - sad but true. Might as well not bother :(:
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
Honestly, there are alot of CMS out there.
If it was to become Open Source i would definatly try fiddle around with it. My skills are pretty limited though so i wouldnt really be capable of helping the production of it. It's really up to you, i'd love to see the original source code, but it wont dramatically influence me if i didn't :P
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
You should make it open source, it's a pretty good system.
:]
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
Ask yourself, why not Open Source?
I wont contribute in any way to it. As said, there are already a lot of CMS throughout the mighty large internet. Releasing open source stuff makes you cool though.
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
Quote:
Originally Posted by
FragFrog
Do you have any idea just how many open source CMS systems there are out there? And from the looks of it, yours is in no way special (or even looks pretty). So sure, go ahead, make a SourceForge page, open it up, but I really doubt you'll get anyone to pitch in - sad but true. Might as well not bother :(:
You know, I really like that response because that's sort of how I feel. I could release the source, but what's the point? I don't know how many CMS systems there are out there (I've been all over the web looking at 100's).. There's gotta be 1,000's.
It's a great start for people making thier own CMS, and since so many people demand versatile CMS systems here for different servers, I figure it could possibly evolve into a few different systems.
My thinking in the whole thing was around the simplicity of WysGui and it's ability to grow. There's no redundant module API that involves inteligent programmers to learn something more primitive then they. All of the technology is done the same way a normal site is.
Let me explain how modules are implemented in WysGui as opposed to Drupal:
Drupal modules:
WysGui Modules:
(Full Article Here ->
http://www.wysgui.com/tutorials/wysgui_modules.php )
A Module (on WysGui) could be a number of forms or functions that make WysGui work. Every form in WysGui is a module. Everything up to the very Administration panel and File Browsers. Some modules are simple, and some complex. Every WysGui Module, no matter what shape or form, consists of one-to-four things:
Settings:
Initial functions and pre-loaded data needed before anything else on the page is loaded (including mark-up)
Actions:
Functions that commit actions on a file, database, or form request. For example, the action to a login form would check to all of your information and log you in, or display an error message. Actions are loaded after settings, but before any mark-up. (This includes but is not limited to Head Data and Form/Content)
Head Data:
functions, settings, or actions that may use JavaScript or JScript to perform certain tasks. This data resides between the <head> </head> tags. Head Data may also consist of CSS styles and various other things.
Form/Content:
HTML used to create the display of the module. This may be blank for some modules, or it may be the sole purpose of others. Admins can sort this as if it were a regular piece of content in WysGui.
Obviously mine follows a more commonly used approach. Every app on the web can be summarized into these 4 parts. Note that you can include local files in any of these 4 parts. By including your ready-made form application into a WysGui module, you can do anything you can do on a site without a CMS, only WysGui makes it a bit easier to manage it, sort it, and coming soon: simply secure it.
I've looked and looked for a CMS that handles modules this way, after giving up, I made WysGui.
Don't you agree this is a better, more stable approach?
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
Quote:
Originally Posted by
s-p-n
You know, I really like that response because that's sort of how I feel. I could release the source, but what's the point? I don't know how many CMS systems there are out there (I've been all over the web looking at 100's).. There's gotta be 1,000's.
Possibly more. However, you have to realise how developers think: either they are stubborn and think their code is best in which case they won't want your code anyway, or they are lazy and want an easy system they can find dozens of plugins for. The major CMS systems out there already have loads of plugins and modules, not to mention tutorials etc available. You have a question about how to do something on wordpress, there's litterally thousands of coders around the globe that could potentially answer your question. With some random flunky CMS system there is no help, there is no guarrantee it'll even be supported, there is probably only a handfull of plugins available, etc.
I once made an open source project callled FrogBlog - a simple, versatile, fast blogging system. Had a project for it on SourceForge, several hundred downloads, yet not a single developer to pitch in and help out. In the end I figured it simply wasn't worth the effort and stopped development - mostly too because it already sufficed for my needs and nobody ever asked me for an update. Looking back at the code now I realise how horrible it was and if I had to make a new blog, I'd definately not use that source again.
Quote:
My thinking in the whole thing was around the simplicity of WysGui and it's ability to grow. There's no redundant module API that involves inteligent programmers to learn something more primitive then they. All of the technology is done the same way a normal site is.
Those "redundant" module API's prevent conflicting dependancies and mingling of form and function - an old coding paradigm and the reason why a lot of the better systems out there use an MFC layout - it is in fact more stable than the system you propose, more redundant, more easily extendable and generally better maintainable. Of course, it is not the only way and most new programmers prefer to work the way you do (I once created a MuOnline website package that used very much the same principles your CMS systems does, which was used by so many servers that it topped ~50.000 pageviews a day), but in the end interlocking dependencies tend to create such a horrible mess of code that they become unmaintainable. Not a problem for new and small projects, but once you start working on something with more people (which ultimately the goal of open source is) this severly hinders progress. Most open source developers tend to know this and focus their efforts on projects not hampered by a lack of modality.
Don't get me wrong - by all means, make your project open source, it will most likely be a good learning experience and at any rate it's something to put on your resume. I just wouldn't expect a dozen programmers to cheer in triumph submitting updates every day just yet :wink:
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
well heres a few things. make sure it uses as little as resources as possible check your sql etc. and just try to make the interface a little more attractive and i would use it
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
For any open-source project on the world, theirs only a handful programmers ACTIVELY working on the project. If you want to work on core functionality, you need to know it pretty much in-and-out. This is often only the programmers who've been in the project for long enough (the leader, hehe).
I currently am working on a C++ GUI system. There's really hundreds if not thousands of those. Why would I even bother you might ask?
- An open-source project lets you REALLY organize the code with the idea that others will be working on it as well. Forces you to use a consistent coding style and documentation. As well as readable and understandable code.
- A big project lets you really face the edges of the programming language. Forces you to use techniques you might have left behind other wise.
For me a big reason to work on the GUI library, is that it teaches me C++. Without this project I might still be far behind.
Open-source is nice, but does mean a LOT of extra work, and not so much in return, unless it gets very popular!
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
I went ahead and made it open source. I went to http://opensource.org/ and made sure WysGui was ready. Did allot of work I might add.
I got mediawiki, figured out how to use it, and made docs. That hardest part was writing, and I still got a bit more to do.. Allot more to do- but it's getting there.
All information is linked to this thread in the Showcase section.
Let me know if it works on your server.
Any ideas for new modules?
I'm thinking of some kind of skin editing module.. Hmm..
Right now you might have to read the docs to mess around with skins. The best way is through Manual edit via the Admin Panel. You can edit the stylesheet/template however you want.
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
GUI pronounced as guy? Naah, more like GU-E.
I find documentation be the hardest part, but it's the most important part! Keep up the good work. Even the best lib is worthless without good documentation.
Re: [WysGUI] To Open Source or Not to Open Source [POLL]
The First time WysGui was voted best at something was today!
Help with my effort and vote for WysGui here,
http://php.opensourcecms.com/scripts...%20/%20Portals
@Daevius, LoL! That's the first thing anyone said about the whole GUI thing, (I'm surprised). I was expecting any problem with that but the pronunciation. I'm not worried about the pronunciation, I'll have all that changed when need be. People just need to get used to the fact that 'wys' doesn't sound like 'wizz' anymore, it's 'wise'. And 'GUI' doesn't sound like 'gooie' anymore, it's 'guy'. Haha.. If only it were that easy..
