Menu
▾
▴
openvrml-develop — OpenVRML developers mailing list
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(25) |
Dec
(46) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(3) |
Feb
(23) |
Mar
(6) |
Apr
(15) |
May
(16) |
Jun
(24) |
Jul
(16) |
Aug
(92) |
Sep
(31) |
Oct
(40) |
Nov
(24) |
Dec
(32) |
| 2002 |
Jan
(22) |
Feb
(4) |
Mar
(38) |
Apr
(52) |
May
(38) |
Jun
(61) |
Jul
(44) |
Aug
(9) |
Sep
(15) |
Oct
(13) |
Nov
(34) |
Dec
(25) |
| 2003 |
Jan
(26) |
Feb
(10) |
Mar
(10) |
Apr
(5) |
May
(30) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(29) |
Oct
(12) |
Nov
(18) |
Dec
(14) |
| 2004 |
Jan
(18) |
Feb
(23) |
Mar
(17) |
Apr
(17) |
May
(9) |
Jun
(10) |
Jul
(1) |
Aug
|
Sep
|
Oct
(4) |
Nov
(9) |
Dec
(29) |
| 2005 |
Jan
(37) |
Feb
(24) |
Mar
(6) |
Apr
(4) |
May
(2) |
Jun
(18) |
Jul
(3) |
Aug
(14) |
Sep
(6) |
Oct
(7) |
Nov
(25) |
Dec
(21) |
| 2006 |
Jan
(21) |
Feb
(17) |
Mar
|
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
(13) |
Sep
(4) |
Oct
(22) |
Nov
(31) |
Dec
(19) |
| 2007 |
Jan
(10) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(1) |
Jun
(8) |
Jul
(13) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(3) |
Dec
(5) |
| 2008 |
Jan
(13) |
Feb
(5) |
Mar
(7) |
Apr
(13) |
May
(12) |
Jun
(8) |
Jul
(24) |
Aug
(25) |
Sep
(12) |
Oct
(16) |
Nov
(1) |
Dec
|
| 2009 |
Jan
(4) |
Feb
(13) |
Mar
(9) |
Apr
|
May
(2) |
Jun
|
Jul
(11) |
Aug
(6) |
Sep
(2) |
Oct
(15) |
Nov
(11) |
Dec
|
| 2010 |
Jan
(4) |
Feb
(11) |
Mar
(38) |
Apr
(7) |
May
(13) |
Jun
(4) |
Jul
(17) |
Aug
(1) |
Sep
(13) |
Oct
(10) |
Nov
(4) |
Dec
|
| 2011 |
Jan
(6) |
Feb
(1) |
Mar
|
Apr
(6) |
May
(8) |
Jun
(2) |
Jul
(10) |
Aug
(2) |
Sep
|
Oct
|
Nov
(2) |
Dec
(1) |
| 2012 |
Jan
(3) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(7) |
Jun
(8) |
Jul
(1) |
Aug
|
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(4) |
Nov
(3) |
Dec
|
|
From: Braden M. <br...@en...> - 2000-11-15 03:12:14
|
I'm CC'ing the mailing list; if you haven't already, you might want to subscribe. On Tue, 14 Nov 2000, Gilles GALLEE wrote: > i couldn't checkout module "librml97" with wincvs 1.0.6. > CVSROOT is "ano...@cv...:/data/cvs" > > The error message printed by wincvs is : > cvs checkout -P libvrml97 (in directory E:\users\Gilles2\OPENVRML_CVS) > cvs [checkout aborted]: connect to cvs.openvrml.org:2401 failed: > Connection refused > > I made an error but where ? Maybe Chris can help you, but I have no experience with WinCVS. I do note a number of docs on the subject here: <http://sourceforge.net/docman/?group_id=1> (section 7). -- Braden N. McDaniel e-mail: br...@en... <http://www.endoframe.com> Jabber: br...@ja... |
|
From: Jeff D. <ig...@po...> - 2000-11-10 21:51:58
|
I've noticed that OpenVRML exists both at openvrml.org, and sourceforge.net, complete with CVS repositories and mailing lists at both places. Is this some weird schism, are you trying to transition over to (or away from) sourceforge, or is something even stranger going on? If I wanted to write a bit of code, where should I go? -jeff |
|
From: WilTech <in...@wi...> - 2000-11-10 04:11:38
|
I guess I won't need help getting the s/w to work with VC++ 4.0. I just = bought Version 6. Cheap! Only about $36 after rebate for the standard = version... Joseph |
|
From: S.K.Bose <bo...@pa...> - 2000-11-08 10:40:21
|
On Tue, 7 Nov 2000, WilTech wrote: > Greetings to everybody! > > Let me introduce myself. I'm new to this list. I'm 21, and I (am trying to) run a business doing web programming and 3D design. > I want to be able to have my "own" -- thanks, GPL! -- VRML browser that I can pass out to customers. > So Lookat looks good! However, my copy of MS Visual C++ is old, version 4. (Actually, it's my younger brother's copy!) and won't load .dsp or .dsw files. It wants .mak s! > > Can anyone give me a hand with getting something going here? Oh, yes... I also need to know if my version of MFC will be sufficient for the job. > The new parser is compiled with MSVC++6 and it is working without failure. I have no idea with MSVC++4. I am having doubt because new parser is using lot many advance features of C++ (Is there anybody who successfully installed new parser with MSVC++4?) Thanks, Bose |
|
From: WilTech <in...@wi...> - 2000-11-08 04:54:51
|
Greetings to everybody!
Let me introduce myself. I'm new to this list. I'm 21, and I (am =
trying to) run a business doing web programming and 3D design. =20
I want to be able to have my "own" -- thanks, GPL! -- VRML browser =
that I can pass out to customers.=20
So Lookat looks good! However, my copy of MS Visual C++ is old, =
version 4. (Actually, it's my younger brother's copy!) and won't load =
.dsp or .dsw files. It wants .mak s!
Can anyone give me a hand with getting something going here? Oh, =
yes... I also need to know if my version of MFC will be sufficient for =
the job. =20
=20
Thanks much!
Joseph Sullivan
I=20
|
|
From: Braden M. <br...@en...> - 2000-11-07 06:34:22
|
On Sat, 4 Nov 2000, Braden McDaniel wrote: > * Take ANTLR out of the automated build process. This would mean that any > changes to the ANTLR input file would require manually running ANTLR to > generate new output code. This would almost certainly be coupled with > checking the generated sources into CVS. cks will probably like this > option :-). And even though this complicates the build process for > developers, it looks like the best option to me right now, too. I've got the changes to do this in my tree. I intend to commit them and release 0.9.0pre2 in the next day or two, unless someone hollers. -- Braden N. McDaniel e-mail: br...@en... <http://www.endoframe.com> Jabber: br...@ja... |
|
From: Braden M. <br...@en...> - 2000-11-05 04:41:03
|
[Note: None of what I'm about to say applies to any changes before 0.9.0. But I wanted to go ahead and ask about this stuff while it's fresh on my mind.] Right now, we export a bunch of symbols and install a bunch of header files associated with libantlr. Since it's conceivable that The Real libantlr could coexist on a system with our library, I think this is Bad Form. I think the need to do all of this could be eliminated if there's agreement that we don't need to be making the parser public. If we don't need *those* symbols/headers public, I don't think we need any of the ANTLR stuff public either. -- Braden N. McDaniel e-mail: br...@en... <http://www.endoframe.com> Jabber: br...@ja... |
|
From: Braden M. <br...@en...> - 2000-11-05 00:51:21
|
Because of "issues" with the way automake handles BUILT_SOURCES, the build system wants to run ANTLR at times even when the ANTLR-generated sources exist and are up-to-date. I've played around with a few things, including simply eliminating the BUILT_SOURCES variable, but so far I have not been able to kick automake into submission. Here are the options I see: * Jettison automake. Unless we'd also be replacing other build tools, we'd either need to find something else that does what automake does, or start writing Makefile.ins by hand. I don't know of anything else that does what automake does, and I'm not going to start writing Makefile.ins by hand. (As far as I'm concerned, this really isn't an option.) * Take ANTLR out of the automated build process. This would mean that any changes to the ANTLR input file would require manually running ANTLR to generate new output code. This would almost certainly be coupled with checking the generated sources into CVS. cks will probably like this option :-). And even though this complicates the build process for developers, it looks like the best option to me right now, too. Comments? Other options? -- Braden N. McDaniel e-mail: br...@en... <http://www.endoframe.com> Jabber: br...@ja... |
|
From: Braden M. <br...@en...> - 2000-10-26 05:10:48
|
For the last few days I've spent my evenings resolving issues with building with gcc 2.96 that comes with Red Hat 7.0. I think they are all resolved at this point, with the caveat that you still must explicitly set CFLAGS at configure time to turn off optimization. (I have found no way to get libtool not to generate the -fPIC flag.) We'll have to put a note about this in README and INSTALL. The forthcoming 0.9.0pre2 release will include these fixes; of course, there's always CVS for the impatient. The last thing that's holding up this release on my end is getting the tarball to build without requiring an installation of ANTLR. Is there anything other folks would like to get in for this release? -- Braden N. McDaniel e-mail: br...@en... <http://www.endoframe.com> Jabber: br...@ja... |
|
From: Christopher K. S. J. <cs...@qu...> - 2000-09-22 14:23:53
|
Mostly this is a test message, but also: has anyone looked at scripting lately? Some of the problems that I thought were due to event naming have turned out to be problems with MF* support in the javascript interfaces. -cks |
2 messages has been excluded from this view by a project administrator.
