RegDevelop: Thousands of Geeks Versus Thousands of C# Programmers

Creating a Bridge Between Programmers and Users



RegDevelop is the Next Generation of creating application.

Thousands of Geeks/Tweakers && Thousands of Programmers

Regdevelop will start the idea of creating application (Tweaking and Customization app like WinBubble) that can be edited, shared and updated by a Normal User.

All the Programs created using Regdevelop can be updated by any users.



---------------------------NOTE------------------------------
It will only focused on Creating Apps in Customization Programs like WinBubble. UI and Registry settings can be updated by the normal users...

The more advance one... can be updated by the C# Programmers.
Its a good way to start something new.
---------------------------------------------------------------
Hello guys, Its been a while since I updated my programs.
I've been busy and it's very difficult to SET your mind and Environment into
something.

Thanks a lot to all the people who help me and sent emails

Always, encourage me when your down and also when you don't know what to do Next.

The truth is, Its an accident how I've learn how to accomplish
my idea before: IDE for Geeks? IDE for ALL!

Just came to me, 3-weeks ago while studying C#...

Please give some comments and suggestions.
Any idea will be noted.

Thanks in Advance!!! I hope this will be Great.

Enjoy!

By the way, Thank you Gary...
This is it... Programming and Tweaking for All!
-------------------------------------------------------

License plans: (Not Yet Final)
1. The program will become Open Source GPL v3 once
once it has a name. maybe after 1-3 years.

why? I believed this will become a security for original ideas in Open Source.

2. For the meantime, I will gather funds through
donations and create a descent website.
But I know, Its difficult. But I have no choice.

3. Everbody can update/help in developing the program but you can't release any that directly compete with the program. (For Now only of course)

4. Once it became an open source, the license will follow.

What do you think???

 

Ok, Lawrence you asked so I will be perfectly honest with you. The idea of enabling non programmers to create registry tweaks scares me to death. We have enough trouble now with folks who think they are experts giving bad advice to others. This sort of application will make that easier. What if someone who is a total novice creates a tweak that works great on their own machine but renders someone else's machine unbootable or causes it to corrupt some data?

If you were enabling non-programmers to do anything else EXCEPT tweaking the operating system, I would applaud your effort. But unleashing folks who don't know what they are really doing with the internals of the operating system is, to me, unwise.

Now having said that, there are two things you could (and SHOULD) do to mitigate my fears.

1. Require that every tweak be fully documented. Each tweak should show EXACTLY what the registry entry looks like BEFORE and AFTER the tweak.

2. Require that every tweak creates a registry export file of the BEFORE state of any entry that is about to be changed. That should be something BUILT IN to your part of the application, so that the novices have no choice but to do this. This way if someone creates a tweak that really screws up some users system, that user will have a way to get their machines back up.

You asked!

Gary

 

I'm with Gary on this one. I'm calling the authorities.

 

I would add to Gary's item (2) that any acceptable form of such an application must also have the means to repair the registry using the exported file, even if the damage is so bad that the OS won't boot to a useable point.

 

yeahhh... but If the user creates a program like that He/She will be responsible for that. You can't create the program without writing
an Authors Name.

Anyway, The registry Settings can be seen directly, so No Fear.

Of course, It has a Reg Backup, the user will be guided by reading the documentations in the website and It has a restore point creator.

License plans:
1. The program will become Open Source v3 once
once it has a name. maybe after 1-3 years.

why? I believed this will become a security for original ideas in Open Source.

2. For the meantime, I will gather funds through
donations and create a descent website.
But I know, Its difficult. But I have no choice.

3. Everbody can update/help in developing the program but you can't release any that directly compete with the program. (For Now only of course)

4. Once it became an open source, the license will follow.

What do you think???

 

Lawrence,

What I think is you aren't listening to what we are saying. Let me make it PERFECTLY CLEAR.

It is a STUPID, CARELESS, DANGEROUS thing to make it so easy for folks who have no idea how to write a program to be able to modify the internal workings of an operating system. Modifying the way an operating system works requires careful testing across a wide variety of machines and scenarios before the modification is published. Unfortunately this is not the way many "tweaks" are tested. And your idea for a program is going to make it even easier for this sort of untested junk to reach a wider audience.

I and others have tried to make it clear to you how dangerous this can be, and some of the things that you COULD do to make it safer. Yet, you seem to ignore them with RIDICULOUS statements like: "the user creates a program like that He/She will be responsible for that", "It has a Reg Backup" and "It has a restore point creator".

Lets take these one at a time. First YOU are responsible for creating this tool. YOU are responsible for putting this into the hands of inexperienced users, so YOU are just as culpable as the He/She. And your solution to the issue of rolling back the changes made is to backup the entire registry or create a system restore point and to require the end user to do this at their own discretion. Sorry that is NOT a solution. First, because it requires a rollback of the ENTIRE registry or the system restore point. And second because it requires the end user to take apprpriate precautions manually. So if I create a registry backup, use one of these applications and then don't find out until a few days latter that something is wrong, my only solution is to restore my entire registry? Sorry Lawrence, if you REALLY think that is an optimal solution, you so wrong. It makes me worry much more that you really don't know what you are doing. The same is true of the system restore point idea. Do you really mean I have to roll back my entire system to the point in time where I ran the application just to undo something it did?

You and I have had this same conversation several times for almost a year, with WinBubbles. I said then that as a novice programmer you had no business writing an application that tweaked the operating system as your first foray into programming. I admonished you, that if you DID want to embark on such an endeavor, that you should do it in the most transparent way possible with every tweak fully documented in the application itself showing the before and after state of each and every change. You have done nothing but pay lip service to that idea. Saying repeatedly that you would do it, then making lame excuses when I called you out for NOT doing it.

