xmljs-users

[xmljs-users] visual studio xmldocs for Version 3.1 w3c dom

[Sky S. <sky...@gm...>]

find the file and details here
http://skysanders.net/subtext/archive/2009/07/31/.net-regex-for-javadocs-and-implementation-example-against-xml-for.aspx
.

I will process the rest of the relevant files when I have time.

Sky

Re: [xmljs-users] visual studio xmldocs for Version 3.1 w3c dom

[David J. <dj...@gm...>]

Hi Sky,

Sorry it's taken so long to respond to your post. I took a look at your link
and had to do a double take. I didn't know that Visual Studio could do this
with Javascript. Very cool!

Would you be interested in providing maybe a sample project that
demonstrates how you would use this in Visual Studio? I have to admit my
Visual Studio experience is fairly limited (WCF mostly, and then only about
9 months worth so far) so something basic that can be documented for a
beginner would ideal.

If you are interested, I'd love to incorporate your sample project into our
documentation and your new xmldoc-enabled scripts into the main
distribution. Dmitry has been kicking around some ideas for a new release
for a while now and maybe this could be part of it. Time permitting, it
would be even cooler if you could contribute the xmldoc-age of the other
primary scripts as well...

Thoughts?


Best regards,

David



On Fri, Jul 31, 2009 at 5:11 AM, Sky Sanders <sky...@gm...> wrote:

> find the file and details here
> http://skysanders.net/subtext/archive/2009/07/31/.net-regex-for-javadocs-and-implementation-example-against-xml-for.aspx
> .
>
> I will process the rest of the relevant files when I have time.
>
> Sky
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> xmljs-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmljs-users
>
>

Re: [xmljs-users] visual studio xmldocs for Version 3.1 w3c dom

[Sky S. <sky...@gm...>]

David,
I would love to contribute.

But I have only one concern: namespacing.

As it stands, the xml4script is a great package but it pollutes the window
object, making collisions with other code/libraries quite likely as well as
exposing private implementation details.

I have been through most of the main scripts and a non-breaking move to
'unobtrusive' javascript using namespaces is possible as far as I can see.
For backwards compatibility we could use a set of alias that expose only the
public API.

I am willing to do most of the heavy lifting in this area.  I would want to
get a latest stable snapshot from all contributors before I begin.

any thoughts on my thoughts? ;-)



Hi Sky,
>
> Sorry it's taken so long to respond to your post. I took a look at your
> link and had to do a double take. I didn't know that Visual Studio could do
> this with Javascript. Very cool!
>
> Would you be interested in providing maybe a sample project that
> demonstrates how you would use this in Visual Studio? I have to admit my
> Visual Studio experience is fairly limited (WCF mostly, and then only about
> 9 months worth so far) so something basic that can be documented for a
> beginner would ideal.
>
> If you are interested, I'd love to incorporate your sample project into our
> documentation and your new xmldoc-enabled scripts into the main
> distribution. Dmitry has been kicking around some ideas for a new release
> for a while now and maybe this could be part of it. Time permitting, it
> would be even cooler if you could contribute the xmldoc-age of the other
> primary scripts as well...
>
> Thoughts?
>
>
> Best regards,
>
> David
>
>
>>   find the file and details here
>> http://skysanders.net/subtext/archive/2009/07/31/.net-regex-for-javadocs-and-implementation-example-against-xml-for.aspx
>> .
>>
>> I will process the rest of the relevant files when I have time.
>>
>> Sky
>>
>
>

Re: [xmljs-users] visual studio xmldocs for Version 3.1 w3c dom

[David J. <dj...@gm...>]

Hi Sky,

I think that would be a significant improvement of the code. There would be
a lot of work updating the docs and the test suites, but that's do-able
given time. I presume you're only suggesting doing this for the sax and w3c
parser? I wouldn't think doing this for the "classic" DOM would justify the
effort...

Best regards,

David

On Tue, Aug 25, 2009 at 12:57 PM, Sky Sanders <sky...@gm...> wrote:

