tcl-core

[TCLCORE] Thanks for OpenACS/TCL/Tk conference

[Harald O. <har...@el...>]

Dear OpenACS/TCL/tk team members,

please allow me to say "thank you" for the great OpenACS/TCL/Tk user 
conference in Vienna at the University of Economics.

It was a great meeting with awesome organisation, speaker with 
presentations and panels, participants present and on the net.

The presentations are here:
https://openacs.org/conf2024/info/schedule
Live recordings will be added soon.

My highlights:
- TCL/Tk 9 is ready and may be released soon. I was surprised, that the 
pannel sees even Tk in a better state and ready for release.
- TCL and Tk should be continued to be coupled in (major) releases. 
Package managers like Reinhard from Suse require clear releases to put 
in common distributions
- Any TCL/Tk 9 ready extension should do an official release, as package 
managers require this (often also for legal reasons). It is not 
sufficient to have it in a branch.
- More reviews on commits on the main branches are seen helpful
- Source code management of packages is an issue. A first step would be 
a list (at tcl-lang.org) of officially supported packages. Not 
maintained packages should be put at a common place (on chiseal or github).
- Markdown documentation is seen as a great step. Semantic documentation 
may follow as a second step.
- JSON with tdom was my personal highlight, as I currently need that 
(thanks Rolf, for the favour). And it was surprising, that Antonio also 
spoke about it in his awesome VR talk and other OpenACS people liked it, 
as it is anyway included in OpenACS.
- NaviServer/OpenACS is not well known in the TCL community. An OpenACS 
instance as a groupware may be helpful to internal organisation like 
inter-TCT communication. The Naviserver/OpenACS community also found out 
that more should be done for beginners. Naviserver/OpenACS is very fast 
and highly secure and ready for business critical applications. The 
first wish of the panel was to move the source away from CSV to GITHUB 
and friends.
- Some future users were well integrated in the conference and got lots 
of support.
- Tk evolution includes the new text widget (if the bugs are fixed) and 
an enhanced and compatible canvas, maybe with components from tkpath to 
feature more coordinate flexibility, anti-aliasing and alpha-channel.

Thank you all to make this happen.

The next conference (2025) will not take place in Vienna due to internal 
points. So, a location for 2025 is pending. Thanks for any proposal. It 
is hard to reach the standard of the WU, so smaller without streaming 
etc. is also ok.

Thanks for anybody, who made this happen: Stefan, Gustaf, Sebastian, 
Monika and the WU team!

Take care,
Harald

P.S.: I hope, you all got home well. There was a thunderstorm and the 
airport was close to be closed just after the conference. My train got 2 
hours delayed but I arrived well in Berlin.

Re: [TCLCORE] Thanks for OpenACS/TCL/Tk conference

[Neophytos D. <neo...@gm...>]

My highlights are different from Harald's but I will keep most to myself
except for one: Our community is shrinking and personal agendas can
exacerbate this issue. Thanks for having us in Vienna.

- Neophytos

On Sun, Jul 14, 2024 at 3:17 PM Harald Oehlmann <har...@el...>
wrote:

> Dear OpenACS/TCL/tk team members,
>
> please allow me to say "thank you" for the great OpenACS/TCL/Tk user
> conference in Vienna at the University of Economics.
>
> It was a great meeting with awesome organisation, speaker with
> presentations and panels, participants present and on the net.
>
> The presentations are here:
> https://openacs.org/conf2024/info/schedule
> Live recordings will be added soon.
>
> My highlights:
> - TCL/Tk 9 is ready and may be released soon. I was surprised, that the
> pannel sees even Tk in a better state and ready for release.
> - TCL and Tk should be continued to be coupled in (major) releases.
> Package managers like Reinhard from Suse require clear releases to put
> in common distributions
> - Any TCL/Tk 9 ready extension should do an official release, as package
> managers require this (often also for legal reasons). It is not
> sufficient to have it in a branch.
> - More reviews on commits on the main branches are seen helpful
> - Source code management of packages is an issue. A first step would be
> a list (at tcl-lang.org) of officially supported packages. Not
> maintained packages should be put at a common place (on chiseal or github).
> - Markdown documentation is seen as a great step. Semantic documentation
> may follow as a second step.
> - JSON with tdom was my personal highlight, as I currently need that
> (thanks Rolf, for the favour). And it was surprising, that Antonio also
> spoke about it in his awesome VR talk and other OpenACS people liked it,
> as it is anyway included in OpenACS.
> - NaviServer/OpenACS is not well known in the TCL community. An OpenACS
> instance as a groupware may be helpful to internal organisation like
> inter-TCT communication. The Naviserver/OpenACS community also found out
> that more should be done for beginners. Naviserver/OpenACS is very fast
> and highly secure and ready for business critical applications. The
> first wish of the panel was to move the source away from CSV to GITHUB
> and friends.
> - Some future users were well integrated in the conference and got lots
> of support.
> - Tk evolution includes the new text widget (if the bugs are fixed) and
> an enhanced and compatible canvas, maybe with components from tkpath to
> feature more coordinate flexibility, anti-aliasing and alpha-channel.
>
> Thank you all to make this happen.
>
> The next conference (2025) will not take place in Vienna due to internal
> points. So, a location for 2025 is pending. Thanks for any proposal. It
> is hard to reach the standard of the WU, so smaller without streaming
> etc. is also ok.
>
> Thanks for anybody, who made this happen: Stefan, Gustaf, Sebastian,
> Monika and the WU team!
>
> Take care,
> Harald
>
> P.S.: I hope, you all got home well. There was a thunderstorm and the
> airport was close to be closed just after the conference. My train got 2
> hours delayed but I arrived well in Berlin.
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core
>

Re: [TCLCORE] Thanks for OpenACS/TCL/Tk conference

[Patrick M. <dus...@gm...>]

I'd like to say, I think Tcl/Tk is amazing, and in my personal 
experience I've found the community to be welcoming, encouraging, and 
kind. I hope this trend will reverse and the community will grow, and 
Tcl/Tk will find more adoption and popularity in the future, it's very 
underappreciated.

Regards,
- PM

On 14/07/2024 21:01, Neophytos Demetriou wrote:
> My highlights are different from Harald's but I will keep most to myself 
> except for one: Our community is shrinking and personal agendas can 
> exacerbate this issue. Thanks for having us in Vienna.
> 
> - Neophytos
> 
> On Sun, Jul 14, 2024 at 3:17 PM Harald Oehlmann 
> <har...@el... <mailto:har...@el...>> wrote:
> 
>     Dear OpenACS/TCL/tk team members,
> 
>     please allow me to say "thank you" for the great OpenACS/TCL/Tk user
>     conference in Vienna at the University of Economics.
> 
>     It was a great meeting with awesome organisation, speaker with
>     presentations and panels, participants present and on the net.
> 
>     The presentations are here:
>     https://openacs.org/conf2024/info/schedule
>     <https://openacs.org/conf2024/info/schedule>
>     Live recordings will be added soon.
> 
>     My highlights:
>     - TCL/Tk 9 is ready and may be released soon. I was surprised, that the
>     pannel sees even Tk in a better state and ready for release.
>     - TCL and Tk should be continued to be coupled in (major) releases.
>     Package managers like Reinhard from Suse require clear releases to put
>     in common distributions
>     - Any TCL/Tk 9 ready extension should do an official release, as
>     package
>     managers require this (often also for legal reasons). It is not
>     sufficient to have it in a branch.
>     - More reviews on commits on the main branches are seen helpful
>     - Source code management of packages is an issue. A first step would be
>     a list (at tcl-lang.org <http://tcl-lang.org>) of officially
>     supported packages. Not
>     maintained packages should be put at a common place (on chiseal or
>     github).
>     - Markdown documentation is seen as a great step. Semantic
>     documentation
>     may follow as a second step.
>     - JSON with tdom was my personal highlight, as I currently need that
>     (thanks Rolf, for the favour). And it was surprising, that Antonio also
>     spoke about it in his awesome VR talk and other OpenACS people liked
>     it,
>     as it is anyway included in OpenACS.
>     - NaviServer/OpenACS is not well known in the TCL community. An OpenACS
>     instance as a groupware may be helpful to internal organisation like
>     inter-TCT communication. The Naviserver/OpenACS community also found
>     out
>     that more should be done for beginners. Naviserver/OpenACS is very fast
>     and highly secure and ready for business critical applications. The
>     first wish of the panel was to move the source away from CSV to GITHUB
>     and friends.
>     - Some future users were well integrated in the conference and got lots
>     of support.
>     - Tk evolution includes the new text widget (if the bugs are fixed) and
>     an enhanced and compatible canvas, maybe with components from tkpath to
>     feature more coordinate flexibility, anti-aliasing and alpha-channel.
> 
>     Thank you all to make this happen.
> 
>     The next conference (2025) will not take place in Vienna due to
>     internal
>     points. So, a location for 2025 is pending. Thanks for any proposal. It
>     is hard to reach the standard of the WU, so smaller without streaming
>     etc. is also ok.
> 
>     Thanks for anybody, who made this happen: Stefan, Gustaf, Sebastian,
>     Monika and the WU team!
> 
>     Take care,
>     Harald
> 
>     P.S.: I hope, you all got home well. There was a thunderstorm and the
>     airport was close to be closed just after the conference. My train
>     got 2
>     hours delayed but I arrived well in Berlin.
>     _______________________________________________
>     Tcl-Core mailing list
>     Tcl...@li... <mailto:Tcl...@li...>
>     https://lists.sourceforge.net/lists/listinfo/tcl-core
>     <https://lists.sourceforge.net/lists/listinfo/tcl-core>
> 
> 
> 
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core