And now you want to make it easy for other non programmers to do the same thing? How long do you think it will be before some script kiddie decides to use your new program to create a deadly payload just for the shear fun of it? Or worse to deliver some back door to be used in some nefarious identity theft scheme.

I spelled out a way that you COULD make this application totally transparent, by having the core application itself (not the part that He/She creates) display the before and after state of each change and a registry backup of just the portions of the registry that are about to be changed.

But once again you have chosen to ignore the advice. Good luck. Don't be surprised when I continue to voice my opposition to this.

Gary

 

Nice one... Thank you for the detailed explanation.

I think I have a solution for that...

I can make it like this: If somebody created an application.

At first, It will be noted that the user who downloaded the program MUST
verify that the created program is SAFE to USE.

For example, If you created the program. You need to send the created program to me for verification. And After that, If its good and SAFE.

The program will have a Permanent Homepage in my website.
Every settings will be fully documented and backup by Microsoft
Articles. If not, by the authors themselves.

In that way, the people will have confidence on the System.

METHOD 2: There is an Intelligent System I'm creating for few days now... but I don't know if it will be available when after launch. To break up the silence, It is a system that maps the safe Registry Settings and the dangerous ones. So, It will reduce dramatically the problems in Tweaking.

But it will take time and Testing... For the meantime, The Documentations of the Intelligent System will be available only to the people who donated more in the program.

Hopefully this will reduce the potential problems and increase confidence about Tweaking.

Don't worry, Documentations will spam the web. No settings will be hidden.

Beginners: They can take advantage because it can accelerate the learning curve. Appreciate Programming...

In return, Users MUST verify the program in my website...

What do you think?

 

You really just killed the idea of opensource and actually I don't trust your program.

 

Don't worry it will be an opensource once the app is in the mature stage.
probably GPL/LGPL or maybe MS Type Open source.

For now, I don't have enough money to put a website and maintain the app so, for now... the above license will be used.

mmm...Its not what you think.
It will only focused on Creating Apps in Customization Programs like WinBubble. UI and Registry settings can be updated by the normal users...

The more advance one... can be updated by the C# Programmers.
Its a good way to start something.

 

real c# programmers don't use the registry except if they really need to.

 

This seriously fails.

I'm with Silas, i'm calling the authorities too.

Gary has pretty much explained why this is EPIC FAIL, and the fact that you intend to open source it is meaningless.

Ordinary users who think they are better than they are shouldn't be able to redistribute badly conceived registry tweaks that look like they were constructed by a knowledgeable user.

I feel a disturbance in the force....

 

so, what can you suggest? Close Source?

It means... If you have a bad program (Registry tricks). Anybody who have a knowledge on that portion
can easily updated and maybe send the author an email for update.

Anyway, For the meantime, I will strictly advice the users who downloaded the created program to check if that program has been verified or not. I will create a list / database for the verified programs.

Im planning to create a tweaker created by the tool, example: NBR Tweaker and promote it.
All the stuff that can be found in Here only. So, If I will create something to others... It will be another unique program because it will corresponds to the articles in the website.

-----------------------------------------------
I think I will try to study Ubuntu if I can make a great app using Mono.
C# is promising... and great.

 

I read this only quickly, but Lawrence, you need to accept that the problem here is the whole idea. People that don't know what they are doing shouldn't play in the registry, thats why its not readily visible to people. Also, just because someone writes a program via this and ruins their computer, doesn't mean they will accept it as your fault, it will come back to you, however innocent you think you are. Bad idea.

 

How about linking/creating Sets of Documents that can be use?
I mean tons of Registry tips and tricks...

Teaching them is the answer... I don't want to monopolize the articles.
I want to MERGE ALL OF THEM. I will link it to the set of websites available.

or maybe just directly link it to microsoft articles.

or give the beginners something to start and leave it to Google.

 

Lawrence which part of BEGINNERS HAVE NO PLACE MUCKING ABOUT IN THE REGISTRY don't you understand? It is not about teaching THEM it is about teaching YOU, it is a STUPID idea to be encouraging beginners to mess with the registry. That is NOT the place where you should begin the learning process. And the sooner you stop trying to encourage beginners that they should play with the registry, the better off we will all be.

I tried to convince YOU of that when you first started on WinBubbles and admitted to all of us that it was your first attempt at programming. I tried to tell you then that it was foolish for you to embark on that, since with one little screwup, you could render a lot of folks' machines unusable. But despite my and other folks efforts, you ignored us and went ahead and created a "tweaker" app that hid everything it did so that even if something did get screwed up it would be impossible for anyone to figure out what went awry. And now you want to enable a whole army of other folks to do the same STUPID IDIOTIC thing you did?

I am tired of trying to convince you by being nice. This has gone on for over a year now. It's no more mister nice guy. YOU NEED TO SHUT THE HELL UP AND LISTEN TO WHAT WE ARE TELLING YOU. SOME OF US HAVE BEEN IN THIS INDUSTRY FOR A VERY LONG TIME. AND WE KNOW THAT WHAT YOU ARE PROPOSING IS WRONGHEADED, DANGEROUS AND POSSIBLY DISASTEROUS. Clear enough for you yet?

Gary

 

ok, I will focus on intermediate and advance users only. Also, to Websites Authors only.

I'm not yet sure.
I may change it to close source.
and go for pay for download or something.

I don't know, that way, the balance will follow...

Thanks everyone. I need to decide and think more...

 

Open source/closed source has nothing to do with the problem. The problem is the idea.