Re: [cross-project-issues-dev] Policy for examples - and sdk's

[Hubert H Leung <hkyleung@xxxxxxxxxx>]

For TPTP, we have the distinction between
user vs ISV documentation and examples.  User documentation and examples
are for end users of the product, which will be translated.  ISV documentation
and examples target extenders/exploiters of the project.  ISV docs
and examples won't be translated.  With this definition, user documentation
and example are considered runtime, and are included in the callisto update
site.  The ISV docs are example are packaged as part of the SDK and
are currently not part of Callisto.  


_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382

Randy Hudson <hudsonr@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/06/2006 11:18 PM

Please respond to
Cross project issues

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>, cross-project-issues-dev-bounces@xxxxxxxxxxx
Subject	Re: [cross-project-issues-dev] Policy for examples - and sdk's

I disagree on the "extender" examples.  The Eclipse Project
and the GEF Project have always kept such examples separate. I think it
makes sense to allow experienced clients to download just the "SDK",
and NOT have it pollute the UI with wizards, action sets, and bogus editors
for common file types (e.g. xml). It's also a smaller download, if all
I am trying to do is step through your code in the debugger.

Also, I think some commercial products have install options which include
"SDK" features instead of just the runtimes.

-Randy

Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/06/2006 09:11 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>, cross-project-issues-dev-bounces@xxxxxxxxxxx
Subject	Re: [cross-project-issues-dev] Policy for examples - and sdk's

This helps. We now need to have those guidelines followed by all the callisto
projects :-) 
The example I had in mind at the time was VE, where I don't think the examples
bring any particular value to the user. 

PaScaL

David M Williams <david_williams@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/06/2006 05:24 PM

Please respond to
Cross project issues

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject	Re: [cross-project-issues-dev] Policy for examples - and sdk's

I suspect the answer is entirely who the auidenance is ... if for "end
user" then good policy to be part of "runtime" (which also
includes "user doc" (from a callisto point of view ... doesn't
mean that under the covers it might be in a seperate feature/plugin, for
those that literally want just some minimum runtime). 

But if for an "extender", then ... SDK. (and source and ISV doc
included with SDK). 

And in general, I think from Callisto's point of view ... should just be
"runtimes" and "SDKs" ... with the biggest distinction
being the audience of "end users" vs. "extenders" ..
but, I'm sure, there's fuzzy areas. 


Does this help? Have any examples in mind? (is that a pun?)

Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/06/2006 04:21 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject	[cross-project-issues-dev] Policy for examples

Having played around with the content from the callisto site, I would like
to know what is the policy for projects to make their examples available:
- are they coming in the "runtime" feature?
- are they part of the SDK feature? 
- are they coming separetly? 

PaScaL_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev