Awesome :)
Interesting!
Are these all stable enough to be installed here, at least for 'testing'...?
Ideally, yes. Probably even enabled by default if I'm honest. The feature is a big draw for some and given the "only triggers on @" there's not even a performance concern.
Interesting question, what would happen with the above sentence as typed?
| 1. | currently I'm using /\@(\w+)/ (I'm not a regex expert, this'll probably fail on a few valid usernames) |
\w+ shouldn't match the ", but if you're doing that on the client side it should be fine.
(It is more of an issue on the server side because all display names and usernames are all pushed through htmlspecialchars first)
Regarding core vs not core, I found through bad experience that 'core plugins' do not work that well from a user perspective. They embody everything that is wrong with Core Features: having to go to an unrelated page that was convenient for the developers to just grab everything together, and it is a proven cause of support requests. Not that there won't be support requests anyway but at least some people will use search and just straight up exploration to find it otherwise.
I'd rather either have it totally as a plugin, or fully core, I don't see that any intermediate measure suits anyone but us from a purely convenient point of view.
I would love to see both this and the notifications core being core features and completely integrated. Seems to me that might be faster?
Actually mentions would fail absolutely miserably for usernames with a space, I gotta figure something out for this.
@Admin: This is perhaps a crude test, but how would @Maxwel do for the later project? I'm not entire sure if this'll work like the way it's supposed to.
@Maxwel: What do you think of the project itself? Care to elaborate on your findings? Perhaps add another prospect given by @Trish to @Soxell?
What about @-Lük-? How would this really work? Would it work? Or would it not work? Does't it require a massive amount of overhead for bear that shouldn't be born?*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: smf_gallery_members
type: range
possible_keys: real_name
key: real_name
key_len: 767
ref: NULL
rows: 44
Extra: Using where*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: smf_gallery_members
type: range
possible_keys: real_name
key: real_name
key_len: 767
ref: NULL
rows: 44
Extra: Using where*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: smf_gallery_members
type: range
possible_keys: real_name
key: real_name
key_len: 767
ref: NULL
rows: 44
Extra: Using where*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: smf_gallery_members
type: range
possible_keys: real_name
key: real_name
key_len: 767
ref: NULL
rows: 44
Extra: Using where*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: smf_gallery_members
type: range
possible_keys: real_name
key: real_name
key_len: 767
ref: NULL
rows: 44
Extra: Using where
Thought I should mention... (Ah, ah.)
(Where do I post my updated files anyway..?)
Yesterday I fixed the silly bug where doing @Nao on a single line without any other punctuation would fail to 'detect' it.
For the record: it was due to the strip_tags call. It can be called, but it should add an exception parameter of '<br>'. Otherwise, multiple lines are put together without any separator, and you know what that means... Something like @NaoSecond line.
Oh and is markReadForNotifier disabled for this site? It isn't marking my notifications as read when I view this topic.
Although I should probably use email template but I'm not sure if that'll fix this problem.
I need to figure out how plugins and email templates in general should work ;)
What about read notifications greyed?
Well I did say I uploaded it to satisfy your curiosity. And if you want to improve it even more. You have svn access on plugins, don't you..?
May I ask what the point of putting it on github is? It can only be used in Wedge... ^^