| |
|
Tuesday, July 02, 2002
|
|
What I want is dynamic page generation, so if I change something in one of my headers, etc., I don't need to re-generate and re-publish every single page on my site.
[Greg Reinacker's Weblog]
It's almost as if you'd need a dependancy list. So as pages (or templates) change, only those pages that depend on the changes need to be regenerated/uploaded.
As for your changing header comment, I would think a properly designed blogger could generate a web.config with the desired data. Combine that with templates that pull information out of the web.config and you should be all set.
2:40:18 PM 
|
|
|
... using XHTML 1.0 Transitional doesn't lock out older browsers. You can still do presentation markup in XHTML 1.0 Transitional right in the code. What kills the older browser is when you commit to removing the presentation from the XHTML, and relying on recent versions of CSS. My site was just fine w/ old browsers w/ XHTML 1.0 Transitional, but when I moved to XHTML 1.0 Strict + CSS, I decided to give unformatted content to old browsers. They can still read the site, but there's no presentation to it at all... just black normal text on white background in the medium font size.
[The .NET Guy]
<whisks away to do a "View Source" on Brad's site />
Interesting... I also checked out your site with Navigator 4.x. I see what you mean by "no presentation at all" :)
2:33:14 PM
|
|
|
Dave: "On Sept 11, the first-hand accounts from amateurs with keyboards, telephones, digital cameras, relatives at the scene, were just a demo of what's coming in the next few years."
[Adam Curry: Adam Curry's Weblog]
2:10:14 PM
|
|
|
Microsoft spent $100M on .Net security
Microsoft's much-publicized security push has cost real money--$100 million of person-hours went into the two-month hiatus in development of .Net server, according to David Thompson, vice president of Microsoft's Windows server products group.
[ZDNet News]
10:26:29 AM
|
|
|
A .Net blog tool, 'cause when you've got a hammer....
Seriously considering writing my own blogging tool as none of the ones that exist meet my stringent requirements:
- Open Source
- Produces only valid XHTML
- .Net - well, not mandatory, but definitely a plus, as far as hammer fulfillment goes.
- Uses CSS for style
- Small and fast
- Can be used from multiple locations to edit the same site
- Only requires an FTP-only site, no server-side scripting required,
no PHP, SSI, CGI, etc.
[BitWorking]
Cool idea! After looking through my referer logs the first few days of my blog, I came across someone that has started a .NET blogger, although it didn't appear to have been updated in a while.
I'm wondering though:
- Only XHTML? How will that affect older (IE 5.x/Netscape 4.x) browsers?
- Used from multiple locations: Love this idea! But could be security issues (opening a hold in a firewall port for remote administration).
- No server-side scripting required: Definitely. But make sure the blogger can produce .ASP, .ASPX, etc... files in case we bloggers want to use this capability
And what about templates?
7:39:36 AM
|
|
|
GACUtil Add-In.
I needed a simple way to invoke GACUtil as a custom build step. Utility makefiles were clunky, NAnt was too extensive (but cool) and the BuildRules sample wasn't quite extensive enough. So I built my own.
[sellsbrothers.com: Windows Developer News]
7:23:47 AM
|
|
|
Updated .NET CollectionGen.
"CollectionGen is a Custom Tool Add-In to VS.NET to generate type-safe collections. The updates are as follows:
"-Finally someone has figured out the XSLT garbage bug! Thanks, Matthias Hess!
"-Removed the need for a .reg file, so now registration is just 'regasm /codebase collectionGen.dll'.
"Also, Jon Flanders put together a collection gen project item wizard that adds a new XML file with the Custom Tool property pre-set. I'm having a little trouble packaging it for distribution, but if anyone wants to hack on it, send me an email."
[sellsbrothers.com: Windows Developer News]
7:23:03 AM
|
|
|
|
© Copyright 2002 Patrick Steele.
Last update: 8/2/2002; 9:15:08 AM.
|
|
|
