Next version news...

[laseray]

Hi,

It has been quite a while since the last version. Not to worry, work
is being done on a new version. At this point it is too preliminary,
with many little tweaks needed before it is ready for prime time.

There will be a beta version, with some things unfinished/partially
implemented so that users can get some use out of the new features.
Plus, given that it will not be near completion at that point I can
have some useful feedback about what to fix going forward. Following
the beta there will be a (series of) release candidate(s) where more
fixes will be put in place, made possible in part from valuable user
comments (you will all be my translator guinea pigs! :) ).

It could still be a few weeks now before the beta, but I am coming
closer to freezing the features and settling on what to put out.

Thanks for your patience, I'm certain you will really like the new
stuff to come...

Cheers,

Raymond

[Sadi]

Hi Raymond,

(For your consideration during the run-up to the next version of OmegaT
+)

IMHO it might be helpful to develop a methodology for quickly
incorporating Pluses to OmegaT source codes so as to keep pace with
the developments in OmegaT.

In this way, there might be more frequent releases of OmegaT+ more in
line with OmegaT , although many of these releases might be merely
preserving the existing Plus features of OmegaT+ but offering the
newly developed features in OmegaT quicker to OmegaT+ users.

Kind regards,

Sadi

[laseray]

Hi Sadi,

On Feb 10, 6:48 am, Sadi <sadiyumu...@gmail.com> wrote:
> (For your consideration during the run-up to the next version of OmegaT
> +)
>
> IMHO it might be helpful to develop a methodology for quickly
> incorporating Pluses to OmegaT source codes so as to keep pace with
> the developments in OmegaT.
>
> In this way, there might be more frequent releases of OmegaT+ more in
> line with OmegaT , although many of these releases might be merely
> preserving the existing Plus features of OmegaT+ but offering the
> newly developed features in OmegaT quicker to OmegaT+ users.

I know you intend well by writing this, but the reality is that many
of the features in OmegaT(OT), that may or may not be in OmegaT+, now
or in the future, are just not very well thought out. In fact, this is
one reason why it takes long between versions of OmegaT+. I have to
carefully go over all code changes that are made in OT to a feature I
am considering to add and then rewrite, if not completely replace,
code due to a lack of quality. Those features may work on the surface,
but I see much evidence of maintenance problems and insufficient
reasoning before they are added in.

I am actually focused on doing things differently than OT going
forward. Plus, there are significant parts of the code in OmegaT+ that
are different than OT now that make it near impossible to just take a
feaure and copy/paste it into place. Implementing some method of
keeping pace, so to speak, would be a lot more work than it is worth.

Of course, more features from OT will be added, but with more effort
towards quality over quantity. And note there are more applications
and other things to take features and ideas from that can go in the
program than just OT.

We can add all the little incremental improvements we like, but where
are the big ideas for this technology that can make a large
difference? Let us try to find some of those also.

Raymond

[Sadi]

Hi Raymond,

Thanks for the info, I understand you better now...

Regards,

Sadi