Re: [Kernow] split TabbedView

[Andrew W. <and...@gm...>]

On 8/13/07, Florent Georges <dar...@ya...> wrote:
> Andrew Welch wrote:
> > I like it, but I'm not sure it's the Right Thing to do at
> > the moment.
>
>   Maybe.  On the other hand, I feel that we think this is
> the moment for such kind of changes when this is too late.
> Actually, I started the split because I have some ideas for
> new features, but I don't feel brave enough to change such a
> monster, with a too wide area not tested between the final
> user and the transform, schema or xquery packages.


ha ha TabbedView is a "monster", but its not so bad with an IDE.


>   I have another idea regarding the GUI: adding a new little
> controller to manage the synchronisation between the combo
> box and the button used to represent an input or output in
> the various tabs.

Sounds interesting.

>   With this little controller and the new use of Source for
> inputs, it would be far more easy to add one feature I am
> waiting for: inline inputs (writing documents, queries or
> stylesheet directly in a text area, or with c'n'p, without
> using temporary files).  Simple but very useful I think.
> (so yes, there was a concrete feature at the end ;-))

Yes, I've thought about this... but the problem is editing XML / XSLT
directly in the JTextArea - it's not much fun, so you may as well
stick to using a proper editor for those tasks.


> Schematron and XTC ;-).
>
>   I have also thought about two features that doesn't need
> work on the TabbedView: adding XML Catalogs support and
> logging support (with a view of the logs).

Logging is certainly on the TODO list, as is redirecting the message
output to a supplied writer (for anyone using the API and not the
GUI).  Improved ANT support would be good too, so that once you have a
set of transforms that you want to run repeatedly, you just have to
run the one ant buildfile.

I'd also like to try and get some "pretty printing" in the output
window, so that XML elements are coloured.

I've always been careful not stray too far from Kernow being a wrapper
for Saxon towards an IDE.  That's why I removed Relax NG support, as
Saxon isn't an RNG processor.

Anyway, as you have done a lot of the work already it would be a shame
not use it, I think you should finish it off and commit it.  If it all
goes wrong you'll have to help me sort it out ;-)

-- 
http://andrewjwelch.com