Menu
▾
▴
ids-devel — IDS developers use this list
You can subscribe to this list here.
| 2001 |
Jan
(2) |
Feb
(48) |
Mar
(16) |
Apr
(14) |
May
(42) |
Jun
(36) |
Jul
(57) |
Aug
(13) |
Sep
(2) |
Oct
(23) |
Nov
(17) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(5) |
Feb
|
Mar
(10) |
Apr
(1) |
May
(6) |
Jun
|
Jul
(2) |
Aug
(1) |
Sep
(12) |
Oct
(26) |
Nov
(11) |
Dec
(37) |
| 2003 |
Jan
(11) |
Feb
(27) |
Mar
(5) |
Apr
(21) |
May
(11) |
Jun
(38) |
Jul
(8) |
Aug
(29) |
Sep
(2) |
Oct
|
Nov
(7) |
Dec
(5) |
| 2004 |
Jan
(5) |
Feb
(2) |
Mar
(19) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
(1) |
Dec
|
| 2005 |
Jan
|
Feb
(3) |
Mar
(3) |
Apr
(4) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(8) |
|
From: <lj...@ma...> - 2001-04-09 08:19:39
|
> You can see examples at > http://arwen.hn.org/~john/ids-0.7/localizations/ . Does anyone know if the > US English file would suffice for UK English? I don't see anything obvious > like "colour." :) I have had a look at the US-English and none of it seems offensive to those of us who prefer UK-English. The only localization-related issue is the reference to Shutterfly.com which is largely irrelevant to people outside North America. I don't know of a UK or European equivalent. - Lewis |
|
From: John M. <mo...@mu...> - 2001-04-06 03:20:05
|
Hello. Here's what I've been working on: http://arwen.hn.org/~john/ids-0.7/ New features so far: * added support for internationalization (i18n! hehe) * produces XHTML 1.0 compliant code http://www.w3.org/TR/xhtml1/ * added support for GUI themes * incorporated Anthony's comment filtering patch- great idea! So far, we have i18n support for Deutsch, US English, and Nederlands. If you or someone you know would like to contribute a language plug-in, please let me know. You can see examples at http://arwen.hn.org/~john/ids-0.7/localizations/ . Does anyone know if the US English file would suffice for UK English? I don't see anything obvious like "colour." :) The same goes for themes- http://arwen.hn.org/~john/ids-0.7/themes/ . If you don't want to worry about XHTML compliance, that's OK. I can easily convert files with HTML Tidy. One subtle change- album icons are now PNG's. I chose to do this because PNG offers transparency. The background color/image can change in themes, so I didn't want the corners of album images to always be white. Some older browsers can't display PNG's and some modern browsers don't display transparency, but I'd rather that it look good for some users instead of looking bad for everyone. We can probably use the updater script to update old JPEG album icons to PNG. If anyone is planning to submit patches, the coming weeks would be a good time. I'm going to focus on making more themes, so the code should stay pretty stable. http://arwen.hn.org/~john/ids-0.7a5.tar.gz John |
|
From: Anthony A. D. T. <aa...@ve...> - 2001-04-05 07:32:49
|
Here are patches to 0.6a that implement an embedded comment filter -- a configurable regexp to be removed from embedded comments. This is so that browsers don't have to see strings like CREATOR: XV Version 3.10a Rev: 12/29/94 Quality = 60, Smoothing = 0 as part of the embedded comments as displayed on the image page. I've factored out the Canon/Sony camera-specific strings that were previously hardcoded in the code and made them part of the default value for embeddedFilter. In the future I may extend this into a general-purpose modifier for embedded comments, allowing one to specify a sort of template, printf-style. Please forgive me if the patches are malformed. I haven't done this in a while. |
|
From: Craig <9j...@ql...> - 2001-04-01 00:37:02
|
Hi, I understand that individual directories can be passworded by putting .htaccess files in them, but that only puts a password on that directory, all the images except for the original are stored in the image-cache directory. if I had pictures that i didn't want everyone to see i would feel more comfortable if the images that had been resized were stored in the same password protected directory as the original. That way people couldn't access the picture even if they knew the URL for that cached image. I haven't looked at version 6.0 yet, so this may have already been fixed or I could be completely wrong and this isn't an issue. Craig McFetridge |
|
From: John M. <mo...@mu...> - 2001-03-27 22:50:14
|
I've released a new IDS 0.6a distribution. This fixes a corrupt stylesheet and incorporates Caleb's patch. http://ids.sourceforge.net/ John |
|
From: asja <as...@se...> - 2001-03-27 14:48:36
|
On Mon, Mar 26, 2001 at 06:49:53PM -0500, Caleb Epstein wrote:
> Not sure if anyone else has been bitten by this, or if the
> latest code handles it, but I just ran nito an issue w/IDS
> when run wiht PerlMagick 5.30 (the debian unstable distro is
> using this now).
I ran into trouble three days ago installing the latest perlmagick
which comes with debian/unstable. It was 5.30-5.
It was not the first time that perlmagick failed to work in my
system right after an upgrade, but this time i noticed something
different:
>
> In the function getImageDimensions() in idsShared.pm, the
> Image::Magick::Ping() method is expected to return a
> comma-delimited dtring. It appears in 5.30 that it now
> returns an array in array context and only the image FORMAT
> when called in scalar context. The fix is to re-code the
> function as follows:
>
> sub getImageDimensions {
> my $imageName = shift(@_);
> my $preview = new Image::Magick;
> my ($width, $height, $size, $format) = $preview->Ping ($imageName);
> if ($width =~ /,/) {
> ($width, $height, $size, $format) = split /,/, $width;
> }
> return ($width, $height);
> }
>
> This ought to be backwardly compatible with 5.29's behavior.
Yes, this works and it is an elegant solution, but if i downgrade the
perlmagick 5.30-5 back to 5.30-2 (the only official .deb i managed to find
searching around...), the ids' 0.6 original code works perfectly again,
without any modification!
Note that on the perlmagick's page they still show how to parse the Ping()
method the old fashion...
So it could be a build-specific problem, not a version-specific one...
However this is really a boring issue: BTW it's the only trouble i got with
debian/unstable in the last year!
Best Regards
.asja
|
|
From: Caleb E. <ca...@bk...> - 2001-03-26 23:50:03
|
On Fri, Mar 23, 2001 at 07:08:31PM -0500, John Moose wrote: > Hello. I just released the final version of IDS 0.6. > http://ids.sourceforge.net/ Thanks to Eric Case for the website > redesign. John Not sure if anyone else has been bitten by this, or if the latest code handles it, but I just ran nito an issue w/IDS when run wiht PerlMagick 5.30 (the debian unstable distro is using this now). In the function getImageDimensions() in idsShared.pm, the Image::Magick::Ping() method is expected to return a comma-delimited dtring. It appears in 5.30 that it now returns an array in array context and only the image FORMAT when called in scalar context. The fix is to re-code the function as follows: sub getImageDimensions { my $imageName = shift(@_); my $preview = new Image::Magick; my ($width, $height, $size, $format) = $preview->Ping ($imageName); if ($width =~ /,/) { ($width, $height, $size, $format) = split /,/, $width; } return ($width, $height); } This ought to be backwardly compatible with 5.29's behavior. -- cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg. |
|
From: John M. <mo...@mu...> - 2001-03-24 00:08:41
|
Hello. I just released the final version of IDS 0.6. http://ids.sourceforge.net/ Thanks to Eric Case for the website redesign. John |
|
From: John M. <mo...@mu...> - 2001-03-17 22:48:06
|
Hello. IDS 0.6b1 is now available: http://arwen.hn.org/~john/ Please let me know if you find any bugs. I'm aiming for a public release in the next week. I'm pleased to report that IDS works under Mac OS X with no modifications. New in this pre-release: - Oren's patch to fix the album icon function - An upgrader script to convert from IDS' old file structure to the new layout in 0.6 (thanks, Clayton). This script still needs more of a user interface, but it worked well enough to convert my primary IDS site to 0.6b1: http://toasty.mcs.muohio.edu/~moosejc/photoalbum/ - The remove image, rename image, and rename album functions in the admin CGI now work. They also will rename or delete the appropriate files in the album-data and image-cache directories. - The pages produced by IDS are HTML 4.01 compliant according to http://validator.w3.org/ - Bug-fixes: * the commentviewer script now displays multi-line comments correctly * albums with ampersands in their names caused odd behavior with the album icon functions * I had to disable "use strict refs" in the Image::Info portion of "generateImage" (index.cgi). Otherwise, some images would produce an error: "Can't use string ("x") as an ARRAY ref while 'strict refs'." I'd appreciate it if someone smarter than me could fix the code such that I didn't have to do that. Thanks, John |
|
From: Caleb E. <ca...@bk...> - 2001-03-12 17:07:03
|
On Sat, Mar 10, 2001 at 09:56:41PM -0500, John Moose wrote: > IDS 0.6a10 is now available: http://arwen.hn.org/~john/ The code > cleanup continues... All IDS scripts are now running under "use > strict." Most of them will also run with taint-checking turned > on. I'm curious to see if this will work under mod_perl. Attention IDS mission control: we HAVE mod_perl! Repeat: we HAVE mod_perl! It works! Great job! -- cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg. |
|
From: John M. <mo...@mu...> - 2001-03-11 02:54:51
|
IDS 0.6a10 is now available: http://arwen.hn.org/~john/ The code cleanup continues... All IDS scripts are now running under "use strict." Most of them will also run with taint-checking turned on. I'm curious to see if this will work under mod_perl. I fixed a bug that was preventing the search functions from finding the comment files. I fixed a bug that was causing the generatePrevNext function to create bogus directories in the image-cache. I added the ability to specify the max number of comments to be displayed in the commentviewer CGI to the prefs. In the past, users of the admin CGI have experienced unexpected results if they reloaded a page after performing certain actions. For example, if someone rotated an image, their browser would then be pointed at: /ids/admin/index.cgi?mode=rotateimage°rees=90&itemtorotate=test/test.jpg If they reloaded the page, the image would be rotated again. The admin CGI now uses the HTTP "Location:" header to redirect them to the correct page. In the case above, this would be: /ids/admin/index.cgi?mode=editimage&image=test/test.jpg They can now hit reload as often as they want, and everything will behave normally. Please let me know if you find any bugs. John |
|
From: John M. <mo...@mu...> - 2001-03-09 01:21:17
|
IDS 0.6a9 is now available: http://arwen.hn.org/~john/ This one includes some changes to the functions that generate album thumbnail icons. First, I fixed the bug reported by Caleb. I then replaced the simple one-level deep image searching function with a File::Find function that will find all of the images in every subdirectory and choose one randomly. (I don't notice any speed difference.) This eliminates the need to manually create icons for albums that contain only other albums. The album's icon is now visible on every album's page in the admin CGI, as is a button that will randomly pick another image for that icon. Known bug (since a8): When a user's preferred sort method is "date" and they open an album for the first time, the album's contents all show up with a date in 1969. Any ideas? I suspect that it has something to do with when the fillDateHash function is called. The mod_perl install was too much for me. Caleb, let me know how I can help with the code cleanup. I did notice that IDS now runs under "use strict;" rather than "use strict qw(vars);" and the index script can run with taint mode turned on. John |
|
From: John M. <mo...@mu...> - 2001-03-08 12:52:03
|
I'd love it if we could get IDS to run under mod_perl. I'll see what I can do about those annoying global variables tonight. John On Wednesday, March 7, 2001, at 06:52 PM, Caleb Epstein wrote: > On Wed, Mar 07, 2001 at 05:11:59PM -0500, Caleb Epstein wrote: > >> >> I'm playing with runnign ids under mod_perl instead of as an >> external CGI. The following changes to index.cgi and >> admin/index.cgi seem to make it work properly (the >> admin/idnex.cgi was causing errors, but I made the same change >> to the top level index.cgi just in case): >> >> Change the line whcih says: >> >> use idsShared; >> >> to read >> >> use idsShared qw(/^.*/); >> >> This causes all of the EXPORT_OK symbols to be imported from >> idsShared, otherwise they end up in a different namespace and >> when they are used in the CGI scripts, we die(). > > After further examination, this doesn't really work. I still > get errors like this: > > Global symbol "$albumtodisplay" requires explicit package name at > /var/www/photo/admin/index.cgi line 601. > Global symbol "$description" requires explicit package name at > /var/www/photo/admin/index.cgi line 604. > Global symbol "$adminContent" requires explicit package name at > /var/www/photo/admin/index.cgi line 618. > Global symbol "$idscgi" requires explicit package name at > /var/www/photo/admin/index.cgi line 625. > > Mod_perl is a real bear w/non-OO code. > > -- > cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust > Bunny Mfg. |
|
From: Caleb E. <ca...@bk...> - 2001-03-07 23:51:18
|
On Wed, Mar 07, 2001 at 05:11:59PM -0500, Caleb Epstein wrote: > > I'm playing with runnign ids under mod_perl instead of as an > external CGI. The following changes to index.cgi and > admin/index.cgi seem to make it work properly (the > admin/idnex.cgi was causing errors, but I made the same change > to the top level index.cgi just in case): > > Change the line whcih says: > > use idsShared; > > to read > > use idsShared qw(/^.*/); > > This causes all of the EXPORT_OK symbols to be imported from > idsShared, otherwise they end up in a different namespace and > when they are used in the CGI scripts, we die(). After further examination, this doesn't really work. I still get errors like this: Global symbol "$albumtodisplay" requires explicit package name at /var/www/photo/admin/index.cgi line 601. Global symbol "$description" requires explicit package name at /var/www/photo/admin/index.cgi line 604. Global symbol "$adminContent" requires explicit package name at /var/www/photo/admin/index.cgi line 618. Global symbol "$idscgi" requires explicit package name at /var/www/photo/admin/index.cgi line 625. Mod_perl is a real bear w/non-OO code. -- cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg. |
|
From: Caleb E. <ca...@bk...> - 2001-03-07 22:10:22
|
I'm playing with runnign ids under mod_perl instead of as an external CGI. The following changes to index.cgi and admin/index.cgi seem to make it work properly (the admin/idnex.cgi was causing errors, but I made the same change to the top level index.cgi just in case): Change the line whcih says: use idsShared; to read use idsShared qw(/^.*/); This causes all of the EXPORT_OK symbols to be imported from idsShared, otherwise they end up in a different namespace and when they are used in the CGI scripts, we die(). -- cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg. |
|
From: Caleb E. <ca...@bk...> - 2001-03-07 20:50:21
|
On Tue, Mar 06, 2001 at 10:12:51PM -0500, John Moose wrote: > Hi. IDS 0.6a8 is now available: http://arwen.hn.org/~john/ Minor bug report. If you have a subdirectory in your albums hierarchy which itself contains no images (e.g. it contains only other subdirs, which contain the images) ids dies as a result of the code in generateAlbumPreview(). This used to work (you'd get a crosshatched gray image as the album preview instead of an error message). -- cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg. |
|
From: John M. <mo...@mu...> - 2001-03-07 20:22:05
|
It would appear that I forgot to send out an e-mail. How embarrassing... John On Wednesday, March 7, 2001, at 03:17 PM, Randy Maas wrote: > I've been out of it for the last few days (week?). Did I miss an email > about 0.6a7? > >> Is anyone else working on something they'd like to have included in the >> 0.6 release? > > I probably won't have time to work on anything. Sorry, > > All the best, > Randy > > > _______________________________________________ > IDS-devel mailing list > IDS...@li... > http://lists.sourceforge.net/lists/listinfo/ids-devel |
|
From: Randy M. <ra...@ac...> - 2001-03-07 20:13:22
|
I've been out of it for the last few days (week?). Did I miss an email about 0.6a7? > Is anyone else working on something they'd like to have included in the > 0.6 release? I probably won't have time to work on anything. Sorry, All the best, Randy |
|
From: John M. <mo...@mu...> - 2001-03-07 03:32:46
|
Hi. IDS 0.6a8 is now available: http://arwen.hn.org/~john/ New in this release: - I abstracted the sort functionality, which makes it really easy to add new sort methods. Users can now sort by name, date, size, or "intelligent sort" (Randy's sort function). The sort method is now invoked properly for the previous and next image links on the image pages. The user's preferred sort method is saved in a cookie. The site's admin can set a default sort method in the prefs. - I moved the preferences-editing functions out of the admin CGI and into their own CGI. At the same time, I divided the prefs page into 4 categories: site, album, image, and comments. - I fixed a bug that caused a custom album icon to be overwritten whenever the album was viewed with the admin CGI. - The site's admin can disable the display of EXIF tags or embedded JPEG comments on image pages. This can save time, preventing a load of Image::Magick and/or Image::Info. I look forward to your comments. Is anyone else working on something they'd like to have included in the 0.6 release? I'm planning on finishing up in the next couple of weeks. John |
|
From: thinc <id...@pu...> - 2001-03-01 02:41:31
|
another feature would be the ability to upload other file types (other that= gif or jpg) and have them converted ---tom *********** REPLY SEPARATOR *********** On 2/28/2001 at 3:39 PM Patrick Devine wrote: >On Wed, 28 Feb 2001, Daryl Smith wrote: > >> Depends on what you feel the goal of IDS is. I think >> it is to put your pictures on the web for others to view. >> I want others to view my pictures. > >After reading John's email, I think he's pretty much on track. The gamma >correction and cropping features would be nice and not impossible to >implement (and could result in some better looking pictures), but the >features which give a site sticky-ness are probably what are going to >get people to keep coming back. > >One thought which I started tossing around was adding types of media (like >PDF's or PostScript files) instead of just jpegs which could be >thumbnailed and be presented in a similiar fashion. That could end up= being a >really useful tool for collaborative projects across the net, but I'm not >sure if it's the right direction for ids.. > >--Patrick. > > > >_______________________________________________ >IDS-devel mailing list >IDS...@li... >http://lists.sourceforge.net/lists/listinfo/ids-devel |
|
From: Patrick D. <pa...@va...> - 2001-02-28 22:13:36
|
On Wed, 28 Feb 2001, Daryl Smith wrote: > Depends on what you feel the goal of IDS is. I think > it is to put your pictures on the web for others to view. > I want others to view my pictures. After reading John's email, I think he's pretty much on track. The gamma correction and cropping features would be nice and not impossible to implement (and could result in some better looking pictures), but the features which give a site sticky-ness are probably what are going to get people to keep coming back. One thought which I started tossing around was adding types of media (like PDF's or PostScript files) instead of just jpegs which could be thumbnailed and be presented in a similiar fashion. That could end up being a really useful tool for collaborative projects across the net, but I'm not sure if it's the right direction for ids.. --Patrick. |
|
From: Randy M. <ra...@ac...> - 2001-02-28 20:24:06
|
> Does anyone have any suggextions on implementing image and album > hitcounters? You could try having the cgi script do that directly. A be more complex method would be to read the server logs. Kinda like: total the hits since a certain date, add it to your counter, and display the results. Are you interested in have the counters displayed on the pages themselves, or just in the administration section (eg "under statistics"?), possibly via a simpler cgi script. I'd like to see it with the later. All good things, Randy |
|
From: Daryl S. <dw...@mi...> - 2001-02-28 19:19:51
|
Depends on what you feel the goal of IDS is. I think it is to put your pictures on the web for others to view. I want others to view my pictures. Perhaps we should focus on features that make the viewing experience the best. Of course certain admin features are desireable... but if I can get more people to enjoy viewing the pictures, I will manually handle some of the admin tasks.... dressing them up and cropping them. As far as picture color correction... I have found Photoshop's Ctrl-Shft-L feature to work 98% of the time. Snow pictures... gray to white, dark to bright. The "Normalize" feature of the Gimp and ImageMagick do this pretty well too. It would be cake to throw the ImageMagick normalize into the admin page. Maybe a few of the other auto level features. But should it be part of the IDS admin section? Daryl Patrick Devine wrote: > > On Wed, 28 Feb 2001, Caleb Epstein wrote: > > > On Tue, Feb 27, 2001 at 09:48:12PM -0500, John Moose wrote: > > > > > Does anyone have any suggextions on implementing image and album > > > hitcounters? I'm planning to work on that next. > > > > I can't think of anything more useless than hit counters on > > web pages. Why would anyone want these? > > Well, it is nice to see usage stats on the site, but this can be > accomplished with other packages. Page counters themselves are pretty > tacky though. I thought those went out of style in the 90's.. (: > > > Personally, I'd like to see some additional ImageMagick > > functionality available from the admin front end, specifically > > being able to brighten or darken photos (I guess this is > > changing the gamma), cropping (I suspect this will be hard to > > implement -- how do you indicate the crop marks?) and maybe > > more. > > Gamma correction would be very nice. I have a problem where some of my > PowerShot 10 photos look fine on my monitor at work, but terrible on my > monitor at home (too dark). Cropping wouldn't actually be all that > difficult either, you just need to put the image into an image map in the > cgi form, and track where a person clicks on the image (potentially even > drawing a box on the image with the two points). > > --Patrick. |
|
From: Daryl S. <dw...@mi...> - 2001-02-28 18:31:31
|
I really am interested in the hit count to see what photos are popular & building a gallery off that. I think it might be useful to have the "popular gallery" option of containing X number of the most popular photos from each album. When they click on one of the popular images, in addition to the normal layout, there could be a link to take them to the album index page containing the popular photo (photo subjects tend to be grouped together). That way if your site contains hundreds of photos, people can find the good ones and be "lured" into viewing more. Viewers are always curious what other people find interesting. Looking at my apache stats, I have seen people come to my site, start viewing the first album index and then shortly leave (without having viewed the best pictures buried in another album.) John Moose wrote: > > Specifically, I'm interested in using the data generated by the hitcounters > to create a gallery containing the most popular images on a site. IDS' most > popular features have been those that build a sense of community- the guest > comments, for example. > > John > > on 2/28/01 12:39 PM, Caleb Epstein at ca...@bk... wrote: > > > On Tue, Feb 27, 2001 at 09:48:12PM -0500, John Moose wrote: > > > >> Does anyone have any suggextions on implementing image and album > >> hitcounters? I'm planning to work on that next. > > > > I can't think of anything more useless than hit counters on > > web pages. Why would anyone want these? > > > > Personally, I'd like to see some additional ImageMagick > > functionality available from the admin front end, specifically > > being able to brighten or darken photos (I guess this is > > changing the gamma), cropping (I suspect this will be hard to > > implement -- how do you indicate the crop marks?) and maybe > > more. > > _______________________________________________ > IDS-devel mailing list > IDS...@li... > http://lists.sourceforge.net/lists/listinfo/ids-devel |
|
From: Patrick D. <pa...@va...> - 2001-02-28 18:14:17
|
On Wed, 28 Feb 2001, Caleb Epstein wrote: > On Tue, Feb 27, 2001 at 09:48:12PM -0500, John Moose wrote: > > > Does anyone have any suggextions on implementing image and album > > hitcounters? I'm planning to work on that next. > > I can't think of anything more useless than hit counters on > web pages. Why would anyone want these? Well, it is nice to see usage stats on the site, but this can be accomplished with other packages. Page counters themselves are pretty tacky though. I thought those went out of style in the 90's.. (: > Personally, I'd like to see some additional ImageMagick > functionality available from the admin front end, specifically > being able to brighten or darken photos (I guess this is > changing the gamma), cropping (I suspect this will be hard to > implement -- how do you indicate the crop marks?) and maybe > more. Gamma correction would be very nice. I have a problem where some of my PowerShot 10 photos look fine on my monitor at work, but terrible on my monitor at home (too dark). Cropping wouldn't actually be all that difficult either, you just need to put the image into an image map in the cgi form, and track where a person clicks on the image (potentially even drawing a box on the image with the two points). --Patrick. |
7 messages has been excluded from this view by a project administrator.
