I haven't had a chance to talk to MGN about this, but I believe we are both backlogged with other projects. A D7 version will definitely happen, but I just don't know when.
I'm going to leave this issue open until something happens for D7.
Yes. Backlogged is a good word for it. I have recently ajaxified some of the forms for the drupal 6 version and am testing some new features, but its happening slowly. I will be happy to work on a D7 port when I get the chance, but I don't expect to make much progress (on D7) in the next couple of months. Hopefully shoot for a stable 6.x-2.x release and then port to D7.
Can only API, not others, be developed parallel with 6.x-2.x? If so it will be nice for testing with D7. After API is reached to stable state other modules can be added. Is it a good idea?
A lot has change in D7, so we'll probably need to take a hard look at the current code and see what makes sense. I've been out of the loop for a while, so MGN will have a better idea.
I've been planning to get back into the game and start working on Gradebook again. However, finding the time has been hard and I definitely can't start till at least late April.
These are some dev notes for later reference (when I have time to act on them).
Grades should become first-rate entities in D7. This would let them be fieldable which opens up some really interesting possibilities. I see the following fields being core to each grade entity instance:
User ID
Grade value
Grade value type (for flexibility in grade valuation)
I didn't include any node reference information because ultimately we shouldn't assume grades are only attached to node entities. Maybe they can be attached to comments, files, etc. We can take a look at the work being done in the Relation module (http://drupal.org/project/Relation) to handle this concept.
We could also abstract the user information from the grade entity, but I don't immediately see the need. Maybe someone wants to store grades for people that don't have user accounts?
As for grades being fieldable, here is my line of thinking. Grade would be the entity type, and a grade type would be the entity bundle. Doing it this way would let us attach different fields to different grade types. We could have the basic grade type with no fields, and another grade type with a comment field. When Gradebook is hooked up to record grades for say a node, you'd select the grade type to use. The fields on the grade type would then be there for every grade entered.
The other great thing about grades being fieldable is that we can automatically take advantage of any new field type that pops up in contrib, including the media module.
This sounds like a great idea. I'll have to read up on this, since I haven't worked with fields in D7 yet. this might be a great opportunity to learn.
I was planning on doing a straightforward port, just to get gradebook up and running on D7. This sounds like a fairly fundamental change. Need to consider the upgrade path as well.
Yes and no. We already have the grade table. It would just be a matter of exposing it as first rate entities. We'd need to add a 'type' column at some point to support multiple bundles but could initially use one hard coded bundle like 'user' does.
As for fields, the grade table columns can be exposed as pseudo fields. This is what happens with node titles. They are not true fields since they can't be removed and such, but they still show up in the 'manage fields' page for reordering. It's a piece of cake to do.
Some of the stuff I was mentioning about entity relations can be done later.
The upgrade path shouldn't be a big issue with these things in mind.
Update: I have been working on porting gradebookapi to drupal 7 now. I think I have just about figured out the changes required by the new database api.
I've created a 7.x-2.x-dev branch and have ported gradebookapi, gradebook, and the gradebook_scales modules (so far). I am working on the remaining gradebook submodules (gradebook_responses, _attachments, _roster). The D7 version works pretty much the same way as the D6 version with a couple of enhancements along the way.
Views, quiz, rules, etc. integrations also need attention - I haven't had a chance to consider these yet.
The documentation hasn't been adjusted for D7 yet.
Comments
Comment #1
sadist commentedsubscribe.
Comment #2
SanDiego commentedsubscribing...
Comment #3
rwohlebI haven't had a chance to talk to MGN about this, but I believe we are both backlogged with other projects. A D7 version will definitely happen, but I just don't know when.
I'm going to leave this issue open until something happens for D7.
Comment #4
MGN commentedYes. Backlogged is a good word for it. I have recently ajaxified some of the forms for the drupal 6 version and am testing some new features, but its happening slowly. I will be happy to work on a D7 port when I get the chance, but I don't expect to make much progress (on D7) in the next couple of months. Hopefully shoot for a stable 6.x-2.x release and then port to D7.
Comment #5
tutumlum commentedCan only API, not others, be developed parallel with 6.x-2.x? If so it will be nice for testing with D7. After API is reached to stable state other modules can be added. Is it a good idea?
Comment #6
rwohlebA lot has change in D7, so we'll probably need to take a hard look at the current code and see what makes sense. I've been out of the loop for a while, so MGN will have a better idea.
Comment #7
tutumlum commentedIs there any chance to start D7 version?
Comment #8
rwohlebI've been planning to get back into the game and start working on Gradebook again. However, finding the time has been hard and I definitely can't start till at least late April.
Comment #9
MGN commentedRealistically....it will probably be sometime in May for me - not until I stick a fork in this semester...
Comment #10
tebb commentedFollowing.
Comment #11
rwohlebThese are some dev notes for later reference (when I have time to act on them).
Grades should become first-rate entities in D7. This would let them be fieldable which opens up some really interesting possibilities. I see the following fields being core to each grade entity instance:
I didn't include any node reference information because ultimately we shouldn't assume grades are only attached to node entities. Maybe they can be attached to comments, files, etc. We can take a look at the work being done in the Relation module (http://drupal.org/project/Relation) to handle this concept.
We could also abstract the user information from the grade entity, but I don't immediately see the need. Maybe someone wants to store grades for people that don't have user accounts?
As for grades being fieldable, here is my line of thinking. Grade would be the entity type, and a grade type would be the entity bundle. Doing it this way would let us attach different fields to different grade types. We could have the basic grade type with no fields, and another grade type with a comment field. When Gradebook is hooked up to record grades for say a node, you'd select the grade type to use. The fields on the grade type would then be there for every grade entered.
The other great thing about grades being fieldable is that we can automatically take advantage of any new field type that pops up in contrib, including the media module.
Comment #12
MGN commentedThis sounds like a great idea. I'll have to read up on this, since I haven't worked with fields in D7 yet. this might be a great opportunity to learn.
I was planning on doing a straightforward port, just to get gradebook up and running on D7. This sounds like a fairly fundamental change. Need to consider the upgrade path as well.
Comment #13
rwohlebYes and no. We already have the grade table. It would just be a matter of exposing it as first rate entities. We'd need to add a 'type' column at some point to support multiple bundles but could initially use one hard coded bundle like 'user' does.
As for fields, the grade table columns can be exposed as pseudo fields. This is what happens with node titles. They are not true fields since they can't be removed and such, but they still show up in the 'manage fields' page for reordering. It's a piece of cake to do.
Some of the stuff I was mentioning about entity relations can be done later.
The upgrade path shouldn't be a big issue with these things in mind.
Comment #14
MGN commentedUpdate: I have been working on porting gradebookapi to drupal 7 now. I think I have just about figured out the changes required by the new database api.
Comment #15
houstonaplus commentedsubscribe
Comment #16
tmuras commentedsubscribing
Comment #17
artatac commentedSub
Comment #18
Broda commentedsub
Comment #19
MGN commentedI've created a 7.x-2.x-dev branch and have ported gradebookapi, gradebook, and the gradebook_scales modules (so far). I am working on the remaining gradebook submodules (gradebook_responses, _attachments, _roster). The D7 version works pretty much the same way as the D6 version with a couple of enhancements along the way.
Views, quiz, rules, etc. integrations also need attention - I haven't had a chance to consider these yet.
The documentation hasn't been adjusted for D7 yet.
Still much to to do!
Comment #20
Carlos Miranda Levy commentedComment #21
Adel commentedSubscribing !
Comment #22
Adel commentedComment #23
rwohlebPlease do not change who this issue is assigned to.
Comment #24
chaosmind commentedSubscribe
Comment #25
Adel commentedSorry :s
Comment #26
truongquangphuc commentedWaitting for D7 version ........=,="
Comment #27
AntiNSA commentedsub
Comment #28
rwohleb*cough* There is a follow button now. *cough*
Comment #29
eveemy commentedHI
I want to create students assignment, quiz, homework etc.
But i do not know Which module I want to use for this?
Anyone can help me please?
Comment #30
rwohlebPlease don't change the issue settings. We don't have a Drupal 7 version yet.
Comment #31
rpeters commentedDo you have time when D7 will be released?
Comment #32
trentharlem commentedIn addition to the Follow button, (clears throat) perhaps we could add a "Donate" button to help move things along.
Comment #33
possibrifollowing and testing out dev
Comment #34
csardev commentedsubscribe
Comment #35
csardev commentedsubscribe