Help With Plating #11

Don,

Sounds fair. Are we able to upload images ourselves and enter comments now?

OK. I'm going to start pecking away at the basic data entry. Starting with plate 0, I'll add recut info for each position, if any.

Oops, I'm unable to make any changes to the page.

Don, would I be able to get editing access?

Guys,
Yes, you will need a log in name and password, please contact me and I will get it set up.
Don

Thanks Don. Email sent.

I will use the numbers as I add recut information. They can be removed later if not needed.

I loaded in all the recut varieties for plate 0, both panes.

Could a user search for a recut variety using key words? For example typing, 'two lines triangle' would then highlight any position on that pane, with recuts that include those words. ie, two lines recut upper right triangle.

I am not sure if Don is going to put in a pull down list for the plates but a pull down list with the recutting variety number would be better than guessing what words to search for.

Stampcrow, I just looked at what you did. That was a lot of work. I was able to search by recutting variety # so the pull down menu might not be necessary. I might even start liking this thing...

Left pane of plate 1e varieties are loaded in. I don't have any plated 1e left side stamps to upload. I did upload my 94R1e. I also uploaded my 15L0. It's not 1200dpi, so it's just a place filler for now. Although it does show the variety #27 recut clearly.

I can add a drop down box but the issue becomes adding new entries for it. Drop down boxes have to be populated in some way, this is usually done via hard coding or via another lookup table. The challenge with a tool like this is that we have multiple people entering information. So while I can implement a drop down every time stampcrow adds some new recut data I would have to go back and add the same thing to the drop down source or table. So drop down are best once the items in it are well defined and do not have to constantly be updated.

Note: I have implemented another 'Hi Res Image' column for holding a second image. It also has an associated second field for storing the generate thumb nail image. (When we upload the Hi Res image, the code automatically generates a 100 pixel high thumbnail image and then stores it in another folder. So for every Hi Res field we add we need a second filed in the database to hold the thumb data.) At some point storage space and performance issues will limit the number of Hi Res images we will want to deal with.

I have also added access to the archive via Stamp Smarter menu as shown below…


Don

Awesome job guys. I like it!

Sinclair, Good to see you in this discussion.

I can't use the e-mail function within this community as of yet, but I'll be there soon. I still consider myself a novice at this, so not looking for access to this database. However, feel free to use any stamp I've uploaded on this site for the database--even if only a placeholder.

Art

Just realized that this was my 49th post.

OK. both panes of plate 1e have varieties listed.

Thanks for all the effort stampcrow. I have added support for the third hi res image and related thumbnail (for each position). I also added a query on the opening page that always shows how many images are currently in entire database (currently 64). Also made some formatting and layout changes to primary page.
Don

Don,

It would be good to have a return key result in a new line for the text in the comments fields so the individual comments can be separated.

In the 40R1L record, I entered a recutting comment in the Comments field rather than the Recutting Info field because I didn't like it running together (even after two return keys).

Classic,
The issue is that the edit page used a plain text editor; this submitted vanilla ASCI text to the database.

I have changed the page to support an HTML editor (just like what this forum uses). This support the functionality that you mentioned, adding cartridge returns. It also support many other features such as fonts, colors, links, etc.

This is a bit of a double edge sword. The database will now hold HTML code instead of plain text. This doesn't cause me heartburn but it may be problematic for others that follow us in the future. (They may try to display this field as plain text instead of as HTML code.)

But give it a try and see if you like it better.
Thanks,
Don