|
|
 next
|
  Subject: Stylus Studio 3.1 Beta 2 now available!
Author: Minollo I.
Date: 04 Sep 2001 04:17 PM
|
http://download.exceloncorp.com/downloads/studio/iftw_beta/stylus%20studio.htm
This is a list of changes in beta 2:
*** Source Code Control Integration
Stylus Studio now support MSSCCI (MicroSoft Source Code Control Interface).
That means that Stylus Studio supports any source code control system which
supports the same interface used by Microsoft VisualStudio (and
VisualStudio .net).
So far, we have tested the integration with:
- Source Safe
- Clearcase/Attache
- CVS (using the latest version of the Zeus CVS Provider and with some
additional configuration needed in the SourceControl|Properties dialog)
*** Context Sensitive Editing in XML Editor
When editing an XML document associated to a schema (DTD or XML Schema),
the SenseX functionality which helps in the creation of new tags is now
context sensitive. If you have a schema where {books} are made of {book}
which are made of {title} and {author}, adding an element child of {books}
will list only {book}; adding an element child of {book} will list only
{title} and {author}
*** Improved Handling of Custom Extensions
Custom extensions associated to the various plugins/editors contained in
Stylus Studio are now properly recognized and displayed in the Open File
dialog.
Also, you can make Stylus Studio become the default application associated
to custom extensions.
Also, the "All Files" filters is now available in contexts where it was not
displayed before.
*** XPath Expressions in Watch Window
When XSLT processing is suspended during a debug session, it is possible to
ask Stylus Studio to evaluate an XPath expression in the current processor
context. That can be done displaying the Watch window and typing an XPath
expression in a field.
*** Customizable Default Fonts and Syntax Coloring
In Tools|Options|Editor Format it is now possible to customize the default
font name and size that any Stylus Studio editor should display (in
XML/XSLT editing the font will be automatically changed if the current
selection is not able to support the character set contained in the
displayed document).
It is also possible to customize the colors used in syntax highlighting by
the editors.
*** Associate XML Document to Schema Command
The XML editor now exposes a command (XML|Associate XML With Schema...)
that creates for you the proper syntax required by the XML document to be
associated with the selected DTD or XML Schema document(s).
It is now also available a button in the XML Editor toolbar which lets you
jump to any of the schema files associated to the XML document.
*** External XSLT Processing Displayed in Preview Window
The result of external XSLT processing (coming from the MSXML, Xalan-J or
custom external processor set in the XSLT scenario property dialog) is
displayed in the preview window pane instead of in an external application.
Of course, back-mapping from the XSLT result window to the source is not
available when external XSLT processing is chosen.
*** Projects Store Relative Path Information
When projects are saved, references to the files part of the project are
now saved relative to the path of the project file. That lets you move or
share projects more easily.
It is now also possible to "Save as..." a project.
*** Fixes and Minor Improvements
Several bugs and issues have been addressed in Beta 2, many of them thanks
to the feedback provided on the SSDN forums; these are a few details about
them:
- Java SenseX crashes and erroneous activation during string and comment
editing
- Un-needed reset of the window position in XSLT editor while stepping
through processing in debug mode
- Crashes editing DTD
- Variable window was always displaying XSLT values associated to the top
stack frame, ignoring stack frame selection in the Stack window
- Crashes in command line utility when specifying input/output paths
relative to the current utility directory or when importing/including
documents with a path relative to the master XSLT document
- Don't touch content when indenting
- Added standard key bindings to the Open File dialog
- Validation of an XML document is halted after a user-specified (Tools|XML
Editor) number of errors is reported
- Clicking on the XSLT schema tree +/- buttons doesn't cause the current
template in the XSLT editor window to change
- Possibility to drag&drop files from the Stylus Studio project window on
other applications supporting file drag&drop operations
- Fixed regression: printing functionality in XSLT editor is back
- Output window supports CTRL+C to copy text and wraps long lines
- Fixed a few defects (crashes or wrong processing results) in XSLT and
XPath processors
|
 top
|
  Subject: Re: Stylus Studio 3.1 Beta 2 now available!
Author: (Deleted User)
Date: 22 Oct 2001 12:19 PM
|
At 07:47 AM 10/22/2001 -0400, you wrote:
>From: "Leonard Walstad"
>
>Can you tell us what is needed to configure a Zeus CVS source code control
>client? You noted this was necessary in the original message of this thread:
Hi Leonard,
to get a local copy of a CVS repository you can follow these steps:
- File | Project | New Project Wizard
- Choose "Project From SCC"
- Pick up "Zeus SCC-CVS" from the combo box, check the "Recursively Import
All Subprojects" and click the "Advanced" button
- At this point you need to get the informations to reach the CVS
repository; usually the user has to type a command line like "cvs
-d:pserver:user@server:/cvsroot/projectname login" followed by a "cvs
-d:pserver:user@server:/cvsroot/projectname co module"; in this case, you
need to type "module" as the Project Name,
":pserver:user@server:/cvsroot/projectname" as the Auxiliary Path, and pick
an existing local directory for the Working Dir setting (e.g. try with
"jEdit", ":pserver:anonymous@cvs.jedit.sourceforge.net:/cvsroot/jedit" and
"c:\temp")
- When you press OK, the files will be downloaded from CVS, and all the
files that can be opened by Studio will be added to the project
Hope this helps,
Alberto
|
|
|
|
|
