XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1123)
- Stylus Studio Technical Forum (13809)
-> + Bug- Display of Redefined sche... (2)
-> + A question about processing in... (2)
-> + XML to XML Mapping (2)
-> + Web Service - Was Working, But... (3)
-> + Window Contents do not resize (8)
-> + BaseCatalog Not Adding to Proj... (3)
-> + SS Does not like # in the file... (6)
-> + Bad Context Menu Text (2)
-> + XSLT and EDI x12 (3)
-> - Batch validation (1)
-> + Visual C++ Runtime Error (3)
-> - WSDL's, XML Mappings To DB fie... (1)
-> + SS crashes when trying to save... (3)
-> + XML Pipelines (4)
-> + Handle Music Playlists in Styl... (2)
-> + Using a font in FOP (9)
-> + Automation in .NET/WebService ... (3)
-> + Convert .CSV file to XML (6)
-> + FOP Plugin does not install wi... (8)
-> + startup fault (2)
-> + xsd sequence question (5)
-> + Licence authentication failed ... (3)
-> + .NET API for the X12 To XML Ad... (6)
-> + data in tabular format (2)
-> + How to convert the xml String ... (4)
-> + SS Schema Validation misses an... (2)
-> + Problem in converting EDI file... (2)
-> + Generating image from XML and ... (2)
-> + Auto Schema builder is not cre... (3)
-> + XML/SQL update more tables (2)
-> + Default toolbar blocked (3)
-> + Stylus vs Altova Mapforce - St... (4)
-> + Problem with namespace while v... (3)
-> + Web Service Call - "unqualifie... (3)
-> + XML to SQL Server 2005 (2)
-> + XHTML with multiple schemas (2)
-> + Compare Stylus Studio with OBO... (2)
-> + Deploying java app using deplo... (3)
-> + Validating XML through Schema (3)
-> + Connecting to Informix 7.31 (2)
-> + EDI/XML question (4)
-> + X12 to XML Adapter (2)
-> + XSD conversion (2)
-> + Schema DateTime exception (2)
-> + Plug In Failure to regsiter (2)
-> + Reading EDIFACT (3)
-> - XML Playlist (1)
-> + Edit Xml In Place with Xslt vi... (5)
-> + validation error (9)
-> + Install error (2)
-> + how to get the xpath of xml el... (2)
-> + Can Stylus Studio be installed... (2)
-> + Built in XSLT Processor Too Sl... (2)
-> + Documentation (5)
-> + WSDL files (3)
-> + Generic flat file -> xml conve... (4)
-> + Stylus Studio crash after edit... (3)
-> + Does any one have a example to... (2)
-> + ComplexType Inheritance (6)
-> + Problem with starting (2)
-> + Icons (2)
-> + Using Saxon with xslt 2.0 (4)
-> + Wrong graphics size in preview... (2)
-> + TRANG and disable-abstract-ele... (5)
-> + Urgent: License Authentication... (3)
-> + Converting XML to CSV (10)
-> + conditional page body with XSL... (2)
-> + converting DTD to XSD (2)
-> + Stylus Studio doesn't appear t... (2)
-> + Embed XML-to-XML Mapping UI in... (3)
-> + Convert to XML (2)
-> + Tutorial Instructions Do Not M... (2)
-> + How can the attached file be e... (2)
-> + How to Generate xml file from ... (2)
-> + Multi-threaded Flat to XML ada... (2)
-> + XML Transformation -- Help Nee... (2)
-> + Loop in XSL (2)
-> + No error message when there sh... (2)
-> + Problems activating key in Sty... (2)
-> + sax parser (2)
-> + Hyperlink in xsl (2)
-> + Connection Timeout (5)
-> + SAX Parser error bcos of speci... (4)
-> + Running Java Code created by S... (3)
-> + Convert To XML - Sub Regions (2)
-> + create j2ee deploymeny descrip... (3)
-> + encoding (2)
-> + "SDQ format" processing (6)
-> + Base type could not be found (3)
-> + Changing default directory for... (3)
-> + XSLT Debug Call Stack doesn't ... (13)
-> + Basing XSLT on Schema (2)
-> + Xpath and the not operator (7)
-> + WSDL does not load properly (2)
-> + Stylus Studio won't run (7)
-> + XSLT Group By (2)
-> + Access problems to Tamino XML ... (2)
-> + Utilizing Stylus Studio for au... (4)
-> + Running Java file created from... (4)
-> + Showing All Validation Errors ... (6)
-- Previous [1681-1700] [1701-1720] [1721-1740] Next
+ Website Feedback (243)
+ XSLT Help and Discussion (7447)
+ XQuery Help and Discussion (1861)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (361)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Guy CoombesSubject: Stylus Studio HTML Integration
Author: Guy Coombes
Date: 07 May 2001 11:44 AM
Not sure if this is the right place, but:
I am currently taking HTML pages that I have previously programmed with Macromedia Dreamweaver to pieces. I am then putting them back together again in Stylus Studio.
I guess this is the state of play in XML/XSL development, but it does seem a bit daft.
Does eXcelon have any plans to integrate closer with a WYSIWYG HTML Editor - or even a text-based editors, like UltraEdit?
Guy

