quote:

---

Originally written by spy.there:

I am sorry for your bad karma and hope, the times change soon for you.

Nevertheless I dare to bother you (or somebody else, who could give me a hint) with a silly question about graphics formation. In Louvre you write that gif is preferred. When I change my jpgs to gifs, a lot of colours are spoiled. So I sent the graphics as jpgs. What are you doing with jpgs?
Is there a special trick to transfer a jpg into gif without loss? I work with Photoshop. Any advice is appreciated.

---

quote:

---

Originally written by spy.there:

I am sorry for your bad karma and hope, the times change soon for you.

Nevertheless I dare to bother you (or somebody else, who could give me a hint) with a silly question about graphics formation. In Louvre you write that gif is preferred. When I change my jpgs to gifs, a lot of colours are spoiled. So I sent the graphics as jpgs. What are you doing with jpgs?
Is there a special trick to transfer a jpg into gif without loss? I work with Photoshop. Any advice is appreciated.

---

quote:

---

Originally written by Silence in Motion:

I mean like this

---

quote:

---

Originally written by Silence in Motion:

I mean like this

---

quote:

---

Originally written by Andrea:

Brett, what format can you get the Alexandria data to me in? It would be useful to have an existing dataset to work on.

---

quote:

---

Originally written by Andrea:

Doing it for one would do it for others very easily.

If I were hypothetically to make this hypothetical database for Blades, speaking in a purely hypothetical manner, what data do you think would be useful to store? Basically what you have at Alexandria?

I've also been thinking that it'd be useful to have a separate table for designers. That way, one would simply have to modify their contact info once and it would change all of their scenario records.

What do you think?

Er, hypothetically.

---

quote:

---

Originally written by Andrea:

It would be feasible to develop a community-serviced scenario database. You'd simply have a password system -- scenario designers sign up for an account; you add a few administrators; other than that, the scenario designers themselves add and modify their scenario entries and upload the appropriate files.

This system would make it so that the only administrative red tape would be that required to manage accounts and keep an eye out for abuse.

Combine this with an Alexandria-style system and you have a searchable scenario database, complete with scores, kept current by those with the most interest in keeping it so.

Scenarios by people who are no longer around in the community could be grandfathered in by the administrators, since there's little chance of the original author needing to modify the record.

All it requires is some scripting, some HTML, and a nice SQL database. And effort. And interest.

I've been planning on implementing such a system for Pyg. It'll be fun.

---

quote:

---

Originally written by Shyguy:

I can't open a .sit file! Don't think any Windows users can. Give me a break!

I give up.

-------------------------------------------------

---