Recommended Posts

Update:

Even though NFiles actually uploading is being odd, I'm still working on portions. Tonight I started working on the NeoIMG portion some more, and still working on it as I type this.

I'm finding myself writing all new code for NeoIMG, though - so it's taking longer than expected...though not much longer. I mainly have to code a list of signatures, the files they hold, and an option to move your NFiles images over to the NeoIMG system. I have the rest of the code already done, it just needs a little tweaking.

Quickie "Before Bed At 2:30am" Update:

I got a lot more work done in the past two hours. I've made the system copy files from your NFiles folder into the NeoIMG folder (with the ability to mass-copy), delete a signature folder (and all files under it), and strengthen security - though I have one massive hole that could ruin the site right now - you can pretty much mass delete everything on my domain name with the delete command. Obviously will be fixed, but not tonight.

I'm pretty sure I can get a live test going after sleep and work today (actual signature working).

Edit: Can't sleep without the evil mass delete bug fixed. Is fixed now.

How come you are copying them over? Cant you just reference them? Seems like that would waste space/cpu/whatever...

like for example...i have no idea how you are storing the information for files...but...you could...

upload image (lets call it Image.jpg)

image.jpg has 'types' associated with it...

one type is uploaded file people can call on normally... (eg standard)

and you could also choose (maybe a simple checkbox?) if that image should be included in those for your sig...

then when you go to the sig page..

display (allImages in filesThisPersonHas that typeIncludes(forSig))

then you could also have properties stored with each file...like what categories or bins or similar you talked about before it belongs to if it has been set up with the sig thing

so for image.jpg it would have these properties perhaps:

types:

{

standard,

sig

}

sigProperties:

{

sig stuffs go in here..or null if not used as sig image

}

...obviously very much englishized for demonstration...but...just an idea :)

Very first NeoIMG Live Test:

neoimg.jpg

Three different random files. Refresh to hit the random counter again and see another.

Note: It really is random, so it might hit the same one twice, or three times. It doesn't know you've looked at the same one before, and that wouldn't really be random if it did. :p

SkyyPunk: Thanks to you I scrapped over 240 lines of code and wrote NeoIMG from the ground up. :p Took me five hours! I'm glad I did though, as it's much more efficient this way.

As of now, you can add any image to a NeoIMG signature right from the File Manager. There are a few minor bugs still, but I'll fix those another time. I also plan on allowing images to be placed in multiple signatures.

I didn't say it was public yet, just working. :p I want to squish a few more bugs and add a few more security features before I turn it on. It will happen today though. After work.

One thing I want to do before launch is allow images to be used in multiple signatures. Another would be to finish up the "How do I use NeoIMG" page, as well as provite a link for you to use NeoIMG.

The link will be formatted like this:

http://nfiles.nwserver.net/sig.x/username/signame/neoimg.jpg

Though I might change it to this:

http://nfiles.net/sig.x/username/signame/img.jpg

or this:

http://nfiles.net/sig.x/username/signame.jpg

http://nfiles.nwserver.net/sig.x/username/signame.jpg

Probably one of these last two. Shorter is better. :)

Today's Update:

NeoIMG mostly completed - still missing a few things, but it's useable.

In fact, you can use it right now.

To add a file to a signature, open the file preview window for the file you want to add (images only, duh), and enter a signature name into the NeoIMG box.

Once you add an image, you get a new link in the main details box. This will be your link to use for sigs, whatever. Works pretty much like the image view that I made for normal images.

I will say one thing: After coding NeoIMG, I have a new found love for arrays.

I dont know if there is a way to handle this...but...I was uploading an image...it was a lot larger than i thought, so I refreshed the page to stop uploading it...it still shows up as a file i uploaded, the preview screen doesnt like it (just shows a black box), but the image url does work, just showing the partial upload...i dont know if you can tell whether the transfer is complete or not...maybe grab size of file, then compare it to when transfer completes, if not a match, dont actually keep that file...

Right now I'm unsure about the partial upload check, but I fixed the image preview problem.

I tried using PHP's upload array to tell me if it's partial or not, but that just outputs that it's not partial and sends it to your account anyways.

  • 2 weeks later...

Tonight's update:

After putting NFiles on the side for a few weeks, I began working on it again tonight. My primary goal tonight was to start and finish the backup upload mirror (for when NFiles is PMSing and not uploading files) - which I did. The space was kindly donated by Gelob at SpamTheBox.com.

This mirror relies pretty much totally on FTP not going down on either server (mirror and primary NFiles server). It's a lot of code that I probably will remove when I finally open the source.

Which brings me to the end of this update - I have decided to open up the NFiles source (100% of it and any removed code that I can find) to anybody who wants to use it or grab code from it for use in other projects.

For the PHP wizards, you will more than likely notice that I am no guru - I just know how to make A work with B. :) I learned a lot making NFiles, and know enough to optimize older code now - but I'll probably not do that. Too much work for something that already works fast.

  • 1 month later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.