Any plans for this, and if not, may I contribute to an effort to make a near future G1.x.x release, XHTML1.0 transitional compliant? Would not this be useful to many?
Sincerely,
Stephen Jones
It would certainly be desirable. Useful... well, it's not the most critical issue with G1 from our standpoint, but it would be nice to have.
G2 is being built up to be XHTML 1.1 strict compliant (or maybe even XHTML 2 depending on when G2 and XHTML 2 are complete). So at least we'll get it right for G2.
My main concern for G1 is that it will require such a *large* code overhaul. Making thousands of tiny changes to code can make for code maintenance nightmares. People with customisations will have a very difficult time upgrading.
The way I'm hoping to approach this issue is this: (please provide feedback!)
We'll make some small changes that get us most of the way: we'll add alt="" tags and ending "/"s to <img> tags, <br /> tags, etc. If you're willing to create a patch, we'll try and get these changes in quickly. (But hold off, as the Gallery v1.x code is going to change *dramatically* in the next month or so...)
As for things such as making sure element attributes are properly quoted (e.g. <p class="error"> rather than <p class=error>), we'll change these as we come across them. I'm going to take a look at just how much of the G1 code we're willing to change, and how big a project this would be. If it turns out to be not that bad, then I certainly think we could go ahead and make the necessary changes, in which case your assistance will certainly be welcome!
-Beckett (
)
phineasflapdoodle
Joined: 2003-05-08
Posts: 11
Posted: Sat, 2003-06-14 16:33
Thanks Beckett, and when it comes time and the decision is made, please let me know; I'd be very happy to help, and I have seen most of those many little changes that would be needed.
So as to accomodate all those that have hacked G1, my suggestion: As G1 nears the end of it's development life, eg. 6 months from now and the final release (assuming there is a final, LOL) is Gallery 1.4.2 (just as an an illustration example), efforts could be made such that, that G1 release could be split into 2 releases, the first, as-is, and the second, XHTML 1.0 transitional compliant. Since the Gallery team wouldn't be going forward (my assumption again) with further work or releases of G1, that approach might be nice.
Hell, just spur of the moments thoughts.
Sincerely,
Stephen
beckett
Joined: 2002-08-16
Posts: 3474
Posted: Sat, 2003-06-14 16:51
Some more tidbits:
1. Gallery v1.x. is currently and will forevermore be in a "maintenance" mode. This means we don't have huge grandiose plans for G1 (that's what G2 is for), but we're going to keep improving/fixing it as long as people still use it and there is a demand for changes. I don't see G1 going away any time soon... So we're going to be supporting/changing/improving G1 for a long time to come.
2. There's no reason we can't make a branch for Gallery that's XHTML compliant. We can test it separately, and then merge it into the main code once we're happy with it.
Anyway... I'll try and keep you updated in this post as to what's happening with G1. I'd love to have a longer discussion... we tend to hang out in the #gallery IRC chatroom on irc.freenode.net. Or email. Or right here...
phineasflapdoodle
Joined: 2003-05-08
Posts: 11
Posted: Wed, 2003-06-18 08:49
#1 sounds like a winner, but mainly for all the userbase! sure puts a much bigger burden for much longer time, on all you developers, but that's neither here nor there.
#2 sounds great.
I'll try and meet up with you on freenode, soon, and yes, sure do keep me posted as you've got time. cool.
Posts: 3474
It would certainly be desirable. Useful... well, it's not the most critical issue with G1 from our standpoint, but it would be nice to have.
G2 is being built up to be XHTML 1.1 strict compliant (or maybe even XHTML 2 depending on when G2 and XHTML 2 are complete). So at least we'll get it right for G2.
My main concern for G1 is that it will require such a *large* code overhaul. Making thousands of tiny changes to code can make for code maintenance nightmares. People with customisations will have a very difficult time upgrading.
The way I'm hoping to approach this issue is this: (please provide feedback!)
We'll make some small changes that get us most of the way: we'll add alt="" tags and ending "/"s to <img> tags, <br /> tags, etc. If you're willing to create a patch, we'll try and get these changes in quickly. (But hold off, as the Gallery v1.x code is going to change *dramatically* in the next month or so...)
As for things such as making sure element attributes are properly quoted (e.g. <p class="error"> rather than <p class=error>), we'll change these as we come across them. I'm going to take a look at just how much of the G1 code we're willing to change, and how big a project this would be. If it turns out to be not that bad, then I certainly think we could go ahead and make the necessary changes, in which case your assistance will certainly be welcome!
-Beckett (
)
Posts: 11
Thanks Beckett, and when it comes time and the decision is made, please let me know; I'd be very happy to help, and I have seen most of those many little changes that would be needed.
So as to accomodate all those that have hacked G1, my suggestion: As G1 nears the end of it's development life, eg. 6 months from now and the final release (assuming there is a final, LOL) is Gallery 1.4.2 (just as an an illustration example), efforts could be made such that, that G1 release could be split into 2 releases, the first, as-is, and the second, XHTML 1.0 transitional compliant. Since the Gallery team wouldn't be going forward (my assumption again) with further work or releases of G1, that approach might be nice.
Hell, just spur of the moments thoughts.
Sincerely,
Stephen
Posts: 3474
Some more tidbits:
1. Gallery v1.x. is currently and will forevermore be in a "maintenance" mode. This means we don't have huge grandiose plans for G1 (that's what G2 is for), but we're going to keep improving/fixing it as long as people still use it and there is a demand for changes. I don't see G1 going away any time soon... So we're going to be supporting/changing/improving G1 for a long time to come.
2. There's no reason we can't make a branch for Gallery that's XHTML compliant. We can test it separately, and then merge it into the main code once we're happy with it.
Anyway... I'll try and keep you updated in this post as to what's happening with G1. I'd love to have a longer discussion... we tend to hang out in the #gallery IRC chatroom on irc.freenode.net. Or email. Or right here...
Posts: 11
#1 sounds like a winner, but mainly for all the userbase! sure puts a much bigger burden for much longer time, on all you developers, but that's neither here nor there.
#2 sounds great.
I'll try and meet up with you on freenode, soon, and yes, sure do keep me posted as you've got time. cool.