News:

Bored?  Looking to kill some time?  Want to chat with other SMF users?  Join us in IRC chat or Discord

Main Menu

Adding a new CSS file instead of editing an existing CSS file - SMF 2.0

Started by ElectricSquid, October 28, 2009, 01:08:53 PM

Previous topic - Next topic

sangwe11

Quote from: Arantor on November 23, 2009, 01:29:04 PM
That would be telling... :P

Let's just say that when it's done it'll be in a class of its own, and if it does get approved (which I'm slightly hesitant about right now!) it'll be done by bending a rule or two.

Now surely thats not allowed :D

You may be on the Customizer Team, but don't think you can go breaking the rules ! ;D

Arantor

OK, here's a hint.

The package I'm working on uses AJAX to callback to the forum. But for that, SSI.php is way too expensive to run any more than 'occasionally', so I wanted to use the SMF API file (see Download/Tools) but it isn't ready for 2.0.

So yesterday I sat and ported it to 2.0, including adding PostgreSQL support to it as well. Depending on the testing and feedback I think it's safe to use *that* since it's as close to an official lightweight SSI.php as I can get without breaching the coding guidelines, since it is multi backend the way I coded it.

The one thing that worries me is that it sets a precedent for not using $smcFunc, which also does string cleaning - while my version of SMF API doesn't. But (personally) IMO that's no different to modding on 1.1 where mod authors have to do their own string cleaning anyway.
Holder of controversial views, all of which my own.


sangwe11

Quote from: Arantor on November 23, 2009, 01:49:03 PM
OK, here's a hint.

The package I'm working on uses AJAX to callback to the forum. But for that, SSI.php is way too expensive to run any more than 'occasionally', so I wanted to use the SMF API file (see Download/Tools) but it isn't ready for 2.0.

So yesterday I sat and ported it to 2.0, including adding PostgreSQL support to it as well. Depending on the testing and feedback I think it's safe to use *that* since it's as close to an official lightweight SSI.php as I can get without breaching the coding guidelines, since it is multi backend the way I coded it.

The one thing that worries me is that it sets a precedent for not using $smcFunc, which also does string cleaning - while my version of SMF API doesn't. But (personally) IMO that's no different to modding on 1.1 where mod authors have to do their own string cleaning anyway.

Ahh I see ..

Well good luck, and I hope it passes!

Arantor

Well, the API is incomplete; it only has two of the three backends, and it caused a stir because of how it does things. But we'll wait and see. Even if it doesn't, I have the mod for my own use and the API for my larger project.
Holder of controversial views, all of which my own.


sangwe11

Quote from: Arantor on November 23, 2009, 02:07:16 PM
Well, the API is incomplete; it only has two of the three backends, and it caused a stir because of how it does things. But we'll wait and see. Even if it doesn't, I have the mod for my own use and the API for my larger project.

Well I don't quite know what it will be used for, but if it would be any use to me, even if it doesn't pass, your still allowed to give the source away right ?

Arantor

I can but I'm not happy about doing so yet. I'm reasonably happy with how the MySQL stuff works, but PostgreSQL amounts to 'untested'.

PLUS, it's much much easier to have vulnerabilities here, because it is little more than raw mysql_query and pg_query statements.
Holder of controversial views, all of which my own.


sangwe11

Quote from: Arantor on November 23, 2009, 02:12:52 PM
I can but I'm not happy about doing so yet. I'm reasonably happy with how the MySQL stuff works, but PostgreSQL amounts to 'untested'.

PLUS, it's much much easier to have vulnerabilities here, because it is little more than raw mysql_query and pg_query statements.

Thats fine. I don't need it right now (I don't even know what it does!) I was just checking if it was still ok to give it to people if it failed.

Arantor

SMF API is like an uber-lite version of SSI, but geared less to displaying content and more to integrating the code elsewhere.

Gives you the ability to authenticate a user, a function for creating a new user (without manually worrying about the DB structure) manually create the cookie, that kind of thing.
Holder of controversial views, all of which my own.


sangwe11

Quote from: Arantor on November 23, 2009, 02:20:25 PM
SMF API is like an uber-lite version of SSI, but geared less to displaying content and more to integrating the code elsewhere.

Gives you the ability to authenticate a user, a function for creating a new user (without manually worrying about the DB structure) manually create the cookie, that kind of thing.

Ahh I see.

I can see some uses in that, for a stand alone project I am making.

Advertisement: