Home » Eclipse Projects » Eclipse Platform » [ANN] CodePro Studio 2.3.1 Beta Available
| [ANN] CodePro Studio 2.3.1 Beta Available [message #133247] |
Fri, 19 September 2003 15:58  |
Eclipse User |
|
|
|
Updates beta versions of CodePro Studio, CodePro Express, CodePro Advisor,
CodePro Agility and CodePro Build are now available:
http://www.instantiations.com/codepro/ws/beta/
http://www.instantiations.com/codepro/ws/beta/docs/
The 2.3.1 beta includes the following enhancements:
o Support for Eclipse 3.0 M3
o Enhanced Metrics facility
- Added many new metrics
- Added new basics metrics
- Added new complexity metrics
- Added new dependency metrics
- Added new Halstead metrics
- Enhanced Metrics view
- Added drill down in the metrics view
- Added scope changing "Go Into" command
- Added "Go To File" command
- Added "Disable Metric" command
- Ability to configure metrics from Metrics view
- Enhanced the Metrics preference page
- Added metric groups
- Added metric rule sets
- Added a "Find Metric" button
- Added thresholds and trigger points
- Added metric description page
- Added "Compute Metrics Using" command
- Enhanced HTML report
o Enhanced Code Audit view
- Enhancements to various audit rules
- 9 additional audit rules (343 total)
- Added 5 new property file audit rules
- Added 5 new XML audit rules
- Additional resolutions to fix more audit violations (63% coverage)
- Enhanced audit rule framework to handle non Java files
- Added Audit rule set Copy command
o Enhanced Collaboration Tools
- Added new commit broadcast facility
o Added a DTD for creating pattern files
See the product version history for further details...
http://www.instantiations.com/codepro/ws/beta/docs/history.h tml
--
-Eric Clayberg
Sr. Vice President of Product Development
Instantiations, Inc.
mailto:cpsws-support@instantiations.com
http://www.instantiations.com
http://www.instantiations.com/codepro/ws/
|
|
| | |
| Re: [ANN] CodePro Studio 2.3.1 Beta Available [message #133439 is a reply to message #133286] |
Fri, 19 September 2003 23:10  |
| Eclipse User |
|
|
|
"Genady" <eclipse@genady.org> wrote in message
news:bkfo9j$o91$1@eclipse.org...
>
> Why when I try to download the beta is says to me
>
> The CodeProStudio file cannot be downloaded
> by the account [username = genadyb@cs.technion.ac.il]
> because your evaluation or support period has expired.
Indeed it has. We normally allow folks to evaluate our products for 30 days.
If that isn't enough time, we will happily extend the eval period for some
reasonable, mutually agreed upon period (even 90 days or more for some
folks). What we want to avoid, however, are situations where folks serially
evaluate the product over and over again and never buy anything from us.
> Do I need to contact you each time a new beta is released?
I note that you have evaluated the product for 30 days several times over
the last couple of years. If you are seriously interested in potentially
buying the product, then by all means contact us for another evaluation
period.
If you are interested in the product, but it's outside of your price range,
we might be able to come up with some other arrangement. For example, we are
always looking for new audit rules and design patterns. Build a couple of
audit rules for us or a pattern or two, and I will give you a free license.
Introduce us (e.g., help us set up a web cast or other meeting) to a company
that might want twenty or more copies of our product, and I will give you a
free license. Help us close a deal for ten copies of more, and I will give
you a free license. Or, come up with something equally creative and mutually
beneficial.
> I believe the betas are time limited anyway ...
They aren't, but the overall eval period is. We are a small, commercial
software products company. Our business is selling software, and while I
would love to give the stuff away, I can't feed my family that way.
-Eric Clayberg
Sr. Vice President of Product Development
Instantiations, Inc.
mailto:cpsws-support@instantiations.com
http://www.instantiations.com
http://www.instantiations.com/codepro/ws/
|
|
| |
| Re: [ANN] CodePro Studio 2.3.1 Beta Available [message #133508 is a reply to message #133452] |
Sat, 20 September 2003 08:55 |
| Eclipse User |
|
|
|
Originally posted by: vkyr.nospam-ision.net
"Eric Clayberg" <clayberg@instantiations.com> schrieb im Newsbeitrag
news:bkghib$a81$1@eclipse.org...
> "Valentino Kyriakides" <vkyr@nospam-ision.net> wrote in message
> news:bkfq77$q5l$1@eclipse.org...
> > Seems Instantiations still has this limited (somehow user puzzling)
based
> > account system they had before. - I once gave up for looking after their
> > tools, even they might have made great progress in the meantime, since I
> > always also over and over run into the same accounting problems. You
> always
> > had to send emails and renew old contact data in order to get any valid
> > account login data and to be able to fetch a demo afterall.
>
> Actually, all you ever had to do was contact me. I gave you a free
one-year
> license to the product about 18 months ago and would have happily renewed
it
> for you had you asked. Send me an e-mail.
It's correct that I once got a better longer time access login account
license for your web server from you, which allowed to download updates of
the tryouts over some longer period. However, what I meant here related to
the post of Genady was related to your web server download access section
and maybe I didn't expressed it very well. So let me try to give a better
description of what I meant.
Since all the Instantiations software products already have a build in
demo/full version time based license management protection (right?), I
always wondered that in order to download a demo/tryout version from the
Instatiations web server's download section one always needs again also a
special account/password, which is again time limited (it's a sort of double
time limited protection here). - Wouldn't it be Ok to let people request a
demo/tryout via a fillout page and then send them a demo key via email and
the URL where they can download the demo from?
> > To Eric I would recommend, to manage that his company eases and changes
> this
> > sort of limited log in account process for people who are interested in
> > their dev tools!
>
> What would you suggest as an alternative? If we allowed folks to evaluate
> the product for an indefinite period, what incentive would they have for
> buying anything?
Eric I think we misunderstood each other here. Of course Instantiations has
to protect it's intellectually work from piracy etc. and it's natuaral that
you want to sell the fruits of your hard work. - In my understanding each
Instanciations product has defacto a build in license protection scheme,
which determines if a given serial key is a time limited demo/tryout key or
a purchased full version key, right? So your servers download section for
fetching tryouts wouldn't need a seperate account/license key scheme just in
order to download a demo, or?
> As I explained to Genady, we have to be able to sell our
> products in order to stay in business. If you compare our eval process to
> those in place at other commercial software companies, it is very simple
and
> (for the most part) automated. Many of our commercial competitors require
> you to speak with a sales rep *before* you get an eval license key (which
> might only be good for 15 days at that).
Yes I agree here, but it wasn't usually the point I meant. AFAI remember
your products have a build in protection scheme and if somebody requests a
demo/tryout version she/he will get a demo key for the software and can then
download the demo from some place of your server. - But in order to be able
to download a demo version at all, one again needs an account/license key
pair for your webserver, which is also time limited. It's this second point
I meant, why always this double protection scheme if the software is already
protected and time limited? - Did you made bad experiences the other
(...easier to download tryouts...) way around?
Hope you can catch and better understand now what I usually meant, if not
drop me an email and I try explain it better.
Regards
Valentino
|
|
|
| Re: [ANN] CodePro Studio 2.3.1 Beta Available [message #133599 is a reply to message #133508] |
Sun, 21 September 2003 09:22 |
| Eclipse User |
|
|
|
"Valentino Kyriakides" <vkyr@nospam-ision.net> wrote in message
news:bkhihu$uto$1@eclipse.org...
>
> Since all the Instantiations software products already have a build in
> demo/full version time based license management protection (right?)
License keys come in two forms - time-based (for evals) and permanent (for
purchases). The file that you download is the same whether you buy the
product or evaluate it.
> I always wondered that in order to download a demo/tryout version from the
> Instatiations web server's download section one always needs again also a
> special account/password, which is again time limited (it's a sort of
double
> time limited protection here). - Wouldn't it be Ok to let people request
a
> demo/tryout via a fillout page and then send them a demo key via email and
> the URL where they can download the demo from?
The same download control system is used for evaluator and purchasers. When
you buy the product, you get 90 days of tech support and downloads included
in the price. The product may also be purchased with a year of support and
upgrade protection. Every download account is time-limited to some period -
whether it be a year in the case of a purchase with tech support or 30 days
for an evaluation. When a purchaser renews their tech support for anther
year, their download access is renewed for another year.
With your suggestion above, what would prevent someone from requesting a new
eval every 30 days, or easily accessing updates after their support period
has expired? We do major updates every 2-3 months (~5 times a year) with
beta updates every couple of weeks. With the volume of new features and
enhancements we are adding, there is a real incentive for purchasers to get
support and upgrade protection in order to receive the stream of updates.
Time-limited download accounts (which are very common with other vendors as
well) gives us a way to control that.
That said, we are always open to better ideas that would make it easier for
folks to evaluate the product while still protecting us from serial
evaluators who merely want to use the product long term without paying for
it. We also want to make sure that their is an incentive for purchasers to
renew their support contracts in order to retain access to the update
stream.
> Eric I think we misunderstood each other here. Of course Instantiations
has
> to protect it's intellectually work from piracy etc. and it's natuaral
that
> you want to sell the fruits of your hard work. - In my understanding each
> Instanciations product has defacto a build in license protection scheme,
> which determines if a given serial key is a time limited demo/tryout key
or
> a purchased full version key, right?
Correct.
> So your servers download section for fetching tryouts wouldn't need a
> seperate account/license key scheme just in order to download a demo, or?
Correct. Purchasers and evaluators download the same files. The only
difference is whether the license key unlocks the product for 30-days or
permanently.
> Yes I agree here, but it wasn't usually the point I meant. AFAI remember
> your products have a build in protection scheme and if somebody requests a
> demo/tryout version she/he will get a demo key for the software and can
then
> download the demo from some place of your server. - But in order to be
able
> to download a demo version at all, one again needs an account/license key
> pair for your webserver, which is also time limited. It's this second
point
> I meant, why always this double protection scheme if the software is
already
> protected and time limited? - Did you made bad experiences the other
> (...easier to download tryouts...) way around?
Yes. Our biggest concern is how best to prevent folks from serially
evaluating the product without ever buying anything. Here are our general
requirements:
1) Make it easy for a new evaluator to try the product for some fixed time
period
2) Make it easy for us to extend someone's evaluation period if they
genuinely need more time
3) Make it hard for folks to serially evaluate (use) the product without
making a decision
4) Make it easy for purchasers to download updates during their support
period
5) Make it hard for purchasers to download updates after their support
period has expired
6) Make it easy for us to follow up with evaluators to provide support,
training (e.g., webcasts) and sales assistance during the evaluation period
I'm sure there are lots of ways to achieve each individual goal, but we need
to satisfy all of the above goals at once. Thus, there is a constant tension
between making things too easy or too hard. Making it too easy to evaluate
the product would make it hard to sell the product. Conversely, making it
too hard to evaluate the product would also make it hard to sell the
product.
Specific suggestions for overhauling the entire evaluation, licensing and
download access system are welcome. We are not wedded to the one we have. In
fact, as an incentive to folks out there reading this, I will give anyone
who makes a suggestion that we end up implementing a free license to the
product. Post them here or send me e-mail.
-Eric Clayberg
Sr. Vice President of Product Development
Instantiations, Inc.
mailto:cpsws-support@instantiations.com
http://www.instantiations.com
http://www.instantiations.com/codepro/ws/
|
|
| |
| Re: [ANN] CodePro Studio 2.3.1 Beta Available [message #133982 is a reply to message #133599] |
Mon, 22 September 2003 15:40 |
| Eclipse User |
|
|
|
Originally posted by: vkyr.nospam-ision.net
"Eric Clayberg" <clayberg@instantiations.com> schrieb im Newsbeitrag
news:bkk8kh$mis$1@eclipse.org...
> ...
> ...
> The same download control system is used for evaluator and purchasers.
When
> you buy the product, you get 90 days of tech support and downloads
included
> in the price. The product may also be purchased with a year of support and
> upgrade protection. Every download account is time-limited to some
period -
> whether it be a year in the case of a purchase with tech support or 30
days
> for an evaluation. When a purchaser renews their tech support for anther
> year, their download access is renewed for another year.
Ah that makes it clearer, so I see and understand now why and where the
difference is. - Before it wasn't obvious to me, that you use the server
side time limited download account for tryout or purchase tech support
tracking too. I always thought that the support (not meaning updates or new
releases here, just help support etc.) for a purchased version of one of
your software products isn't time limited.
> With your suggestion above, what would prevent someone from requesting a
new
> eval every 30 days, or easily accessing updates after their support period
> has expired?
1. Folks who once requested a trial/demo of the software are collected in a
sort of database.
2. The serials/key files for a software are time limited and should be
changed periodically for updates and new releases. This also makes it at
least a little bit more difficult for crackers to setup an always working
universal key code geneartor or the like.
Related to the above mentioned point 1. and your "...what would prevent
someone from requesting a new eval every 30 days..." now. If some bad minded
person fakes his contact data and email address that's again no protection
and that person will sure get a new 30 day eval.
> We do major updates every 2-3 months (~5 times a year) with
> beta updates every couple of weeks. With the volume of new features and
> enhancements we are adding, there is a real incentive for purchasers to
get
> support and upgrade protection in order to receive the stream of updates.
> Time-limited download accounts (which are very common with other vendors
as
> well) gives us a way to control that.
Yes, it's better than nothing related to protection, even I think this
approach (as most others too) has also it's weaknesses.
> That said, we are always open to better ideas that would make it easier
for
> folks to evaluate the product while still protecting us from serial
> evaluators who merely want to use the product long term without paying for
> it. We also want to make sure that their is an incentive for purchasers to
> renew their support contracts in order to retain access to the update
> stream.
> ...
> ...
> ...
> Yes. Our biggest concern is how best to prevent folks from serially
> evaluating the product without ever buying anything. Here are our general
> requirements:
>
> 1) Make it easy for a new evaluator to try the product for some fixed time
> period
> 2) Make it easy for us to extend someone's evaluation period if they
> genuinely need more time
> 3) Make it hard for folks to serially evaluate (use) the product without
> making a decision
> 4) Make it easy for purchasers to download updates during their support
> period
> 5) Make it hard for purchasers to download updates after their support
> period has expired
> 6) Make it easy for us to follow up with evaluators to provide support,
> training (e.g., webcasts) and sales assistance during the evaluation
period
>
> I'm sure there are lots of ways to achieve each individual goal, but we
need
> to satisfy all of the above goals at once. Thus, there is a constant
tension
> between making things too easy or too hard. Making it too easy to evaluate
> the product would make it hard to sell the product. Conversely, making it
> too hard to evaluate the product would also make it hard to sell the
> product.
I fully agree. - However, the harder thing is -as always- to find the best
golden middle way which will please both sides of the named coin.
> Specific suggestions for overhauling the entire evaluation, licensing and
> download access system are welcome. We are not wedded to the one we have.
In
> fact, as an incentive to folks out there reading this, I will give anyone
> who makes a suggestion that we end up implementing a free license to the
> product. Post them here or send me e-mail.
Well, I for my part think, that if I would find an optimal general solution
to this problem domain, I would better build a product out of it and sell it
as an product to you and other companies who may suffer from these problems.
And as an prove of the quality for the found solution (the specific
protection/security product), I would of course apply it on itself for
demostration purposes. ;-). - Not really meant seriously, even it might be
some thoughts worth!
Regards
Valentino
|
|
|
| Re: [ANN] CodePro Studio 2.3.1 Beta Available [message #134003 is a reply to message #133439] |
Mon, 22 September 2003 20:38 |
| Eclipse User |
|
|
|
This is an interesting issue and vendors choose different approaches.
BEA, for example, make 30 day evals freely available whilst Parasoft
do three day evals of their JTest product and also seem to be successful.
A few years ago I evaluated the predecessor product (VAssist) and
was very impressed with it. I subsequently purchased ten copies of the
low end edition for my then team. Sometime later I was interested in
forming a view as to whether the (then new) Eclipse product added value
to the (better) Eclipse IDE. After some frustration with expired paswords I
was able to do this, but didn't elect to purchase (the team chose a
different IDE.)
I'm now in a different team (same employer) and we're standardizing on
Eclipse. I'd like to know how much value the new CodeStudio product offers,
though
when I last attempted to register and download I received a form email
pointing out
that I'd already evaluated the product in the past.
I don't know whether you've already been bitten by the serial demo
downloader problem, but if so, this would seem to be a fairly easy thing to
detect.
My suspicion is that the current approach reduces your pool of potential
customers.
my two cents,
Peter Booth.
"Eric Clayberg" <clayberg@instantiations.com> wrote in message
news:bkggcq$9hs$1@eclipse.org...
> "Genady" <eclipse@genady.org> wrote in message
> news:bkfo9j$o91$1@eclipse.org...
> >
> > Why when I try to download the beta is says to me
> >
> > The CodeProStudio file cannot be downloaded
> > by the account [username = genadyb@cs.technion.ac.il]
> > because your evaluation or support period has expired.
>
> Indeed it has. We normally allow folks to evaluate our products for 30
days.
> If that isn't enough time, we will happily extend the eval period for some
> reasonable, mutually agreed upon period (even 90 days or more for some
> folks). What we want to avoid, however, are situations where folks
serially
> evaluate the product over and over again and never buy anything from us.
>
> > Do I need to contact you each time a new beta is released?
>
> I note that you have evaluated the product for 30 days several times over
> the last couple of years. If you are seriously interested in potentially
> buying the product, then by all means contact us for another evaluation
> period.
>
> If you are interested in the product, but it's outside of your price
range,
> we might be able to come up with some other arrangement. For example, we
are
> always looking for new audit rules and design patterns. Build a couple of
> audit rules for us or a pattern or two, and I will give you a free
license.
> Introduce us (e.g., help us set up a web cast or other meeting) to a
company
> that might want twenty or more copies of our product, and I will give you
a
> free license. Help us close a deal for ten copies of more, and I will give
> you a free license. Or, come up with something equally creative and
mutually
> beneficial.
>
> > I believe the betas are time limited anyway ...
>
> They aren't, but the overall eval period is. We are a small, commercial
> software products company. Our business is selling software, and while I
> would love to give the stuff away, I can't feed my family that way.
>
> -Eric Clayberg
> Sr. Vice President of Product Development
> Instantiations, Inc.
> mailto:cpsws-support@instantiations.com
> http://www.instantiations.com
> http://www.instantiations.com/codepro/ws/
>
>
|
|
| |
| Re: [ANN] CodePro Studio 2.3.1 Beta Available [message #134121 is a reply to message #133982] |
Mon, 22 September 2003 23:03 |
| Eclipse User |
|
|
|
"Valentino Kyriakides" <vkyr@nospam-ision.net> wrote in message
news:bknj13$e3q$1@eclipse.org...
>
> Ah that makes it clearer, so I see and understand now why and where the
> difference is. - Before it wasn't obvious to me, that you use the server
> side time limited download account for tryout or purchase tech support
> tracking too. I always thought that the support (not meaning updates or
new
> releases here, just help support etc.) for a purchased version of one of
> your software products isn't time limited.
We will generally answer product questions and take bug reports from anyone
using or evaluating the product. When someone purchases support from us (and
most product purchasers do), they get several things:
1) Priority technical support (7 days a week) - we will address their
problems before doing anything else
2) Access to all major updates during the support period (e.g., upgrade
protection) - approximately 4-5 per year
3) Access to all beta versions (which we refresh every couple of weeks) -
approximately 20 updates per year
4) Direct engineering access in order to request new features (for example,
we added >100 new audit rules in our 2.2 release with more than half of them
direct customer requests)
> 1. Folks who once requested a trial/demo of the software are collected in
a
> sort of database.
We do that now.
> 2. The serials/key files for a software are time limited and should be
> changed periodically for updates and new releases.
Eval keys are time limited by default for 30-days, but can be set for any
reasonable period requested by the evaluator. We do a lot of 45-day evals
and some 60-day evals. The purchased product keys are not time limited. We
do occasionally change the serial number scheme for a major update
(supported customers get the new keys for free), but avoid changing the
serial number keys too often as that causes a license key distribution
problem for our large customers.
> I fully agree. - However, the harder thing is -as always- to find the
best
> golden middle way which will please both sides of the named coin.
Indeed. We are always looking for the right balance.
-Eric Clayberg
Sr. Vice President of Product Development
Instantiations, Inc.
mailto:cpsws-support@instantiations.com
http://www.instantiations.com
http://www.instantiations.com/codepro/ws/
|
|
|
| Re: [ANN] CodePro Studio 2.3.1 Beta Available [message #134147 is a reply to message #133286] |
Tue, 23 September 2003 02:19 |
| Eclipse User |
|
|
|
Hi!
I think Instantiations can do everything they consider opportune
to protect your software, and the potential clients are free to
opt or not to agree the Instantiations policy (and obviously,
opine about this policy). The time will confirm Instantiations
if your policy is useful or not.
IMHO the Instantiations policy is tedious for the tester. But
Instantiations have the right to use this policy, and I have the
right to not solicit more evaluations.
Francesc
Genady wrote:
> Eric,
> Why when I try to download the beta is says to me
> The CodeProStudio file cannot be downloaded
> by the account [username = genadyb@cs.technion.ac.il]
> because your evaluation or support period has expired.
> Do I need to contact you each time a new beta is released?
> I believe the betas are time limited anyway ...
> Genady
> Eric Clayberg wrote:
> > Updates beta versions of CodePro Studio, CodePro Express, CodePro Advisor,
> > CodePro Agility and CodePro Build are now available:
> >
> > http://www.instantiations.com/codepro/ws/beta/
> > http://www.instantiations.com/codepro/ws/beta/docs/
> >
> > The 2.3.1 beta includes the following enhancements:
> >
> > o Support for Eclipse 3.0 M3
> > o Enhanced Metrics facility
> > - Added many new metrics
> > - Added new basics metrics
> > - Added new complexity metrics
> > - Added new dependency metrics
> > - Added new Halstead metrics
> > - Enhanced Metrics view
> > - Added drill down in the metrics view
> > - Added scope changing "Go Into" command
> > - Added "Go To File" command
> > - Added "Disable Metric" command
> > - Ability to configure metrics from Metrics view
> > - Enhanced the Metrics preference page
> > - Added metric groups
> > - Added metric rule sets
> > - Added a "Find Metric" button
> > - Added thresholds and trigger points
> > - Added metric description page
> > - Added "Compute Metrics Using" command
> > - Enhanced HTML report
> > o Enhanced Code Audit view
> > - Enhancements to various audit rules
> > - 9 additional audit rules (343 total)
> > - Added 5 new property file audit rules
> > - Added 5 new XML audit rules
> > - Additional resolutions to fix more audit violations (63%
coverage)
> > - Enhanced audit rule framework to handle non Java files
> > - Added Audit rule set Copy command
> > o Enhanced Collaboration Tools
> > - Added new commit broadcast facility
> > o Added a DTD for creating pattern files
> >
> > See the product version history for further details...
> >
> > http://www.instantiations.com/codepro/ws/beta/docs/history.h tml
> > --
> > -Eric Clayberg
> > Sr. Vice President of Product Development
> > Instantiations, Inc.
> > mailto:cpsws-support@instantiations.com
> > http://www.instantiations.com
> > http://www.instantiations.com/codepro/ws/
> >
> >
|
|
|
Goto Forum:
Current Time: Sun May 11 13:03:16 EDT 2025
Powered by FUDForum. Page generated in 0.05043 seconds |
Home