search

vampiricwulf / tanoshiine

Real-time imageboard in node v14.5.0 and redis
MIT License
5 stars 1 forks source link

Feature Request: Area to Request Features and Submit Bugs with Cache #9

Closed seastones closed 9 years ago

seastones commented 9 years ago

Ideally a box next to the Identity and Email boxes that will submit feature requests and bug reports into a sort of cache accessible to mods and admins which can then be further pushed here to Github. The former so people don't have to log an account, the latter so it can't be spammed like hell.

seastones commented 9 years ago

A good idea would be to have them taggable as feature requests or bug reports as well...

seastones commented 9 years ago

It also might be a neat idea to make it visible to the public such that others could comment on or vote on things as well. New ideas and a bit of communal effort.

vampiricwulf commented 9 years ago

2307115dffb16a686335f4e03af67bc245cbd520 Part way there, could use help on the saving from spam part. @bakape

bakape commented 9 years ago

Recaptcha. Take a look at report/*. Although, if you are also going to use Backbone.js, it will need to be loaded as a View on standard index pages.

vampiricwulf commented 9 years ago

Although, if you are also going to use Backbone.js, it will need to be loaded as a View on standard index pages.

I don't understand Backbone.js enough to know what you mean by that.

bakape commented 9 years ago

Eh, you could learn a bit of Backbone or find a generic recaptcha guide and read up on recaptcha-npm.

vampiricwulf commented 9 years ago

Do I need to use Backbone? I made this with normal html and formidable. Wouldn't switching to backbone mean I also have to redesign the html into backbone?

bakape commented 9 years ago

If you can decipher what the models do, you can write the same in plain JS/jQ.

vampiricwulf commented 9 years ago

What would the benefit be? I'm already slowly translating it over, it's just weird.

bakape commented 9 years ago

In this particular case - only readability.

vampiricwulf commented 9 years ago

Looks to be the exact opposite to me. This is making things so damn complex that I don't know what the hell I'm even supposed to do.

bakape commented 9 years ago

In time you will learn to love the simplicity of Backbone

vampiricwulf commented 9 years ago

But this isn't simple, I don't understand any bit of this. Why the hell is there so much this in the report/client.js? What the hell is okyaku.dispatcher and will i need it? How the hell does the report/client.js know what the report config settings are if they're never require()'d? Where the hell am I pushing this model? Everything looks like it goes into view, what do I even need to put into the model?

bakape commented 9 years ago

this

That refers to the scope of the Model/View/etc.

okyaku.dispatcher

Websocket communication parser

How the hell does the report/client.js know what the report config settings are if they're never require()'d?

Some configs are passed on to the client in some way. In this case it is done by make_client.js

Where the hell am I pushing this model?

Pushing?

Everything looks like it goes into view, what do I even need to put into the model?

Whatever you want. Backbone is very liberal on how you use it.

vampiricwulf commented 9 years ago

Pushing?

menuOptions.push('Report');

Report goes to every menu. Where would a suggestion box get pushed to? I'm really not understanding the benefits of using this, I have no idea how I grab values put into the suggestion box and I have no idea where to even do anything. Report is so different from what I'm trying to do that it's making me even more confused.

bakape commented 9 years ago

The benefit is that it's a template. You can copy it with different options as much as you want and even have the instances communicate between each other.

As to how to solve this, I have no clue. Have not yet looked at the reporting code and you have written plenty of stuff, I have never used and would need extra time to figure out.