[rules-dev] Project Idea - pure HTML5 Audit log

[Mark Proctor]

On 06/02/2012 20:17, Wolfgang Laun wrote:
> OK, so it's still around.
>
> But why should one convert perfectly good (if unstable) XML to JSON
> just to generate HTML5? Seems to be a simple case for XSLT 2.0 - or what
> am I missing?
if the component is pure html5/javascript, and it's to be dynamic so it 
can receive continued updates, it'll need a data format. Sending and 
processing XML in the browser, compared to json, isn't easy; although 
there are some tools out there like GWT which can ease this.

Mark
>
> -W
>
>
> On 06/02/2012, Mark Proctor<mproctor at codehaus.org>  wrote:
>> On 06/02/2012 19:41, Wolfgang Laun wrote:
>>> Is this kind of log still supported with the "stable" API? The Expert
>>> manual contains
>>> (in 8.6.4, The Audit View) a code snippet but the referenced class
>>> (WorkingMemoryFileLogger) isn't in the stable API.
>> WorkingMemoryFileLogger is the old impl, which isn't in -api. End users
>> should be using KnowledgeRuntimeLoggerFactory, which is in -api, and
>> examples should have been updated to use that too.
>>
>> However all the data structures that the logger dumps with xtream will
>> still be on the old core/compiler ones, so we can't consider the log
>> contents to be "stable".
>>
>> Mark
>>> -W
>>>
>>>
>>> On 06/02/2012, Mark Proctor<mproctor at codehaus.org>   wrote:
>>>> I was just making a swing app, for Wumpups, and thought it would be
>>>> really nice if I could embed the audit log that would render in the
>>>> example as it was executing. I can't re-use the existing stuff, as it's
>>>> SWT based.
>>>>
>>>> So I thought a nice project for someone would be to make an
>>>> HTML5/Javascript version of the Eclipse graphical audit log. It should
>>>> be able to take json document and render an audit log correctly. This
>>>> component can then be re-used by people anywhere, we can even move the
>>>> SWT version over to the HTML5 version in eclipse, so that we only have a
>>>> single version to maintain.
>>>>
>>>> In theory it's not too difficult, we don't need any fancy canvas stuff.
>>>> Just indent lines and use background coloured spans for highlighting.
>>>> The hardest part of the project is probably getting the current xstream
>>>> document dumped to a sane json format. Luckily xstream already has json
>>>> capabilities, so maybe not too hard.
>>>>
>>>> Any takers?
>>>>
>>>> Mark
>>>> _______________________________________________
>>>> rules-dev mailing list
>>>> rules-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/rules-dev
>>>>
>>> _______________________________________________
>>> rules-dev mailing list
>>> rules-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/rules-dev
>> _______________________________________________
>> rules-dev mailing list
>> rules-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-dev
>>
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev