Skip to main content

Tim Van Wassenhove's (PHP) Blogmarks

Tim Van Wassenhove, a c.l.php regular maintains wonderful blogmarks. Most of the blogs are PHP related and it is faster to access than my Sage, RSS reader. It is interesting to see that Tim has blogmarked my—this simple blog too:)

IMHO, it would be better to display timestamps along with the links and to have a TOC of blogs in the top.

Comments

Anonymous said…
the updated blogmarks are coming... i just lack the time to implement it first couple of days (may be even weeks)

timvw
Apr 15, 2005, 5:43:00 PM
R. Rajesh Jeba Anbiah said…
Thanks Tim. It's really nice to know that.
Apr 16, 2005, 11:39:00 AM
Anonymous said…
Well, i hope you like the blogmarks a little better now :)

I added the list of feeds to the top of the page, added dates to the articles (for those that have dates in their feed anyway) and improved the cache so things go faster ;)
Jul 11, 2005, 8:05:00 AM
R. Rajesh Jeba Anbiah said…
Tim:

Thanks Tim. This is really cool:) But, the caching thing seems to be bit quirky.
Jul 12, 2005, 10:15:00 AM
Post a Comment

Popular posts from this blog

Converting PSD with PHP/ImageMagick

After seeing feature rich options in Imagick PECL extension at Mikko Koppanen 's (the author) website and also impressed with ImageMagick 's features, I have decided to use it for the PSD to XHTML conversion website that I'm architecting and managing. Since, the team wants programming help for converting PSD images, I have tried it (documentation is sparse on PSD handling) Converting PSD to PNG/JPEG/etc Note that, flattenImages() is needed for layered/multi-page PSD file. <?php $im = new Imagick('test.psd'); $im->flattenImages(); $im->setImageFormat('png'); $im->writeImage('test.png'); ?> Extracting PSD layers One by one <?php $im = new Imagick('test.psd'); $im->setImageFormat('png'); for ($i = 0, $num_layers = $im->getNumberImages(); $i $im->setImageIndex($i); $im->writeImage('layer' . $i . '.png'); } ?> Note that, there is a better version below In a single call with writeIm...
5 comments
Read more

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...
Post a Comment
Read more