Postnext
Christopher ParkersonSubject: RE: Stylus Studio HTML Integration
Author: Christopher Parkerson
Date: 07 May 2001 12:59 PM
What type of "closer integration" would you like to see? We do have plans
to provide WYSIWYG HTML functionality in Stylus Studio itself in a release
later this year, which would overlap somewhat with Dreamweaver et al.
However, the major difference is the audience for Dreamweaver and comparable
tools: they are targeted more at graphic artists and designers while Stylus
Studio is targeted at developers. Therefore, we will probably not approach
the level of sophistication that Dreamweaver provides in terms of page
layout, CSS support, and other design-oriented capabilities.

However, we do agree that there needs to be a model for working with such
products when using Stylus Studio. Any information you can give us on what
you would like to see specifically would be extremely helpful.

Thanks,
Chris

--------------------------------------------
Chris Parkerson - Product Manager
Portal Server and Development Tools
eXcelon Corporation
Burlington, MA
(781) 674-5393
http://www.exceloncorp.com
--------------------------------------------


-----Original Message-----
From: edn-stylus-forum Listmanager [mailto:listmanager]
Sent: Monday, May 07, 2001 11:49 AM
To: Recipients of 'edn-stylus-forum' suppressed
Subject: Stylus Studio HTML Integration


From: "Guy"

Not sure if this is the right place, but:
I am currently taking HTML pages that I have previously programmed with
Macromedia Dreamweaver to pieces. I am then putting them back together again
in Stylus Studio.
I guess this is the state of play in XML/XSL development, but it does seem a
bit daft.
Does eXcelon have any plans to integrate closer with a WYSIWYG HTML Editor -
or even a text-based editors, like UltraEdit?
Guy



To reply: mailto:edn-stylus-forum.2859@edn.exceloncorp.com
To start a new topic: mailto:edn-stylus-forum@edn.exceloncorp.com
To login: http://edn.exceloncorp.com/~EDN

Postnext
Guy CoombesSubject: RE: Stylus Studio HTML Integration
Author: Guy Coombes
Date: 07 May 2001 01:41 PM
Hallo Chris,

>What type of "closer
>integration" would you like to
>see?

What I'm thinking in terms of, is something which allows me to write the HTML from within Stylus, instead of creating a page layout somewhere else and cutting it up again to make it dynamic.

>However, the major
>difference is the audience for
>Dreamweaver and comparable
>tools: they are targeted more at graphic
>artists and designers while
>Stylus Studio is targeted at
>developers. Therefore, we
>will probably not approach the
>level of sophistication that
>Dreamweaver provides in terms
>of page layout, CSS support,
>and other design-oriented capabilities.

DreamWeaver UltraDev is a first step towards making an HTML tool a tool for creating dynamic HTML. But it only does Java and ColdFusion. This is not, by all accounts, the real future: that lies squarely with XML/XSL processing.

I would agree that Stylus is aimed more at developers than designers - it's just a question of how long this remains a two-person job.

>However, we do agree that there needs to be
>a model for working with such products when
>using Stylus Studio. Any information you can give us on what you would like to see
>specifically would be extremely helpful.

A really neat integration could be achieved with a tool/component like XSpLit from www.percussion.com. This also uses source from Apache and does a fair job of converting HTML into XSL.

Something like this would speed up XSL production, as it means that the HTML must not be programmed by hand. It also means that were Stylus Studio, for example, to work with XSpLit, or components from Percussion, eXcelon Developers would not have to construct a fully-featured HTML Editor from scratch.

