Seconded. The Navigator is to reach (and partially) to manipulate the instantiated objects in a concrete document, this inspection tool is far more
for development purposes and also about the DOM itself, not just the instances in a concrete document.
ATB
Lothar
Am 23.07.2020 um 09:09 schrieb
Hi Florian,
On Wed, Jul 22, 2020 at 04:58:40PM +0200, Florian Effenberger
wrote:
> One question raised is wrt. navigator overlapping with parts of the tender.
> Answers and insight to that highly appreciated!
My understanding is that the navigator is created for end-users, while
this
Hi Florian, all,
On Wed, Jul 22, 2020 at 04:58:40PM +0200, Florian Effenberger wrote:
> I'd like to collect further feedback on this tender this week, and if there
> is nothing controversial, move to publication afterwards.
I wonder if it would make sense to link this old talk of mine in the
Hello,
I've just published an updated tender draft, based on feedback I received.
One question raised is wrt. navigator overlapping with parts of the
tender. Answers and insight to that highly appreciated!
I'd like to collect further feedback on this tender this week, and if
there is
Hi Lothar,
> a) (Completeness of the specification) Isn't it appropriate to assign the
> right Version of LibO and the UNO API to it, at least what is the version
> (or with what LibO Version delivered) the "WatchCode"-Implementation should
> be used for the UI work? Which version of the XRAY
Hello,
one of the approved [1] tenders is the
Tender for implementing support for a dedicated, built-in UNO object
inspection tool (Xray-built-in debugger)
The board would like to work together in public with all of you on this
tender before it gets officially published. The current draft