> David,
> I would love to contribute.
>
> But I have only one concern: namespacing.
>
> As it stands, the xml4script is a great package but it pollutes the window
> object, making collisions with other code/libraries quite likely as well as
> exposing private implementation details.
>
> I have been through most of the main scripts and a non-breaking move to
> 'unobtrusive' javascript using namespaces is possible as far as I can see.
> For backwards compatibility we could use a set of alias that expose only the
> public API.
>
> I am willing to do most of the heavy lifting in this area.  I would want to
> get a latest stable snapshot from all contributors before I begin.
>
> any thoughts on my thoughts? ;-)
>
>
>
> Hi Sky,
>>
>> Sorry it's taken so long to respond to your post. I took a look at your
>> link and had to do a double take. I didn't know that Visual Studio could do
>> this with Javascript. Very cool!
>>
>> Would you be interested in providing maybe a sample project that
>> demonstrates how you would use this in Visual Studio? I have to admit my
>> Visual Studio experience is fairly limited (WCF mostly, and then only about
>> 9 months worth so far) so something basic that can be documented for a
>> beginner would ideal.
>>
>> If you are interested, I'd love to incorporate your sample project into
>> our documentation and your new xmldoc-enabled scripts into the main
>> distribution. Dmitry has been kicking around some ideas for a new release
>> for a while now and maybe this could be part of it. Time permitting, it
>> would be even cooler if you could contribute the xmldoc-age of the other
>> primary scripts as well...
>>
>> Thoughts?
>>
>>
>> Best regards,
>>
>> David
>>
>>
>>>   find the file and details here
>>> http://skysanders.net/subtext/archive/2009/07/31/.net-regex-for-javadocs-and-implementation-example-against-xml-for.aspx
>>> .
>>>
>>> I will process the rest of the relevant files when I have time.
>>>
>>> Sky
>>>
>>
>>
>

Re: [xmljs-users] visual studio xmldocs for Version 3.1 w3c dom

[Sky S. <sky...@gm...>]

David, you are correct.

I have already made a test run at w3c and sax and it looks doable to me. I
think what stopped me was some obscure code segments that I wanted
clarification on before I invested any more time.

updating tests should not be much work if they are 'properly' implemented.
i.e. testing public api. If so, some alias can make a quick job of it. If
this is not the case I would submit that the tests do need to be revisited.

Do we have the primary contributors of both libraries on board and available
for emergency clarifications?

Sky


Hi Sky,
>
> I think that would be a significant improvement of the code. There would be
> a lot of work updating the docs and the test suites, but that's do-able
> given time. I presume you're only suggesting doing this for the sax and w3c
> parser? I wouldn't think doing this for the "classic" DOM would justify the
> effort...
>
> Best regards,
>
> David
>
>
>
> David,
>> I would love to contribute.
>>
>> But I have only one concern: namespacing.
>>
>> As it stands, the xml4script is a great package but it pollutes the window
>> object, making collisions with other code/libraries quite likely as well as
>> exposing private implementation details.
>>
>> I have been through most of the main scripts and a non-breaking move to
>> 'unobtrusive' javascript using namespaces is possible as far as I can see.
>> For backwards compatibility we could use a set of alias that expose only the
>> public API.
>>
>> I am willing to do most of the heavy lifting in this area.  I would want
>> to get a latest stable snapshot from all contributors before I begin.
>>
>> any thoughts on my thoughts? ;-)
>>
>>
>>
>> Hi Sky,
>>>
>>> Sorry it's taken so long to respond to your post. I took a look at your
>>> link and had to do a double take. I didn't know that Visual Studio could do
>>> this with Javascript. Very cool!
>>>
>>> Would you be interested in providing maybe a sample project that
>>> demonstrates how you would use this in Visual Studio? I have to admit my
>>> Visual Studio experience is fairly limited (WCF mostly, and then only about
>>> 9 months worth so far) so something basic that can be documented for a
>>> beginner would ideal.
>>>
>>> If you are interested, I'd love to incorporate your sample project into
>>> our documentation and your new xmldoc-enabled scripts into the main
>>> distribution. Dmitry has been kicking around some ideas for a new release
>>> for a while now and maybe this could be part of it. Time permitting, it
>>> would be even cooler if you could contribute the xmldoc-age of the other
>>> primary scripts as well...
>>>
>>> Thoughts?
>>>
>>>
>>> Best regards,
>>>
>>> David
>>>
>>>
>>>>   find the file and details here
>>>> http://skysanders.net/subtext/archive/2009/07/31/.net-regex-for-javadocs-and-implementation-example-against-xml-for.aspx
>>>> .
>>>>
>>>> I will process the rest of the relevant files when I have time.
>>>>
>>>> Sky
>>>>
>>>
>>>
>>
>