Why is it not suitable? The kids won't see anything that just pops up and says "This is written in .NET!". Anyway, that's a future idea. Any other suggestions?
Also, I know you. You do not know VB6 well - you're a half-newbie! :D
Printable View
Why is it not suitable? The kids won't see anything that just pops up and says "This is written in .NET!". Anyway, that's a future idea. Any other suggestions?
Also, I know you. You do not know VB6 well - you're a half-newbie! :D
The reason is for the use of .net-that the runtine is abiyt 20mb-and it would take gtoo long to download. Alslo I want kidos to compatible with windows 95 and up-not restr4icted to xp/200/98 only.
No, this is for a future Internet incarnation of KidOS (?), or perhaps a program that couldn't work under Win95 anyway. It will run on every other Windows OS.
Anyone got any new ideas? I'm all out :(
Omar
I know VB6 better, and am not a newbie. In fact I have never writen a line of code in .Net, that is what makes it appealing. Anyway, lets just do it in VB6, we all know it (to some degree). The main thing is to build it. We need to start designating roles. Any thoughts on what parts you guys want?
Here, I want to be a normal KidOS developer (or anything based on that which is better). I was referring to aafuss.
Huh?Quote:
Originally posted by Osnr
Here, I want to be a normal KidOS developer (or anything based on that which is better). I was referring to aafuss.
OK, I would like to be the GUI/interface designere, and a coder. We should have some programming rules. Osnr-has some rules he has made up-ask him if you the .pdf file so you can base some kidos development guidelines on.
I have been devloping in VB for years, and I have my own standards. I will write them up this weekend, and post them. Thanks anyway. Everyone brush up on Objects and Collections :DQuote:
Originally posted by aafuss
OK, I would like to be the GUI/interface designere, and a coder. We should have some programming rules. Osnr-has some rules he has made up-ask him if you the .pdf file so you can base some kidos development guidelines on.
I mean, aafuss is a beginner. I know him, and he doesn't know how to use a toolbar. :D
OK, UI designer and coder.
Ok, I don't have a ton of time to give to building this. I assume no one else really does either. With that in mind, lets take small steps. Lets start with the login stuff, since it is all fresh in our minds. Osnr and aafuss, can you guys make the form and many icons for the log me in buttons, so the users have a variety to choose from. Keep it colorful, but remember to leave room to be able to change the theme. By that I mean make a function to "Get Color Theme". There you can hardcode the colors and Icons until we come up with our theme system. Once we do, you will only have to make the changes to that function. I will start looking at the API for 2K to get the user logins for Senario 2-4. If anyone else decides they want to help, we can figure out what the next steps are needed.
Just post as you get things done, and don't stress about time. We have all the time in the world.:D
???
There's a small problem. I'm far, far away from home for a month. Still have a VB6 laptop though. Aafuss won't be able to do it either. He has a terrible idea of a UI. See here. I can do the login and aafuss might do something else.
YOur link is badQuote:
Originally posted by Osnr
???
There's a small problem. I'm far, far away from home for a month. Still have a VB6 laptop though. Aafuss won't be able to do it either. He has a terrible idea of a UI. See here. I can do the login and aafuss might do something else.
What type?
An indirect ripoff of XP's login or a glorified 2k login?
Then look here.
A kid friendly login. I think we all like the XP idea of showing all the logins with icons. Then the user selects one, and enters a password (or no password for non-readers). Make it however you think it would appeal most to small children.
Yes. By the way, the correct URL to see how ugly aafuss's code is http://sourceforge.net/projects/bsys93/ (I'm too lazy to make it a link, so if it isn't, blame me :D).
Well if you know him, where would he be most useful?
OK, I am doing the basic layout of the login screen now.- attached to post. NOocon, yet-it will let you to start off doing the login system.Quote:
Originally posted by blindlizard
Ok, I don't have a ton of time to give to building this. I assume no one else really does either. With that in mind, lets take small steps. Lets start with the login stuff, since it is all fresh in our minds. Osnr and aafuss, can you guys make the form and many icons for the log me in buttons, so the users have a variety to choose from. Keep it colorful, but remember to leave room to be able to change the theme. By that I mean make a function to "Get Color Theme". There you can hardcode the colors and Icons until we come up with our theme system. Once we do, you will only have to make the changes to that function. I will start looking at the API for 2K to get the user logins for Senario 2-4. If anyone else decides they want to help, we can figure out what the next steps are needed.
Just post as you get things done, and don't stress about time. We have all the time in the world.:D
TERRIBLE!!!
I will do an XP-like login screen. Aafuss, that UI and code is pointless... It's Text1, Command1, there's no proper way to login by typing your username.
I suggest enforcing some rules soon, then he could be useful in anything but UI design. :D
Sunofa #()$%&*!@#)($*%&!@#_)%$)!!!
I had a bunch of stuff typed in and then ....oh well, never mind.....
Take Two:
Ok, all caught up now. Happy New Year All! Now back to busuness.
blindlizard, you asked about SorceForge. Imagine Source Safe on steroids built for the web. It allows people from just about anywhere to work collaboratively on a project. It's built upon the Open Source License foundations. It would allow us to easily work on bits a pieces, keep track of to do lists, mail users/developers, etc.
Sounds like this will done using VB6, not a problem. I agree that the first thing that needs to be done is somekind of standards (for coding as well as UI design). I don't recommend using PDF for any files, ASCII Text or Word Doc should be used.... that way changes can be made as we need to.
As for me, I don't really have a whole lot of time and what time I do have, I tend to dedicate to my family. That said, here's what I am more that willing to do. Reviews, coordinations, testing, documentation, UI design (I've been told I kick arse at this - <shrug>). I also have 7month old who can also help with testing.
For any one interested, here's the info I submitted to SourceForge -- It will take another day or two to find out if it was approved or not.
Quote:
Project Name: KidOS
Description: KidOS (pronounced "Kiddos") is a Microsoft Windows application that will allow parents to create a safe environment for children. The intent is to prevent your $2,000 Quake playing machine from becoming a $2,000 paper weight when your 2 yr old randomly hits the keyboard, somehow managing to type Delete *.*. List of potential features include: Limited Internet access, limited access to programs, varying levels of access/permissions for different age groups, kid friendly (colors, look & feel), themes (Blues Clues, Pokemon, etc.).
Development will be using VB, targeting the Windows environment.
License: GNU General Public License (GPL)
Project Public Description: KidOS aims to make sure that your 2yr old doesn't accidently type DELETE *.* and wiping our your entire system. Stranger things have been known to happen.
Anyway, Ithink using plain text files and Word documents is way better than PDF files-for documentation/development guidelines. Also Iwill be able to use the SF site-as I have an account over there.
Same here. I agree... It's just that PDF files were quicker at the time I made mine.
I love the SourceForge description. I will start on the standards doc tomorrow. It will be basicly like the Microsoft suggestion naming conventions for VB.Quote:
Originally posted by techgnome
Sunofa #()$%&*!@#)($*%&!@#_)%$)!!!
I had a bunch of stuff typed in and then ....oh well, never mind.....
Take Two:
Ok, all caught up now. Happy New Year All! Now back to busuness.
blindlizard, you asked about SorceForge. Imagine Source Safe on steroids built for the web. It allows people from just about anywhere to work collaboratively on a project. It's built upon the Open Source License foundations. It would allow us to easily work on bits a pieces, keep track of to do lists, mail users/developers, etc.
Sounds like this will done using VB6, not a problem. I agree that the first thing that needs to be done is somekind of standards (for coding as well as UI design). I don't recommend using PDF for any files, ASCII Text or Word Doc should be used.... that way changes can be made as we need to.
As for me, I don't really have a whole lot of time and what time I do have, I tend to dedicate to my family. That said, here's what I am more that willing to do. Reviews, coordinations, testing, documentation, UI design (I've been told I kick arse at this - <shrug>). I also have 7month old who can also help with testing.
For any one interested, here's the info I submitted to SourceForge -- It will take another day or two to find out if it was approved or not.
Include indentation. I love indented code - it's much easier to read. Indenting with Tab key. I haven't read the MS suggested naming conventions, but if it doesn't include indenting, add it! :D
Also, I think we need a somple painting priogram for KidOS? Anyway, any good login screen forms for kidos yet? And I agree with the code should be indenred-makes it much eaiser to read/understand.
I disagree, I think it should not be indented, infact, let's just put it all on one line..... :D j/k -- couldn't resist.Quote:
Originally posted by aafuss
Also, I think we need a somple painting priogram for KidOS? Anyway, any good login screen forms for kidos yet? And I agree with the code should be indenred-makes it much eaiser to read/understand.
Good news all! The SourceForge account has been approved.
http://sourceforge.net/projects/kidos/
If you don't already have an SF account, please create one now, those who do have an account, click on the "[View Members]" link on the right hand side under Developers. Then click on the "email .... " link under my name. Let me know your SF account name and I will get you added to the developer list.
Ok, I signed up for a new account. How long before I get it activated? No email from them yet.
Ok, it finally came. Gnome my username is blindlizard. Thanks for setting this up.
OK I'm going to sign up. You'll recognize me.
My username is Osnr. Aafuss has a leftover account from his failed project.
No problem. You're set up.Quote:
Originally posted by blindlizard
Ok, it finally came. Gnome my username is blindlizard. Thanks for setting this up.
Osnr, you're added too.Quote:
Originally posted by Osnr
My username is Osnr. Aafuss has a leftover account from his failed project.
I started writing up naming / coding conventions, but I have decided just to use Microsoft's. It is much easier. Here is a link to MSDN. http://msdn.microsoft.com/library/de...nsoverview.asp
There are 3 links that define the conventions (Object Naming, Constant and Variable Naming, and Structured Coding).
I do want to amend somthing, when making an SQL query, do not define the string variable to hold it as QRY. Stick with the normal string declaration i.e. strSQL = "SELECT soemthing FROM something".
If I find other things I don't agree with , I will let everyone know.
Osnr I thought you were Aafuss's friend. You slam him A LOT!Quote:
Originally posted by Osnr
My username is Osnr. Aafuss has a leftover account from his failed project.
I'd like to go one step further and suggest that we avoid Databases all together..... distributing MDAC can be a real pill.....Quote:
Originally posted by blindlizard
I started writing up naming / coding conventions, but I have decided just to use Microsoft's. It is much easier. Here is a link to MSDN. http://msdn.microsoft.com/library/de...nsoverview.asp
There are 3 links that define the conventions (Object Naming, Constant and Variable Naming, and Structured Coding).
I do want to amend somthing, when making an SQL query, do not define the string variable to hold it as QRY. Stick with the normal string declaration i.e. strSQL = "SELECT soemthing FROM something".
If I find other things I don't agree with , I will let everyone know.
:)
I disagree with one naming convention:
Instead of "mstrString" or "glngLong" let's add in an underscore, for readability, so they become "m_strString" and "g_lngLong".
Also it does say to indent code.
Yeah let's avoid the database - plain delimited text files and/or the registry are fine.
Boy I take a day off to recover from New Year's Eve and I miss a ton.
I'm finally caught up. This looks great!
cbond, when you get a SF account set up, let me know & I'll add you to the list of developers.Quote:
Originally posted by cbond
Boy I take a day off to recover from New Year's Eve and I miss a ton.
I'm finally caught up. This looks great!
We need *more* developers. Anyone want to post in the Project Requests forum?
Good call.... done:
http://www.vbforums.com/showthread.p...hreadid=222999
I'll also post in a few other places, and on my site too.
Ok, I guess we don't need databases for this. I just want that in there incase we do :)Quote:
Originally posted by techgnome
I'd like to go one step further and suggest that we avoid Databases all together..... distributing MDAC can be a real pill.....
I thought that same thing when I read it. It doesn't really matter to me. Lets take a vote, what does everyone else think?Quote:
Originally posted by Osnr
:)
I disagree with one naming convention:
Instead of "mstrString" or "glngLong" let's add in an underscore, for readability, so they become "m_strString" and "g_lngLong".
Also it does say to indent code.
Yeah let's avoid the database - plain delimited text files and/or the registry are fine.
*** Oh, more ammendents to the Conventions. ***
In the Structured Conventions, add a line to the procedure header that is Author: with your full name, SF/VBForums username, and email.
Also, add a line Date: with the date you created the procedure.
Then if you edit someones code, add a line that says Edited By: and the same info as author, and a line that is Edited Date: with the date you made the changes. Finally a line that is Chages: explainations of what changed.
Example
VB Code:
Since this will be open source, may I suggest that you use the your SF email addr..... or not include the email at all, since it can be easily derrived from the SF user name (SF_UserName@sourceforge.net)Quote:
Originally posted by blindlizard
*** Oh, more ammendents to the Conventions. ***
In the Structured Conventions, add a line to the procedure header that is Author: with your full name, SF/VBForums username, and email.
Also, add a line Date: with the date you created the procedure.
Then if you edit someones code, add a line that says Edited By: and the same info as author, and a line that is Edited Date: with the date you made the changes. Finally a line that is Chages: explainations of what changed.
Example
VB Code:
Sounds good. Just user SF email not SF user and not regular email. But do add your VBForums user name.Quote:
Originally posted by techgnome
Since this will be open source, may I suggest that you use the your SF email addr..... or not include the email at all, since it can be easily derrived from the SF user name (SF_UserName@sourceforge.net)
VB Code:
Wow, bold comments... Looks weird.Quote:
Originally posted by techgnome
Since this will be open source, may I suggest that you use the your SF email addr..... or not include the email at all, since it can be easily derrived from the SF user name (SF_UserName@sourceforge.net)
Another thing I didn't notice in the conventions. This one is obvious, but I want it said none the less.
We are going to use Hungarian Notation when creating Variables and Procedure names. All that means is that each word in the name start with a capital letter. i.e. strDatabaseConnection. capital D and Captial C. Connstants however are all uppercase and word seperated by underscore (_) i.e strDATABASE_CONNECTION
I disagree with naming conventions for constants. What if you have to change a constant's data type? Then you have to replace all instances of the constant's name. Just use uppercase and underscores for contants.
Well if you have to chage data types then you will probably have to chagne your code any way. If I am using a constant integer to pass to an API and someone changes it to a string, my code will blow up. But if they change it to a string and change the name to strCONSTANT and my code is intCONSTANT then Option Explicit will pick it up before it compiles.Quote:
Originally posted by Osnr
I disagree with naming conventions for constants. What if you have to change a constant's data type? Then you have to replace all instances of the constant's name. Just use uppercase and underscores for contants.
I agree with Osnr on constants. They should just be capped. No prefixing.
CONNECTION_STRING
Let's consider this an unofficial vote. What about you, aafuss?
I prefer prefixing even on constants. I just think it makes the code more readable and more clear.Quote:
Originally posted by Osnr
Let's consider this an unofficial vote. What about you, aafuss?
my official unofficial vote: Won't matter to me. My personal pref is to not prefix constants (makes them easier to find). But since I don't plan to do much coding, it's really up to you guys.
I think prefixing on constants makes the code unreadable and unclear.
Well, we're tied 2-2. I'm just waiting for aafuss's vote.
How can explaining the data type make it unclear?Quote:
Originally posted by Osnr
I think prefixing on constants makes the code unreadable and unclear.
W/o the data typing it makes it painfully clear that it is a constant.Quote:
Originally posted by blindlizard
How can explaining the data type make it unclear?
Tell ya what..... everyone create a quick doc on what they would like to see as the standards. Email them to me at [email protected], I'll condence them and repost it back to everyone for comment. The sooner we can get through this, the sooner we can get going. But, at the same time, we need to make sure we set a solid foundation.
Or you can tell me where to go & how to get there (I won;t mind, I get it all day long).
I think everything but the constants declaration has been agreed on. I imagine that constants will be used mainly for APIs, so with that in mind, if you write an API function either use or don't use the prefix. I doubt anyone else will be using your constants
I agree.