eCommerce Tycoon

**ForrestCroce** · 03-05-2008, 01:17 AM

Quote:

Originally Posted by nanimo

Its really a dead-end: selling low your coding effort wont be worth, selling high nobody will pay for it, giving it free its like shooting ducks in the dark (you never know if you hit any and if you do you wont see them) lol

If you give all of your code away, or sell it at rock bottom prices, you'll have a hard time getting people to pay what you probably want to charge down the line. You can raise your prices, but it can be turbulent. That's not to say you shouldn't put good stuff up for free, even open source, and use it to bring people in to the better stuff they can pay for; it sounds like you want to do that with things you spent less time on.

Quote:

Originally Posted by nanimo

BTW, ever happened to you getting lost while naming variables and functions? Its so many i'am handling that im starting to give nonsense names to the things.

Are they scoped globally?

**nanimo** · 10:13 AM

No, not global variables, the local variables inside the functions, for example:

PHP Code:


			
$bla = '';
if(condition) $bla = value;
return(template($bla));

**willcode4beer** · 03-05-2008, 07:16 PM

Quote:

Originally Posted by nanimo

Lol, i never said i would code a poll script, but if we make a comparative, if according you a poll script worths $10-20, the whole package im developing (which includes polls) may be worth $100-200..of course nobody who loves cheap hot-dogs would ever pay that

BTW, ever happened to you getting lost while naming variables and functions? Its so many i'am handling that im starting to give nonsense names to the things.

Name functions are what they do, name variables after what they are.
If you start down the path of nonsense names, you'll find maintenance and bug fixes will be more costly and time consuming.

I'd recommend you give "Code Complete" by Steve McConnell a read.

**nanimo** · 03-05-2008, 08:27 PM

Bleh...im not that lost.

**chrishirst** · 03-06-2008, 04:35 PM

I use a letter indicating scope g_ = global, m_ = module, l_ = local to function, p_ = passed as a parameter.

Then a type indicator _lng = long, _i = int, _s = string, _o = object

followed by "a" if it is an array , then the meaningful name

SO!

g_saURIParts would be a Global String Array that contained the parts of a Internet address.

As Paul says, Do NOT go down the nonsense name route. It WILL cause you problems

**Capt Quirk** · 03-06-2008, 09:23 PM

Quote:

Originally Posted by nanimo

Bleh...im not that lost.

I was lost after "Script"...

**nanimo** · 09:01 AM

I decided..i will be selling my product for 20 euros
Btw, how do i set a license to sell a php script? Just write down my own stuff or can i use a public one?

**Learning Newbie** · 04:04 PM

Quote:

Originally Posted by chrishirst

I use a letter indicating scope g_ = global, m_ = module, l_ = local to function, p_ = passed as a parameter.

Then a type indicator _lng = long, _i = int, _s = string, _o = object

followed by "a" if it is an array , then the meaningful name

Ahhh, so you have thousands of variables named things like

g_nzstrBeginningCustNumberS, m_nSize, hwndParent and lpszFile

In the 1890s when code was written in LNEDIT it was extremely helpful to look at a variable name and know it was a global, null terminated string pointer, but IDEs are really good today. I can just hover the mouse over the name of a variable and get it's type, scope, and XML documentation, if any exists. Which means we can use more meaningful, more readable variable names. It's time for Hungarian Notation to die.

Quote:

But then something kind of wrong happened.
The dark side took over Hungarian Notation.
Apps Hungarian had very useful, meaningful prefixes like “ix” to mean an index into an array, “c” to mean a count, “d” to mean the difference between two numbers (for example “dx” meant “width”), and so forth.
Systems Hungarian had far less useful prefixes like “l” for long and “ul” for “unsigned long” and “dw” for double word, which is, actually, uh, an unsigned long. In Systems Hungarian, the only thing that the prefix told you was the actual data type of the variable.
This was a subtle but complete misunderstanding of Simonyi’s intention and practice, and it just goes to show you that if you write convoluted, dense academic prose nobody will understand it and your ideas will be misinterpreted and then the misinterpreted ideas will be ridiculed even when they weren’t your ideas. So in Systems Hungarian you got a lot of dwFoo meaning “double word foo,” and doggone it, the fact that a variable is a double word tells you darn near nothing useful at all. So it’s no wonder people rebelled against Systems Hungarian.

**chrishirst** · 03-07-2008, 05:15 PM

Quote:

Ahhh, so you have thousands of variables named things like

I Used to

The more recent stuff is more like SQL.ConnString = "Whatever" or Config.IsActive = true, because I tend to code many things into class modules (even in ASP VbScript )

**ECSuite_Russell** · 03-07-2008, 05:30 PM

Quote:

Originally Posted by Learning Newbie

Ahhh, so you have thousands of variables named things like

g_nzstrBeginningCustNumberS, m_nSize, hwndParent and lpszFile

In the 1890s when code was written in LNEDIT it was extremely helpful to look at a variable name and know it was a global, null terminated string pointer, but IDEs are really good today. I can just hover the mouse over the name of a variable and get it's type, scope, and XML documentation, if any exists. Which means we can use more meaningful, more readable variable names. It's time for Hungarian Notation to die.

Wait... what???

1890's.. you must be like the Dilbert character with 200 years of unix experience

**vangogh** · 03-07-2008, 07:51 PM

John you don't look your age at all. How do you stay so young looking. I mean you must be..what...like 140?

You need to start selling that fountain of youth stuff.

**Learning Newbie** · 03-10-2008, 05:39 PM

Quote:

Originally Posted by chrishirst

I Used to

The more recent stuff is more like SQL.ConnString = "Whatever" or Config.IsActive = true, because I tend to code many things into class modules (even in ASP VbScript )

You know, I had no idea that was possible (class modules in VBScript) until abut a year ago when I had to do some work in Excel? That's one of the reasons I was so excited about ASP.NET and just C#.NET

**chrishirst** · 03-11-2008, 07:16 PM

Quote:

That's one of the reasons I was so excited about ASP.NET and just C#.NET

And it's one of the reasons I can't get excited (or even enthusiastic) about .net

**fitnfree** · 03-14-2008, 08:45 AM

From a "script buyers" viewpoint...

I'm happy to pay for good scripts because I stink at programming skills but sometimes I get ripped and that I don't care for. So a couple tips from someone happy to pay for a good, quality script:

Offer GOOD customer service and answer any inquries regarding your product quickly. Don't just offer a "forum" or an "FAQ" for people to find answers. Have an e-mail address and/or telephone number people can call with questions. Forums are great for regular users, but not for people just considering buying who don't want to spend an hour or more surfing through a forum, or don't want to join just to ask one simple question.
Always have a demo online -- nothing makes me run faster than a big sale page for a script with no demo to see it in action.
Have set up tutorials online and offer set-up help. Depending on how complex your program is, you could even charge a one-time fee for set up help.

Hope that helps a little. I sincerely believe hard work on a script is well worth paying for if it's a good one.