Spudinski

If you do need to open-ness of a VPS, but don't know *nix, I'd suggest you select a managed package. It'll set you back almost half of what you pay per annual, but it is worth it for you.

PHP is a programming language, these days. One can make system utilities with PHP, one can create graphical front-ends with PHP(& GTK) and one can translate PHP into a compiled form(Hippo?). The correct term is developer, for any web-based language. Scripters: An informal term used when creating(hacking together) a small program/tool, such as a common system tool. Developers: People using libraries to develop something. Programmers: People who program those libraries. (en)Coders: People who build the tools needed to do the above. Example: I developed an application to represent a GUI for administration. I programmed an application to perform common tasks on the system. I created an encoder to to translate system signals into input for my application. I scripted a interface handler to identify my program as a daemon on the system. That's just my two cents.

There are instances where one would want to unhook a "right-click" event on web pages. They may not be for the reasons you would use it for, but I'll give an example where it would be beneficial to stop right clicking: You are running an emulated(no hardware requiring) application that attempts to have the UI(User Interface) match very closely to the real operating system. This could be because of any reason, but mainly I would think if you ran an SaaS(Software as a Service) application with a custom client(web browser). Now, right-clicking normally brings up an context menu with commonly used functions to a user's disposal. These could potentially be appended to or replaced entirely, so it does something like create a CRUD(Create Read Update Delete) menu specific to the web site. Other uses would be for uses in BB(browser based) Games, such as an FPS where right-click would be to dodge an attack or reload a weapon. Although context menu's aren't supported(except Opera) at this time, there is some discussion going on about it. Please see the following link for the proposed ideas: https://www.w3.org/Bugs/Public/show_bug.cgi?id=13608

Working with redundant scripts is a pain, and from personal experience it suppresses the ability of future generations of the application. A application I'm currently assigned to is much like this, even though it's more SaaSy. We can not upgrade to PHP 5.4 because it still uses features deprecated in the new release, and because of a few other reasons. Neither can we develop a new version of the application, because so many other features requires certain parts of the code base. I even had a bug today where one javascript file w so old that it created a bug because of deprecated features within the JS engine of most browsers. But most of all, we really do not have the time to develop a new system purely because of the maintenance(bug fixes, additions, client-specific, etc) of the current application. If you have the chance to develop a new generation/version of the engine, I would say do it. I wouldn't say you drop previous versions right now, but they shouldn't be your highest priority.

I'd vouch for that as well. :) But welcome ezRPG people.

*facepalm* You don't specify MCCodes specifically.

I'm not going to help because you use plaintext passwords.

There are many o' scripts for this. Google it.

*standing ovation*  

Quite a good question, I'll try to answer it from what I remember. When I first began researching an appropriate database wrapper to use, it was between mysqli and PDO. I tried to compensate for both by using (then) new features in PHP 5.3.2 such as structures and namespaces, where I could programmatically switch between multiple database wrappers, even if it weren't for the same DBMS. This failed horribly, and I ended up creating such a complex implementation of a database class that it either became too limited or unstable to use. I opted for a single database wrapper after that, and kept the idea of being able to switch between database wrappers on the fly. Initial versions of the database wrapper was an abstract class with predefined methods. All it needed was a specific driver's class to extend into it. I doubted that method as well, as abstract functions(interfaces) are not compatible with early versions of PHP5. It could be implemented again, but I'll keep it within a dev branch until PHP5.3.2 and PHP5.4 installations have increased. My last and final attempt is what is currently implemented, a single database wrapper. I have researched mysqli and PDO to decide which would fit best with the application. While mysqli held it's advantages over PDO in certain cases, I found that PDO was faster to implement and build onto. Things like transactions(currently all queries are sent as one) can easily be used, and while I know mysqli(and even mysql) can do the same I prefer my objects. But, if I had to pick one reason why I settled on PDO, it's because it has much more OO functionality that can actually be maintained. Although I wouldn't say that classes currently are interchangeable, but if needed another driver can be "popped" in. I hope that answer's your question.

There isn't something such as too many queries. A single query could be made up of five or ten sub-queries. As long as you are using your DBMS wisely and optimize your queries as best possible, you can have millions within a single application. Another thing, you do get to a point within your application where queries begins to be resource intensive. That is the point where you rethink your current database design, and implement either a query cache, use DBMS replication servers or implement a load balancing scheme. I'd say if your query executes in less than a second on average, you're doing quite all right. (Note: this depends on many factors, but for un-indexed tables an average of 2.5s on complex queries is completely normal)

I already edited my post. Try it.

