[ https://issues.jboss.org/browse/TEIIDDES-1119?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1119: ---------------------------------------- IRC conversation... {code} (10:30:57 AM) phantomjinx: I am saving the imported meds (those for teiid) to the hiddenProject/imported (10:31:17 AM) phantomjinx: yet the userMeds are saved to the plugin's runtime directory (10:31:39 AM) phantomjinx: I'm kinda evenly split on which they should be saved to (10:31:47 AM) phantomjinx: the imported ones I mean (10:32:00 AM) blafond: Is it time to implement the concept of a User Global Workspace folder? (10:32:19 AM) blafond: outside of Eclipse? (10:32:35 AM) phantomjinx: No. I don't think so. I just think one or other rather than both (10:33:07 AM) blafond: well for now, then maybe use runtime directory too (10:33:17 AM) phantomjinx: The userMed directory is outside of eclipse in that its on the actual filesystem (10:33:38 AM) phantomjinx: ... and does actually require the workspace to be loaded which was a worry about 2 hours ago (10:33:43 AM) blafond: Though I still hate the issues with switching workspaces and having to sync profiles, servers, MEDs by hand (10:33:47 AM) phantomjinx: doesnt even (10:34:08 AM) phantomjinx: How often do you switch workspaceS? (10:34:26 AM) ***phantomjinx has never switched workspace since starting on the designer project (10:34:31 AM) blafond: I don't at the moment. But I'd really like to (10:34:57 AM) blafond: My "developer" perspective is probably different than customers/users (10:35:18 AM) phantomjinx: no reason we can't create an exporter that save 'everything' to a jar then imports it back into a new workspace (10:35:37 AM) phantomjinx: like eclipse can do with the preferences (10:35:50 AM) blafond: I'd like to have the ability to create a new Workspace to work on testing certain use-cases and be able to Select my global folder and have my CP's already usable, have my custom MEDS usable, etc... (10:36:29 AM) phantomjinx: its just an import/export algorithm so could keep a jar stored in $HOME, create new workspace, import jar (10:36:55 AM) phantomjinx: update jar = load workspace, export stuff to existing jar (10:37:05 AM) blafond: But if I add a new CP for testing, I have to "Export" the whole set of info to the jar for re-import (10:38:16 AM) phantomjinx: A connection profile consists of what? (10:38:35 AM) phantomjinx: some properties ... some jars for the driver (10:38:39 AM) blafond: XML definition (could be binary or text) plus actual jars (10:39:55 AM) phantomjinx: yeah ... as long as an export/import pair can be implemented for all bits and pieces the result will be a single file (eg. *.mytdstuff) that can be loaded into a different workspace (10:39:56 AM) blafond: vision for Komodo is to handle this via the persisted MS workspace tree which will include Data Source/Connection Definition (10:40:25 AM) phantomjinx: well it may be useful to really sort this then, especially the interface (10:40:46 AM) phantomjinx: since the latter will be really useful for komodo and only its implementations will be different (10:41:24 AM) blafond: I'm still not convinced that having a common non-zip'd folder won't be better... and could offer options to create/archive snapshots of this folder which can be used to overide (10:41:51 AM) phantomjinx: If you prefer a directory then that is just an implementation detail (10:42:22 AM) blafond: concept is to get get away from .metadata schstuff (10:43:00 AM) blafond: Maybe this is an Eclipse contribution/concept complete with API and extension points {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)