Menu
▾
▴
tcllib-devel — Discussion of development for tcllib
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(15) |
Nov
(37) |
Dec
(15) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(13) |
Feb
(58) |
Mar
(61) |
Apr
(8) |
May
|
Jun
(18) |
Jul
(51) |
Aug
(11) |
Sep
(41) |
Oct
(19) |
Nov
(39) |
Dec
(14) |
| 2003 |
Jan
(46) |
Feb
(28) |
Mar
(3) |
Apr
(132) |
May
(93) |
Jun
(46) |
Jul
(22) |
Aug
(55) |
Sep
(13) |
Oct
(6) |
Nov
(8) |
Dec
(6) |
| 2004 |
Jan
(28) |
Feb
(60) |
Mar
(9) |
Apr
(28) |
May
(39) |
Jun
(40) |
Jul
(36) |
Aug
(13) |
Sep
(21) |
Oct
(38) |
Nov
(25) |
Dec
(8) |
| 2005 |
Jan
(6) |
Feb
(14) |
Mar
(1) |
Apr
(2) |
May
(17) |
Jun
(9) |
Jul
(7) |
Aug
(90) |
Sep
(44) |
Oct
(40) |
Nov
(22) |
Dec
(1) |
| 2006 |
Jan
(31) |
Feb
(10) |
Mar
(1) |
Apr
(3) |
May
(8) |
Jun
(28) |
Jul
(5) |
Aug
(42) |
Sep
(40) |
Oct
(40) |
Nov
(27) |
Dec
(26) |
| 2007 |
Jan
(14) |
Feb
(13) |
Mar
(3) |
Apr
(3) |
May
(22) |
Jun
|
Jul
|
Aug
(17) |
Sep
(10) |
Oct
|
Nov
(24) |
Dec
(5) |
| 2008 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(4) |
May
(18) |
Jun
(10) |
Jul
(1) |
Aug
(10) |
Sep
(5) |
Oct
(3) |
Nov
(5) |
Dec
(3) |
| 2009 |
Jan
(17) |
Feb
(31) |
Mar
(5) |
Apr
(6) |
May
(15) |
Jun
(52) |
Jul
(48) |
Aug
(39) |
Sep
(6) |
Oct
(11) |
Nov
(8) |
Dec
(6) |
| 2010 |
Jan
(2) |
Feb
(3) |
Mar
(1) |
Apr
|
May
(3) |
Jun
(12) |
Jul
(1) |
Aug
|
Sep
(4) |
Oct
|
Nov
(4) |
Dec
(1) |
| 2011 |
Jan
(3) |
Feb
(21) |
Mar
(17) |
Apr
(8) |
May
(10) |
Jun
(7) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
(3) |
| 2012 |
Jan
(1) |
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(6) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(8) |
| 2013 |
Jan
(3) |
Feb
(7) |
Mar
(3) |
Apr
(1) |
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
(3) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2014 |
Jan
(1) |
Feb
(12) |
Mar
(4) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(9) |
Nov
(4) |
Dec
(1) |
| 2015 |
Jan
|
Feb
|
Mar
(2) |
Apr
(3) |
May
(17) |
Jun
(4) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2016 |
Jan
(9) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(8) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
(10) |
Mar
|
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
(3) |
Mar
|
Apr
(17) |
May
|
Jun
(1) |
Jul
|
Aug
(4) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2020 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
(11) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(4) |
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(6) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andreas K. <and...@su...> - 2019-04-10 19:06:53
|
On Wed, 10 Apr 2019 12:44:03 -0500 Andy Goth <and...@gm...> wrote: > On 4/9/19 10:46 PM, Andreas Kupries wrote: > > If you are tracking Tcllib's > > [timeline](https://core.tcl.tk/tcllib/timeline) you might have seen > > that I am currently working in a branch [1] on a full set of guides > > for the various roles (user, installer/builder, > > developer/maintainer, release manager) associated with Tcllib. > > Cute, putting this email in markdown format. Made it easier to write the links. > The big issue I see is extraneous backslashes in verbatim code blocks, > those being lines of text that begin with at least four spaces. Yes. Arjen noted the same. I confirmed that pandoc does not like it either. I am currently working on that. Clearly I am overquoting the special characters. They are not special in the verbatim block and thus should not be quoted when I emit MD. > I'm not sure where to go to see any examples of this, but I am curious > of extraneous backslashes are also present within `...` code spans. Will check. Likely yes. And confirmed that pandoc treats specials in `...` like in verbatim, and when quoted the quotes are passed through also. This is currently no trouble because the doctools md generator does not emit `...` sequences for anything. It is something to watch for however should that happen in the future. > Here is the markdown rules reference: > > https://core.tcl.tk/tcllib/md_rules Thanks -- Andreas Kupries SUSE Software Canada ULC EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/ Tcl'2019, Nov 4-8, Houston, TX, USA. http://www.tcl.tk/community/tcl2019/ |
|
From: Andy G. <and...@gm...> - 2019-04-10 17:44:11
|
On 4/9/19 10:46 PM, Andreas Kupries wrote: > If you are tracking Tcllib's > [timeline](https://core.tcl.tk/tcllib/timeline) you might have seen > that I am currently working in a branch [1] on a full set of guides > for the various roles (user, installer/builder, developer/maintainer, > release manager) associated with Tcllib. Cute, putting this email in markdown format. > I am looking for feedback on things as simple as spelling and > phrasing, up to higher-level discussion about maintainer commitments > and the purpose of branches, how to work with them, etc. The big issue I see is extraneous backslashes in verbatim code blocks, those being lines of text that begin with at least four spaces. Plenty of examples here: https://core.tcl.tk/tcllib/doc/trunk/embedded/md/tcllib/files/modules/doctools/doctools_lang_syntax.md Here is the source for the above: https://core.tcl.tk/tcllib/artifact?fn=embedded/md/tcllib/files/modules/doctools/docidx_lang_intro.md&ci=trunk&txt=1 I'm not sure where to go to see any examples of this, but I am curious of extraneous backslashes are also present within `...` code spans. Here is the markdown rules reference: https://core.tcl.tk/tcllib/md_rules -- Andy Goth | <andrew.m.goth/at/gmail/dot/com> |
|
From: Andreas K. <aku...@sh...> - 2019-04-10 04:02:05
|
Hello to all 45 of you with an account at the Tcllib repository which has an email address in the contact field. I assume that you are at least a user of Tcllib, and possibly even a contributor or maintainer for one or more of its packages. I am broadcasting this message to all of you because I do not know who of you is also subscribed to the [Tcllib-devel](https://lists.sourceforge.net/lists/listinfo/tcllib-devel) [mailing list](mail:tcl...@li...). The list is cc'd however, to keep things open. With the administrative stuff done, let us come to the meat. If you are tracking Tcllib's [timeline](https://core.tcl.tk/tcllib/timeline) you might have seen that I am currently working in a branch [1] on a full set of guides for the various roles (user, installer/builder, developer/maintainer, release manager) associated with Tcllib. While there are still substantial holes in the guide for a release manager I believe that the other guides are now pretty complete, i.e. ready for a larger review of their contents. I am looking for feedback on things as simple as spelling and phrasing, up to higher-level discussion about maintainer commitments and the purpose of branches, how to work with them, etc. If you are (planning to be) a maintainer for one or more packages the [Maintainer commitments](https://core.tcl.tk/tcllib/doc/doc-overhaul/embedded/m d/tcllib/files/devdoc/tcllib_devguide.md#subsection2) are especially important and should be reviewed. While I tried to be sensible it is entirely possible that I did not succeed. The 'kind communication' part is essentially a belaboring of `be kind to each other when discussing things`. Very easy to forget, as such I believe the reminder is necessary. The plan is to integrate the feedback and then later merge the branch back to the trunk, at which point the guides would become official. All the new documentation is reachable via the new [Index Page](https://core.tcl.tk/tcllib/doc/doc-overhaul/embedded/index.md), in the section "Guides To Tcllib" at the top. __Note__ that the link points to a document on the branch, this is not yet the main index serving as Tcllib's homepage. To keep a modicum of forward momentum I am limiting the feedback period to a bit under three weeks, starting from now to Sunday April 28, 2019, 12:00 GMT. This is `clock format 1556452800`. ~ ~ ~~ ~~~ ~~~~~ ~~~~~~~~ ~~~~~~~~~~~~~ [1]: https://core.tcl.tk/tcllib/timeline?r=doc-overhaul "doc-overhaul" -- See you, Andreas Kupries <aku...@sh...> <http://core.tcl.tk/akupries/> Developer @ SUSE Software Canada ULC <and...@su...> EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/ Tcl'2019, Nov 4-8, Houston, TX, USA. http://www.tcl.tk/community/tcl2019/ ------------------------------------------------------------------------------- |
|
From: Arjen M. <Arj...@de...> - 2019-04-08 08:12:51
|
Hi Andy, There are several modules within Tcllib that have C-based accelerations - json and struct are two examples. I suggest you use the approach applied there to model your C-version of argparse on. Regards, Arjen -----Original Message----- From: Andy Goth <and...@gm...> Sent: 08 April 2019 08:29 To: tcl...@li... Subject: [Tcllib-devel] pipeline and argparse I'd like to put my pipeline package into Tcllib, but it depends on my argparse package which is not in Tcllib. It may seem like the obvious solution is to also put argparse into Tcllib, but I'm not sure how well that will work with my long-term goals for argparse. Right now argparse is written in pure Tcl 8.6, but once I knock out the rest of my interface-relevant ideas, I want to reimplement it in C to be a loadable extension with a stubs-enabled C API. That makes me think it should be its own TEA-compliant project rather than a Tcllib module, but then if I don't put argparse into Tcllib, I shouldn't put pipeline or other packages that depend on argparse into Tcllib either. Guidance? Thoughts? https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.tcl-lang.org%2Fpage%2Fpipeline%23853e5dc13add203ce4b75e513189e8f07dc4af458b61e91ce34c3afea8c1e210&data=02%7C01%7C%7C3d2c52339aca4d86f86408d6bbeb780d%7C15f3fe0ed7124981bc7cfe949af215bb%7C0%7C1%7C636903017351072710&sdata=gstUnlodUhpkXyL9eSiyurpAkxKOqfHvtO7SVPSFHR8%3D&reserved=0 https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.tcl-lang.org%2Fpage%2Fargparse&data=02%7C01%7C%7C3d2c52339aca4d86f86408d6bbeb780d%7C15f3fe0ed7124981bc7cfe949af215bb%7C0%7C1%7C636903017351082719&sdata=hx0v51TkM8iDmsnmtxX8ZLsgnWBDyoJjWyxUaZ47BnE%3D&reserved=0 -- Andy Goth | <andrew.m.goth/at/gmail/dot/com> _______________________________________________ Tcllib-devel mailing list Tcl...@li... https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Ftcllib-devel&data=02%7C01%7C%7C3d2c52339aca4d86f86408d6bbeb780d%7C15f3fe0ed7124981bc7cfe949af215bb%7C0%7C1%7C636903017351082719&sdata=lwmryFJZSmIAyZezfP5nsGPeFMigYnkEE3V%2FiO8RtXI%3D&reserved=0 DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |
|
From: Andy G. <and...@gm...> - 2019-04-08 06:28:47
|
I'd like to put my pipeline package into Tcllib, but it depends on my argparse package which is not in Tcllib. It may seem like the obvious solution is to also put argparse into Tcllib, but I'm not sure how well that will work with my long-term goals for argparse. Right now argparse is written in pure Tcl 8.6, but once I knock out the rest of my interface-relevant ideas, I want to reimplement it in C to be a loadable extension with a stubs-enabled C API. That makes me think it should be its own TEA-compliant project rather than a Tcllib module, but then if I don't put argparse into Tcllib, I shouldn't put pipeline or other packages that depend on argparse into Tcllib either. Guidance? Thoughts? https://wiki.tcl-lang.org/page/pipeline#853e5dc13add203ce4b75e513189e8f07dc4af458b61e91ce34c3afea8c1e210 https://wiki.tcl-lang.org/page/argparse -- Andy Goth | <andrew.m.goth/at/gmail/dot/com> |
|
From: Andreas K. <aku...@sh...> - 2019-02-21 16:46:33
|
> Am 21.02.2019 um 06:41 schrieb Andreas Kupries: > > The next steps are to go over a number of pending branches, test them, > > and merge. I will start with the older branches first, with thanks to > > their authors for waiting patiently. > > Thank you, Andreas, for all the love you are giving to tcllib. You are welcome. > Small branch "png-get-physical-dimension" is ready for merge and here is > one developper to be found. Yes, that branch is on my list. Currently working on porting gam-namespacex-improve. A bit more complicated than I thought, as the work was based on a modified namespacex vs trunk. > Thank you, > Harald -- See you, Andreas Kupries <aku...@sh...> <http://core.tcl.tk/akupries/> Developer @ SUSE (MicroFocus Canada LLC) <and...@su...> EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/ ------------------------------------------------------------------------------- |
|
From: Harald O. <har...@el...> - 2019-02-21 07:26:38
|
Am 21.02.2019 um 06:41 schrieb Andreas Kupries: > The next steps are to go over a number of pending branches, test them, > and merge. I will start with the older branches first, with thanks to > their authors for waiting patiently. Thank you, Andreas, for all the love you are giving to tcllib. Small branch "png-get-physical-dimension" is ready for merge and here is one developper to be found. Thank you, Harald |
|
From: Andreas K. <aku...@sh...> - 2019-02-21 05:57:11
|
The current head of Tcllib trunk ([e6742077ec]), committed and pushed yesterday evening PST, passed the entire testsuite for me now, against Tcl core versions: 8.4.20 - [649ee985ae] 2013-06-03 18:08 UTC 8.5.19 - [523e36b232] 2019-01-28 16:12 UTC 8.6.9 - [60d2391840] 2019-02-18 20:38 UTC I dropped doing tests against 8.7 for the moment. While an old a2 reported test failures I have issues with installing the current [fc1de63689], something related to the new zipfs and its initialization. As it is still marked as an alpha I decided that it is ok to go without it. As my commit and push of the testsuite fixes implies, I have opened the trunk to commits by myself now. (Much later than I wanted). The next steps are to go over a number of pending branches, test them, and merge. I will start with the older branches first, with thanks to their authors for waiting patiently. After that comes updating and modernizing the "README.developer" file, and adding a file about communication. On a branch, of course, so that we can discuss the changes before committing to them (by merging to trunk). Where `we` will be as many of Tcllib maintainers and developers as can be found (Good thing that the accounts come with email addresses). > In recent days a lot of sparks have flown in the Tcler's chat about > breakage in the Tcllib trunk branch, named "trunk" (what a surprise, > not), standard conformity, breaking the trunk, backward compatibility, > etc. [...] -- See you, Andreas Kupries <aku...@sh...> <http://core.tcl.tk/akupries/> Developer @ SUSE (MicroFocus Canada LLC) <and...@su...> EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/ ------------------------------------------------------------------------------- |
|
From: Andreas K. <aku...@sh...> - 2018-12-10 04:18:57
|
In recent days a lot of sparks have flown in the Tcler's chat about
breakage in the Tcllib trunk branch, named "trunk" (what a surprise,
not), standard conformity, breaking the trunk, backward compatibility,
etc.
No agreements seems to be reached, the fire is still crackling.
I am now clamping down so that when I am back from my upcoming
vacation things will not have devolved into a worse shape than things
currently are.
Wrt the vacation, some more notes: I will be on vacation coming
Saturday, Dec 15, till Jan 3. That means that my free time in the
evenings of the coming week is spent prepping for that.
Add to that that at work I am currently working on a complex version
bump of our code to sync to a more recent release of the complex
upstream project we are using.
I do not really have the time and mind and brain cycles to mediate
this, nor even to review changes.
Despite the evermore clear need that I will have to.
Thus, here are the rules coming down from me in my role as the main
admin for Tcllib:
(1) The current head of the trunk branch of Tcllib is
https://core.tcl-lang.org/tcllib/info/63590365a7174ad1
(2) The trunk branch is now __closed__ to any and all commits and
merges from anybody.
For the next 4 weeks __nothing__ shall happen on trunk (see above
about my vacation).
When I am back from the vacation, and hopefully well rested I am
opening the trunk to merges. By me. Then I will start and check
the state of trunk with respect to tests, and such, and go over
commits in contention.
Yes, this makes me a bottleneck, i.e. merges are done as I am able
to review the incoming proposed changes. While I dislike that, it
looks to be that such a gate is needed.
Please take the time to either come to an agreeable settlement, or
to prepare your respective cases of what you believe should
happen.
(3) Development work can still be done while I am away, however it
__must__ be done in branches.
When the work in the branch is considered complete
- make a ticket and assign to me
- send me mail
- both
I will then review, possibly bounce back to fix whatever I find,
possibly make my own changes to make it acceptable, if they are
small enough.
As a general note I believe that short, focused (feature) branches
are better than long-running (variant) branches.
For the record, it might also be the time to take the disagreement to
here, the tcllib-devel mailing list
Air it here in the more open than the Tcler's Chat, and connected
#tcl, and slack [1].
Actually, discussion about packages and modules to put on the chopping
block ... Tcllib-devel shall be the official place for that. Ditto for
discussions about larger changes of direction for the whole thing.
[1] https://tcl-lang.slack.com/messages/CB29QE8UR/
--
See you,
Andreas Kupries <aku...@sh...>
<http://core.tcl.tk/akupries/>
Developer @ SUSE (MicroFocus Canada LLC)
<and...@su...>
-------------------------------------------------------------------------------
|
|
From: <con...@tc...> - 2018-07-31 17:34:04
|
Hello tcllib-devel, fyi ... 25th Annual Tcl/Tk Conference (Tcl'2018) http://www.tcl.tk/community/tcl2018/ October 15 - 19, 2018 Crowne Plaza Houston River Oaks 2712 Southwest Freeway, 77098 Houston, Texas, USA Important Dates: [[ Attention! Counting down we are now bit a shy of 4 weeks to the submission deadline. * [Registration is open](https://www.tcl.tk/community/tcl2018/register.html) * [Submission is open](https://www.tcl.tk/community/tcl2018/cfp.html) * Our Keynote speaker is [Andrea Casotto](https://www.tcl.tk/community/tcl2018/bios.html#acasotto) * [The tutorials are known](http://www.tcl.tk/community/tcl2018/tutorials.html) Just follow the link. ]] Important Dates: Abstracts and proposals due August 20, 2018 Notification to authors August 27, 2018 WIP and BOF reservations open July 23, 2018 ** may change ** Registration opens IS OPEN Author materials due September 24, 2018 Tutorials Start October 15, 2018 Conference starts October 17, 2018 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2018 will be held in Houston, Texas, USA from October 15, 2018 to October 19, 2018. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences (Proceedings: http://www.tcl.tk/community/conferences.html) have seen submissions covering a wide variety of topics including: * Scientific and engineering applications * Industrial controls * Distributed applications and Network Managment * Object oriented extensions to Tcl/Tk * New widgets for Tk * Simulation and application steering with Tcl/Tk * Tcl/Tk-centric operating environments * Tcl/Tk on small and embedded devices * Medical applications and visualization * Use of different programming paradigms in Tcl/Tk and proposals for new directions. * New areas of exploration for the Tcl/Tk language Submissions should consist of an abstract of about 100 words and a summary of not more than two pages, and should be sent as plain text to tcl...@go... no later than August 20, 2018. Authors of accepted abstracts will have until September 24, 2018 to submit their final paper for the inclusion in the conference proceedings. The proceedings will be made available on digital media, so extra materials such as presentation slides, code examples, code for extensions etc. are encouraged. Printed proceedings will be produced as an on-demand book at lulu.com Online proceedings will appear via http://www.tcl.tk/community/conferences.html The authors will have 30 minutes to present their paper at the conference. The program committee will review and evaluate papers according to the following criteria: * Quantity and quality of novel content * Relevance and interest to the Tcl/Tk community * Suitability of content for presentation at the conference Proposals may report on commercial or non-commercial systems, but those with only blatant marketing content will not be accepted. Application and experience papers need to strike a balance between background on the application domain and the relevance of Tcl/Tk to the application. Application and experience papers should clearly explain how the application or experience illustrates a novel use of Tcl/Tk, and what lessons the Tcl/Tk community can derive from the application or experience to apply to their own development efforts. Papers accompanied by non-disclosure agreements will be returned to the author(s) unread. All submissions are held in the highest confidentiality prior to publication in the Proceedings, both as a matter of policy and in accord with the U. S. Copyright Act of 1976. The primary author for each accepted paper will receive registration to the Technical Sessions portion of the conference at a reduced rate. Other Forms of Participation The program committee also welcomes proposals for panel discussions of up to 90 minutes. Proposals should include a list of confirmed panelists, a title and format, and a panel description with position statements from each panelist. Panels should have no more than four speakers, including the panel moderator, and should allow time for substantial interaction with attendees. Panels are not presentations of related research papers. Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather sessions (BOFs) are available on a first-come, first-served basis starting in July 23, 2018. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in July 23, 2018. Some WIP and BOF time slots will be held open for on-site reservation. All attendees with an interesting work in progress should consider reserving a WIP slot. Registration Information More information on the conference is available the conference Web site (http://www.tcl.tk/community/tcl2018/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference, subscribe to the tcl...@go... list. See: https://groups.google.com/forum/#!forum/tclconference for list information, archive, and subscription. To keep in touch with Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce for list information, archive, and subscription. Conference Committee * Alexandre Ferrieux * Andreas Kupries * Arjen Markus Deltares * Brian Griffin Mentor - A Siemens Business * Clif Flynt Noumena Corp * Gerald Lester RubyLane * Joe Mistachkin Mistachkin Systems * Ronald Fox CAEN Technologies NSCL @ Michigan State University * Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2018 would like to thank those who are sponsoring the conference: * ActiveState Inc * FlightAware * Mentor - A Siemens Business * Noumena Corp * Tcl Community Association |
|
From: Pierre D. <pd...@gm...> - 2018-06-24 13:22:10
|
On Tue, May 15, 2018 at 11:47:58AM +0200, Harald Oehlmann wrote: >Am 15.05.2018 um 11:24 schrieb Pierre DAVID: >> Hi everybody, >> >> could someone have a look on ticket >> 60160205fe965d617482fd65dee13031fc16a1b7 >> https://core.tcl.tk/tcllib/tktview?name=60160205fe >> >> I'm asking for comments before submitting a patch. >> >> Thanks, >> >> Pierre > >Pierre, > >thank you for the message. I think, this is o.k. > >Within the update of the autoproxy package, tls support was also >touched. You may take this package for reference (tcllib folder http). > >- the handshake issue also arised there >- twapi is supported as a 2nd possibility for a tls package > >Do you have write access to core.tcl.tk/tcllib ? >If yes, best would be to prepare a branch. >In the case of the upper package, Andreas cared about it and gave >helpful hints. > The deeper I dig the problem, the more I'm lost. LDAP, as well as many other modules, makes use of the TCL-TLS package. Moreover, applications *must* take care of this package since their documentation explicitely mandate (see "TLS security considerations" in each manpage) the use of tls::init to configure TLS options such as root CA directory/file (while some other TLS options are simply given as ::ldap::* parameters, see ticket). This is incompatible with the use of an alternate TLS package such the one you cite (twapi on Windows). Thus, for applications, there is yet another option, in order to configure the TLS package to use (see ::autoproxy::configure -tls_package), which is rather boring. In my opinion, applications should not have to bother with TLS package at all: they should not have to configure WHICH package to use, neither use any low-level TLS configuration option such as ::tls::init. They should just specify which protocol or root CA location to use, and Tcllib modules should find the appropriate package. In my opinion, the path Tcllib has taken so far to handle TLS is not the right one. I started to implement a ::ldap::tls_options which just specify appropriate options, which are used by ::ldap::secure_connect as well as ::ldap::starttls. Same for ::ldapx::tls which is only a wrapper for the above ::ldap::tls_options. Doing so, LDAP (via a low-level internal Tcllib module) is free to use either TCL-TLS or TWAPI without asking the application to bother with guessing which TLS package is appropriate for the platform. Any opinion on this? Pierre |
|
From: <con...@tc...> - 2018-06-05 05:16:23
|
Hello tcllib-devel, fyi ... 25th Annual Tcl/Tk Conference (Tcl'2018) http://www.tcl.tk/community/tcl2018/ October 15 - 19, 2018 Crowne Plaza Houston River Oaks 2712 Southwest Freeway, 77098 Houston, Texas, USA [ Reminder * [Registration is open](https://www.tcl.tk/community/tcl2018/register.html) * [Submission is open](https://www.tcl.tk/community/tcl2018/cfp.html) * Our Keynote speaker is [Andrea Casotto](https://www.tcl.tk/community/tcl2018/bios.html#acasotto) ] Important Dates: Abstracts and proposals due August 20, 2018 Notification to authors August 27, 2018 WIP and BOF reservations open July 23, 2018 ** may change ** Registration opens IS OPEN Author materials due September 24, 2018 Tutorials Start October 15, 2018 Conference starts October 17, 2018 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2018 will be held in Houston, Texas, USA from October 15, 2018 to October 19, 2018. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences (Proceedings: http://www.tcl.tk/community/conferences.html) have seen submissions covering a wide variety of topics including: * Scientific and engineering applications * Industrial controls * Distributed applications and Network Managment * Object oriented extensions to Tcl/Tk * New widgets for Tk * Simulation and application steering with Tcl/Tk * Tcl/Tk-centric operating environments * Tcl/Tk on small and embedded devices * Medical applications and visualization * Use of different programming paradigms in Tcl/Tk and proposals for new directions. * New areas of exploration for the Tcl/Tk language Submissions should consist of an abstract of about 100 words and a summary of not more than two pages, and should be sent as plain text to tcl...@go... no later than August 20, 2018. Authors of accepted abstracts will have until September 24, 2018 to submit their final paper for the inclusion in the conference proceedings. The proceedings will be made available on digital media, so extra materials such as presentation slides, code examples, code for extensions etc. are encouraged. Printed proceedings will be produced as an on-demand book at lulu.com Online proceedings will appear via http://www.tcl.tk/community/conferences.html The authors will have 30 minutes to present their paper at the conference. The program committee will review and evaluate papers according to the following criteria: * Quantity and quality of novel content * Relevance and interest to the Tcl/Tk community * Suitability of content for presentation at the conference Proposals may report on commercial or non-commercial systems, but those with only blatant marketing content will not be accepted. Application and experience papers need to strike a balance between background on the application domain and the relevance of Tcl/Tk to the application. Application and experience papers should clearly explain how the application or experience illustrates a novel use of Tcl/Tk, and what lessons the Tcl/Tk community can derive from the application or experience to apply to their own development efforts. Papers accompanied by non-disclosure agreements will be returned to the author(s) unread. All submissions are held in the highest confidentiality prior to publication in the Proceedings, both as a matter of policy and in accord with the U. S. Copyright Act of 1976. The primary author for each accepted paper will receive registration to the Technical Sessions portion of the conference at a reduced rate. Other Forms of Participation The program committee also welcomes proposals for panel discussions of up to 90 minutes. Proposals should include a list of confirmed panelists, a title and format, and a panel description with position statements from each panelist. Panels should have no more than four speakers, including the panel moderator, and should allow time for substantial interaction with attendees. Panels are not presentations of related research papers. Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather sessions (BOFs) are available on a first-come, first-served basis starting in July 23, 2018. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in July 23, 2018. Some WIP and BOF time slots will be held open for on-site reservation. All attendees with an interesting work in progress should consider reserving a WIP slot. Registration Information More information on the conference is available the conference Web site (http://www.tcl.tk/community/tcl2018/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference, subscribe to the tcl...@go... list. See: https://groups.google.com/forum/#!forum/tclconference for list information, archive, and subscription. To keep in touch with Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce for list information, archive, and subscription. Conference Committee * Alexandre Ferrieux * Andreas Kupries * Arjen Markus Deltares * Brian Griffin Mentor - A Siemens Business * Clif Flynt Noumena Corp * Gerald Lester RubyLane * Joe Mistachkin Mistachkin Systems * Ronald Fox CAEN Technologies NSCL @ Michigan State University * Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2018 would like to thank those who are sponsoring the conference: * ActiveState Inc * FlightAware * Mentor - A Siemens Business * Noumena Corp * Tcl Community Association |
|
From: Harald O. <har...@el...> - 2018-05-15 09:50:31
|
Am 15.05.2018 um 11:24 schrieb Pierre DAVID: > Hi everybody, > > could someone have a look on ticket > 60160205fe965d617482fd65dee13031fc16a1b7 > https://core.tcl.tk/tcllib/tktview?name=60160205fe > > I'm asking for comments before submitting a patch. > > Thanks, > > Pierre Pierre, thank you for the message. I think, this is o.k. Within the update of the autoproxy package, tls support was also touched. You may take this package for reference (tcllib folder http). - the handshake issue also arised there - twapi is supported as a 2nd possibility for a tls package Do you have write access to core.tcl.tk/tcllib ? If yes, best would be to prepare a branch. In the case of the upper package, Andreas cared about it and gave helpful hints. Thank you, Harald |
|
From: Pierre D. <pd...@gm...> - 2018-05-15 09:24:14
|
Hi everybody,
could someone have a look on ticket 60160205fe965d617482fd65dee13031fc16a1b7
https://core.tcl.tk/tcllib/tktview?name=60160205fe
I'm asking for comments before submitting a patch.
Thanks,
Pierre
|
|
From: <con...@tc...> - 2018-04-05 07:15:47
|
Hello tcllib-devel, fyi ... 25th Annual Tcl/Tk Conference (Tcl'2018) http://www.tcl.tk/community/tcl2018/ October 15 - 19, 2018 Crowne Plaza Houston River Oaks 2712 Southwest Freeway, 77098 Houston, Texas, USA [ NEWS * [Registration is open](https://www.tcl.tk/community/tcl2018/register.html) * [Submission is open](https://www.tcl.tk/community/tcl2018/cfp.html) * Our Keynote speaker is [Andrea Casotto](https://www.tcl.tk/community/tcl2018/bios.html#acasotto) ] Important Dates: Abstracts and proposals due August 20, 2018 Notification to authors August 27, 2018 WIP and BOF reservations open July 23, 2018 ** may change ** Registration opens IS OPEN Author materials due September 24, 2018 Tutorials Start October 15, 2018 Conference starts October 17, 2018 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2018 will be held in Houston, Texas, USA from October 15, 2018 to October 19, 2018. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences (Proceedings: http://www.tcl.tk/community/conferences.html) have seen submissions covering a wide variety of topics including: * Scientific and engineering applications * Industrial controls * Distributed applications and Network Managment * Object oriented extensions to Tcl/Tk * New widgets for Tk * Simulation and application steering with Tcl/Tk * Tcl/Tk-centric operating environments * Tcl/Tk on small and embedded devices * Medical applications and visualization * Use of different programming paradigms in Tcl/Tk and proposals for new directions. * New areas of exploration for the Tcl/Tk language Submissions should consist of an abstract of about 100 words and a summary of not more than two pages, and should be sent as plain text to tcl...@go... no later than August 20, 2018. Authors of accepted abstracts will have until September 24, 2018 to submit their final paper for the inclusion in the conference proceedings. The proceedings will be made available on digital media, so extra materials such as presentation slides, code examples, code for extensions etc. are encouraged. Printed proceedings will be produced as an on-demand book at lulu.com Online proceedings will appear via http://www.tcl.tk/community/conferences.html The authors will have 30 minutes to present their paper at the conference. The program committee will review and evaluate papers according to the following criteria: * Quantity and quality of novel content * Relevance and interest to the Tcl/Tk community * Suitability of content for presentation at the conference Proposals may report on commercial or non-commercial systems, but those with only blatant marketing content will not be accepted. Application and experience papers need to strike a balance between background on the application domain and the relevance of Tcl/Tk to the application. Application and experience papers should clearly explain how the application or experience illustrates a novel use of Tcl/Tk, and what lessons the Tcl/Tk community can derive from the application or experience to apply to their own development efforts. Papers accompanied by non-disclosure agreements will be returned to the author(s) unread. All submissions are held in the highest confidentiality prior to publication in the Proceedings, both as a matter of policy and in accord with the U. S. Copyright Act of 1976. The primary author for each accepted paper will receive registration to the Technical Sessions portion of the conference at a reduced rate. Other Forms of Participation The program committee also welcomes proposals for panel discussions of up to 90 minutes. Proposals should include a list of confirmed panelists, a title and format, and a panel description with position statements from each panelist. Panels should have no more than four speakers, including the panel moderator, and should allow time for substantial interaction with attendees. Panels are not presentations of related research papers. Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather sessions (BOFs) are available on a first-come, first-served basis starting in July 23, 2018. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in July 23, 2018. Some WIP and BOF time slots will be held open for on-site reservation. All attendees with an interesting work in progress should consider reserving a WIP slot. Registration Information More information on the conference is available the conference Web site (http://www.tcl.tk/community/tcl2018/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference, subscribe to the tcl...@go... list. See: https://groups.google.com/forum/#!forum/tclconference for list information, archive, and subscription. To keep in touch with Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce for list information, archive, and subscription. Conference Committee * Alexandre Ferrieux * Andreas Kupries * Arjen Markus Deltares * Brian Griffin Mentor - A Siemens Business * Clif Flynt Noumena Corp * Gerald Lester RubyLane * Joe Mistachkin Mistachkin Systems * Ronald Fox CAEN Technologies NSCL @ Michigan State University * Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2018 would like to thank those who are sponsoring the conference: * ActiveState Inc * FlightAware * Mentor - A Siemens Business * Noumena Corp * Tcl Community Association |
|
From: Pietro C. <ga...@ga...> - 2018-02-21 17:23:33
|
On Feb 21 18 08:25, Andreas Kupries wrote: > >> On Feb 19 18 21:15, Andreas Kupries wrote: >> > >> >A new release of Tcllib, we are now at 1.19. >> >> Hi, as previously mentioned, I see the comm-6.0 test hanging with 8.7a1. >> Please see the log attached, produced with [set comm::comm(debug) 1]. >> >> Any ideas? > >TLS seems to be involved. Which version are you using ? > >Checking my logs ... I have tls 1.6.7.1, and no hang. >Oh, I use 8.7a2. > >Exact commit is >=== 2018-01-11 === 15:45:20 [a0d51b9a0e] It's hanging with 8.7a2 as of core-8-branch [b1bcf543c8]. Tls is at 1.7.14, but that was built with 8.7a1. I will investigate further with different versions of tls. Thanks, -- Pietro Cerutti |
|
From: Pietro C. <ga...@ga...> - 2018-02-21 17:12:34
|
On Feb 19 18 21:15, Andreas Kupries wrote: > >A new release of Tcllib, we are now at 1.19. Hi, as previously mentioned, I see the comm-6.0 test hanging with 8.7a1. Please see the log attached, produced with [set comm::comm(debug) 1]. Any ideas? -- Pietro Cerutti |
|
From: Andreas K. <aku...@sh...> - 2018-02-21 16:40:43
|
> On Feb 19 18 21:15, Andreas Kupries wrote: > > > >A new release of Tcllib, we are now at 1.19. > > Hi, as previously mentioned, I see the comm-6.0 test hanging with 8.7a1. > Please see the log attached, produced with [set comm::comm(debug) 1]. > > Any ideas? TLS seems to be involved. Which version are you using ? Checking my logs ... I have tls 1.6.7.1, and no hang. Oh, I use 8.7a2. Exact commit is === 2018-01-11 === 15:45:20 [a0d51b9a0e] -- See you, Andreas Kupries <aku...@sh...> <http://core.tcl.tk/akupries/> Developer @ SUSE (MicroFocus Canada LLC) <and...@su...> EuroTcl 2018, Jul 7-8, Munich/DE, http://eurotcl.eu/ Tcl'2018, Oct 15-19, Houston, TX, USA. https://www.tcl.tk/community/tcl2018/ ------------------------------------------------------------------------------- |
|
From: Andreas K. <aku...@sh...> - 2018-02-20 05:30:19
|
A new release of Tcllib, we are now at 1.19.
An excerpt from the release README:
7 new packages in 6 modules
52 changed packages in 35 modules
15 internally changed packages in 10 modules
359 unchanged packages in 105 modules
443 packages, total in 130 modules, total
The full details can be found in the release technote.
http://core.tcl.tk/tcllib/technote/0b2528ed32f54c4a8f08951aaa11ff60b3843630
Happy Tcling.
--
See you,
Andreas Kupries <aku...@sh...>
<http://core.tcl.tk/akupries/>
Developer @ SUSE (MicroFocus Canada LLC)
<and...@su...>
EuroTcl 2018, Jul 7-8, Munich/DE, http://eurotcl.eu/
Tcl'2018, Oct 15-19, Houston, TX, USA. https://www.tcl.tk/community/tcl2018/
-------------------------------------------------------------------------------
|
|
From: Pietro C. <ga...@ga...> - 2018-02-18 14:55:37
|
On Feb 16 18 10:12, Andreas Kupries wrote: >On Wed, 14 Feb 2018 08:28:45 +0000 >Pietro Cerutti <ga...@ga...> wrote: > >> On Feb 13 18 00:01, Andreas Kupries wrote: >> > >> >The first release candidate of Tcllib 1.19 is now available. >> > >> >Please test. >> >> Hi, just to tests in the pt module fail on FreeBSD, with Tcl 8.6.8. >> >> Please find the relevant part of the logfile attached. > >This looks to me that your Tcllib 1.19 has a local patch applied, >possibly something to make it compile without warnings, specific to >FreeBSD. > >Can you confirm/falsify ? Ouch, yes, I confirm that the diff is exactly due to a patch we apply to build warning-free. I didn't notice it from the huge test logs, but it clearly shows from your processed output. So sorry for the noise. We do in fact apply a few patches to tcllib. I hope I'll be able to go through them one day and figure out which pieces we can safely do without: https://svnweb.freebsd.org/ports/head/devel/tcllib/files/ Thanks for looking into this! -- Pietro Cerutti |
|
From: Andreas K. <and...@su...> - 2018-02-16 18:13:08
|
On Wed, 14 Feb 2018 08:28:45 +0000 Pietro Cerutti <ga...@ga...> wrote: > On Feb 13 18 00:01, Andreas Kupries wrote: > > > >The first release candidate of Tcllib 1.19 is now available. > > > >Please test. > > Hi, just to tests in the pt module fail on FreeBSD, with Tcl 8.6.8. > > Please find the relevant part of the logfile attached. Thank you very much. First I can say that I do not see any errors with Tcl 8.6.8, which is what I was testing with. Looking at the log I see that the failing tests seem to be for code-generators producing C code. Extracting the expected and actual results using the attached `tsrsplit` script and diffing the two files I see the attached delta (log.udiff). This looks to me that your Tcllib 1.19 has a local patch applied, possibly something to make it compile without warnings, specific to FreeBSD. Can you confirm/falsify ? > > Thanks, > |
|
From: Andreas K. <aku...@sh...> - 2018-02-15 22:58:24
|
> > The first release candidate of Tcllib 1.19 is now available. The files on site now represent the 2nd release candidate. The new SHA256 hashes are attached. The file names and links are unchanged. Changes since the 1st RC: - Update/recreated the certs found under modules/devtools. Using the script `recreate-certs` provided by Roy Keene (tyvm) they were rewritten to be signed with SHA256 instead of the long-deprecated MD5. The script itself was added as well. This will hopefully fix the testsuite issues with TLS/openssl on systems running FIPS 140-2 mode. New origin commit https://core.tcl.tk/tcllib/info/d1e874b7e7 Tagged tcllib-1-19-rc-1 Please continue testing. -- See you, Andreas Kupries <aku...@sh...> <http://core.tcl.tk/akupries/> Developer @ SUSE (MicroFocus Canada LLC) <and...@su...> EuroTcl 2018, Jul 7-8, Munich/DE, http://eurotcl.eu/ Tcl'2018, Oct 15-19, Houston, TX, USA. https://www.tcl.tk/community/tcl2018/ ------------------------------------------------------------------------------- |
|
From: Andreas K. <aku...@sh...> - 2018-02-13 08:16:37
|
The first release candidate of Tcllib 1.19 is now available. Please test. Barring breaking issues this is what I intend to release coming Sunday (Feb 18, 2018). Origin commit https://core.tcl.tk/tcllib/info/aa2214b1fc7d633c Tagged tcllib-1-19-rc-0 SHA256 hashes ... Attached Sizes (ordered by increasing size) 10515 README-1.19.md 17473 README-1.19.txt 6278716 tcllib-1.19.tar.xz 7957464 tcllib-1.19.tar.bz2 10202909 tcllib-1.19.tar.gz 14086366 tcllib-1.19.kit 15476325 tcllib-1.19.zip Donwload links (ordered by increasing size) https://core.tcl.tk/tcllib/uv/README-1.19.md https://core.tcl.tk/tcllib/uv/README-1.19.txt https://core.tcl.tk/tcllib/uv/tcllib-1.19.tar.xz https://core.tcl.tk/tcllib/uv/tcllib-1.19.tar.bz2 https://core.tcl.tk/tcllib/uv/tcllib-1.19.tar.gz https://core.tcl.tk/tcllib/uv/tcllib-1.19.kit https://core.tcl.tk/tcllib/uv/tcllib-1.19.zip -- See you, Andreas Kupries <aku...@sh...> <http://core.tcl.tk/akupries/> Developer @ SUSE (MicroFocus Canada LLC) <and...@su...> EuroTcl 2018, Jul 7-8, Munich/DE, http://eurotcl.eu/ Tcl'2018, Oct 15-19, Houston, TX, USA. https://www.tcl.tk/community/tcl2018/ ------------------------------------------------------------------------------- |
|
From: Andreas K. <aku...@sh...> - 2018-02-09 06:19:36
|
I still plan to look at ticket https://core.tcl.tk/tcllib/tktview/d6c9cfbaf9d9283dd181137c24a1ae1174f79015 (LDIF or LDAPx parser is not working properly: it removes the desired spaces of a ldif file format) and decide on its in/exclusion. Nothing else anymore however, except breaking bugs. Over the comming weekend the RC tarballs will be made for review, and the weekend after that the actual release, pending breaking issues. As usual it has taken way to long. -- See you, Andreas Kupries <aku...@sh...> <http://core.tcl.tk/akupries/> Developer @ SUSE (MicroFocus Canada LLC) <and...@su...> EuroTcl 2018, Jul 7-8, Munich/DE, http://eurotcl.eu/ Tcl'2018, Oct 15-19, Houston, TX, USA. https://www.tcl.tk/community/tcl2018/ ------------------------------------------------------------------------------- |
|
From: <con...@tc...> - 2018-02-06 05:03:49
|
Hello tcllib-devel, fyi ... 25th Annual Tcl/Tk Conference (Tcl'2018) http://www.tcl.tk/community/tcl2018/ October 15 - 19, 2018 Crowne Plaza Houston River Oaks 2712 Southwest Freeway, 77098 Houston, Texas, USA Important Dates: Abstracts and proposals due August 20, 2018 Notification to authors August 27, 2018 WIP and BOF reservations open July 23, 2018 ** may change ** Registration opens August 20, 2018 ** may change ** Author materials due September 24, 2018 Tutorials Start October 15, 2018 Conference starts October 17, 2018 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2018 will be held in Houston, Texas, USA from October 15, 2018 to October 19, 2018. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences (Proceedings: http://www.tcl.tk/community/conferences.html) have seen submissions covering a wide variety of topics including: * Scientific and engineering applications * Industrial controls * Distributed applications and Network Managment * Object oriented extensions to Tcl/Tk * New widgets for Tk * Simulation and application steering with Tcl/Tk * Tcl/Tk-centric operating environments * Tcl/Tk on small and embedded devices * Medical applications and visualization * Use of different programming paradigms in Tcl/Tk and proposals for new directions. * New areas of exploration for the Tcl/Tk language Submissions should consist of an abstract of about 100 words and a summary of not more than two pages, and should be sent as plain text to tcl...@go... no later than August 20, 2018. Authors of accepted abstracts will have until September 24, 2018 to submit their final paper for the inclusion in the conference proceedings. The proceedings will be made available on digital media, so extra materials such as presentation slides, code examples, code for extensions etc. are encouraged. Printed proceedings will be produced as an on-demand book at lulu.com Online proceedings will appear via http://www.tcl.tk/community/conferences.html The authors will have 30 minutes to present their paper at the conference. The program committee will review and evaluate papers according to the following criteria: * Quantity and quality of novel content * Relevance and interest to the Tcl/Tk community * Suitability of content for presentation at the conference Proposals may report on commercial or non-commercial systems, but those with only blatant marketing content will not be accepted. Application and experience papers need to strike a balance between background on the application domain and the relevance of Tcl/Tk to the application. Application and experience papers should clearly explain how the application or experience illustrates a novel use of Tcl/Tk, and what lessons the Tcl/Tk community can derive from the application or experience to apply to their own development efforts. Papers accompanied by non-disclosure agreements will be returned to the author(s) unread. All submissions are held in the highest confidentiality prior to publication in the Proceedings, both as a matter of policy and in accord with the U. S. Copyright Act of 1976. The primary author for each accepted paper will receive registration to the Technical Sessions portion of the conference at a reduced rate. Other Forms of Participation The program committee also welcomes proposals for panel discussions of up to 90 minutes. Proposals should include a list of confirmed panelists, a title and format, and a panel description with position statements from each panelist. Panels should have no more than four speakers, including the panel moderator, and should allow time for substantial interaction with attendees. Panels are not presentations of related research papers. Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather sessions (BOFs) are available on a first-come, first-served basis starting in July 23, 2018. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in July 23, 2018. Some WIP and BOF time slots will be held open for on-site reservation. All attendees with an interesting work in progress should consider reserving a WIP slot. Registration Information More information on the conference is available the conference Web site (http://www.tcl.tk/community/tcl2018/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference, subscribe to the tcl...@go... list. See: https://groups.google.com/forum/#!forum/tclconference for list information, archive, and subscription. To keep in touch with Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce for list information, archive, and subscription. Conference Committee * Alexandre Ferrieux * Andreas Kupries * Arjen Markus Deltares * Brian Griffin Mentor - A Siemens Business * Clif Flynt Noumena Corp * Gerald Lester RubyLane * Joe Mistachkin Mistachkin Systems * Ronald Fox CAEN Technologies NSCL @ Michigan State University * Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2018 would like to thank those who are sponsoring the conference: * ActiveState Inc * FlightAware * Mentor - A Siemens Business * Noumena Corp * Tcl Community Association |
31 messages has been excluded from this view by a project administrator.
