phpix2-devel — Development discussion

Re: [PHPix2-devel] Made a bit of a change.

[Neale P. <ne...@wo...>]

So then, Bryan Kilian <br...@wu...> is all like:
> Okie, I made a bit of a change in the way phpix works. I offloaded the
> images onto a separate script, which deals with resizing and caching.

Good idea!

Re: [PHPix2-devel] Made a bit of a change.

[Neale P. <ne...@wo...>]

Someone's already done that.  They even promised to send the code to me
once, but I never got it.

I think his site had something to do with fishing.  Nice enough guy, he
probably just got too busy and forgot he was going to send me his code.

Or you could just do it yourself, which might be faster than trying to
find the version that's already been done :-)


So then, William Borrelli <boo...@ro...> is all like:
> Sounds good to me. How about someone figuring out how to make PHPix
> into a PHPNuke module. The image galleries that are out there for
> PHPNuke are not nearly as nice as PHPix.

> Bryan Kilian said:
>> Okie, I made a bit of a change in the way phpix works. I
>> offloaded the images onto a separate script, which deals with
>> resizing and caching.
>>=20
>> It's checked into the cvs server, so give it a whirl.
>>=20
>> Thing this means:
>> a) Pages _feel_ faster (even though they aren't necessarily)
>> when we have to do a bunch of conversions. The reason for this
>> is the html renders, and then the pictures get filled in. Before
>> you would wait for all the pictures to convert before anything
>> would render.
>> b) we can move the images out of the webroot.
>> c) because images are not in the webroot, we can do security
>> ourselves, without having to worry about .htaccess files.
>> d) since we can do security ourselves, we can make password
>> protected albums, login ability, and admin stuff (add,delete
>> pictures).
>>=20
>> My next project will be to try get a user login function, once I
>> have that, I'll do an admin interface. Then possibly a user
>> comments section.
>>=20
>> I'll clean up the code a bit more over the next while and add the
>> picture root stuff. (ie, having pictures out of the webroot) I'll
>> leave it so by default it works out of the box.
>>=20
>> Bryan
>>=20
>> perl -e
>> 'map{print(pack(V,exp("21.$_")))}
> (21512211,40167979,2548395575,2745918245)'
>>=20
>> _______________________________________________
>> PHPix2-devel mailing list
>> PHP...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpix2-devel


> ____________________________________________________________________
> Disclaimer: The opinions expressed in this email are not necessarily
> mine, as I've not yet had my medication today.
> =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF


> --------------------------------------------
> This email originated from Booster's Dilemma
> http://boostersdilemma.com/



> _______________________________________________
> PHPix2-devel mailing list
> PHP...@li...
> https://lists.sourceforge.net/lists/listinfo/phpix2-devel

Re: [PHPix2-devel] Made a bit of a change.

[William B. <boo...@ro...>]

Sounds good to me. How about someone figuring out how to make PHPix
into a PHPNuke module. The image galleries that are out there for
PHPNuke are not nearly as nice as PHPix.

Bryan Kilian said:
> Okie, I made a bit of a change in the way phpix works. I
> offloaded the images onto a separate script, which deals with
> resizing and caching.
>
> It's checked into the cvs server, so give it a whirl.
>
> Thing this means:
>  a) Pages _feel_ faster (even though they aren't necessarily)
>  when we have to do a bunch of conversions. The reason for this
>  is the html renders, and then the pictures get filled in. Before
>  you would wait for all the pictures to convert before anything
>  would render.
>  b) we can move the images out of the webroot.
>  c) because images are not in the webroot, we can do security
>  ourselves, without having to worry about .htaccess files.
>  d) since we can do security ourselves, we can make password
>  protected albums, login ability, and admin stuff (add,delete
>  pictures).
>
> My next project will be to try get a user login function, once I
> have that, I'll do an admin interface. Then possibly a user
> comments section.
>
> I'll clean up the code a bit more over the next while and add the
> picture root stuff. (ie, having pictures out of the webroot) I'll
> leave it so by default it works out of the box.
>
> Bryan
>
> perl -e
> 'map{print(pack(V,exp("21.$_")))}
(21512211,40167979,2548395575,2745918245)'
>
> _______________________________________________
> PHPix2-devel mailing list
> PHP...@li...
> https://lists.sourceforge.net/lists/listinfo/phpix2-devel


____________________________________________________________________
Disclaimer: The opinions expressed in this email are not necessarily
mine, as I've not yet had my medication today.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯


--------------------------------------------
This email originated from Booster's Dilemma
http://boostersdilemma.com/

[PHPix2-devel] Made a bit of a change.

[Bryan K. <br...@wu...>]

Okie, I made a bit of a change in the way phpix works. I offloaded the
images onto a separate script, which deals with resizing and caching.

It's checked into the cvs server, so give it a whirl. 

Thing this means:
  a) Pages _feel_ faster (even though they aren't necessarily) when we
  have to do a bunch of conversions. The reason for this is the html
  renders, and then the pictures get filled in. Before you would wait
  for all the pictures to convert before anything would render.
  b) we can move the images out of the webroot.
  c) because images are not in the webroot, we can do security
  ourselves, without having to worry about .htaccess files.
  d) since we can do security ourselves, we can make password protected
  albums, login ability, and admin stuff (add,delete pictures).

My next project will be to try get a user login function, once I have
that, I'll do an admin interface. Then possibly a user comments section.

I'll clean up the code a bit more over the next while and add the
picture root stuff. (ie, having pictures out of the webroot) I'll leave
it so by default it works out of the box.

Bryan

perl -e 'map{print(pack(V,exp("21.$_")))}(21512211,40167979,2548395575,2745918245)'