|
From: Andreas S. <an...@sa...> - 2006-09-04 19:58:42
|
Jonathan and I were discussing when to have the next developer meeting. It currently seems like it'll have to be sometime next week. Any evening next week, except Tuesday and Thursday, would work for me. It'd bee great if we could have a (preliminary) design for the data and class model after the meeting and to start splitting the work so we know where to start. So the preliminary agenda would be something like: * Data model * Class model * More use cases * Maybe some more GUI discussions? * Who does what Btw, I spoke to a guy at Update the other day. He was a bit interested in Phli and seems to have quite a few good ideas about GUI design. He suggested a few design changes to make the software perform better over slow links, e g modem or ADSL. The changes mainly involved making a more sophisticated server which does the resizing (to allow different thumbnail sizes or low-res images for previews) and caches the results. What do you think about this? Should we just go ahead with the current plans and make sure that backend - frontend separation is good enough to add something like this in the future? Or should we try to implement something like this in the first release? Another thing which I think we forgot to talk about during the last meeting was how to handle photo albums. The most obvious implementation would be to use a tag for an album, but what about order? We could implement an index number in the image<->tag relation, but doing this has a few pitfalls, mainly when listing the images in multiple tags or parent tags. //Andreas |