|
Bassam Abdul-Baki wrote: Nah, I thought you're a liar because you're too anal to let this go.
I am anal, but putting it in Trac[^] is good enough for right now. 
|
|
|
|
|
Is there some way to force CPhog to be used? Right now I'm typing into the default CP message window because CPhog didn't pick up on the new message whatever. I cannot get CPhog to load half the time if not more when I'm trying to post a message or a reply. It used to be it always worked for a reply but now it's not even working for that.
|
|
|
|
|
I've got the same problem, though it is a little better then yours. I'd say it works correctly about 70% of the time.
I can imagine the sinking feeling one would have after ordering my book,
only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
|
|
|
|
|
You're both wrong. It works 60% of the time. 
"It is the mark of an educated mind to be able to entertain a thought without accepting it." - Aristotle
Web - Blog - RSS - Math - LinkedIn - BM
|
|
|
|
|
I've turned off the migration code - old preferences won't migrate. That's a shame, but it's the biggest change between the beta and release - i didn't notice it was off until after release, so perhaps that's what's been causing problems.
Ctrl+F5
If anyone still seeing this problem can post specific JS errors, it'd be helpful... i'm probably not gonna spend any serious time on this 'till i get back to Colorado, but it'd be nice to know if there are problems.
---- 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
|
|
|
|
|
Alright folks. We've got a new development server. Click here[^] to upgrade your trunk builds of CPhog to it. Our trac instance is here[^]. 
Josh, you can just use the relocate command to move the repository over to http://svn.gixug.com/cphog. Your old credentials will still work on the new server.
|
|
|
|
|
When I reply to a post, there is a lot of white space below the editing area, screen shot here: http://i16.tinypic.com/5x6h378.png[^]
I'm running FF 2.0.0.4 on XP Pro x64. I didn't have any previous 1.9 builds on this machine, but I've been using 1.9 at home and never saw this problem.
|
|
|
|
|
That is odd. It looks as if the textarea isn't getting hidden before the iframe gets shown. Can you install Firebug and inspect the white area and tell me what tag it belongs to?
|
|
|
|
|
I just grabbed the latest from http://svn.gixug.com/cphog/trunk/cphog.user.js and I no longer see the extra space.
|
|
|
|
|
<tr id="PostContent">
<td width="100%" valign="top" style="border: 2px inset rgb(204, 204, 238); padding: 0px 0px 0px 2px; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; height: 8em;" colspan="4">
<textarea id="ContentText" tabindex="3" name="ContentText" rows="13" cols="75"/>
<iframe id="MidasContentText" tabindex="3">
<html>
<head>
<title/>
<link rel="STYLESHEET" href="chrome://targetalert/content/onMouseoverStyle.css"/>
</head>
<body/>
</html>
</iframe>
</td>
</tr>
Firebug says the extra space belongs to <iframe id="MidasContentText">. It still happens when I disable TargetAlert, so that's not the cause. Also, I found that clicking the [<>] button makes empty space appear around other sides of the edit box.
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
