Am Freitag 11 Januar 2008 schrieb Petit Eric: > 2008/1/6, Hendrik Sattler <[EMAIL PROTECTED]>: > > Hi, > > > > the development and release process of openobex seems to be stalled at > > the moment. Thus, I would ask to define release goals for openobex-1.4 in > > an open discussion on this list. > > Since Marcel is very quiet (though he does a good job at bluez), I take > > Christian as authoritive person for the project. > > > > There are some patches pending around and maybe it would be nice to have > > a modernized development environment than current SF.net which sucks a > > lot :-(, like an awful complicated and SLOW site. > > The already present trac on openobex.org is a good start but I would like > > to: - move the revision control to there, too, thus changing from CVS to > > SVN - move the bugs from SF.net to trac tickets > > - integrate patches from those bug reports > > - ask to be able to get more involved (and others may too) > > > > Additionally, I plan to update the Debian package to current CVS to be > > able to support IPv6 and hereby ask Christian to also support that in > > obexftp, but first release obexftp-0.22, finally, please or use the > > milestone stuff at the trac page to be able to see what's left. > > > > Additionally, we should drop some non-sense from openobex-apps: it should > > only contain real test application that can actually unit-test the > > library (the current ones cannot) and remove all the other simple > > "applications" that already have better replacements: > > - remove ircp, irxfer, obex_test_cable(==total non-sens), irobex_palm3 > > and obex_tcp > > - change obex_test in a way that makes it possible to > > (semi-)automatically test it > > > > Somehow we have to move along... > > > > Comments are welcome. > > > > HS > > hi HS and folk > Do think about something for WIN32 portage, like the CR LF problem > when downloading a file for example and also BT discovery ..... > PS: i'm in holiday at Réunion Island so i'll answer as i can when i > have time and web connection
This is not supposed to discuss obexftp actually. And since all data is treated as binary data, there is no CRLF problem (maybe a windows file descriptor issue). bluetooth discovery on windows, well... actually a nobrainer (see MSDN). It's rather a question of putting that into the DLL (like USB discovery but with totally unique identifier). HS ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
