hi all.
now that the gem-0.90 release is out for some weeks, i think it is time
to start some traffic on this list again.
(but of course: what to talk about now ? we used to discuss the release
for years...)
some points:
-------
stable:
i have branched v0_90 for bug-fixes on the latest stable release
--------------------
further development:
wini has done some research on opensource-development and has found out
that os-dev can be organized effectively in (surprise:) several ways to
…
[View More]achieve an optimum development/stability-ratio:
(the following is a translation from german and it is already some weeks
ago, so i might use the wrong termini)
a) pope: one person revises all code and decides which parts of the
development should go into the next release
b) committee: a small team off people does like the pope.
c) branching: each new feature is branched off the main CVS-trunk. as
soon as it has become stable the branch is merged with the main trunk.
i don't think that a) would be a very good idea (as it has proven to
lead to major quarrels and misunderstanding)
as for b) it seems like a bit of an overhead, as the core-development
team is so small, that all of us would be in the committee.
so i favour c) (with some b)): each development should be forked into a
separate branch in the CVS; the core-developpers of this branch work on
the code until they consider it stable and then make a call for testing
via the list. after it has proven to run stable on all platforms this
tree is merged back in.
i would suggest that the releasing should be done on each merge of a
development-branch to the main-trunk that adds new functionality. (this
can be discussed; it is just fundamentally different from the last release)
the main-trunk can be used for bug-fixing...
-------------
new features:
i'm looking forward to vertex-manipulation, pixel-shaders, multiple
gemwins, MMX/SSE2, new pixel-effects, pixel-analysis and tons of other
things.
cheers, comments ? and happy coding
mfg.as.dr
IOhannes
[View Less]
IOhannes m zmoelnig wrote:
> chris clepper wrote:
>
> right.
> i have just made some changes because of the newWave-bug that cyrille
> discovered and now i'm hesitating to check in ;-)
>
> i do think, we could relax the branching to "heavy changes" (e.g: what
> you call "changing the core functionality" and which could seriously
> break things, e.g. because the GemState is changed.
>
> as for small objects that are not likely to break anything (…
[View More]especially:
> compilation!!!) they probably should go into the main dev-trunk
> immediately.
>
>
> now i'll wait for some comments too, until i check in (to be honest: i
> was thinking slowly and have committed it to the v0_90 already; but at
> l(e)ast i thought...)
ok, as there have been no comments at all i have branched and checked in
the newWave-changes;
branch-name: newWave_textures
aim: make textures work correctly on newWave
changes done so far:
- more support for texture-coordinates
- switchable texture-algorithm: normal(0) vs. spheric(1)
- removed a lot of variables that i could not understand and that didn't
do anything in the actual code.
some tests are required to merge it back again.
mfg.a.sdr
IOhannes
PS: should we setup something like gem-cvs so everyone would know
automatically when changes are made ? the traffic isn't that high so we
could eventually use this list ????
[View Less]
hello,
I just notice a change with newWave texturing.
The texture is no more distorded with 0.90 like it was with 0.88
I prefer the way it was, does the old comportement is lost?
I also notice that it is no more possible to texture the primitive in
line or point mode (only fill).
anyway, when opening the "exemple/07.texture/05.newWave.pd" help file,
the primitive is all the same color. I need to destroy and create a
second time the gem-windows to have the correct texture on the …
[View More]primitive
(util next time you start pd).
this bug is happening only with newWave, not with other primitives.
I tried on 2 computers : windowsXP and osX 10.3. both with latest gem
version found on the iem website.
(pd 0.37.1)
Cyrille
[View Less]
Hi all,
I'm enjoying gem 0.90 but I'm having some problems with pix_video under
Linux.
Alpha blending doesn't work with pix_video using [alpha] and
[colorRGB]in the renderchain (it worked in 0.888-cvs).Should I use
[pix_alpha] instead ?
Mixing pix_video with pix_buffer_read flips the resulting image. Setting
m_image.image.upsidedown=false in videoV4L.cpp and using [pix_video]
with [pix_flip] solves this problem (ugly workaround).
Also I'm looking for a way too zoom a pix but pix_zoom never …
[View More]worked for me.
I'm using RH8 2.4.21 and TNT2 with nvidia drivers.
Thanks for any advice and great work !!
Mirko Petrovich
Santiago de Chile
[View Less]