|
Nothing. I've been slammed with work, and David got a job (and, possibly, a real hobby  ).
I'll probably open things up again once Life tapers off a bit. December generally does that to me...
---- You're right.
These facts that you've laid out totally contradict the wild ramblings that I pulled off the back of cornflakes packets .
|
|
|
|
|
A job is something to get you out of the house. Is something wrong with CPHog and FF3? My signatures don't seem to get saved.
|
|
|
|
|
Too lazy and scared to disable CPHog since my work FF no longer supports it, but if you edit a CPHog message without it, and vice-versa, does it see it as a CPHog message still, and vice-versa?
|
|
|
|
|
CPhog messages are tagged with a hidden DIV appended to the message. If you post a message using CPhog and then edit it without CPhog, the tag will persist... unless you edit it out.
---- You're right.
These facts that you've laid out totally contradict the wild ramblings that I pulled off the back of cornflakes packets .
|
|
|
|
|
Shog9 wrote: unless you edit it out
Is that an option?
|
|
|
|
|
|
What do you want it changed to? I can add a "@media tv { PRE { ... } }" entry in the main CSS file if you want.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
I think just making it bold would make a world of a difference.
But I am unsure how it will work. Do I have to specify something within my browser (FF3) to make it use the tv rules rather than the ordinary rules? 
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
You don't even need Javascript. FF allows custom, site-specific CSS rules to be applied via the userContent.css file. If you don't already have one, then in your profile directory (on windows, this is under ~/Application Data/Mozilla/Firefox/Profiles) in the chrome subdirectory, create a file named userContent.css and put the following in it (perhaps modified to be less offensive to the senses first):
@-moz-document url-prefix(http:
{
pre
{
font-family: Comic Sans MS !important;
font-weight: bold;
color: #A01010;
}
}
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
Aye, caramba!
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
Ah - that saves me some time 
(Am I the only one who reads "!important" as "Not important"?)
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Sh*t pommes frites and holy macaronis - it worked very well! Thank you!
|
|
|
|
|
I just bumped the jQuery version to 1.2.6. This should boost speed a bit more. The other thing that we might want to do is move from using the old interface plugin to the new jQuery UI stuff.
|
|
|
|
|
Apparently we don't use the interface plugin at all? Not sure why it was there, except that I thought maybe we'd be doing some fancy stuff...
|
|
|
|
|
Yeah... I guess the stuff that would be most useful, like dialogs and geometry, i already had routines for pre-jQuery.
Of course, now that the geometry stuff is in jQuery proper, it'd be a shame not to use it...
The resizing stuff in jQuery.UI could be useful. I'm thinking drag-resizing for message editors and such.
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
Not sure if this[^] will help you at all but it's there if it makes things easier.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
FWIW, jQuery 1.2.6 includes an unfortunate bug that hurts CPhog due to certain shortcut keys we add to the site. It loses the altKey state in events dispatched via jQuery (jQuery wraps the browser's event object to smooth out discrepancies between browser implementations, and an off-by-one error causes it to skip copying the altKey attribute).
We use a patched version of jQuery to avoid this bug, and i've emailed you separately with this version in case you have need of it. FWIW, the jQuery we use is served from CP already (my member area) or from David's SVN server (for trunk / testing versions), so it doesn't really make much difference in speed. If and when CP starts using jQuery natively, we'll have to make a call as to whether we want to continue using our own version, or go with CP's (would probably hurt load time to use both, but jQuery actually does support this fairly well, and if CP is slow to update it would allow us to continue living on the bleeding edge... )
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
QuickRefresh got moved out to its own plugin...if there's any problems, mention them. But it looks like everything's good...
|
|
|
|
|
I've never tried that before...
Last modified: 6mins after originally posted -- Holy crap...you can!
|
|
|
|
|
![Sheep | [baah]](https://www.codeproject.com/script/Forums/Images/sheep.gif)
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
Having fun?
|
|
|
|
|
Hadn't realized those were missing 'till they showed up again... 
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
Heh. Yeah. I was just goofing off with putting in array comprehensions where they're useful when I realized that I thought I had screwed it all up. So I fixed it. 
|
|
|
|
|
By the way, if we want to use let or yield, we're gonna have to bump the cphog.user.js file again. Basically, the section where we inject greaseSrc needs to change from:
greaseSrc.language = "javascript";
to
greaseSrc.type = "application/javascript;version=1.7";
I'm going to recommend we hold off on that and bump directly to 1.8 when Fx3 gets released. Thoughts?
|
|
|
|
|
I'm not convinced that 1.8 brings enough to the table to justify it just yet (well, the function(x) x syntax is kinda nice, but that actually works without specifying the version).
Let's plan on bumping it to 1.7.
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
