Dear Developers,
I just posted on the user list to David about the aborted RG 1.7.3.
I mentioned my thoughts as to why this was aborted. Here is the recap:
> I would imagine that Michael thought things had slowed down in the svn
> branch and that there were enough bug fixes to roll out a new release.
>
> Unfortunately, we had some recent feature additions that created another
> nasty bug in the event rulers. Until that is fixed, it would be unwise
> to release it.
>
> It doesn't make any sense to release a version with a known new bug--one
> that has personally crashed my RG setup a few times this last week. So
> we either will need to fix this bug, or remove the offending new feature
> until this can be resolved.
>
> Plus I imagine, there were a couple other tweaks that were made that may
> not be production ready, yet--more event ruler issues, like bar width,
> the velocity adjust feature, and a consensus on event selection methods
> and displaying of such events. I think that covers it.
>
> I would assume Michael is waiting on bug fixes and executive decisions
> between he and Chris about some of these updates before rolling out RG
> 1.7.3. I also hadn't seen any talks about these issues though Michael
> has clearly asked for input.
So I bring this to the developer thread for discussion:
1. What are we doing about event ruler selection?
Are we changing boxes to blue? Are are using red outlines, both? Are we going
to use a monochromatic blue scale to approximate the the value of selected
events in the ruler, or are we going to do a shading or screening of some sort?
Are we going to leave it be with two distinct selection methods? These need
discussed before proceeding.
2. What are we doing about the event ruler bug?
Are we going to role back this feature as well, or are we going to fix this
bug? I'm certain all of this is related to question 1. My only real
preference here is that whoever created the bug should step up and either fix
it or ask for help to resolve it.
I don't have a real interest in this one except that somewhere in all of this
is a bug that is crashing my RG setup. I'd like that resolved.
3. What are we doing about event ruler widths?
Are we going to role back the width adjustment to the former wide width? My
understanding is that that update was part of a effort that is now on hold
until the port is finished.
So we should role it back, or we should finish out the logical line of thought
and increase number of events drawn with the "draw line of controllers" to
match the new bar line width. I think it looks silly the way it is now. So it
is just a cosmetic issue. But doing so would satisfy those that have asked for
a higher density controller setting. This could be a mid-stream compromise
until a more elegant solution is rolled out after the port.
------
So with that, I throw this back to the developer's court. Please discuss so we
can get some direction on these issues.
I will get back to my small part of the humbling RG port.
Sincerely,
Julie S.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
