Re: [bme-develop] Dirctory structure and filenames

[Sir M. <obe...@ho...>]

Aloha!

It looks like I can't send attachment to our mail list, I'll send you the 
icon file seperately in a minute....

>Is important to standardize the filenames, classes etc. So far there
>where two types different names for classes, I had MSNClassName from
>the first versions of the code, then I incorporated the
>BMsnServerHandlers. I like the java standard for class names where
>each
>word of the name is capitalized, MsnClassName, and that would be the
>name of the file, just adding the extension .h/.cpp
>Also, I was thinking to take MsnOtherWindows.h/.cpp and put every
>class
>in it's own file.

I agree with the FirstLettersCapitalised naming scheme.

Me too. Since I mainly a java programmer I'm already accustomed to 
this....one question though, do we also use the java convention to start 
method name with a non-capitalised character? that is also important I 
think, to agree on that...so Be or Java way...I agree on separating every 
class into it's own header and source file...

	 	> Another thing is the directory structure, so far there is only a src/
>
>directory and all the code is in there. We could organize it a little
>better, as Simon suggested. I have attached my suggestion, take a
>look.

This is much better.

maybe also separate the headers and the source into different 
subdirectories...

	 	Just a few changes:
- Project files (.proj and .rsrc) should be "Bme.proj" (we also need to
decide between "bme" "Bme" "BMe" or "BME"!)
haha don't mind what it should be called...though I have a little preference 
for Bme and bme....

	 	- Remove spaces in folder names ("Msn Protocol" to either "MsnProtocol"
or just "Protocol" (I don't see us supporting multi protocols, although
I could be wrong)).
I believe cvs also can't handle dirs with spaces, but I can be wrong....we 
also need a directory for the icons...I'll attach the zip to this email....

	 	- I don't know if we want seperate folders for old and new UI. I want
to change quite a lot, add some windows and remove some others, but I
could just edit the existing files I suppose. However that means any
work-in-progress stuff won't have a full CVS history. For example, the
conv window will use a new BListView sytle - this will probably take a
while until it works as well as a BTextView approach, so either we will
be left with a CVS version that doesn't work very well for a while, or
I will have to develop it until it's finished and then commit it all at
once. Neither of these are very good solutions IMHO, so I'd prefer two
directories - a "New_UI" one and a "BeMSN_UI" one. That way we can work
together on the new UI in CVS, without having to sacrafice the current
UI, which works fine already.

Problem with this approach is that you're working with two different UI 
codes....things will get broken anyway in the near future...and in this way 
we can get confused on what  code we should work...If  we go for this 
approach I think we have to make some good descisions on how to carry out 
the further programming,

regards,

Tim

_________________________________________________________________
MSN Search, for accurate results! http://search.msn.nl