Quote:

 

..I began thinking about an easier way to approach coding so that coders don't have to worry as much about providing support for their codes.

Quote:

 

There are a few individuals who release many codes, so this could become very bothersome - for both the coder, who would have to take time to answer the questions, and to the individual who doesn't get his or her questions answered.

Quote:

 

..I feel that a plug-in system would be able to solve the problems I have mentioned. I am fairly certain that this would be able to alleviate some of the issues coders face. It would also provide a wider range for coding possibilities in the future. I'm fairly certain that this could provide the room needed to create things that require more interaction with the database..

Tony

Jun 27 2009, 01:57 PM

Quote:

 

..I began thinking about an easier way to approach coding so that coders don't have to worry as much about providing support for their codes.

So who would support their codes? You can't surely expect others to do it?

Quote:

 

There are a few individuals who release many codes, so this could become very bothersome - for both the coder, who would have to take time to answer the questions, and to the individual who doesn't get his or her questions answered.

If someone creates something, they should offer support for it, regardless.

Quote:

 

..I feel that a plug-in system would be able to solve the problems I have mentioned. I am fairly certain that this would be able to alleviate some of the issues coders face. It would also provide a wider range for coding possibilities in the future. I'm fairly certain that this could provide the room needed to create things that require more interaction with the database..

I, and others, have mentioned a resource database a few times. In fact . . .



. . .

Tony

Jun 27 2009, 01:57 PM

Quote:

 

..I began thinking about an easier way to approach coding so that coders don't have to worry as much about providing support for their codes.

So who would support their codes? You can't surely expect others to do it?

Quote:

 

There are a few individuals who release many codes, so this could become very bothersome - for both the coder, who would have to take time to answer the questions, and to the individual who doesn't get his or her questions answered.

If someone creates something, they should offer support for it, regardless.

Quote:

 

..I feel that a plug-in system would be able to solve the problems I have mentioned. I am fairly certain that this would be able to alleviate some of the issues coders face. It would also provide a wider range for coding possibilities in the future. I'm fairly certain that this could provide the room needed to create things that require more interaction with the database..

I, and others, have mentioned a resource database a few times. In fact . . .



. . .

Tony

Jun 27 2009, 02:36 PM

It would be the same thing no?

Why would there be no support? Yes the system will hopefully have one-click-installs, but that won't prevent in-compatibility; or users having questions; or users not understanding something.

Users will still need to speak to the creator in some way about something.

With your idea of create, submit, forget; the RDB Team will not only have to screen everything, and make sure it works with other codes (and on its own); but answer questions about it, and chase people down to fix something; or up-date the code; or add something new people ask about.

Maybe I'm not understanding you correctly?

Nivexonix

Jun 27 2009, 05:45 PM

Tony

Jun 27 2009, 02:36 PM

It would be the same thing no?

Why would there be no support? Yes the system will hopefully have one-click-installs, but that won't prevent in-compatibility; or users having questions; or users not understanding something.

Users will still need to speak to the creator in some way about something.

With your idea of create, submit, forget; the RDB Team will not only have to screen everything, and make sure it works with other codes (and on its own); but answer questions about it, and chase people down to fix something; or up-date the code; or add something new people ask about.

Maybe I'm not understanding you correctly?

Ah, ok. Now I see what you mean. I forgot about compatibility with other codes.

Code:

 

Jory.BannerRotator.execute()
{
// My code here
}

Jory

Jun 28 2009, 11:32 AM

Oh, I do know how to solve the compatebillity issue: Upon registration, you get a username. Each code also has a "codename". Both these names are valid Javascript class/variable names. Then if I where to want to make a code called "Banner Rotator", it would be something like this:

Code:

 

Jory.BannerRotator.execute()
{
// My code here
}

That way, if somebody else wants to make a banner rotator, it would be in otherpersonsusername.BannerRotator.execute(). (FYI, execute() gets automatically called by our hypothetical system. )

Do note I'm not sure this exact syntax is valid in Javascript. But I'm sure there is something close enough.

Code:

 

var Jory = {
BannerRotator:{
execute:function(){
// do something
}}}

Code:

 

var Jory = new Object();
Jory.BannerRotator = new Object();
Jory.BannerRotator.execute = function(){
// do something
}

Code:

 

// these are Jory's codes
var Jory = {
BannerRotator: {
execute:function(){
// do some BannerRotator code here, I guess
}
},
DestroyYourBoard: {
execute:function(){
// put a code to destroy your board here
}
},
DecimateTheUniverse: {
execute:function(){
// you get the drift
}
},
BeReallyCool: {
execute:function(){
// indeed
}
}
}

Code:

 

var Jory = {
BannerRotator:function(){
// do some banner rotation here.... woooot!
},
DestroyYourBoard:function(){
// and so on
},
DecimateTheUniverse:function(){
// ... do I even need this here anymore? :O
},
BeReallyCool:function(){
// yep.
}
}

Jory

Jun 28 2009, 11:32 AM

Oh, I do know how to solve the compatebillity issue: Upon registration, you get a username. Each code also has a "codename". Both these names are valid Javascript class/variable names. Then if I where to want to make a code called "Banner Rotator", it would be something like this:

Code:

 

Jory.BannerRotator.execute()
{
// My code here
}

That way, if somebody else wants to make a banner rotator, it would be in otherpersonsusername.BannerRotator.execute(). (FYI, execute() gets automatically called by our hypothetical system. )

Do note I'm not sure this exact syntax is valid in Javascript. But I'm sure there is something close enough.