Scratch

  Well, basically, it's online project hosting. There's a online section for our project. Certain people login and can retrieve the files, thus, able to see it. Then you can make changes (only certain people) and commit the updated code back to the SVN.

So just remember to update your local copy every time before you make changes, and try not to make changes at the same time to avoid conflicts. 

Read up on it. It's really useful. 


And what will this project be officially called?

SULI (Scratch Updating Links/Images) sounds good.
Or maybe SAFFS (Scratch API For Forum Signatures)?


I believe Google Code is the best SVN host, but I don't think you have a google account, do we have to work that out. And LS97 too. 

Last edited by fg123 (2012-06-24 14:44:38)

But this won't exactly be the whole API, just the dynamic signature part.

dynsig? That sound's weird. Scratch Updating Signature Data Platform?

SusDap?

Ah! I see, so this topic is for the whole API, which currently is just images and links. The SULI won't really be the whole project's name. Just part of it. So perhaps this would be called the Scratch Forum API.

I'm starting on the site graphics now. I thought I'd try out the Scratch 2.0 graphics since that would link the API nicely to Scratch.

http://www.api2.comeze.com/

Does someone want to add "API" or something to this image:
http://alpha.scratch.mit.edu/scratchr2/ … ogo_sm.png? (without losing the transparency!!!)

Last edited by sparks (2012-06-25 04:53:26)

I've also been thinking about names, and found a catchy "Dynapics", but that doesn't really fit in with the full purpose of the project. Dynalinks, DynaData...

As for the SVN issue, if you all don't mind, I would much rather use just one testing server for all code, since I am lucky enough to have Dreamweaver CS6 with integrated automatic FTP.

So, what is fg going to work on?

TRIPLE POSTSPLOSION!

Hehe. Ah. Sorry to hear you have a cold - and just before your holiday too!

I use fireFTP and tbh I'm fine with not working with an SVN for this project, I don't think the number or members merits its use.

I've tried dreamweaver, I didn't like it all that much, I'm a pure text programmer at heart. Notepad++ is my baby 

I was looking into latin words for things that the project does in the hope that there would be a cool name for it. The only one that seemed cool was "API Novum" which means new or modern.

For now, How about just putting API? I was imagining three coloured dots in the bottom of the logo.

Scratch
       (a)(p)(i)

Overlapping slightly.

I'm having trouble getting the navigation text to stay in the box.

Last edited by sparks (2012-06-25 07:59:18)

sparks wrote:

What aspect of the api isn't/won't be images or links?

Oh, right.    I didn't think of that.
(Dyndat.)

LS97 wrote:

fg123 wrote:

LS97 wrote:

Well, having a cookie with a username is not validation enough for the obvious reason that it can be changed way too easily, so I hope you don't mean that 

However a hashed cookie of username+password+secrethashphrase+maybeIPaddress is undiscoverable and inimitable, therefore ultra secure! 

Now, if you take that chain and MD5 it, it will enforce the security. 

Maybe you missed it, but I did say "hashed"... 

Missed that too. I was tired yesterday xD

sparks wrote:

TRIPLE POSTSPLOSION!

Hehe. Ah. Sorry to hear you have a cold - and just before your holiday too!

I use fireFTP and tbh I'm fine with not working with an SVN for this project, I don't think the number or members merits its use.

I've tried dreamweaver, I didn't like it all that much, I'm a pure text programmer at heart. Notepad++ is my baby 

I was looking into latin words for things that the project does in the hope that there would be a cool name for it. The only one that seemed cool was "API Novum" which means new or modern.

If we don't use SVN, we'll end up having to redownload the whole site every time we want to update...

fg123 wrote:

If we don't use SVN, we'll end up having to redownload the whole site every time we want to update...

No... you can keep a cache of the files on your computer if you like, but all you have it do really is download the single file you need to edit before you change it, and then re-upload it once you're done!

fg123 wrote:

Ah, that's another way to do it. I'm just used to using SVN to develop projects. 

Well, there's always a first time to change that 
I think we're sticking to FTP then, right? All this discussion confuzzled me

Updated the logo, is it OK? I followed what sparks asked for...

See, with SVN it would be much easier. But whatever. 

I'll do some updates now.