|
See post in The Lounge...
(almost pulled it at the last minute, after it stalled horribly during testing... then realized i'd disabled my browser cache earlier.  )
----
Yes, but can you blame them for doing so if that's the only legal way they can hire programmers they want at the rate they can afford?-- Nish on sketchy hiring practices
|
|
|
|
|
We may want to do a small upgrade of jQuery to 1.1.3.1. The new version is checked into the repo.
|
|
|
|
|
fair 'nuff. Gotta have that working IE translucency... 
---- Yes, but can you blame them for doing so if that's the only legal way they can hire programmers they want at the rate they can afford?-- Nish on sketchy hiring practices
|
|
|
|
|
Think maybe we should do a release? The current version is pretty snappy. And I'm okay with shipping this version as is (with the exception of turning off the debug page in the Preferences lightbox)...or at least removing the button that deletes all your prefs.
Also, since yesterday was my last day at my old job, I'm getting an external svn server set up and will be migrating the CPhog svn repo there as soon as I get back from vacation. Nobody'll be touching that server till then, so we should be able to keep running on trunk. I'll get that all sorted once I get back to the land of plentiful internet.
Anyway, if there are any problems with the current trunk version, now's the time to air 'em. Otherwise I'd like to do a release.
|
|
|
|
|
|
David Stone wrote: Anyway, if there are any problems with the current trunk version, now's the time to air 'em.
I'm still not wild about the speed - we do too much unnecessary DOM manipulation when loading threads. But, we could probably release what we have now and leave fixing that for a later release. I'm due to be out of town for a couple of weeks, after which i'll have more time and a faster laptop... so one way or another, i'll get happy with the speed. 
I guess if no-one else feels like there are show-stoppers, we can dump what we have now. The forum watch and quickbio stuff oughta make a few people happy. 
----
Yes, but can you blame them for doing so if that's the only legal way they can hire programmers they want at the rate they can afford?-- Nish on sketchy hiring practices
|
|
|
|
|
Eh. Hold of just a bit. I have a few changes I'm making right now.
|
|
|
|
|
Alright. I'm done. I moved QuickBio out into its own plugin area (like ForumWatch). Just keeps things a bit cleaner. I reworked the inline menu code (the menu that pops up for the smileys, fonts, etc) and it's noticeably faster now. The only major updates we've done for this release are QuickBio and ForumWatch and moving the prefs into GlobalStorage. There are some speed improvements in small areas. I'm expecting we'll do more speed stuff for the next release. (2.0?) And the next release will have a better control panel in the lightbox and user-configurable key-bindings and all that jazz. We should also work on the CP API stuff so that we can have good abstractions for the things we do the most.
This should also be the last time we need to update the cphog.user.js file...ever. It does the most minimal bootstrapping job it can. All it loads is FreshGrease and jQuery.
I'm driving back to San Diego tomorrow from Austin. I'll have net access some of the time and I'll probably check my e-mail every so often. Go ahead and do the release tomorrow if everything looks fine to you. All my tests have worked just fine, so it should be good to go.
One last note. The changelog file is currently living in my profile and the URL to it is hardcoded in cphogHelp.js. If you want to change that so it's hosted in your account, that's okay...or you can leave it as is. I don't really care. Remember to grab the new images as well.
Last modified: 39mins after originally posted --
|
|
|
|
|
Fantastic. Not sure if it's the new jQuery or other changes you made, but load times are subtly but noticeably better.
I'm stuck behind a crappy firewall here in the office 'till my car gets done being fixed; if no-one has started screaming about monsters by then, i'll release it. Otherwise, i'll just post in The Lounge about how great it is and nya nya nya y'all don't get it...
----
Yes, but can you blame them for doing so if that's the only legal way they can hire programmers they want at the rate they can afford?-- Nish on sketchy hiring practices
|
|
|
|
|
|
Since there seem to be an awful lot of worthless posts getting vote-deleted lately, i figured someone might find this useful, if only in satisfying their curiosity:
Download userscript here[^]. Adds "show content" link to deleted posts.
It's not polished at all - notably, it doesn't work if you navigate to a post using the keyboard or a direct link. But frankly, i haven't found it useful enough to spend any time on it, so... take it for what it's worth.
----
Yes, but can you blame them for doing so if that's the only legal way they can hire programmers they want at the rate they can afford?-- Nish on sketchy hiring practices
|
|
|
|
|
When you click on the Show Content and then click on the Username to show the account profile, it doesn't work. If you click on the Username without clicking on Show Content, it works fine.
|
|
|
|
|
Huh, weird. Eh, quick'n'dirty is as...whatever.
----
Yes, but can you blame them for doing so if that's the only legal way they can hire programmers they want at the rate they can afford?-- Nish on sketchy hiring practices
|
|
|
|
|
Quick 'n' Dirty, what every man wants. 
|
|
|
|
|
In this post[^] the poster wrote some code in bold, but the colorizer overrides that formatting with its own, so I can't tell which part of the code he's talking about. It would be nice to have another link at the top of the block that reverts back to the regular <pre> styles.
|
|
|
|
|
Sounds reasonable. Done.
(you may need the latest userscript[^] to see the toolbar, but there ought to be a show original item on it now...)
----
i hope you are feeling sleepy for people not calling you by the same.
--BarnaKol on abusive words
|
|
|
|
|
Sweet! ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif)
|
|
|
|
|
Move the mouse over a message or username that is towards the bottom of the screen such that there's not enough room to preview either, and it flickers forever.
|
|
|
|
|
Huh? Not sure what you're talking about - i can hover over anything* without flicker... 
*except a candle flame. But i don't really want to hover over those...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
|
|
|
|
|
If you have FF[^] maximized and move the mouse to the last post above the bottom of your desktop, you may see it flicker[^]. I know it does on mine.
|
|
|
|
|
Hmm... 'fraid i just don't see it.
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
|
|
|
|
|
I'm on my laptop now and I don't see it at home. I consistently see it at work. Must be a plugin or something.
There are II kinds of people in the world, those who understand binary and those who understand Roman numerals. Web - Blog - RSS - Math
|
|
|
|
|
Any chance you can add the post preview in the messages posted page please?
"The trouble with the profit system has always been that it was highly unprofitable to most people." - E. B. White
Web - Blog - RSS - Math - LinkedIn - BM
|
|
|
|
|
Only by loading all 50 messages in the background. That would be... slow.
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
|
|
|
|
|
Didn't you do it for regular posts?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
