[bug] Static rendering

[Tom Weir]

A work around you might want to try...
use a common unix app called 'wget' to recursively spider your internal dev
site. Then upload the results to your production site. 

Unfortunately, apple no longer (I believe as of 10.1) ships wget with OS X,
so you'll need to download the source & compile it. If you're on the Windows
side of things, it comes with an environment called 'cygwin' (a bash shell
for windows, among other things...)

Tom

-----Original Message-----
From: Kelly Thomas [mailto:kthomas at siu.edu]
Sent: Friday, February 22, 2002 12:07 PM
To: userland
Subject: Re: [bug] Static rendering


This morning I read in interesting digest...

>> Now I have been getting some off list feedback suggesting I'm not alone
>> in my complaint that Radio/Manila/le-projet-du-jour get way more
>> attention than Frontier, even though we Frontier customers pay the big
>> bucks. As a customer, I feel neglected and disrespected,
> 
> Hi everyone,
> 
> I wrote Michel the following message off list and he pointed out, rightly
I
> think, that he would appreciate some public support of his position.
> 

Sometimes I feel this way too.

I don't have a problem with Dave or Userlands professionalism. I don't think
anyone should attack that. I think they are great guys. I'm glad they are
not stone-cold, corporate, yuppie-tweed, *@#&'s. They do great work and seem
to work hard. 

For several years I've been a rather casual user compared to you guys who
develop software in the Frontier environment. We're not spending big dollars
but we are consistent in our purchase. We use Frontier/Manila every day and
recently have grown very dependant on it for our publishing solutions. What
I've observed is that Userland breaks new ground but does not always tidy
the details. They are a small company and I think their (or Dave's) priority
is to "damn the torpedoes, full speed ahead ahead." Other companies are
guilty of this, resources can only go so far. You have to focus.

On the other hand, maybe I'm wrong but there seem to be countless bugs in
static rendering that I can't even begin to fathom. It seems to me like it
was just tossed in with the deal "because we could add this feature quick
and easy this way" and not thought out real deep. Maybe I'm wrong. And I've
can't find hardly anything about making it work correctly.

It's like I've got this new car where the power window won't work and all
the dealer says is, "it was a good price, it runs ok right?" yea, but I was
expecting the window over here to work.

Matter of fact, static rendering is a deal killer for us as we are legally
required to host our web pages off campus. It's ok to have a "development"
 server on site but commercial pages have to be hosted off campus.

I hope someone can look into fixing up static rendering and making it a
solid reliable useable feature.

Thanks for reading my flame. :-)


Kelly Thomas     
Microcomputer Specialist III
WebMaster
SIU - http://www.dailyegyptian.com