ChangeSet ID: 25823
CVSROOT: /opt/cvs-commit
Module name: appdb
Changes by: wineowner(a)winehq.org 2006/06/19 11:32:11
Modified files:
. : TODO
Log message:
"EA Durbin" <ead1234(a)hotmail.com>
Update the TODO to reflect that we keep this information in the wiki now
Patch: http://cvs.winehq.org/patch.py?id=25823
Old revision New revision Changes Path
1.22 1.23 +2 -71 appdb/TODO
Index: appdb/TODO
diff -u -p appdb/TODO:1.22 appdb/TODO:1.23
--- appdb/TODO:1.22 19 Jun 2006 16:32:11 -0000
+++ appdb/TODO 19 Jun 2006 16:32:11 -0000
@@ -1,74 +1,5 @@
WineHQ Application Database TODO List
-####################
-# Unassigned TODOs #
-####################
+For the current TODO list please refer to the Wine Wiki at:
-AppDB Todo:
-
- * Improve application/version submission process
- Currently a user submits an application/version and a admin reviews it and
-either makes changes to it and accepts it or writes a comment and rejects it. Upon
-rejection the submission is deleted
-
- It would be more useful if instead of deleting the submission the submission
-was instead passed BACK to the person who submitted it so they could ammend it and
-resubmit it.
-
- * Add support for spell checking application, version submissions, description text
-and forum postings.
-
- * Allow admins to view both the application submission AND the version submission. In
-maybe 50% of the applications I accept I find out that the version submission was the
-default template with no testing information and/or was formatted in a difficult to
-understand way that required rejection. Seeing the application and the version at
-application processing time would let the admin decide at that time whether to accept or
-reject based on both the application and version.(Chris M - in progress)
-
- * Allow maintainers to handle screenshot and version submissions for the applications
-they maintain. The maintainer system has been a great success so far with over 150
-applications maintained by users of the appdb. These maintainers reply to forum postings
-for particular apps, edit and update application howto's and descriptions, and can add
-screenshots without appdb maintainer interaction. Having application maintainers also
-process screenshot and new version submissions would take more load off of the highest
-level maintainers of the appdb who have to go through all screenshots and all new
-versions that have been submitted.
-
-Continuing this distribution of work to individual experts should let us provide more
-accurate and complete information.
-
- * Overhaul the look and feel of the appdb. It looks a bit clunky in areas and I think
-with some polish it would be more pleasing to the eye and easier to maintain the look and
-feel.
-
- * Bugzilla/Appdb bug integration
- - Links between bugs and the appdb app
- - Scott, can you fill in more here?
- * Bugzilla/Appdb login integration, Single signon for bugzilla and appdb.
- - Need to figure out how to combine the two sets of account databases
- - How to provide the bugzilla and appdb authentication cookies
- - How to make the changes to both appdb and bugzilla as localized as possible
- to keep both applications usable for non-Wine related databases
- * Way to feedback information to the owner of the application to tell them that you use the app under wine
- - Might be as simple as adding a note to the application with the appropriate vendor email address.
-
-
-# support for merging applications together. We frequently have duplicate applications that need merging and its difficult to by hand
-
-# support for merging versions together
-
-# incorporate templates into appdb to simplify code, Jeremy says we can borrow from lostwages(winehq.org/cvsweb/lostwages) for this
-
-# add a system that will allow users to monitor an app without becoming a maintainer.
-
-# add wineversion, distro, source/package fields to the user_list table.
-
-# add wineversion, distro, source/package fields to the appComments table.
-
-# add new table for maintainer ratings. fields: userid, appId versionId ,rating, wineversion, distro, source/package
-
-##################
-# Assigned TODOs #
-##################
-
-# add distro table and administration screens for it. (Chris)
+http://wiki.winehq.org/AppdbInfo
Module: wine
Branch: refs/heads/master
Commit: c13f097de3ce04b98dad8a5a3f504055a276946b
URL: http://source.winehq.org/git/?p=wine.git;a=commit;h=c13f097de3ce04b98dad8a5…
Author: Jason Green <jave27(a)gmail.com>
Date: Fri Jun 16 23:01:20 2006 -0400
wined3d: Correct implementation of D3DSIO_LOOP.
I initially misread the specification. src0.x is the iteration count,
not the max amount for the loop register. This fixes that.
---
dlls/wined3d/glsl_shader.c | 13 ++++++++-----
1 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/dlls/wined3d/glsl_shader.c b/dlls/wined3d/glsl_shader.c
index a9b5820..91961eb 100644
--- a/dlls/wined3d/glsl_shader.c
+++ b/dlls/wined3d/glsl_shader.c
@@ -333,8 +333,10 @@ void shader_generate_glsl_declarations(
}
/* Declare loop register aL */
- if (reg_maps->loop)
+ if (reg_maps->loop) {
shader_addline(buffer, "int aL;\n");
+ shader_addline(buffer, "int tmpInt;\n");
+ }
/* Temporary variables for matrix operations */
shader_addline(buffer, "vec4 tmp0;\n");
@@ -1157,7 +1159,8 @@ void shader_glsl_sincos(SHADER_OPCODE_AR
/** Process the D3DSIO_LOOP instruction in GLSL:
* Start a for() loop where src0.y is the initial value of aL,
- * increment aL by src0.z while (aL < src0.x).
+ * increment aL by src0.z for a total of src0.x iterations.
+ * Need to use a temporary variable for this operation.
*/
void shader_glsl_loop(SHADER_OPCODE_ARG* arg) {
@@ -1166,9 +1169,9 @@ void shader_glsl_loop(SHADER_OPCODE_ARG*
char src0_mask[6];
shader_glsl_add_param(arg, arg->src[0], arg->src_addr[0], TRUE, src0_reg, src0_mask, src0_str);
-
- shader_addline(arg->buffer, "for (aL = %s.y; aL < %s.x; aL += %s.z) {\n",
- src0_reg, src0_reg, src0_reg);
+
+ shader_addline(arg->buffer, "for (tmpInt = 0, aL = %s.y; tmpInt < %s.x; tmpInt++, aL += %s.z) {\n",
+ src0_reg, src0_reg, src0_reg);
}
/** Process the D3DSIO_ENDLOOP instruction in GLSL: