Highlander, Together and unit testing - and OTA


I wonder if it is possible to say something already now about
Highlander and perhaps also about future versions of BDS (CDS?)

The reason is that I have become addicted to unit testing and
interactive design.

Besides of programming in Delphi, I also use Visual Studio. For Visual
Studio, there already is a lot of applications/tools that integrate
with the IDE. I am convinced this is the future, and since Delphi has
its OTAPI - I am curious to know if this will be better documented to
tempt software makers to write add-ins for Delphi.

For VS there already are add-ins for doing semi automated unit testing,
and I just can't live without it anymore.

Now UML, having spent days, even weeks trying many UML tools, I
stumbled across the product everyone (at least many here :) disables or
uninstalls prior to running BDS. To make I long story short - I just
love the product, that is the stand-alone Together for VS 2005.
I can't live without this anymore either.

The question is whether the "CodeGear Together" is different from the
stand-alone product, and if they have parted, going their own separate
ways. The question also is whether the Together integration in Delphi
will support "live source" and the ability to generate sequence
diagrams from the source, like you can in the VS 2005 version.


--
Ingvar Nilsen
http://www.ingvarius.com
.

Relevant Pages

  • Re: Delphi Product Manager questioned
    ... they need to support in order for BDS to be considered a viable alternative ... DevCo will get more resources, I'm not certain it will be enough. ... with those that have suggested similar for Delphi pretty much from its start ... a mixed-mode compiler would address many of the .NET interop issues ...
    (borland.public.delphi.non-technical)
  • Re: Delphi Product Manager questioned
    ... To me the choice of Delphi is effectively a "lock-in" to Windows ... because adoption might take 6 months to a year that BDS can afford to ... Developers need time to learn new things and to figure ... MS can just kill interop when they want and then it's going to be ...
    (borland.public.delphi.non-technical)
  • BDS 2006 brings blind Delphi programmers back into the game!
    ... I just wanted to send a note thanking DevCo - excuse me, still Borland - for putting MSAA support into the ActionBand driven menus of BDS 2006! ... For those of you who are not familiar with MSAA: MSAA (Microsoft Active Accessibility) is a technology that allows special software for the blind or visually impaired, screen readers or screen magnifiers, access to otherwise very graphical or in other way inaccessible UI components. ... Since Delphi 4 or 5, this is the first version that adds, not removes, accessibility features for blind or visually impaired Delphi programmers. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi and the ALM vision?
    ... ALM strategy: Why does Borland continue to develop it's own C++ compiler? ... > By underwriting BDS development costs, making Delphi cheaper to produce. ... BDS, not Delphi. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi Product Manager questioned
    ... Delphi was able to do "more" than MS in many areas, ... I beleive this can happen again with dotNET, ... it ignores the more recent historical events of BDS' current .NET support. ... Tough decisions have to be made in tough ...
    (borland.public.delphi.non-technical)