(Sorry, I sent this first from the wrong email address.) Dear Oxygen people, First a note of encouragement... I recently talked a coworker into trying the Oxygen XSLT tracer. Soon after that, I heard from our boss that she finds it really useful. (She was already an Oxygen user, but didn't know how to start the XSLT tracer.) Also, this past week our boss ordered two additional copies of Oxygen for our team. Several of us are learning XSLT, and I had told him how much it helps to be able to see what's going on when you're not confident of how XSLT works. I told him you could get an XSLT tracer with Oxygen for under $100, or go with XMLSpy Professional for $500. That made it a no-brainer. :-) Now the feature request: In Oxygen projects, I usually "Link to external folders". That works just right for me, but it also brings in certain files I don't want to clutter up my Project pane... like my .svn folders and *.bak files. Can there be a setting to let us specify filename patterns that the Project pane will ignore? Thanks, Lars
Dear Lars, Thank you for the encouragement and appreciation. We added the feature request to our bugzilla but not with a high priority. That means it will not go in the upcoming release. It seems common practice that the files listed in all the folders of one project are covered by a relatively small set of filename patterns. As a consequence we may provide the possibility to edit a list of patterns applied to all linked folders of the project that will define the set of all *allowed* filenames. What do you think ? -- Best regards, Sorin <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com/ Lars Huttar wrote:
(Sorry, I sent this first from the wrong email address.)
Dear Oxygen people,
First a note of encouragement... I recently talked a coworker into trying the Oxygen XSLT tracer. Soon after that, I heard from our boss that she finds it really useful. (She was already an Oxygen user, but didn't know how to start the XSLT tracer.) Also, this past week our boss ordered two additional copies of Oxygen for our team. Several of us are learning XSLT, and I had told him how much it helps to be able to see what's going on when you're not confident of how XSLT works. I told him you could get an XSLT tracer with Oxygen for under $100, or go with XMLSpy Professional for $500. That made it a no-brainer. :-)
Now the feature request: In Oxygen projects, I usually "Link to external folders". That works just right for me, but it also brings in certain files I don't want to clutter up my Project pane... like my .svn folders and *.bak files. Can there be a setting to let us specify filename patterns that the Project pane will ignore?
Thanks, Lars
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
On Tuesday 12 April 2005 09:09, Sorin Ristache wrote:
We added the feature request to our bugzilla but not with a high priority. That means it will not go in the upcoming release. It seems common practice that the files listed in all the folders of one project are covered by a relatively small set of filename patterns. As a consequence we may provide the possibility to edit a list of patterns applied to all linked folders of the project that will define the set of all *allowed* filenames. What do you think ?
While I like the ideas here I would like to suggest a different approach, that of 'Workspaces.' The problem with the current tree is that it is a snapshot of the dirname and basename objects. If you delete a file it is not immediately removed from the project tree. If you rename a file, it is not renamed in the tree and can only be added manually via add or import functions. This method wastes lot of time, especially when doing restructuring on projects. I would like to suggest that the project tree be replaced with a class that allows interaction directly wit the filesystem. That way a use can choose to see .svn or not. To make it easy to load a project, enable the user to create workspaces. A workspace has a logical name and includes 1 or more directories in the local filesystem and 0 or more remote filesystems (SMB, FTP, WebDav, etc.) Workspace may also include 0 or more other Workspaces, but not itself. Having created a Workspace, when starting work the user would select the workspace the want and start working. [wrkspace-name] +- /dirname/ | +- basename1 | |- basename2 +- /mount/ | +- /dirname/ | | |- basename1 | | |- basename2 +- {othr-wrkspace-name} | +- /dirname/ | | |- basename1 | | |- basename2 | +- /mount/ | | +- /dirname/ | | | |- basename1 | | | |- basename2 +- {othr-wrkspace-name} | +- /mount/ | | +- /dirname/ | | | |- basename1 | | | |- basename2 More dynamic and flexible, support for sym links would be nice :-) -- Sean Wheller Technical Author sean@inwords.co.za 084-854-9408 http://www.inwords.co.za Registered Linux User #375355
participants (3)
-
Lars Huttar -
Sean Wheller -
Sorin Ristache