Writing HTML by hand is of course massively less time-consuming with the auto-complete feature of Stylus Studio, but clicking and dragging would be a real breakthrough.

In general, I have the feeling that people understand HTML far better than they do XSLT. That being the case, reaching out further into HTML territory is probably bringing XML/XSL processing closer to a lot more developers.

HTH

Guy

Postnext
Christopher ParkersonSubject: RE: Stylus Studio HTML Integration
Author: Christopher Parkerson
Date: 07 May 2001 02:15 PM
Comments indented below...
Chris

--------------------------------------------
Chris Parkerson - Product Manager
Portal Server and Development Tools
eXcelon Corporation
Burlington, MA
(781) 674-5393
http://www.exceloncorp.com
--------------------------------------------


From: "Guy"

Hallo Chris,

>What type of "closer
>integration" would you like to
>see?

What I'm thinking in terms of, is something which allows me to write the
HTML from within Stylus, instead of creating a page layout somewhere else
and cutting it up again to make it dynamic.

* You'll get a lot of this in the forthcoming Stylus Studio support for
WYSIWYG HTML editing. We are looking at more developer-oriented tools like
DreamWeaver UltraDev to attempt to find an appropriate balance.

>However, the major
>difference is the audience for
>Dreamweaver and comparable
>tools: they are targeted more at graphic
>artists and designers while
>Stylus Studio is targeted at
>developers. Therefore, we
>will probably not approach the
>level of sophistication that
>Dreamweaver provides in terms
>of page layout, CSS support,
>and other design-oriented capabilities.

DreamWeaver UltraDev is a first step towards making an HTML tool a tool for
creating dynamic HTML. But it only does Java and ColdFusion. This is not, by
all accounts, the real future: that lies squarely with XML/XSL processing.

I would agree that Stylus is aimed more at developers than designers - it's
just a question of how long this remains a two-person job.

* Unless you turn the artists into engineers or the engineers into artists,
in most companies, it will remain a two person job. Creating the magic tool
that blends the best of both worlds is a challenge. Having used UltraDev, I
don't think it completely succeeds at this: it is still too heavy on the
design side, typical of Macromedia products. Our goal is to make developers
of XML-based applications successful. This means focus more on
programmer-oriented tools than designer-oriented tools, although I agree
there is need for a balance given that on smaller projects, the lines
between designer and developer get blurred or do not exist.

>However, we do agree that there needs to be
>a model for working with such products when
>using Stylus Studio. Any information you can give us on what you would
like to see
>specifically would be extremely helpful.

A really neat integration could be achieved with a tool/component like
XSpLit from www.percussion.com. This also uses source from Apache and does a
fair job of converting HTML into XSL.

Something like this would speed up XSL production, as it means that the HTML
must not be programmed by hand. It also means that were Stylus Studio, for
example, to work with XSpLit, or components from Percussion, eXcelon
Developers would not have to construct a fully-featured HTML Editor from
scratch.

Writing HTML by hand is of course massively less time-consuming with the
auto-complete feature of Stylus Studio, but clicking and dragging would be a
real breakthrough.

In general, I have the feeling that people understand HTML far better than
they do XSLT. That being the case, reaching out further into HTML territory
is probably bringing XML/XSL processing closer to a lot more developers.

* Stylus Studio's forthcoming WYSIWYG capabilities will address this. There
will, of course, be another beta program when these features are available
so you can give them a spin and give feedback ;->

HTH

Guy

* Thanks for the helpful feedback!

Chris


To reply: mailto:edn-stylus-forum.2863@edn.exceloncorp.com
To start a new topic: mailto:edn-stylus-forum@edn.exceloncorp.com
To login: http://edn.exceloncorp.com/~EDN

Posttop
Guy CoombesSubject: Stylus Studio HTML Integration
Author: Guy Coombes
Date: 07 May 2001 02:31 PM
Hallo Chris.

The question of whether the designers become engineers or the engineers designers is a difficult one.
One indication is that over here in Germany at my local tech college they now run Bachelor course called Multimedia System Design. These students are training in design _and_ IT.
I'm not sure how if it's working or just giving a lot of people a headache =)
I'm also thinking back 5 years to when there were an awful lot of IT people churning out HTML. Thanks to competition to provide robust, comfortable tools, a lot of this work is now done directly by designers.
Anyway, I'm looking forward to the next version of Stylus Studio already...

Cheers,
Guy

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.