The get to the PROBLEM. It's a parse error, you used a semi-colon which isn't correct. [color=#333333]$connect = mysql_connect("xxxxxx","xxxxxxx","xxxxxxx"); or die ("Couldnt Connect To Database"); Should be: [/color][color=#333333]$connect = mysql_connect("xxxxxx","xxxxxxx","xxxxxxx") or die ("Couldnt Connect To Database"); [/color]

That's a "long" query? Do a EXPLAIN. I.e. EXPLAIN your sql

To Alain... Within my country, we have something called the "Consumer Act" of 2008. I know the UK has something similar, I'll find it when I get home later tonight. It states that you can't attempt to sell somebody bundled items as a product, for which you can not transparently show the benefits(locally) of it. In this situation, Alain, you are bundling templates, modules and the right to use it. If I do not require the template or modules, you can't force me to buy the more expensive product just so I have a right to use the product.   Oh, @Everyone else. Get off your wagons. SirChick: I'd suggest you read what this is about. Further more, this isn't 1940 where the creator has the last say. If you want more rights, you need to create an righted entity, a common human falls short with regards to setting their own terms to sell something.

I'd suggest you get a lawyer to write up an agreement for you. What you are saying is illegal to do.

Skeleton is a Modular Application Framework, designed and built by none other than me. My goal was to reach a point where I could have a scalable and very lightweight framework where I could just pop in features and templates as I needed. I've used this application on tens of websites now, and with great success. I've decided to make my little project completely open source, and have hosted it on github. You can find it here: https://github.com/nands/skeleton There are currently two branches, being "master" and "development". The master branch is where official versions are committed to, and dev(elopment) is where any potentially unstable features and versions are. I hope you all can contribute to this project, and share what you know. Right now, I'm working on creating PHPDoc for every single thing the framework does. Afterwards, I will be on a fault finding mission, and will improve it to work with a custom set TPL engine. Additionally, I've set a goal for version 1.0 for this, which hopefully will be reached sometime(July). Looking forward to seeing some people. S.

I wouldn't, it is just to prove a point. People already have 90% of what they need, they only needs to fill in the gaps. It wasn't a good thing to release the alpha version to people who weren't over viewed. Developers will spawn to it.

When I just saw this topic's title I though... "Oh goody... here comes another flame war". Good one.   You make it sound like you are the only one who actually invests time and capital into a project, which is really not true. Most developers who do something for the community, ends up making it open source, or at least for non-commercial purposes. After which, they "ask" you nicely IF you would be kind enough to donate to the cause, so they're financial losses are covered. There are many examples of this out there, and some of them invested a lot more capital and time into their projects.   I can't remember someone saying this, but if I could just in with the imaginary person there... Sure, many developers who know how much effort goes into something like this would go and say, "how the hell did he manage to do this in such a short amount of time?". You might have ninja developing skills I don't know about, but when you raise the bar on your job and family(?), it seems quite... (what's the word I'm looking for) mysterious.   That's a statement, not a question to answer. It's like I don't like Oracle, but I don't see them springing up and defending themselves though.   Or, we could just alter the alpha release. It is legal...   And that would be your opinion for a change. Most of us have long either created our own private product(which yes, we compare every other developer's with), or opted for another. I personally created my own, and it landed me a very decent job opportunity. But not everyone is the type of person that has to post every two seconds and bloat or disarm people about their own creation.

Nicely said rulerofzu. @Danny, I'll donate half to your cause. :P

Ok, was a bit early for me then. I do not think I am negative, I'm realistic. I also don't believe my overall posting attitude is negative, I didn't even try to be with my last post on this thread. If you could point out what about my posts are negative, I'd gracefully keep it in mind when posting. I might not know everything about web games, but I know how to develop them and what makes them tick psychologically. That gives me the knowledge to make accurate assumptions, maybe they are not correct some times, indeed, but that is seldom. -------------------------------------- I was asking the original question as reference to other people. As you know, MCCodes is a company much more than community, mainly because they are focused on the profit of what they do. That may differ with you, and your new release of a GE, but it does not exempt you to be seen as an entity with a product for sale. With regards to profit, I would think that the amount is not to be spoken about, as it should remain confidential between you and whomever work with you on the project. As for your salary, I really could care how much someone other than me makes. The stability of your code I was referring to, I am actually promoting it. My views on it is that developers shouldn't expect to create a module for your engine and have it stay indefinitely usable without making changes as the source continues to expand and improve. I have to be realistic here, it is going to go through major changes within the next few months, and potential developers should know that they will have to keep a close eye on it. I am fond of improvement, well, over reusing, and I would also have suggested that approach.   I would gladly continue talk you away from a public board if you think I'm breaking down the reputation of your project.

:D -tooshort-

Yes Stewie...

We could... Or, we could teach you how to do it yourself. Here's a nice slide presentation: http://css.maxdesign.com.au/ Or a long winded document... http://www.echoecho.com/cssselectors01.htm

Contradicts with...   Are you trying to build a community or company? It seems vague, to me at least. @Dave: I'm sure there will be the initial rush of MCCodes ported to New Worlds Engine modifications, if you get into that it'll have you make a quick buck or two. After that, I'm unsure. MCCodes will still have the overwhelming hold on people as they do now, seeing how easy it is to get it nowadays. Over the next few months, my best predictions are that New Worlds Engine will continue to be developed, and a lot of inconsistencies will(should) be found as it's still pretty new, and mainly because it only had(?) one developer. The life cycle of the code isn't going to be stable, and by no means would I discourage anyone from buying it because of that. But, to contradict that myself, I could be wrong as well(not likely though), in the sense that the engine will be stable. (Newbs: Code being unstable has two meanings; either it's inferior(doesn't work), or it means that code is going to be changed(regularly). My intention is the latter.) I quite like New Worlds Engine and, despite my personal concerns, I wish for it to become mainstream. I just don't think it will be within the next six months, as it still has a long way to go to please game owner's needs. To sum everything up, I'm not going to jump on the bus just yet. Maybe buy a dev license, and see how it goes.