Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Nao
7516
Plugins / Re: Personal plugin showcase (yes, I'm an attention grabbing git)
« on October 8th, 2011, 11:11 PM »
Well that's the idea...!
If you don't know what to do next, do you want me to post my personal to-do list that I don't know when I'll be able to tackle? :P
If you don't know what to do next, do you want me to post my personal to-do list that I don't know when I'll be able to tackle? :P
7517
The Pub / [Archive] Re: Logo Madness
« on October 8th, 2011, 10:33 PM »
I like the 'petals' logo above, it looks nice.
Here's another attempt, this time I've made it all into an arc... Like it, too.
Here's another attempt, this time I've made it all into an arc... Like it, too.
7518
Plugins / Re: Personal plugin showcase (yes, I'm an attention grabbing git)
« on October 8th, 2011, 10:32 PM »
Nice!
7519
The Pub / Re: Spell checker
« on October 8th, 2011, 10:30 PM »
Yup, agreed...
Well, now is the moment where everyone says, "if AeMe doesn't handle avatars and attachments then it's better off as a plugin", I know I know :P (Except it'll do it... One day. Uh. Let's pray.)
Well, now is the moment where everyone says, "if AeMe doesn't handle avatars and attachments then it's better off as a plugin", I know I know :P (Except it'll do it... One day. Uh. Let's pray.)
7520
The Pub / Re: Spell checker
« on October 8th, 2011, 07:29 PM »
Hmm yeah, looks like direct support for pspell was dropped in 5.3 in favor of enchant... Which wasn't core before 5.3. Uh, so that pretty much rules out the possibility of using it in Wedge without hacks and such. Sucks... Unless we simply disable the spellcheck feature for PHP < 5.3.
7521
The Pub / Re: Spell checker
« on October 8th, 2011, 04:57 PM »
He said its easier for him is all. I don't know of anyone who uses it-- even though it's pretty cool. But not very practical. Should be unlined really. Inlined.
7522
The Pub / Re: Spell checker
« on October 8th, 2011, 04:52 PM »
My only user who needs it actually uses Word to type his posts and leverage spellchecking. I guess to each their own.
7523
Features / Re: New revs - Public comments
« on October 8th, 2011, 10:14 AM »
Will have a look.
Installer -- I rarely run it. I suppose it's linked to the caching error.
Installer -- I rarely run it. I suppose it's linked to the caching error.
7524
Features / Re: Aeva - Forum owned albums
« on October 7th, 2011, 10:18 PM »
Goes without saying.
7525
Features / Re: Aeva - Forum owned albums
« on October 7th, 2011, 08:35 PM »
Keep me posted. Been a long time.
7526
The Pub / Re: Replacing the recycle bin
« on October 7th, 2011, 08:34 PM »
Well what stops us from adding a per user option for hiding deleted posts ;) things like that...
7527
Features / Re: Aeva - Forum owned albums
« on October 7th, 2011, 07:08 PM »
You can manually set id_owner to 0 in the database, IIRC it'll simply ignore the owner in that situation.
I always wanted to re-implement that into AeMe, but couldn't bother with the extra UI...
I always wanted to re-implement that into AeMe, but couldn't bother with the extra UI...
7528
Features / Re: New revs - Public comments
« on October 7th, 2011, 07:07 PM »
I think you could have guessed I was planning to split the Display template into several functions just like I did for the index template... But the good news is that you did it in a very clean way and I couldn't have done it better so it's all good :) (Maybe I would have removed the spellchecker though... I'm not exactly sure how useful it is in these days when most browsers have inline spellchecking.)
(Plus, I'm having such a hard time working on Wedge these days...)Quote from Arantor on October 6th, 2011, 07:46 PM It's the easy part to me... :^^;:Quote Sure. The 'approved' field can really have any value at this point... As long as the only valid value for showing a post is '1'...
I've started work on it, BTW. Although I'm currently trying to determine whether I should keep it as 'approved' or use the opportunity to rename it to 'status'.Quote Possibly. But maybe we should also log the contents of the empty skeleton for admins to look into...
Quote from Arantor on October 7th, 2011, 11:14 AM I have absolutely no idea why this shouldn't be done... I'll be working on it. It's not like it can't be reverted...
Oh, and one thing that could be improved... Testing for some values and, if they're not true, either don't add the corresponding block, and simply removeBlock() it... (Well, the problem with the second solution is that when we start using an object for this, it'll be a tad slower than just unsetting the block in the skeleton array...)
What do you think of this?
Another possible improvement: allow for params to be passed to template functions. Something like, loadBlock('mod_buttons', 'upper'), with 'upper' being passed to the template function so that it knows what to show.
Having trouble with the postlist (i.e. topic posts) layer...
So, if I want to load the layer into default, surrounded by blocks, I have to do it this way...
Code: [Select]
I'd say it's pretty ugly.
Other solutions:
- add the ability to specify layers directly within the block list, by specifying a sub-array, and possibly other blocks inside the array.
- just forget about it...
- add the layer after the main block code, and add to loadLayer() the ability to inject a layer before or after a *block*, just like loadBlock offers the ability to inject a block before or after a block or a layer. This is my favorite solution (I like the second one equally, though... :^^;:), but it may make the code even more confusing... (?)
Opinions?
(Plus, I'm having such a hard time working on Wedge these days...)
I'm not so bothered by the physical status part, though that is ultimately the way to do it. What concerns me is how we show the user. How do we display it?
I'd also prefer to separate deleted-by-author from deleted-by-moderator.
I've started work on it, BTW. Although I'm currently trying to determine whether I should keep it as 'approved' or use the opportunity to rename it to 'status'.
As far as empty-skeleton errors, that implies a logic error, and if there isn't a fatal error shown to the user, what would happen? I'd argue that a page with no content is less helpful than a page with an error message.
Posted: October 7th, 2011, 04:28 PM
@ Nao: Something in my brain told me not to make the title_upper and _lower parts (which are used for the page titles/go up+down areas) into a template layer but I'm not sure *why* my brain told me that. If you wanna change it, please go right ahead.
Posted: October 7th, 2011, 04:32 PM
Oh, and one thing that could be improved... Testing for some values and, if they're not true, either don't add the corresponding block, and simply removeBlock() it... (Well, the problem with the second solution is that when we start using an object for this, it'll be a tad slower than just unsetting the block in the skeleton array...)
What do you think of this?
Another possible improvement: allow for params to be passed to template functions. Something like, loadBlock('mod_buttons', 'upper'), with 'upper' being passed to the template function so that it knows what to show.
Posted: October 7th, 2011, 04:37 PM
Having trouble with the postlist (i.e. topic posts) layer...
So, if I want to load the layer into default, surrounded by blocks, I have to do it this way...
loadBlock(
array(
'report_success',
'display_draft',
'title_upper',
'topic_poll',
'linked_calendar',
)
);
loadLayer('postlist', 'default', 'child');
loadBlock('display_posts', 'postlist');
loadBlock(
array(
'quick_access',
'mod_buttons',
'quick_reply'
),
'',
'add'
);I'd say it's pretty ugly.
Other solutions:
- add the ability to specify layers directly within the block list, by specifying a sub-array, and possibly other blocks inside the array.
- just forget about it...
- add the layer after the main block code, and add to loadLayer() the ability to inject a layer before or after a *block*, just like loadBlock offers the ability to inject a block before or after a block or a layer. This is my favorite solution (I like the second one equally, though... :^^;:), but it may make the code even more confusing... (?)
Opinions?
7529
Features / Re: New revs
« on October 7th, 2011, 05:16 PM »
rev 1072
(2 files -1, 5kb)
- Reverted an accidental commit. (images/.htaccess)
! Syntax error in rev 1063. (Security.php)
! Template blocks were always ignored if not found. This is okay, except for the actual main function. I suspect this is something I did during my testing phase and I forgot to restore it... (Subs-Template.php)
* Indenazi. (Subs-Template.php)
(2 files -1, 5kb)
- Reverted an accidental commit. (images/.htaccess)
! Syntax error in rev 1063. (Security.php)
! Template blocks were always ignored if not found. This is okay, except for the actual main function. I suspect this is something I did during my testing phase and I forgot to restore it... (Subs-Template.php)
* Indenazi. (Subs-Template.php)
7530
The Pub / Re: Replacing the recycle bin
« on October 7th, 2011, 04:21 PM »
Also, we need to ensure admins can actually delete the posts forever -- for instance spam posts, etc. There's no point in bothering users with a topic bump if they can only see "This post was deleted by a moderator - reason: spam"...