On Tuesday 19 July 2005 01:56, you wrote:
> > - Investigate whether it is possible to use GalleryPluginMap to store
> > information about the location of installed plugins, or a
> > filesystem-based solution is required.
> How did that go? Do you think that it's possible to easily store this
> info in the database?
Unfortunately, it looks like it's not that easy. I ran into a similar problem
as earlier. In order to load data from the database, Gallery::search needs to
be called from GalleryCoreApi::relativeRequireOnce, from which
Gallery::getStorage is called. But getStorage also uses relativeRequireOnce
and we get into an infinite loop that causes the web server to segfault.
This specific case was just one example, and from what I've seen, it may be
very difficult to call _any_ Gallery API function from relativeRequireOnce.
That's why for now I've decided to use a flat file in g2data to store the
plugin locations. I will now start implementing the required changes to core
to support plugins in g2data. If it is later decided that the database can be
used after all, it should not be very hard to refactor the code to implement
> > July 16-19:
> > - Mountaineering in Montenegro :-)
> And how did *that* go? Sounds like a whole lot of fun.. I want to see
> the pictures!
It _was_ a whole lot of fun, but also pretty physically demanding. We climbed
up three peaks of Durmitor, the mountain we were on, including the highest.
We were practically climbing all day and just returning to our apartments for
the night to get some sleep and recover for the next day. I also found out
how it looks and feels to be caught in a hailstorm and a thunderstorm in the
mountains 3+ hours away from the nearest inhabited village :) Here are some
of the pictures I took: http://www.flickr.com/photos/jselesi/sets/618141/.
> > July 24 - Milestone: Core support completed
> > - Do any remaining core work based on review results.
> I'll budget some time to do an extensive code review at this point.
I've also just found out that I mostly won't be at home from July 22-24 (some
family matters). This I did not expect - I will try to do as much of the
weekend's scheduled work by Friday as possible, to be a bit ahead of schedule
so my absence does not impact the rest of it by much. I'll send you the code
for review on Friday so you can have a look at it at the time you planned.
> > July 25-26:
> > - Come up with a PHP-based, self-extracting package specification.
> > - Write user stories for repository tools (index generator and package
> > management) to narrow down the exact features required.
> > - If not done already, discuss and define all possible module variants
> > that can be created.
> > - Write initialization code for repository tools:
> > - Have basic Gallery functionality up and running.
> > - Be able to get a complete list of modules.
> > - Be able to use Gallery APIs.
> This seems like a lot of work for 2 days. I'm guessing that this will
> take you more like 3+ days.
Possibly. I was originally hoping to write all of the user stories and nail
down the exact features that are required sooner than they've been scheduled,
for example on the 24th, but now I don't think I'll be able to do this. Your
other comments on places where you think I'll need more time than I budgeted
all come from the fact that not all details have been defined yet. I'll write
them down as soon as possible, so the entire picture is clear.