Topic: New development hub.

[Construed]

Indeed, Were almost ready to start adding QFG2

[void]

And for reinventing the wheel, I made this 9 years ago.

And this is exactly, what it looks like, from a technical point of view. I'm sorry, but as a professional web programmer for over 7 years I clearly do not see anything that new or special here. To make it even worse, your technical approach seems to be way behind todays standards, no offense.

For example, you're using HTML 4.01, a standard which has been used around ten years ago. Then you implement a frameset, also something that is definitely out of date. The way you're utilizing JS doesn't look like you're making great use of PHP, hence I don't expect any database binding, which should be absolutely mandatory and ready to go even before you start coding a single line on the front-end.

From time to time I'm working on a web based application framework for my company. I started in 2007 and literally for years I did not even think of having a GUI. Most of the time went into the kernel. I'm sorry for contradicting here, but as you're claiming this as your own idea (which is hard to argument even if you did it 9 years ago because other software already existed then) i think it has to give proof of its quality. And as far as I can see it is not the case, at least not for me.

[Construed]

Like I said, I made it 9 years ago, the html 4.0 itself proves that atleast and its nothing to throw in some php/mysql at a later time, but i'm not working on it anymore.

The order of which to implement php is more of a personal preference.
I know every single line of code in every file that pertains to that website and the given technologies so really its easier for me to implement.

[void]

Well, I don't want to spoil this for you, don't get me wrong here. I really admit the work and effort you put in your project, but I just wanted to point out that in a common way you would most likely do the technical concept and strategies behind in prior, allowing you to get plain view on how the interface should look like. I always obey the form-follows-function rule here, since it is clearly more profitable to me (as well as every professional I've been speaking yet).

Ensuing from this point of view, I'd be interested in how you decided to manage the asynchronous data transmissions that are required once you're getting into iframes and common GUI stuff (such as window positioning, dimension keeping, user preferences e.g). Right now you're only using JavaScript and referred to your statement about the triviality of implementing server side scripting and databases I am wondering how exactly you planned to integrate this after the interface has been done. Will you allow user login and furthermore preferences storage? This would include a snapshot of any windows and things going on in the GUI, and as we are talking about a passive and non-persistent connection, this could get a real pain in the ass if not well designed.

[Construed]

Yea, I was just going to piece together various open source php scripts and edit all the database references to match my own.

But like every project I do the world hates it.
Although I expect things to be as such, perhaps I'm not meant to produce crowd pleasing entertainment products but instead AI killing machines and other warfare devices.

That's about the only other thing I have a desire to pursue.

[Darius Poyer]

You're all kinds of crazy Grim.

[Construed]

Yep, Bi-polar, explosive disorder, ADHD, the list goes on and on...
But then again most geniuses were also insane

[WHAM]

Yep, Bi-polar, explosive disorder, ADHD, the list goes on and on...
But then again most geniuses were also insane

And most insane people were not geniuses, keep that in mind as well.

[Shane 'ProgZmax' Stevens]

I pruned some of the drawn-out off topic banter.

Please remain on topic, guys.  You can discuss mental illness in General Discussion if it's that important.