Thread: RE: [bme-develop] Fw: Issues with project files

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi,

>MYOB sent me.
>
Talk to him about it in BeShare...

>I replied to most of it. I agree with his comments about project
>files though, they could do with reorganising.
>
I also agree with most of his comments

>Theres some serious problems with Bme's BeIDE project files. One
>of
>them is speed - searching all of /boot/home/config/lib causes
>biiiig
>problems if you have all of VLC's build tools and Python
>installed. Not
>that thats a problem, just an "issue". This can be solved by
>making
>people symlink cryptib into the /boot/develop/lib/x86 folder and
>removing the /boot/home/config/lib access path
>
I think we should do this, if it speeds up compiling

>Also, most of the system libraries are included wrong. They
>should not
>be included from /boot/beos/system/lib, they should be included
>from /
>boot/develop/lib, and with the correct architechture first (x86/
>or ppc
>/).
>
This should be fixed too. Also I think we can delete some files from the 
project file, for example libmail.so! why is it necessary? Daniel, I think 
it's best you do that, since you know what files are truly necessary....

>Also, the path to the cryptlib header isn't in the file, and it
>probably should be included as <cryptlib/cryptlib.h> and not
>just as
>cryptlib.h.
>
I had a problem with that too...bme didn't compile until I copied the 
cryptlib header to the /boot/develop/headers/be folder....where should we 
place this header to prevent using entire paths in the #includes?

>Also, it might not be a good idea to have the Net*.cpp files in
>the
>project file, as they're not in CVS...
>
That's my fault, I included them to test against it...but we all have 
Simon's classes and the project files were meant for us in the first 
place....although he has a point....we should upload Simon's debugging 
classes into cvs...could you do that Simon?

>Another suggestion might be to have a BONE project file - you're
>not
>meant to like to libnetapi.so on BONE, it should be libbnetapi.
That's what I'm doing...and I have to change the project file back to the 
old files before uploading into cvs...a r5 and a bone version of the project 
is a better solution...How did you do it anyway, Daniel? compiling against 
libnetapi on my r5 with Bone7a doesn't work, moreover I had to change some 
of the Be net classes headers, to get it to work.

>You also don't need to add the headers to a project file. It
>might
>speed up coding a little, but you can always get to the headers
>by
>right-clicking the little arrow to the side of the file that
>includes
>the header. Not having the header minorly speeds up the opening
>parse
>time.
>
This is a personal opinion of his, and therefore I do not agree...I like to 
have the headers in the project file, it's nice and easy to open them in 
that way, and you have all sources bundled in one project file....the little 
arrow works, I know, but it isn't clear exactly what headers belong to the 
project....

>For purely asthetic regions, I'd move Bme.rsrc up the libraries.
>Its
>another linktime item, so its logical there
>
Ok!

>All this is based off using "BeMSN.proj". This seemed like the
>right
>choice of project file, having three is a liitle confusing :-)
>
Ok BeMSN.proj was there for use with the old gui....Simon's idea to make a 
new folder for the new GUI and making a new project file to have at all 
times a working version with the old GUI was a good one....if it wasn't for 
the changes to the server code it may have worked....now I think it won't 
work anymore...so I suggest deleting all proj files but bme_x86 from cvs 
along with the old UI files....We could then make another proj 
file...bme_x86 would be the r5 one and say bme_x86_BONE the bone 
one...eventually we may have a bme_ppc proj file....

>None of this is meant to be critical mind, you're doing a great
>job
>with Bme. I'm still looking into a ppc port BTW :-) Although I
>do have
>more pressing issues (getting sound to work on my laptop, etc)
>to deal
>with first.
Nice to hear that, I like having a ppc build around....would he have to 
change a lot to make our sources compile on ppc?

>I'm also interested in how the Hotmail integration is going to
>work -
>I've written this before even compiling Bme or looking at the
>code.
>Considering NetPositive doesn't do JScript, and Mozilla/Firefox
>still
>has the "first-window-doesn't-show-requested-page" when running
>as
>native browser, I'm very interested in how an app can use
>Hotmail
>easily
>
As far as I know, hotmail integration in m$n is handled by making an html 
file with a lot of params in it an opening that in a browser... I don't know 
too much about it, but I think it'll open in both net+ and Mozilla 
FireFox...and eventually FireFox won't have that bug anymore so I isn't an 
issue I think....I will start at it soon btw...first the control to open 
mails and then the making of the html-file...

>As goes webcam and voice chat support, this is an area I'm
>interested
>in, as I have a large number of friends overseas who seem to
>assume MSN
>is the defacto standard for video and audio conferencing. To
>confirm
>what one of the dev team said in the TBJ interview - yes,
>supported
>webcams (CPIA parellel ones) do work as media nodes in exactly
>the same
>was a capture card with a TV camera on it does. Unfortunately my
>CPIA
>camera bit the dust a long time ago and my USB one is, clearly,
>unsupported. Also R5's USB kit just *does not* have the kit
>required
>for USB webcams. So when OBOS R1 is out, contact me and bug me
>over
>webcam support :-)
>
Hehe, would be nice to have webcam support....but let's concentrate on more 
important issues first...like getting a r1 of bme out...judging from the 
feedback and reactions on BeShare a lot of people would like to see that, 
and a lot of people are now experimenting with builds from cvs...So we have 
to clean up the cvs first I think, and communicate more with the community, 
to let them now we're still working on it.

>PS: Just compiling now, the code doesn't like BONE 7A here. Or
>it could
>be my headers. But all the BNetEndpoint stuff doesn't compile,
>MsnList.cpp has casting issues, and IconHandle.cpp has
>prototyping
>issues. Some of this could be down to my hacking around with the
>project file though :-)
Bone 7a had some issues, I explained MYOB he had to add a line to the 
NetAddress header and it should work...MsnList doesn't exist anymore in our 
new bme....

Oh btw, daniel I have made a UserPicView....and want to have a look at 
adding support for userpics...is that already possible....anyway I want to 
do at least the UI side of this...and I saw you had a beos.jpg at first for 
the user pic? How do you want to integrate this support, do you have any 
idea? we should at least have a talk about that before I can continue my 
work on the userview,

regards,

Tim

_________________________________________________________________
Play online games with your friends with MSN Messenger 
http://messenger.msn.nl/