We already have a couple of users working with the hub code. Outsourcing the BYOND software code is definitely something we want to do in the future. I believe that it would be more trouble than it's worth at this point, since so much of the infrastructure is poorly designed and undocumented.
Fantastic! That's the way I like it.
Well, documentation's always better, but it can be fun to jump into the middle of alien code and try to figure it out.
One thing I think I can do without too much hassle is completely modularize the graphics code and allow someone else (probably you :) to update the /icon routines. I'll try to think of other items on the List that might be easily massaged.
Gads, I'd love to have a crack at the /icon type. I think I can vastly expand its functionality even without the format going to 24-bit or any-size yet. (For that matter, it couldn't hurt to update the code to prepare for that, huh?)
As for other easily massaged items on the List, several of them would be my own suggestions for the /list datum: Swap(), Insert(), Cull(), and the & and | and ^ operators.
Fantastic! That's the way I like it.
Well, documentation's always better, but it can be fun to jump into the middle of alien code and try to figure it out.
Gads, I'd love to have a crack at the /icon type. I think I can vastly expand its functionality even without the format going to 24-bit or any-size yet. (For that matter, it couldn't hurt to update the code to prepare for that, huh?)
As for other easily massaged items on the List, several of them would be my own suggestions for the /list datum: Swap(), Insert(), Cull(), and the & and | and ^ operators.
Lummox JR