commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc DeXeT (JIRA)" <commons-...@jakarta.apache.org>
Subject [jira] Commented: (JELLY-192) Graphical jelly script viewer
Date Sat, 08 Jan 2005 10:40:13 GMT
     [ http://issues.apache.org/jira/browse/JELLY-192?page=comments#action_57418 ]
     
Marc DeXeT commented on JELLY-192:
----------------------------------

Jelly editor in the mevenide eclipse plugin it's what I use, not what I mean.
Mevenide jelly editor help you (a lot) on very little scope : standard tag lib.
It doesn't taking into account custom lib, doesn't hold variable map (as Ant Eclipse Editor
do).

But my goal is graphical control graph and variable reference holding. Not a "Live" editor.


Waht I'm thinking about it to parse jelly script and to generate a XML document with :
reference and jexl expression mapping
for each tag link to library
for each tag link to public setters
for each expression a link (if any) to variable declaration
and so on.

First the "graphical" xml document could be parsed to generate a HTML document with customizable
xslt
with color highlighting, logical block expand and collapse, link to object type, maybe jpeg
icon for most-used tag (core:if, core:choose, ...)

My goal is also to show it to final user and to say "Hey man, look at this ! Is it how you
see your business logic ? Look ! Is right your customer account is checked _here_ before his
command _here_ is committed _here_ ?"

> Graphical jelly script viewer
> -----------------------------
>
>          Key: JELLY-192
>          URL: http://issues.apache.org/jira/browse/JELLY-192
>      Project: jelly
>         Type: New Feature
>     Reporter: Marc DeXeT
>     Priority: Minor

>
> Jelly script can be very hard to read if there several instructions.
> I think it would be interesting for users as developers to get a graphical user-friendly
viewer.
> Each jelly script is an XML well formed document, and each tag is associated to library.
> They are designed to get parsed and associated to any alternativ representation.
> It's just an idea now.
> But what about creating an functional representation of each tag :
> We have already library associated to namespace.
> Usually 'var' attribute value is an object reference.
> With instropection tools we can get setters and object type.
> So we have almost everything to establish control graph, reference usage and type maps.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message