@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16752
Irc2PGuest33667
Irc2PGuest51880
Irc2PGuest97218
Onn4l7h
Sisyphus
Sleepy_
T3s|4_
Teeed
aargh2
ac9f_
b3t4f4c3__
b4dab00m
bak83_
duanin2
duanin2_
eyedeekay_
john231
leopold
makoto
mesh
nilbog-
not_bob_afk
poriori_
profetik1
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
tr
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
zzz
ok I banged out a search backend in 10 minutes, tell me where the search box should go
dr|z3d
either above the main torrent table, zzz, or in the navigation bar.
zzz
maybe upper right in line with the header?
dr|z3d
the header being the nav bar?
dr|z3d
question: is the search going to be a single field option without any checkbox or other modifiers?
dr|z3d
if you're intending to implement advanced features, you know, like start - end date fields/dropdowns, or whatever, or search based on status.. then a separate panel is probably better.
zzz
notbob said keep it simple
dr|z3d
ok
dr|z3d
well, try the nav bar first. you can style the search so that it blends in rather than looks like an input box slap bang in the nav.
dr|z3d
if you make it a separate method, then you can insert it wherever you like
dr|z3d
(without having to mess around with the markup)
dr|z3d
public string getSnarkSearch() {..} or whatever
zzz
and from yesterday:
zzz
<zzz> ok plus standalone, a little janky but not bad dr|z3d
zzz
<zzz> why in the world are you doing a XHR for all.css every 5 sec?
zzz
right now it's just ?s=foo
dr|z3d
xhr for the css?
zzz
yes
dr|z3d
you'll have to remind me. where am I doing that?
dr|z3d
oh, all.css
zzz
open inspector
zzz
I forget what js it was coming from
dr|z3d
that'll be torrentDisplay.js
zzz
yeah line 121
zzz
fugly
dr|z3d
bah, behave.
dr|z3d
you're right though, for that specific filter ie none it doesn't need to pull all.css
zzz
should be a way to get the cached resource or something if you really need it
dr|z3d
for any other filter, it does.
dr|z3d
or maybe not. been a while since I had a proper look at that. the filter css ensures we hide the relevant trs.
dr|z3d
all.css is 571b total as transferred, so no biggy. but yeah, I'm tending towards not pulling anything other than the html in ajax requests, generally speaking.
dr|z3d
maybe I'll optimize that and have the js inject the css into <head> instead. dunno. thanks for bringing it to my attention.
zzz
yeah, obviously harmless, but funky
zzz
ok lets see how bad this looks:
zzz
out.write("<form action=\"" + _contextPath + "\" method=\"GET\">" +
zzz
"<input type=\"text\" name=\"s\" size=\"20\" class=\"search snarkNav\">" +
zzz
"</form>");
dr|z3d
I'd suggest you want a button there. that's the visual cue. then you can hide the actual input until mouseover.
dr|z3d
a button being an icon instead of the standard styled square button.
zzz
yeah its funky, speaking of
dr|z3d
:)
dr|z3d
when you say funky I think of Miles Davis or James Brown. more the latter.
dr|z3d
anyways, re i2p+ snark, the filter bar should give you some idea of a query param based alternative.
zzz
did we decide we should AND or OR multiple search terms?