IntraWeb Archive

XI: IntraWeb XI New Roadmap

XI: IntraWeb XI New Roadmap

If you are using IntraWeb 10, you should strongly consider migrating to IntraWeb XI soon.

IntraWeb XI

We have tried over the last months to message the reason behind IntraWeb XI, but somehow the message has not been conveyed well. IntraWeb over the years has gained a lot of legacy code including support and design decisions made around browsers as old as IE 3.0, which did not even support frames. This has created a lot of baggage in the IntraWeb source code.

IntraWeb XI is a step to eliminate much of this old code which complicates the support of IntraWeb. There are some API changes, but our target is to allow users to upgrade projects of any size in less than 15 minutes, and maintain nearly 100% run time compatibility. Some features have been removed, but they are features that do not make sense in the current Internet world, and are used by few users today.

While XI contains some new features, most features are being pushed to XII. This will further stabilize the XI code and give users more confidence moving to XI from 10, and allowing us to put the new features in XII. This will allow users to move and take advantage of the new lighter code base, while allowing others to experiment with the new features in XII betas.

Download

Download the latest version of IntraWeb XI now.

The New XI Plan

Revised from the original XI plan.

Overview

Our original plans for IntraWeb 11 are just too big to perform inone step. During the beta, we still need to maintain 10, and overall itwould prolong the development. Because of this, we have decided tosplit the original plans into IntraWeb 11, and IntraWeb 12. IntraWeb 11will be a major change in our development process moving forward.

IntraWeb XI

To differentiate this, it will be called IntraWeb XI (11 in romannumerals).

We wanted to avoid the confusing mess that some companies havecreated with version identifiers (Windows 3, 3.1 numbers, 95, 98, ME,XP, Vista, and finally back to numbers again, 7), but still somehowsignify that XI is not just the next version of IntraWeb, but a majorchange.

IntraWeb XII

IntraWeb XII is the next version after XI and will contain theintegrationwith CrossTalk and ASP.NET. IntraWeb XI lays the groundwork for thismajor step and will allow us to spend less time on maintenanceversus IntraWeb 10.

Goals

The goals of IntraWeb XI are:

  • Simplified code base for easier maintenance
  • Very high level of compatibility with IntraWeb 10
  • Provide foundation for IntraWeb XII and beyond

New – Integrated Page Mode (In progress)

More information will be posted in the future on this topic.

New – Code Cleanup and Streamlining (Completed)

Despite the fact that IntraWeb some time ago dropped support forKylix, Visual Studio.NET, and Delphi.NET there are still many IFDEFstatements and extra code left over. We generally left them because wedid not want to risk changing working code. As part if IntraWeb XI wewill remove this extra code, and refactor many areas to be much simplernow that we can focus exclusively on native VCL.

New – Simplified Build Process (Completed)

The source code tree has been simplified which makes performing builds easier.

New – More Source

We intend to ship more source code for developers to use.

New – Website (Completed)

The complete Atozed website is being redeveloped from scratch. Wewill keep the general design and layout, however the content is beingreworked from scratch. Other parts of the Atozed site have already beencompleted. Next is the IntraWeb section.

New – Unified Project Type

Services and GUI standalone can now be handled in a single project type.

Discontinued Features

IntraWeb XI will discontinue many older features to allow us tocleanthe code base. Because there aresome users using some of the discontinued features, unlike previousreleases, IntraWeb 10 will continue to be supported after IntraWeb XIis released for these features.

Discontinued – WAP and HTML 3.2

Both of these features have been mature for several years. Whilethey are supported up through IntraWeb 10, no major changes to theirfunctionality has been made since their introduction to IntraWebseveral years ago. A few users do use these features, but they addcomplexity to the code base. WAP and HTML 3.2 users will continue to besupported with our extended support of IntraWeb 10.

Discontinued – Older Browsers

We have yet to decide on what the minimum browser standards will befor IntraWeb XI. We are investigating the following based on current browser usage.

  • Firefox 3.0 – Firefox 2.0 is rarely used.
  • Internet Explorer 7. – IE 6 is waning quickly in usage in favor of 7 and 8. By thetime IntraWeb XI is released, IE 6’s numbers are expected to be veryminimal. In addition, there are several active web campaigns to eliminate supportfor IE 6. In early 2010, a mock funeral was held.
  • Chrome, Safari

Opera numbers continue to drop and are well below below 5%. Applications might run in Opera and no code will be added to prevent such, but we do not plan to make significant tests or investments in special code to run in Opera.

Discontinued – Development Environments

IntraWeb 10 supports Delphi 5 to Delphi 2010 (except Delphi 8), andC++ Builder 5 through CDS 2010. At a minimum we know that we mustsupport Delphi 7. Supporting Delphi 6 and Delphi 5 do not require muchextra effort, but do complicate the build process quite significantly.Our proposed development environment support for IntraWeb XI is asfollows. Users of discontinued environments will still be supported forIntraWeb 10. IntraWeb 10 is not being “end of lifed”.

Version Delphi C++
5 No No 6 Maybe No 7 Yes
N/A 8 No N/A 2005 No No 2006  Yes  Yes 2007 Yes Yes 2009 Yes Yes 2010 Yes Yes

These are the proposed supported environments. If there is enoughdemand for ones marked as “no”, they will be re-examined.

Discontinued – Client Side Data Sets (Completed)

These are not the VCL CSDS, but the IntraWeb ones. These use anolder technology, that we will replace at a later time using newerfunctionality now available in browsers.

Discontinued – Client Side Charts (Completed)

For the same reason as Client Side Data Sets.

Discontinued – umPartial (Completed)

umPartial was many years ahead of its time. Even today umPartial cando many things that AJAX cannot. However maintaining twoimplementations has grown quite complex. From IntraWeb XI and forward,we will continue to upgrade our AJAX support so that it can match allthe features of umPartial and also remain more powerful than other AJAXimplementations.

Discontinued – Page Mode (Completed)

IntraWeb XII will contain a new more advanced page mode with more features and better integration withapplication mode.

Discontinued – Apache DSO (Completed)

CodeGear discontinued it a long time ago and we only “unofficially”support it now, now we will fully discontinue it. Further, Apache cannow run ISAPI DLLs.

Discontinued – DynGrid (Completed)

The DynGrid depended on client side datasets (discontinued) and willbe replaced with an enhanced Silverlight based control.

Discontinued – Tracking Options (Completed)

IntraWeb 10 supports tmURL, tmHidden, and tmCookie. When thetracking options were first designed, most websites did not use cookiesand many users explicitly blocked all cookies. Browsers and websiteshave matured, and on today’s Internet, cookies are much more common. Inthose days, many users also completely disabled Javascript. BothJavascript and cookies are essential to the modern Internet. Users whowhich to control cookies, control them with granularity by monitoringthem, rather than restricting all. Corporations, instead of applyingblanket policies, enforce URL based restrictions.

Using cookies to track sessions allows IntraWeb to implement manymore features, including a better page mode that is integrated withapplication mode, and URL mapping. Because of this, all sessions inIntraWeb XI will be tracked using cookies.

Some users used tmHidden or tmURL to allow single users to runmultiple sessions in separate tabs or windows. tmCookie does not allowthis. We are aware of this need, and because of this a new property named AllowMultipleSessionsPerUser in the ServerController is being added. This will allow users to run separate sessions in each browser tab or window, yet still use cookies.