Coming Expression replacement for FrontPage

[rfr]

I just tried to read and understand the material Microsoft has on Internet
regarding their upcoming replacement for FrontPage called "Expression".
Actually this may be several separate applications rather than an integrated
product like Frontage. Jeez . . . . . does one have to be a techy to use
this stuff . . or what. This material is incomprehesible to alot of us who
already make good use of Frontpage and author/develop good web material.

It looks to me like Microsoft is going the way of the old IBM, as they
developed, things got more and more complicated and things were done in more
and more stepes in less and less obvious ways. Software code got bloated and
complicated.

I was looking for a list of FrontPage features that I use alot like
Insert/Include Content/Page to see if they would still work if and when I
have to switch to the new application. And the division of FrontPage webs
and subwebs is central to my material.

I was also looking for help understanding whether the present ISP Frontpage
Extensions will be necessary, or if there will be newer extensions that an
ISP will need to have installed for each of the various products that will
replace FrontPage.

There is a free Beta available . . . but jeez . . is this compatible with my
present FrontPage webs and subwebs, or would I be shooting myself in the
foot for even downloading it and trying it on my existing web and subwebs.

What happened to the KISS principle?

 

[coreybryant]

In my opinion, Microsoft was trying to re-do the HTML compliant coding.
They could not do it and now Expressions creates coding that is much
more, if not all, compliant.

You can choose what DOCTYPE you want etc. I currently use Expressions
and I can still publish, but using a lot of those components that
require FPSE:
http://www.timeforweb.com/frontpage/forum/forum_posts.asp?TID=5894&PN=1
are probably going to be gone soon to rely on server side languages.
FPSE are not all that secure and when MS came out with FP 2003 but not
FPSE 2003, that was our first clue that something else was in the works

-Corey
http://www.loudcommerce.com/promo/google.asp

 

[rfr]

What I originally liked about FrontPage was the ability to text edit ( for
which I had been using WordPerfect ) and quickly be able to visualize the
results ( for which I had been having to save the results and load it in a
browser . . several steps).

I first used it for a while just to make html text changes and visualize the
results. Then I began to use the publishing feature later.

FP 2003, prior to CSS was able to quickly visualize during the numerous
trial and error test/design stage ideas. YEAH! Unfortunately, lately, since
CSS FP 2003 doesnt render a true visual representation of many of my
documents and I have to resort to evoking the full browser.

FP was simple to use and saved me time and was less frustrating. It actually
made creating web material fun . . and made testing new creative ideas fun
for me.

Also, it helped organize and simplified the movement of material from my
development area ( a drive on my PC) to the server.

FP Sub Webs made the task of authoring and maintaining separate topics
easier in some ways without getting too technical.

And then FP provided help with organizing modules of common code, like
headers, footers. For this I used the FP Insert/Web Component/Include
Content/Page feature. It produced reliable results.

Nothing real techy needed to be learned.

I still use WordPerfect for a few things. Mostly I use WordPerfect Macros
and Merge feature to create HTML documents out of a WordPerfect database in
a batch approach with the files being saved in a FP sub web that I thn do a
Tools/Recalculate Hyperlinks before publishing. This is a poor mans,
non-geeks Database.

FP was useable by more than the geeks or technically inclined people.
Instead of an user base in the tens of thousands of geeks, it probably had a
user base in the tens of millions.

Most people have to spend alot of time learning new software . . I am one
of them . . . more and more of Microsofts software seems to be written for
geeks and people who learn techy stuff quickly. . . perhaps this is bright
and techy people writing software to be used by other bright and techy
people.

I like a standard routine that I can count on. I dont like UN-learning
things to adopt to new software.

I imagine that I will have to make the transition away from FP 2003 . . .
but I am not sure whether I will follow Microsoft to their new world of
techy details, or go over to Dreamweaver, or to another HTML authoring tool.

What I will be looking for is the implementation of features that I
presently use in FP 2003 ( noted above) in a simple understandable way
(techies call it an "interface"). . . and I sure would like a GLOBAL version
of the FP Insert/Web Component/Include Content/Page feature.

 

[rfr]

I want to do my design work, development and deployment with the KISS
principle: Simple tools, solid reliable results. I dont want to have
anything to do with this finicky, obscure, geeky, techy stuff. They can
keep it.

 

[KatWoman]

if MS get rid of the sucking FP extensions it will be worth it!!
Dreamweaver will become possibly more sucky as Adobe known for great
graphics but hideous web design proggies bought them out.And MM flash and
Dreamweaver is not too easy too learn...
I am throwing in the towel for web design..going to pay someone else to do
it
or buy an online site already done and add by upload

 

[rfr]

I understand and identify with your frustration.

Those of us who are not techies but like to do this number in the tens to
hundreds of millions of potential software buyers, whereas the techies of
the world are merely hundreds of thousands to millions. Why cant the
software people see this vastly larger market and design for it rather than
for the narrower market of techy savy geeks?

Web site design used to be more fun. The tools were simple to use and what
you designed would look basically the same to all users. Thos there are
more tools now, you cannot count on what you design will work beyond your
authoring platform.