next »

[qbproger]

Are there any plans for a new release?

Maybe we could put together a list of features/bugs that need to be implemented/fixed before the next release.

Also, I think it would be a good idea to host the files in the files section on sourceforge, and link to that.  Posting files that increases the activity of the project, and it keeps track of downloads.

What are everyone elses' opinions on the subject?

[Marvin Fröhlich]

Hosting the downloads on sourceforge is certainly not a bad idea. I think, we should do that (except for the planned nightly builds).

Putting together a list of features/bugs won't work. I did this two times in the past, but there were always changing priorities and/or people not fulfilling the plans or not subscribing to a topic in that list. This is an open source project, that depends on peoples' moods to get things done.

I'm not sure, when the next release can be expected. I definitely want to finish the model loader rework, which is kind of difficult. After that I think, there's a good point for a cut and for a release. Mathias told me some days ago, that he wanted to create an automation script for nightly builds. No idea, how far he pushed his plans up to now.

Marvin

[Mathias 'cylab' Henze]

The current ant build script has support for creating a release. I just comitted two minor changes to it. The only things missing are binary versions of the XIN and some other documents, which are copied in source form to the release folder. If we add the generated PDF-documents beside the source documents in the build repository, I can adjust this.

@Marvin
What do you think? Would it hurt in your opinion to additionally have the pdfs in the subversion repository?

You can call "ant dist" in xith-tk to create a distribution fileset and "ant release" to create a release zip for download. The release incorporates version and build number. The version can be changed in "xith3d/ant-settings/build-defaults.properties" and the build number is incremented automatically on any call to "dist".

I was anyway waiting for some changes to finish before uploading a new cooker release. So Marvin, just tell me when you think we have suitable codebase for this (Jagatoo input changes are ready I think. What about the Texture-FIlter stuff and the loaders?)

[Marvin Fröhlich]

The current ant build script has support for creating a release. I just comitted two minor changes to it. The only things missing are binary versions of the XIN and some other documents, which are copied in source form to the release folder. If we add the generated PDF-documents beside the source documents in the build repository, I can adjust this.

@Marvin
What do you think? Would it hurt in your opinion to additionally have the pdfs in the subversion repository?

You can call "ant dist" in xith-tk to create a distribution fileset and "ant release" to create a release zip for download. The release incorporates version and build number. The version can be changed in "xith3d/ant-settings/build-defaults.properties" and the build number is incremented automatically on any call to "dist".

Well, I don't know, what your ant script is able to do. But if it is capable of uploading releases, it should also be capable of downloading the XIN PDF from the net. If this is possible, I would prefer the PDF not to be in SVN. If this is not possible, it's also ok to have it in SVN, but it's not the best solution.

It would also be very cool, if those build numbers would be taken from the current SVN release. And additionally it would be great, if the current SVN release was applied to the class "Xtih3D". Maybe it has to be changed to read the number from a file, which can be updated by an script more easily.

What do you think? Is this possible?

I was anyway waiting for some changes to finish before uploading a new cooker release. So Marvin, just tell me when you think we have suitable codebase for this (Jagatoo input changes are ready I think. What about the Texture-FIlter stuff and the loaders?)

JAGaToo input is indeed ready, as well as the Texture-Filter stuff. The only thing, that I am not sure about, are the enums, that reside as inner classes in the AbstractTexture and AbstractTextureImage interfaces. I think, they should be moved as stand-alone enums to some package. But that's not too difficult and time-consuming.

The loaders are my current project and will take some time. I will definitely report, when they're ready. Then we can do a release. My next tasks don't need to be included in this upcoming release. But I will sum them up here just for your information:

• Add an AMotor abstraction to XPAL.
• Create an (or finish the) XPAL implementation for ODEJava.
• Create an XPAL implementation for JBullet.
• Rework the HUD implementation.
  This will not change the HUD's API too much. But should improve rendering performance by far. The prerequisite step, needed to do this has already been done. It was to create a way to do direct texture drawing in an easy and cheap way.

Marvin

[Mathias 'cylab' Henze]

Well, I don't know, what your ant script is able to do. But if it is capable of uploading releases, it should also be capable of downloading the XIN PDF from the net. If this is possible, I would prefer the PDF not to be in SVN. If this is not possible, it's also ok to have it in SVN, but it's not the best solution.

Well, downloading from the net would be no problem beside a possible synchronization problems, if the new XIN PDF is not uploaded before creating a build. Best would be to use OpenOffice command line utilities to generate the PDF files on the fly. Do you know if this is possible?

Uploading the release should still be done manually just because of authentication. Or we could make the script prompt for the account data...

It would also be very cool, if those build numbers would be taken from the current SVN release. And additionally it would be great, if the current SVN release was applied to the class "Xtih3D". Maybe it has to be changed to read the number from a file, which can be updated by an script more easily.

What do you think? Is this possible?

I don't know what you mean by applying the release to the Xith3D class. With the Subversion commandline utility, you can use it to replace the revision in a file: http://blog.taragana.com/index.php/archive/how-to-add-revision-number-id-automatically-to-subversion-files-in-two-simple-steps/ Is that what you mean? This can easily be done from an ant-script, if the path to the svn utility is given.

JAGaToo input is indeed ready, as well as the Texture-Filter stuff. The only thing, that I am not sure about, are the enums, that reside as inner classes in the AbstractTexture and AbstractTextureImage interfaces. I think, they should be moved as stand-alone enums to some package. But that's not too difficult and time-consuming.

I also don't like enums being defined inside of the classes that use them. This is ugly and unpractical for imports. I would place them in the same package level like the public available part of the API they belong to.

The loaders are my current project and will take some time. I will definitely report, when they're ready. Then we can do a release.

Should we wait for this to finish before doing a cooker release or before doing a full release?

My next tasks don't need to be included in this upcoming release. But I will sum them up here just for your information:

• Add an AMotor abstraction to XPAL.
• Create an (or finish the) XPAL implementation for ODEJava.
• Create an XPAL implementation for JBullet.
• Rework the HUD implementation.
  This will not change the HUD's API too much. But should improve rendering performance by far. The prerequisite step, needed to do this has already been done. It was to create a way to do direct texture drawing in an easy and cheap way.

Nice list Keep it up!

[Marvin Fröhlich]

Well, downloading from the net would be no problem beside a possible synchronization problems, if the new XIN PDF is not uploaded before creating a build. Best would be to use OpenOffice command line utilities to generate the PDF files on the fly. Do you know if this is possible?

I guess, synchronization is not a problem. How often is XIN being updated ?
I have no idea about these OpenOffice command line utilities.

Uploading the release should still be done manually just because of authentication. Or we could make the script prompt for the account data...

What ever you like best.

I don't know what you mean by applying the release to the Xith3D class.

Hmm... Bad typo by me. I was talking about the current SVN revision number, that should be written to the org.xith3d.Xith3D class. It is the last parameter in line 59. And possibly the String "prerelease" should be replaced by "cooker" or "alpha" or what ever is released. And of course these version indicators should be copied to the jar's manifest. But I guess, this is already done, right?

Should we wait for this to finish before doing a cooker release or before doing a full release?

I would like these changes to be in the next cooker release, too. I have some holidays this week. So I hope to get it ready soon.

Marvin