[CALUG] Convert. Web pages in .asp to html

[Richard Stuart]

Question for you experts out there. I've not found a basic a solution to get to HTML code and java scripts Perl scripts CGI scripts etc.  Some have suggested rebuilding using Word Press or Drupal.   These seem to limit the basic screen as displayed to about 960 pixels.  In the limited work I've done I have never exercise such a limit.   Why does WordPress and  Drupal have such a limit????  To me it tends to make your web page look like watching a 50's movie on a new laptop or widescreen TV.   Ug!

Sent from my android device.

-----Original Message-----
From: Bryan J Smith <b.j.smith at ieee.org>
To: Brian Harnish <brian at harnish.net>
Cc: Richard Stuart <rl.stuart at verizon.net>, "calug at unknownlamer.org" <calug at unknownlamer.org>
Sent: Sun, 05 May 2013 8:44 PM
Subject: Re: [CALUG] Convert. Web pages in .asp to html

On Sun, May 5, 2013 at 8:04 PM, Brian Harnish <brian at harnish.net> wrote:

> Quite the holy war going on in this thread,
>

Well, in my case, I am all about the exact _opposite_.  "Risk mitigation"
doesn't know "faith" or "allegiance."  But I constantly run into dozens of
people who see it that way.  Why?  Because when it come right down to it,
there are few things that Microsoft does that is not a major risk.  The
only "risk reduction" with most Microsoft solutions is when one is already
using them, so staying with those solutions might be so short-term.

It's just the reality most of us deal with on almost a weekly basis with
customers.  As Gartner warned way back in 1999, no vendor is going to offer
a way out of lock-in.  So expecting open source to solve an issue of
lock-in is really not what open source has ever been about.  It's about
offering a solution to problems, which requires enterprises to make a
conscious and strategic decision to move.  As always, I put things in terms
of risk.

As far too many enterprises are finding out, legacy VB 6 and MS IE 6 are
major risks right now, and their investments have been made in vain
long-term.  And even .NET must be taken on with a full understanding of the
risks involved, should it be leveraged as a solution.  I've taken a lot of
"heat" for balking any time someone states .NET is portable.  And I've
ended up being right in every single case.  Just food for thought ... on a
Linux and open source list.  ;)


> but to answer your question: The way to convert them is to either find
> someone
>
who knows those technologies and agree on a wage for them to do it.
>

Actually, there are a number of automated solutions out there that are
designed to convert ASP to JSP.  Now in several cases, they are not
discrete solutions.  I.e., they often have strings attached with purchasing
their Java Beans and other components that run on your application server.
 In some cases they do comprise of code licensed from Microsoft, but have
been ported to run on a Java vertical stack.  It's really all about what
you need to do.

That's an additional debate between "clean room" and more "intermediate"
migration/porting options.


--
Bryan J Smith - Professional, Technical Annoyance
b.j.smith at ieee.org - http://www.linkedin.com/in/bjsmith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.unknownlamer.org/pipermail/calug/attachments/20130506/ccb94b3d/attachment.htm