Hi all!
I have looked at many PHP-Galleries before i stumbled upon Gallery. The first glimpse at Gallery 2 already caught my attention: i have never seen a php-project with such a beautifull architecture and such wonderful clean source code! Congratulations to you all, this is really impressive!
I installed G2, browsed a bit through the source code and this forum and i have the impression that many parts of G2 already are quite complete and stable. Do you share this opinion?
Do you think G2 can already be used as base for additional enhancements? I am totally aware that its official state is alpha and that you are free to change api's, schema's and stuff like that without prior notice. But from your experience: does this happen regularly?
Thanks for any answers,
Sebastian
Posts: 32509
disclaimer: no g2 developer speaking ;)
it's official status is pre-alpha, so theoretically, everything could change.
but actually, there are very few changes in the architecture (AFAIK), you may have noticed the minor database change topic. this was the first change in the db for a long time (AFAIK) and it's even just a minor change of a column, nothing else.
having said that and knowing that G2's architecture is modular, you're more than welcome to start your own module.
Posts: 974
DigPix, one thing that we don't mention a lot is that if you write good code that follows our conventions we will probably assist with making sure that it works with any further changes.
I still wouldn't recommend that you use G2 for your primary gallery. It's not there yet.
Posts: 31
Hi all,
i hope you had some nice easter holidays... ;-)
Thanks for you answers. I spent the day with a close inspection of the g2 code. I played around a bit and now i think i undestood the most important concepts.
My impression is that the main features actually work quite perfect. Browsing through the forum and the bug database it did not notice any major problems. So i would like to know whether i missed some important bugs?
I do not care about feature-completeness or interface bugs, i think i can deal with this. But are you currently aware of problems like unexpected crashes, data corruption or something like this? (i know that alpha still means data-corruption can occur anywhere during the future development process...)
I am curious because g2 really does not feel like pre-alpha but more like a beta...
Thanks,
Sebastian
Posts: 974
bharat writes good code, when he plans it.
Yes, G2 is already pretty kick-ass, robust, and stable. There are bugs, and there are missing features, but what is there is vigorously tested.
I have been really tempted to convert to G2 lately, because of the speed increases. However, there are still nasty, stinky bugs and missing features buried under the surface of G2. Something could go very wrong with a G2 installation and we don't have tools to recover from such a thing yet.
In addition, we have some specific features that have to be mostly finished before we go alpha. The migration module is one good example. Another big thing is the theming/layout. bharat is finishing a major rewrite of that right now. Honestly, there isn't a whole lot standing between us and alpha.
But, it will be done when it's done.
Posts: 31
> However, there are still nasty, stinky bugs and missing features buried under
> the surface of G2. Something could go very wrong with a G2 installation and we
> don't have tools to recover from such a thing yet.
That's what i wanted to know more about... ;-)
Can you give me some examples what "nasty, stinky bugs" are waiting for me?
Thanks again,
Sebastian
Posts: 974
If I knew what nasty stinky bugs were still hiding in G2 I would be fixing them instead of just assuming that they are there.
Posts: 7988
I don't know of any lurking data corruption issues. There are some minor problems like issues with the ways that we create our derivatives can lead to broken images, but nothing that we can't iron out before alpha.
I am pretty sure that I'm going to make a few more minor database changes between now and alpha, and we won't necessarily provide SQL upgrade scripts. That's why we're calling it pre-alpha now -- not because its unstable but because we don't want to have to write data migration scripts when we make changes to the database structure. Hopefully, we'll start doing that after alpha (but no promises).
Posts: 31
Hi!
Thanks for all your answers. It's fun just reading the source code, because it looks so beautifull...! I think i will use g2...
Thanks again,
Sebastian