This is a great list. Can you codify that in a wiki page? Say Touchpoint Use Cases or some such? That would be really useful for pulling together all the things that need to be done in touchpoints.
Jeff James D Miles <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 08/08/2007 01:57 PM Please respond to Equinox development mailing list <[email protected]> To Equinox development mailing list <[email protected]> cc Subject Re: [equinox-dev] [prov] Native touchpoint I have no idea how these fit into the new scheme. But I will attempt to explain some of the ways we used install handlers and some of the real constraints. - We manage launch parameters through install handlers. This includes the management of a global property file and a user property file. The user property file is modified during the enable phase. For the multiuser case, it is easy to upgrade a user files during an enable/disable phase. It is not really possible to do this during the install by an admin. There has also been discussion that the enable handlers should be immutable (not depend a known state). - We manage JVM features. This had to be done slightly differently because JVM features have so many non-standard properties, We added and manage a plugin property file for these. While this has worked well for us it has a few thorns. There is a question of how to override the JVM properties from the command line or more generally how to combine JVM properties coming from this file and other places. When we attempt to integrate these features into the tooling we have the same questions. - We manage the branding through the property files modified by install handlers. - To some degree we also manage what gets launched. There may be multiple ICONS that represent different launch configurations. The ICON command length is limited so there needs to be an abstraction to handle this. - We manage the invocation of native exe's and bat and .sh. These are a problem because we usually lose the ability to track operations, log errors, etc. - We have also worked on managing native service states through install handlers so that it can be upgraded/installed like any other feature/plugin. Other use cases - There is a need to be able to just unzip a platform and run. This likely implies that there is a need to do dynamic configuration on the first launch for a user. - For multiuser there is a need to be able to know if we are an admin installing into all the shared spaces or if we are just a user launching the platform. The actions performed are different. Chris Aniszczyk/Austin/[EMAIL PROTECTED] Chris Aniszczyk/Austin/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 08/07/2007 09:07 PM Please respond to Equinox development mailing list <[email protected]> To Equinox development mailing list <[email protected]> cc Subject Re: [equinox-dev] [prov] Native touchpoint James can expand, but some things that I recall from a declarative system we built on top of the old installhandler code: * copying files (ie., we package our own launcher and copy it to a proper location... we also package vms as bundles) * native operations * creating icons in menus or on a desktop if available * creating windows registry entries * setting environment variables * modifying files on disk * chmod'ng things * running arbitrary scripts (ya, I know, scary) like .bat or .sh's That's all I can remember off the top of my head. Cheers, --- Chris Aniszczyk | IBM Lotus | Eclipse Committer | http://mea-bloga.blogspot.com | +1.860.839.2465 Pascal Rapicault ---08/07/2007 08:56:18 PM---James, to enlight us, could you please describe the kind of things that you From: Pascal Rapicault <[EMAIL PROTECTED]> To: Equinox development mailing list <[email protected]> Cc: [email protected], [EMAIL PROTECTED] Date: 08/07/2007 08:56 PM Subject: Re: [equinox-dev] [prov] Native touchpoint James, to enlight us, could you please describe the kind of things that you are doing with install handlers? James D Miles <[EMAIL PROTECTED] om> To Sent by: <[email protected]> equinox-dev-bounc cc [EMAIL PROTECTED] Subject [equinox-dev] [prov] Native 08/07/2007 04:41 touchpoint PM Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> Please either add javadoc info or wiki info on the design of the org.eclipse.equinox.prov.touchpoint.natives and . This appears to be where install handler equivalent functionality would be performed. I don't need extensive docs. I just need to know the plan so I can evaluate how it can be used. We use the install handlers extensively in the current eclipse and I am attempting to locate the home for this functionality. Also is Rhino JavaScript envisioned to be the main scripting mechanism for the native touchpoint?_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
