ciphertool-devel Mailing List for Tcl ciphertool (Page 2)
Status: Beta
Brought to you by:
wart
Menu
▾
▴
ciphertool-devel — Developer discussions
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
(3) |
Mar
(23) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Andreas K. <and...@ac...> - 2013-08-06 16:10:02
|
20'th Annual Tcl/Tk Conference (Tcl'2013) http://www.tcl.tk/community/tcl2013/ September 23 - 27, 2013 Bourbon Orleans Hotel New Orleans, Louisiana, USA http://www.bourbonorleans.com/ I am pleased to announce that registration for the Conference is now open at http://www.tcl.tk/community/tcl2013/reg.html To book a room at the conference hotel at reduced rates please follow the instructions on that page. Note that the offer of reduced rates expires on August 19 (In 2 weeks). Book NOW. Our schedule can be found at http://www.tcl.tk/community/tcl2013/schedule.html Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Site/Facilities Chair Arjen Markus Deltares Brian Griffin Mentor Graphics Donal Fellows University of Manchester Gerald Lester KnG Consulting, LLC Jeffrey Hobbs ActiveState Software Inc. Kevin Kenny GE Global Research Center Larry Virden Mike Doyle National Museum of Health & Medicine, Chicago Ron Fox NSCL/FRIB Michigan State University Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2012 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2013-06-05 17:10:32
|
[[ Notes: Abstracts and proposals are now due July 6, 2013 [+ 2 weeks] ]] 20'th Annual Tcl/Tk Conference (Tcl'2013) http://www.tcl.tk/community/tcl2013/ September 23 - 27, 2013 Bourbon Orleans Hotel New Orleans, Louisiana, USA http://www.bourbonorleans.com/ Important Dates: Abstracts and proposals due July 6, 2013 [+ 2 weeks] Notification to authors July 22, 2013 [- 2 weeks] Author materials due September 2, 2013 Tutorials Start September 23, 2013 Conference starts September 25, 2013 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2013 will be held in New Orleans, Louisiana, USA from September 23 - 27, 2013. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences 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 <tclconference AT googlegroups DOT com> no later than August 5, 2013. Authors of accepted abstracts will have until September 2, 2013 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 The authors will have 25 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 August 5, 2013. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in June 3, 2013. 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/tcl2013/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference and Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce to subscribe to the tcl-announce mailing list. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Gerald Lester KnG Consulting, LLC Site/Facilities Chair Arjen Markus Deltares Brian Griffin Mentor Graphics Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Donal Fellows University of Manchester Jeffrey Hobbs ActiveState Software Inc. Kevin Kenny GE Global Research Center Larry Virden Mike Doyle National Museum of Health & Medicine, Chicago Ron Fox NSCL/FRIB Michigan State University Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2013 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2013-04-09 20:57:08
|
[[ Notes: Karl Lehenbauer of FlightAware is confirmed as our Keynote speaker. http://www.flightaware.com ]] 20'th Annual Tcl/Tk Conference (Tcl'2013) http://www.tcl.tk/community/tcl2013/ September 23 - 27, 2013 Bourbon Orleans Hotel New Orleans, Louisiana, USA http://www.bourbonorleans.com/ Important Dates: Abstracts and proposals due June 22, 2013 Notification to authors August 5, 2013 Author materials due September 2, 2013 Tutorials Start September 23, 2013 Conference starts September 25, 2013 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2013 will be held in New Orleans, Louisiana, USA from September 23 - 27, 2013. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences 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 <tclconference AT googlegroups DOT com> no later than August 5, 2013. Authors of accepted abstracts will have until September 2, 2013 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 The authors will have 25 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 August 5, 2013. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in June 3, 2013. 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/tcl2013/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference and Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce to subscribe to the tcl-announce mailing list. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Gerald Lester KnG Consulting, LLC Site/Facilities Chair Arjen Markus Deltares Brian Griffin Mentor Graphics Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Donal Fellows University of Manchester Jeffrey Hobbs ActiveState Software Inc. Kevin Kenny GE Global Research Center Larry Virden Mike Doyle National Museum of Health & Medicine, Chicago Ron Fox NSCL/FRIB Michigan State University Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2013 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2013-02-04 20:36:00
|
20'th Annual Tcl/Tk Conference (Tcl'2013) http://www.tcl.tk/community/tcl2013/ September 23 - 27, 2013 Bourbon Orleans Hotel New Orleans, Louisiana, USA Important Dates: Abstracts and proposals due June 22, 2013 Notification to authors August 5, 2013 Author materials due September 2, 2013 Tutorials Start September 23, 2013 Conference starts September 25, 2013 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2013 will be held in New Orleans, Louisiana, USA from September 23 - 27, 2013. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences 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 <tclconference AT googlegroups DOT com> no later than August 5, 2013. Authors of accepted abstracts will have until September 2, 2013 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 The authors will have 25 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 August 5, 2013. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in June 3, 2013. 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/tcl2013/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference and Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce to subscribe to the tcl-announce mailing list. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Gerald Lester KnG Consulting, LLC Site/Facilities Chair Arjen Markus Deltares Brian Griffin Mentor Graphics Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Donal Fellows University of Manchester Jeffrey Hobbs ActiveState Software Inc. Kevin Kenny GE Global Research Center Larry Virden Mike Doyle National Museum of Health & Medicine, Chicago Ron Fox NSCL/FRIB Michigan State University Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2013 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2012-10-15 17:46:21
|
19th Annual Tcl/Tk Conference (Tcl'2012) http://www.tcl.tk/community/tcl2012/ November 12 - 16, 2012 Sessions: National Museum of Health and Medicine Chicago 175 W. Washington Chicago, IL 60602 Rooms: Holiday Inn Chicago Mart Plaza 350 West Mart Center Drive Chicago, Illinois, USA Map/Transport: https://maps.google.com/maps/ms?msid=204739899073144451536.0004c144222a9036c99f6&msa=0&ll=41.885266,-87.633734&spn=0.008443,0.018818 http://wiki.tcl.tk/28843#pagetoca7e55932 Hello all. This is a reminder that the offer of reduced rates for rooms at the conference hotel expires on October 20, i.e. at the end of this week. Book Now! (if you haven't already). And talk to us should you run into trouble with the Hotel claiming to be sold out already before the deadline. Of course registration for the Conference is still open at http://www.tcl.tk/community/tcl2012/reg.html To book a room at the conference hotel at reduced rates please follow the instructions on that page. Our schedule can be found at http://www.tcl.tk/community/tcl2012/schedule.html Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Site/Facilities Chair Arjen Markus Deltares Brian Griffin Mentor Graphics Donal Fellows University of Manchester Gerald Lester KnG Consulting, LLC Jeffrey Hobbs ActiveState Software Inc. Kevin Kenny GE Global Research Center Larry Virden Mike Doyle National Museum of Health & Medicine, Chicago Ron Fox NSCL/FRIB Michigan State University Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2012 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2012-09-10 18:54:12
|
19th Annual Tcl/Tk Conference (Tcl'2012) http://www.tcl.tk/community/tcl2012/ November 12 - 16, 2012 Sessions: National Museum of Health and Medicine Chicago 175 W. Washington Chicago, IL 60602 Rooms: Holiday Inn Chicago Mart Plaza 350 West Mart Center Drive Chicago, Illinois, USA Map/Transport: https://maps.google.com/maps/ms?msid=204739899073144451536.0004c144222a9036c99f6&msa=0&ll=41.885266,-87.633734&spn=0.008443,0.018818 http://wiki.tcl.tk/28843#pagetoca7e55932 I am pleased to announce that registration for the Conference is now open at http://www.tcl.tk/community/tcl2012/reg.html To book a room at the conference hotel at reduced rates please follow the instructions on that page. Note that the offer of reduced rates expires on October 20. Book early. Our schedule can be found at http://www.tcl.tk/community/tcl2012/schedule.html Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Site/Facilities Chair Arjen Markus Deltares Brian Griffin Mentor Graphics Donal Fellows University of Manchester Gerald Lester KnG Consulting, LLC Jeffrey Hobbs ActiveState Software Inc. Kevin Kenny GE Global Research Center Larry Virden Mike Doyle National Museum of Health & Medicine, Chicago Ron Fox NSCL/FRIB Michigan State University Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2012 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2012-08-07 18:28:26
|
[[
Get your papers, WIPs and posters in.
(We have an exhibition hall with 25 gesture-controlled screens to
show the latter two on).
The deadline for abstracts and proposals is
three weeks away.
]]
[[ Notes:
Colin Walker of F5 is confirmed as our Keynote speaker.
http://www.f5.com
]]
19th Annual Tcl/Tk Conference (Tcl'2012)
http://www.tcl.tk/community/tcl2012/
November 12 - 16, 2012
Sessions:
National Museum of Health and Medicine Chicago
175 W. Washington
Chicago, IL 60602
Rooms:
Holiday Inn Chicago Mart Plaza
350 West Mart Center Drive
Chicago, Illinois, USA
Map:
https://maps.google.com/maps/ms?msid=204739899073144451536.0004c144222a9036c99f6&msa=0&ll=41.885266,-87.633734&spn=0.008443,0.018818
Important Dates:
Abstracts and proposals due August 27, 2012
Notification to authors September 10, 2012
WIP and BOF reservations open August 6, 2012
Author materials due October 29, 2012
Tutorials Start November 12, 2012
Conference starts November 14, 2012
Email Contact: tcl...@go...
Submission of Summaries
Tcl/Tk 2012 will be held in Chicago, Illinois, USA from November 12 -
16, 2012. The program committee is asking for papers and presentation
proposals from anyone using or developing with Tcl/Tk (and
extensions). Past conferences 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 <tclconference AT googlegroups DOT com> no later than August 27,
2012. Authors of accepted abstracts will have until October 29, 2012
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
The authors will have 25 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 August 6, 2012. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in June 2012. 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/tcl2012/) and will be published on
various Tcl/Tk-related information channels.
To keep in touch with news regarding the conference and Tcl events in
general, subscribe to the tcl-announce list. See:
http://code.activestate.com/lists/tcl-announce to subscribe to the
tcl-announce mailing list.
Conference Committee
Clif Flynt Noumena Corp General Chair, Website Admin
Andreas Kupries ActiveState Software Inc. Program Chair
Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Site/Facilities Chair
Arjen Markus Deltares
Brian Griffin Mentor Graphics
Donal Fellows University of Manchester
Gerald Lester KnG Consulting, LLC
Jeffrey Hobbs ActiveState Software Inc.
Kevin Kenny GE Global Research Center
Larry Virden
Mike Doyle National Museum of Health & Medicine, Chicago
Ron Fox NSCL/FRIB Michigan State University
Steve Landers Digital Smarties
Contact Information tcl...@go...
Tcl'2012 would like to thank those who are sponsoring the conference:
ActiveState Software Inc.
Buonacorsi Foundation
Mentor Graphics
Noumena Corp.
SR Technology
Tcl Community Association
|
|
From: Andreas K. <and...@ac...> - 2012-05-30 15:43:09
|
[[ Notes: Colin Walker of F5 is confirmed as our Keynote speaker. http://www.f5.com ]] 19th Annual Tcl/Tk Conference (Tcl'2012) http://www.tcl.tk/community/tcl2012/ November 12 - 16, 2012 Holiday Inn Chicago Mart Plaza 350 West Mart Center Drive Chicago, Illinois, USA Important Dates: Abstracts and proposals due August 27, 2012 Notification to authors September 10, 2012 WIP and BOF reservations open August 6, 2012 Author materials due October 29, 2012 Tutorials Start November 12, 2012 Conference starts November 14, 2012 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2012 will be held in Chicago, Illinois, USA from November 12 - 16, 2012. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences 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 <tclconference AT googlegroups DOT com> no later than August 27, 2012. Authors of accepted abstracts will have until October 29, 2012 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 The authors will have 25 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 August 6, 2012. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in June 2012. 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/tcl2012/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference and Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce to subscribe to the tcl-announce mailing list. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Site/Facilities Chair Arjen Markus Deltares Brian Griffin Mentor Graphics Donal Fellows University of Manchester Gerald Lester KnG Consulting, LLC Jeffrey Hobbs ActiveState Software Inc. Kevin Kenny GE Global Research Center Larry Virden Mike Doyle National Museum of Health & Medicine, Chicago Ron Fox NSCL/FRIB Michigan State University Steve Landers Digital Smarties Contact Information tcl...@go... Tcl'2012 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2012-04-02 19:10:47
|
19th Annual Tcl/Tk Conference (Tcl'2012) http://www.tcl.tk/community/tcl2012/ November 12 - 16, 2012 Holiday Inn Chicago Mart Plaza 350 West Mart Center Drive Chicago, Illinois, USA Important Dates: Abstracts and proposals due August 27, 2012 Notification to authors September 10, 2012 WIP and BOF reservations open August 6, 2012 Author materials due October 29, 2012 Tutorials Start November 12, 2012 Conference starts November 14, 2012 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2012 will be held in Chicago, Illinois, USA from November 12 - 16, 2012. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences 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 <tclconference AT googlegroups DOT com> no later than August 27, 2012. Authors of accepted abstracts will have until October 29, 2012 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 The authors will have 25 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 August 6, 2012. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in June 2012. 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/tcl2012/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference and Tcl events in general, subscribe to the tcl-announce list. See: http://code.activestate.com/lists/tcl-announce to subscribe to the tcl-announce mailing list. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Site/Facilities Chair Brian Griffin Mentor Graphics Ron Fox NSCL/FRIB Michigan State University Arjen Markus Deltares Mike Doyle National Museum of Health & Medicine, Chicago Gerald Lester KnG Consulting, LLC Donal Fellows University of Manchester Jeffrey Hobbs ActiveState Software Inc. Steve Landers Digital Smarties Kevin Kenny GE Global Research Center Contact Information tcl...@go... Tcl'2012 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2011-08-05 20:55:45
|
[[
Get your papers in.
The deadline for abstracts and proposals is
three weeks away.
]]
18th Annual Tcl/Tk Conference (Tcl'2011)
http://www.tcl.tk/community/tcl2011/
October 24 - 28, 2011
Comfort Suites Manassas
Manassas, Virgina, USA
Important Dates:
Abstracts and proposals due August 26, 2011
Notification to authors September 12, 2011
WIP and BOF reservations open August 1, 2011
Author materials due October 9, 2011
Tutorials Start October 24, 2011
Conference starts October 26, 2011
Email Contact: tcl...@go...
Submission of Summaries
Tcl/Tk 2011 will be held in Manassas, Virgina, USA from
October 24 - 28, 2011. The program committee is asking for papers and
presentation proposals from anyone using or developing with Tcl/Tk
(and extensions). Past conferences 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
This year is the fourth year that the Tcl community is participating
in the Google Summer of Code. The conference program committee would
like to encourage submissions that report on the Tcl projects selected
for Google SoC 2011.
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 <tclconference AT googlegroups DOT com> no later than August 26,
2011. Authors of accepted abstracts will have until October 9, 2011
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
The authors will have 25 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.
TCLCA receives first publication rights, and expects that this is the
first time the paper is published. Not a retread from another
conference, etc. TCLCA further receives subsequent publication rights,
to handle the Publish-On-Demand nature of Lulu, our vendor for the
dissemination of the conference proceedings. All other rights are
retained by the author. You can put this on your website, include it
in a book, expand it into a novel, sell the movie rights, etc.
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 August 1, 2011. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in June 2011. 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/tcl2011/) and will be published on
various Tcl/Tk-related information channels.
Reservations for hotel suites can be made by calling
(703) 686-1100. Be certain to mention that you are with the Tcl/Tk
Conference to get the Tcl/Tk Conference room rate.
To keep in touch with news regarding the conference and Tcl events in
general, subscribe to the tcl-announce list. See:
http://aspn.activestate.com/ASPN/Mail/ to subscribe to the
tcl-announce mailing list.
Conference Committee
Clif Flynt Noumena Corp General Chair, Website Admin
Andreas Kupries ActiveState Software Inc. Program Chair
Cyndy Lilagan Iomas Research, LLC
Brian Griffin Mentor Graphics
Ron Fox NSCL/FRIB Michigan State University
Arjen Markus Deltares
Mike Doyle Iomas Research, LLC
Gerald Lester KnG Consulting, LLC
Donal Fellows University of Manchester
Jeffrey Hobbs ActiveState Software Inc.
Steve Landers Digital Smarties
Kevin Kenny GE Global Research Center
Larry Virden Tcl FAQ Maintainer
Steve Redler IV SR Technology
Contact Information tcl...@go...
Tcl'2011 would like to thank those who are sponsoring the conference:
ActiveState Software Inc.
Buonacorsi Foundation
Mentor Graphics
Noumena Corp.
SR Technology
Tcl Community Association
|
|
From: Andreas K. <and...@ac...> - 2011-06-17 16:13:09
|
[[ Important Changes: The Conference Registration Page is live. Regarding special events we are looking into arranging a trip to the Air and Space Museum out near Dulles. This is currently a very tentative thing. If a local person would like to help with this please talk to "cl...@cf...". ]] 18th Annual Tcl/Tk Conference (Tcl'2011) http://www.tcl.tk/community/tcl2011/ October 24 - 28, 2011 Comfort Suites Manassas Manassas, Virgina, USA Important Dates: Abstracts and proposals due August 26, 2011 Notification to authors September 12, 2011 WIP and BOF reservations open August 1, 2011 Author materials due October 9, 2011 Tutorials Start October 24, 2011 Conference starts October 26, 2011 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2011 will be held in Manassas, Virgina, USA from October 24 - 28, 2011. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences 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 This year is the fourth year that the Tcl community is participating in the Google Summer of Code. The conference program committee would like to encourage submissions that report on the Tcl projects selected for Google SoC 2011. 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 <tclconference AT googlegroups DOT com> no later than August 26, 2011. Authors of accepted abstracts will have until October 9, 2011 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 The authors will have 25 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 August 1, 2011. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in June 2011. 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/tcl2011/) and will be published on various Tcl/Tk-related information channels. Reservations for hotel suites can be made by calling (703) 686-1100. Be certain to mention that you are with the Tcl/Tk Conference to get the Tcl/Tk Conference room rate. To keep in touch with news regarding the conference and Tcl events in general, subscribe to the tcl-announce list. See: http://aspn.activestate.com/ASPN/Mail/ to subscribe to the tcl-announce mailing list. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Iomas Research, LLC Brian Griffin Mentor Graphics Ron Fox NSCL/FRIB Michigan State University Arjen Markus Deltares Mike Doyle Iomas Research, LLC Gerald Lester KnG Consulting, LLC Donal Fellows University of Manchester Jeffrey Hobbs ActiveState Software Inc. Steve Landers Digital Smarties Kevin Kenny GE Global Research Center Larry Virden Tcl FAQ Maintainer Steve Redler IV SR Technology Contact Information tcl...@go... Tcl'2011 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2011-04-11 19:08:50
|
18th Annual Tcl/Tk Conference (Tcl'2011) http://www.tcl.tk/community/tcl2011/ October 24 - 28, 2011 Comfort Suites Manassas Manassas, Virgina, USA Important Dates: Abstracts and proposals due August 26, 2011 Notification to authors September 12, 2011 WIP and BOF reservations open August 1, 2011 Author materials due October 9, 2011 Tutorials Start October 24, 2011 Conference starts October 26, 2011 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2011 will be held in Manassas, Virgina, USA from October 24 - 28, 2011. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences 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 This year is the fourth year that the Tcl community is participating in the Google Summer of Code. The conference program committee would like to encourage submissions that report on the Tcl projects selected for Google SoC 2011. 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 <tclconference AT googlegroups DOT com> no later than August 30, 2011. Authors of accepted abstracts will have until October 14, 2011 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 The authors will have 25 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 August 1, 2011. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in June 2011. 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/tcl2011/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference and Tcl events in general, subscribe to the tcl-announce list. See: http://aspn.activestate.com/ASPN/Mail/ to subscribe to the tcl-announce mailing list. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Iomas Research, LLC Brian Griffin Mentor Graphics Ron Fox NSCL/FRIB Michigan State University Arjen Markus Deltares Mike Doyle Iomas Research, LLC Gerald Lester KnG Consulting, LLC Donal Fellows University of Manchester Jeffrey Hobbs ActiveState Software Inc. Steve Landers Digital Smarties Kevin Kenny GE Global Research Center Larry Virden Tcl FAQ Maintainer Steve Redler IV SR Technology Contact Information tcl...@go... Tcl'2011 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2010-09-09 15:51:54
|
17th Annual Tcl/Tk Conference (Tcl'2010) http://www.tcl.tk/community/tcl2010/ October 11 - 15, 2010 Hilton Suites/Conference Center Chicago/Oakbrook Terrace, Illinois, USA Registration for the Conference is open at http://www.tcl.tk/community/tcl2010/reg.html To book a room at the conference hotel at reduced rates follow the link on that page. Note that this offer expires on September 26. Book early. Our schedule can be found at http://www.tcl.tk/community/tcl2010/schedule.html We have special social activites October 15, 2010 - Friday afternoon -- Tour of Fermilab Fermi National Accelerator Laboratory, http://www.fnal.gov/ Tour signup is at the conference, Wednesday, Oct 13. A tour lasts about two hours and begins in Wilson Hall. Visitors view the Laboratory from the 15th floor windows and visit various displays located there. The tour moves to the Linear Accelerator building where visitors see the Cockcroft-Walton, the components in the linear accelerator gallery and the Main Control Room. There is a docent for every 20 people. Registration required since tours must be arranged in advance. October 15, 2010 - Friday evening Dinner-theater at the award winning Drury Lane theater located next to our hotel. Special package price for dinner and theater at $44.00 per person. Regularly $64 per person. Please make reservation and payment at time of registration, or by Wednesday Oct 13 latest (at the conference). "Seven Brides for Seven Brothers" http://www.drurylaneoakbrook.com/ Bill Jenkins is one of the newest and most exciting new directors on the Chicago scene. As Chairman of the Department of Theatre and Dance at Ball State University, he heads one of the nation's largest theatre programs. After admiring his work with other Chicago area theatres, we are very pleased for this opportunity to showcase his talent at Drury Lane. Once Bill shared some of the fresh ideas and insights he had for ÂSeven Brides for Seven BrothersÂ, we knew we would have a great show for the holidays. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Iomas Research, LLC Facilities Coordination Brian Griffin Mentor Graphics Ron Fox NSCL/FRIB Michigan State University Arjen Markus Deltares Mike Doyle Iomas Research, LLC Gerald Lester KnG Consulting, LLC Donal Fellows University of Manchester Jeffrey Hobbs ActiveState Software Inc. Steve Landers Digital Smarties Kevin Kenny GE Global Research Center Larry Virden Tcl FAQ Maintainer Steve Redler IV SR Technology Contact Information tcl...@go... Tcl'2010 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Andreas K. <and...@ac...> - 2010-03-22 16:55:26
|
17th Annual Tcl/Tk Conference (Tcl'2010) http://www.tcl.tk/community/tcl2010/ October 11 - 15, 2010 Hilton Suites/Conference Center Chicago/Oakbrook Terrace, Illinois, USA Important Dates: Abstracts and proposals due August 1, 2010 Notification to authors August 15, 2010 WIP and BOF reservations open August 1, 2010 Author materials due October 1, 2010 Tutorials Start October 11, 2010 Conference starts October 13, 2010 Email Contact: tcl...@go... Submission of Summaries Tcl/Tk 2010 will be held in Chicago/Oakbrook Terrace, Illinois USA from October 11 - 15, 2010. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences 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 This year is the third year that the Tcl community is participating in the Google Summer of Code. The conference program committee would like to encourage submissions that report on the Tcl projects selected for Google SoC 2010. 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 <tclconference AT googlegroups DOT com> no later than August 15, 2010. Authors of accepted abstracts will have until October 1, 2010 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 The authors will have 25 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 August 1, 2010. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in June 2010. 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/tcl2010/) and will be published on various Tcl/Tk-related information channels. To keep in touch with news regarding the conference and Tcl events in general, subscribe to the tcl-announce list. See: http://aspn.activestate.com/ASPN/Mail/ to subscribe to the tcl-announce mailing list. Conference Committee Clif Flynt Noumena Corp General Chair, Website Admin Andreas Kupries ActiveState Software Inc. Program Chair Cyndy Lilagan Iomas Research, LLC Facilities Coordination Brian Griffin Mentor Graphics Ron Fox NSCL/FRIB Michigan State University Arjen Markus Deltares Mike Doyle Iomas Research, LLC Gerald Lester KnG Consulting, LLC Donal Fellows University of Manchester Jeffrey Hobbs ActiveState Software Inc. Steve Landers Digital Smarties Kevin Kenny GE Global Research Center Ken Jones Avia Training Larry Virden Tcl FAQ Maintainer Steve Redler IV SR Technology Contact Information tcl...@go... Tcl'2010 would like to thank those who are sponsoring the conference: ActiveState Software Inc. Buonacorsi Foundation Mentor Graphics Noumena Corp. SR Technology Tcl Community Association |
|
From: Wart <wa...@ko...> - 2004-04-03 05:24:34
|
On Wed, 2004-03-31 at 20:12, Alex Griffing wrote: > Hi Mike, > > To address the problem of redundant keys possibly generating conflicts, > maybe there could be a canonical key which doesn't contain any redundant > key information and then an auxiliary key that contains the other > information. For example, for an aristocrat, it could be something like: > > cipher1.type=aristocrat > cipher1.author=alex > cipher1.title=foo > cipher1.ciphertext="..." > cipher1.plaintext="..." > cipher1.key="..." "..." > cipher1.auxkey.subtype=k4 > cipher1.auxkey.keyword1="blah" > cipher1.auxkey.keyword2="word" > > I left out the ciphertext, plaintext, and key since I was too lazy. > Anyway, the only key information you need to encipher/decipher would be > in cipher1.key, but any additional information could be in > cipher1.auxkey. Also I guess it would be good to be clear which values > get quotes around them and which don't. This sounds good. Let's use the "key" attribute to be the canonical key attribute for all ciphers then. Here is some clarification on the use of quotes in the key: "Quotation marks must be used to delimit any part of a multi-part key that contains spaces. The quotation marks are optional if the multi-part key part does not contain any spaces. Quotation marks are also optional for single part keys, such as the trifid, even if they contain spaces." I'll add the save file description along with the list of cipher names, key descriptions, and any type-specific attributes to the ciphertool documentation. ciphertool's parser for the new format has already been written. I'm in the process of adding unit tests for the various corner cases now. --Mike |
|
From: Wart <wa...@ko...> - 2004-04-01 01:41:00
|
I forgot to send this to ciphertool-devel. Sorry! On Tue, 2004-03-30 at 20:43, Alex Griffing wrote: > type > period > plaintext > ciphertext > key > keyword > author > title > language I would like to propose that this is the canonical set of information that defines a cipher. Any additional properties are not allowed to override the values above. For example, if an aristocrat cipher has the "key" and "k1key" properties defined, the "key" property must take precedence when an application creates a particular cipher instance. This will prevent problems if multiple attributes contain redundant information. But this also means that we need to come up with a standard way of describing cipher keys so that they are understandable to different applications. We also need a standard set of names for the different cipher types. The general format for keys that I've been using for substitution ciphers is a pair of strings delimited by quotation marks: cipher1.key="ciphertext" "plaintext" As an example: cipher1.type=aristocrat cipher1.key="abcdefghijklmnopqrstuvwxyz" "b c d " Note that this is only a partial key. It could also have been written as: cipher1.type=aristocrat cipher1.key="amw" "bcd" Transposition ciphers use an alphabetic key, where a=1, b=2, etc.: cipher1.type=columnar cipher1.key=cba Since the key structure can vary between cipher types, we will need to generate a list of key formats for all cipher types. The formats must allow for partial keys, as in the aristocrat example above. As an alternative, we could use multiple key properties to describe more complicated keys: cipher1.type=trisquare cipher1.key.part1=abcdefghiklmnopqrstuvwxyz cipher1.key.part2=abcdefghiklmnopqrstuvwxyz cipher1.key.part3=abcdefghiklmnopqrstuvwxyz Here is a list of the cipher names and key structures currently used by ciphertool. Most of these formats were chosen to match the internal key representations used by ciphertool. Feel free to make suggestions for changes. type=aristocrat # key="ct" "pt" # length of ct and pt strings in the key must be identical key="abcdefghijklmnopqrstuvwxyz" "bcdefghijklmnopqrstuvwxzya" key="abc" "def" type=amsco # key contains letters to indicate the order in which columns are read # a=1, b=2, etc. key="dacb" type=baconian key="abcdefghijklnopqrstuvwxyz" "aabbaabbaabbaabbaabbaabbaa" type=beaufort type=vigenere type=variant type=porta type=gronsfeld # key is a set of ct -> pt substitutions, in order. The # length of the pt/ct pairs must match. # If the period and key are both specified then the period # must match the key length. If only the key is specified # then the period is determined by the length of the key. # If only the period is specified then the key is a # string containing repeats of the letter 'a'. period=6 # In this example, 'a' stands for 'd' in column 1, 'a' # stands for 'e' in column 2, etc. key="denser" "aaaaaa" type=bazeries # The key is the polybius square, read off by rows, and # followed by the numeric decimation numbers. ACA standards # require that the polybius square e derived from the # decimation number. This key format does not impose # such a restriction. key="fortyheusandwvibcgklmpqxz 43275" type=bifid type=bigbifid # The key is a pair of strings containing plaintext letters # and their positions in the keysquare. The positions are # given as 2 digits indicating the row and column where the # letter appears in the key. '0' is used to indicate that # the row/column is not known. For example, "03" indicates # that the letter is in the 3rd column, but the row is not # known. "00" can be used to indicate that neither the row # nor the column is known, or the letter can simply be omitted # from the first string. The position string must be exactly # twice as long as the plaintext string. bigbifid and bigplayfair # keys use a 6x6 keysquare, so valid row and column values range # from 0 to 6. key="abcdefghiklmnopqrstuvwxyz" "24253132113334352241144223134344455121151252535455" key="abc" "012344" type=fmorse type=morbit type=pollux # The key is a pair of strings containing the plaintext # characters and their fractionated morse substitutes. The # fractionated morse substitution string must be exactly # 3 times as long as the plaintext string. The morbit # substitution string must be twice as long. The pollux # substitution string must be the same length as the # plaintext string. key="abcdefghijklmnopqrstuvwxyz" "..x.xx-..-.-.---.x--.-----x-x.-x-..--xx.-.x.....x.-.x.x.x.-xx-.x--x-xxx..x-xx-" key="abc" "..x.xx-.." type=foursquare type=twosquare # The key is a pair of polybius keysquares, read off by # rows. Spaces are used to indicate blank cells in # the keysquares. The first keysquare is the first # plaintext substitute, the second keysquare is the # second plaintext substitute. key="pdfsvibgqwcahoxteknyurlmz" "puzlefdcbaghikmsrqontvwxy" type=grandpre # The key is the 8x8 keysquare, read off by rows. Spaces # are used to indicate blank cells in the keysquare. key=gymkhanaacquaintrewardeddefiniteexposurenovelizeinjuriesambition type=grille # I'm not quite sure what the hell I was thinking with # this one... key=1342342142313321322441441311411243314143342412423421424324211232311243323313223224413411314234214213 type=gromark # The key is the k3mixed alphabet key=aemuicjqzlfnwrbhpysgoxvdkt type=homophonic # The key is a pair of ciphertext / plaintext strings. Use # spaces in the plaintext string to indicate unknowns. key="01 26 51 76" "xmas" key="01 26 51 76" "x s" type=columnar type=myszcowski type=nitrans # The key is the order in which the columns are read out # from the tableau. These types use letters instead of # numbers for the key values in order to support # periods > 9. For the myszcowski, duplicate letters # may be used. If a letter is duplicated then the next # letter in the sequence is skipped. key=cdab key=aacceeeh type=nicodemus # The nicodemus key is a pair of strings representing # the vigenere/variant/beaufort encoding key and the # order in which the keys are read off. key="bumblebee aihbgdcef" type=phillips type=playfair type=bigplayfair # The key is the polybius keysquare, read off by rows. # Spaces are used to denote empty cells in the keysquare # The key must be exactly 25 letters long, except for # the bigplayfair key which must be 36 characters long. key=maeksoyflvrbgnwtchpxudiqz type=ragbaby # The key is the 24 letter keyed alphabet key=sailorbcdefghkmnpqtuvwyz type=route # The key is a pair of numbers indicating which route was # used to read/write the plaintext. See # http://ciphertool.sourceforge.net/cipher/route.html # for a list of the 48 defined routes. key=23 11 type=swagman # Please don't make me try to explain this one... I # get confused every time I look at it. key=2415345321312455341212534 type=trifid # The key is the 27 character keyed alphabet. key=quickstep#abdfghjlmnorvwxyz --Wart |
|
From: Wart <wa...@ko...> - 2004-03-31 19:55:09
|
I'll start working on a new reader/writer for this format for ciphertool. After the reader/writer is working then I'll convert the sample ciphers to the new format. Luckily ciphertool already uses a single procedure for reading and one more for writing files, so the transition to the new format should be pretty painless. --Mike On Wed, 2004-03-31 at 11:34, Alex Griffing wrote: > That looks great! > > -Alex |
|
From: Alex G. <za...@za...> - 2004-03-31 19:34:34
|
That looks great! -Alex |
|
From: Wart <wa...@ko...> - 2004-03-31 19:21:56
|
Hi Alex,
On Wed, 2004-03-31 at 07:04, Alex Griffing wrote:
> Well here are a couple related situations I'd like to avoid:
>
> 1) I'm adding a new k2-keyed patristocrat to the list. I've entered
> the k2 keyword, the plaintext, the ciphertext, and the type. However,
> when I run the program it complains that there is no 'bacontext'
> associated with this cipher entry.
>
> 2) I've added a new cipher type with the new attribute 'cipherfoo' and
> I've written new code to deal with it. I don't want to have to go back
> and add 'cipherfoo=' to every cipher entry (of all types) in the list.
I think these problems can be easily avoided. If the attributes are all
optional (except for ciphertext), then the file loader wouldn't complain
if any property was missing unless the file loader explicitly requires
certain property combinations (such as 'period' for type=vigenere).
Here are the steps that a "read_file" function would perform:
1) Open the file for reading
2) Read the file line by line.
a) If a line ends with '\', string the '\' and append the next line
to it.
b) If a line starts with '#', discard it.
4) Split each line into key/value pairs. Throw an error if a '=' is not
found anywhere on the line.
3) Group the lines by cipher id (for files containing multiple ciphers).
5) Iterate through each group
a) Look for the ciphertext. Throw an error if the ciphertext isn't
found.
b) Perform basic validation of values. For example, all periods
must be integers, or the cipher type must be one of a specific set of
known cipher types.
c) Look for the cipher type. Perform any type-specific validation
of parameters. For example, the width for a route cipher must evenly
divide into the length of the ciphertext. Another example is that the
bacontext can only appear with the baconian cipher.
d) Populate some sort of cipher data structure with the set values.
e) return some sort of cipher data structure containing the found
properties
The validation checks only check for very basic inconsistencies. This
lets us store only the known information in the cipher file. It allows
for easy addition of new properties since the validation can simply
ignore any properties that it does not recognize. The following would
all be valid files:
-----
# This is a basic aristocrat file that hasn't been solved
cipher1.type=aristocrat
cipher1.ciphertext=ab cde fgh ijklm
-----
# This file contains a solved vigenere and an unsolved aristocrat
cipher1.type=vigenere
cipher1.ciphertext=abcdefghijklmn
cipher1.period=3
cipher1.key=dog
cipher1.keyword=dog
# Here is the aristocrat in the same file
cipehr2.type=aristocrat
cipher2.ciphertext=ab cde fgh ijklm
-----
# This file contains unknown ciphertext
cipher1.ciphertext=abcdefghijkl
-----
# This file introduces a new attribute
cipher1.type=aristocrat
cipher1.ciphertext=ab cde fgh ijklm
cipher1.new_attribute=anything can go here
By separating the cipher data from the validation code we can write
strict or loose validators. New attributes can be added without
breaking existing validation code. Inconsistent attribute combinations
(route with length 12 and width=5) can be handled appropriately.
Unnecessary attributes can be ignored (such as the period for an
aristocrat) or generate a non-fatal warning.
Does this sound like something that would suit your needs?
--Mike
> Wart wrote:
>
> >On Tue, 2004-03-30 at 20:43, Alex Griffing wrote:
> >
> >
> >>>Major tasks:
> >>>
> >>>1) Add an "encode pt key" subcommand to all cipher types to make it easy
> >>>to encrypt plaintext using a given key. This will make it possible to
> >>>write scripts that encode the same plaintext or different plaintext
> >>>samples in a variety of ways to analyze the statistical characteristics
> >>>of the encryption methods.
> >>>
> >>>2) Implement a new more portable file format for cipher data. Some
> >>>discussion has already begun on this. We need to continue the
> >>>discussion and come to a conclusion on the final format.
> >>>
> >>>
> >>>
> >>These sound like projects that could be helpful for lots of people
> >>working on classical cryptology.
> >>
> >>
> >
> >The first project was spawned out of laziness. I got annoyed by
> >hand-encoding the sample bifid cipher included with ciphertool. :)
> >
> >As I might have mentioned before, the
> >
> >
> >>cipher file format problem seems like an almost contrived example for
> >>what xml is for. I've never used xml though, and I don't know if this
> >>would be a sledgehammer vs. fly situation.
> >>
> >>
> >
> >Having worked a lot with XML, I think it would be a little bit of
> >overkill for this situation. XML is much more suited for highly
> >structured and hierarchical data. Here we just have a simple list of
> >key/value pairs with no strong structure.
> >
> >The big problem with using XML, though, is the amount of work required
> >to read/write it. XML parsers do exist for Tcl. But the API for using
> >XML parsers in general tends to be somewhat verbose. And the use of XML
> >would add another dependency on an external software package. If
> >possible, I like to keep the number of external dependencies to a
> >minimum.
> >
> >The Java property file syntax might be better suited for this data. The
> >format for this file type is a set of key/value pairs separated by a
> >single '=' character. Keys can only contain alphanumeric characters,
> >including '.', '-', and '_', but not '='. Values can contain any
> >character. A backslash '\' at the end of a line indicates that the
> >value continues on to the next line. For example:
> >
> >type=aristocrat
> >ciphertext=ab cde fgh ijklm
> >plaintext=my dog \
> >has fleas
> >key=abcde fleas
> >title=Sample
> >author=wart
> >
> >If we want to support multiple ciphers in a single file then we can
> >prefix each key name with a unique, but arbitrary, cipher id:
> >
> >cipher1.type=aristocrat
> >cipher1.ciphertext=ab cde efghi
> >...
> >cipher2.type=vigenere
> >cipher2.period=6
> >
> >
> >
> >> type
> >> period
> >> plaintext
> >> ciphertext
> >> key
> >> keyword
> >> author
> >> title
> >> language
> >>
> >>
> >
> >I'll add to this:
> >
> >for aristocrat types:
> >
> >k1key
> >fixedkey
> >k2key
> >
> >for morse types (pollux, morbit, fractionated morse):
> >
> >morsetext
> >
> >for baconian types:
> >
> >bacontext
> >
> >for progressive types:
> >
> >progressionEncoding
> >progressionIncrement
> >
> >
> >
> >>might all fit in well as attributes. Some of these could be forbidden
> >>from use in certain cipher types (eg. period/aristocrat). Others could
> >>be mandatory (eg. period/vigenere). Author and title could, for
> >>example, always be optional regardless of cipher type.
> >>
> >>
> >
> >Instead of being forbidden, couldn't they just be ignored by the
> >function that reads the file? For example, if an aristocrat is loaded,
> >then the period field would just get ignored.
> >
> >All of these
> >
> >
> >>conditions could be enforced by the xml DTD (document type definition)
> >>
> >>
> >
> >xml dtds (and xml schema) introduce a little more complexity. If you
> >don't use a validating xml parser then the DTD and schema aren't used
> >and are pretty much useless. If you use a validating xml parser when
> >you read the files, then the DTD or schema must be made available to the
> >parser. This means they have to be made available in a well-known
> >location. This is all entirely possible, but I feel that it's a little
> >bit of overkill for ciphertool.
> >
> >The property file syntax can also be validated, but the validation would
> >have to be part of the function that reads the file. I don't think
> >that's such a bad thing. I'm not sure that there's too much we need to
> >validate anyway. The only real required field that I see is the
> >'ciphertext' field. I envision using the files to store everything from
> >unidentified ciphertext (type is 'unknown' or missing), to half-solved
> >ciphers (type is known, period is '0' or missing), to completed ciphers
> >(keyword is known). In some cases a field might be required but not
> >known (the period for an unsolved vigenere for example).
> >
> >On the other hand, having stricter validation of
> >
> >
> >
> >>Or it could all be in plain text files which might make more sense if
> >>not many people are using it.
> >>
> >>
> >
> >I think the property file format would be a little better suited for our
> >purpose. I could probably still be convinced to make more fields
> >required or make more fields required only for certain cipher types
> >(period, for example). It's getting late, I'll sleep on it.
> >
> >--Wart
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by: IBM Linux Tutorials
> >Free Linux tutorial presented by Daniel Robbins, President and CEO of
> >GenToo technologies. Learn everything from fundamentals to system
> >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> >_______________________________________________
> >ciphertool-devel mailing list
> >cip...@li...
> >https://lists.sourceforge.net/lists/listinfo/ciphertool-devel
> >
> >
> >
> >
> >
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> ciphertool-devel mailing list
> cip...@li...
> https://lists.sourceforge.net/lists/listinfo/ciphertool-devel
|
|
From: Alex G. <za...@za...> - 2004-03-31 18:02:07
|
Here's a really interesting project (at least to me): http://www.phil.uni-passau.de/linguistik/mitarbeiter/schneider/NTL/ - Alex |
|
From: Alex G. <za...@za...> - 2004-03-31 15:05:20
|
Well here are a couple related situations I'd like to avoid: 1) I'm adding a new k2-keyed patristocrat to the list. I've entered the k2 keyword, the plaintext, the ciphertext, and the type. However, when I run the program it complains that there is no 'bacontext' associated with this cipher entry. 2) I've added a new cipher type with the new attribute 'cipherfoo' and I've written new code to deal with it. I don't want to have to go back and add 'cipherfoo=' to every cipher entry (of all types) in the list. Wart wrote: >On Tue, 2004-03-30 at 20:43, Alex Griffing wrote: > > >>>Major tasks: >>> >>>1) Add an "encode pt key" subcommand to all cipher types to make it easy >>>to encrypt plaintext using a given key. This will make it possible to >>>write scripts that encode the same plaintext or different plaintext >>>samples in a variety of ways to analyze the statistical characteristics >>>of the encryption methods. >>> >>>2) Implement a new more portable file format for cipher data. Some >>>discussion has already begun on this. We need to continue the >>>discussion and come to a conclusion on the final format. >>> >>> >>> >>These sound like projects that could be helpful for lots of people >>working on classical cryptology. >> >> > >The first project was spawned out of laziness. I got annoyed by >hand-encoding the sample bifid cipher included with ciphertool. :) > >As I might have mentioned before, the > > >>cipher file format problem seems like an almost contrived example for >>what xml is for. I've never used xml though, and I don't know if this >>would be a sledgehammer vs. fly situation. >> >> > >Having worked a lot with XML, I think it would be a little bit of >overkill for this situation. XML is much more suited for highly >structured and hierarchical data. Here we just have a simple list of >key/value pairs with no strong structure. > >The big problem with using XML, though, is the amount of work required >to read/write it. XML parsers do exist for Tcl. But the API for using >XML parsers in general tends to be somewhat verbose. And the use of XML >would add another dependency on an external software package. If >possible, I like to keep the number of external dependencies to a >minimum. > >The Java property file syntax might be better suited for this data. The >format for this file type is a set of key/value pairs separated by a >single '=' character. Keys can only contain alphanumeric characters, >including '.', '-', and '_', but not '='. Values can contain any >character. A backslash '\' at the end of a line indicates that the >value continues on to the next line. For example: > >type=aristocrat >ciphertext=ab cde fgh ijklm >plaintext=my dog \ >has fleas >key=abcde fleas >title=Sample >author=wart > >If we want to support multiple ciphers in a single file then we can >prefix each key name with a unique, but arbitrary, cipher id: > >cipher1.type=aristocrat >cipher1.ciphertext=ab cde efghi >... >cipher2.type=vigenere >cipher2.period=6 > > > >> type >> period >> plaintext >> ciphertext >> key >> keyword >> author >> title >> language >> >> > >I'll add to this: > >for aristocrat types: > >k1key >fixedkey >k2key > >for morse types (pollux, morbit, fractionated morse): > >morsetext > >for baconian types: > >bacontext > >for progressive types: > >progressionEncoding >progressionIncrement > > > >>might all fit in well as attributes. Some of these could be forbidden >>from use in certain cipher types (eg. period/aristocrat). Others could >>be mandatory (eg. period/vigenere). Author and title could, for >>example, always be optional regardless of cipher type. >> >> > >Instead of being forbidden, couldn't they just be ignored by the >function that reads the file? For example, if an aristocrat is loaded, >then the period field would just get ignored. > >All of these > > >>conditions could be enforced by the xml DTD (document type definition) >> >> > >xml dtds (and xml schema) introduce a little more complexity. If you >don't use a validating xml parser then the DTD and schema aren't used >and are pretty much useless. If you use a validating xml parser when >you read the files, then the DTD or schema must be made available to the >parser. This means they have to be made available in a well-known >location. This is all entirely possible, but I feel that it's a little >bit of overkill for ciphertool. > >The property file syntax can also be validated, but the validation would >have to be part of the function that reads the file. I don't think >that's such a bad thing. I'm not sure that there's too much we need to >validate anyway. The only real required field that I see is the >'ciphertext' field. I envision using the files to store everything from >unidentified ciphertext (type is 'unknown' or missing), to half-solved >ciphers (type is known, period is '0' or missing), to completed ciphers >(keyword is known). In some cases a field might be required but not >known (the period for an unsolved vigenere for example). > >On the other hand, having stricter validation of > > > >>Or it could all be in plain text files which might make more sense if >>not many people are using it. >> >> > >I think the property file format would be a little better suited for our >purpose. I could probably still be convinced to make more fields >required or make more fields required only for certain cipher types >(period, for example). It's getting late, I'll sleep on it. > >--Wart > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >ciphertool-devel mailing list >cip...@li... >https://lists.sourceforge.net/lists/listinfo/ciphertool-devel > > > > > |
|
From: Wart <wa...@ko...> - 2004-03-31 07:48:43
|
On Tue, 2004-03-30 at 20:43, Alex Griffing wrote: > > >Major tasks: > > > >1) Add an "encode pt key" subcommand to all cipher types to make it easy > >to encrypt plaintext using a given key. This will make it possible to > >write scripts that encode the same plaintext or different plaintext > >samples in a variety of ways to analyze the statistical characteristics > >of the encryption methods. > > > >2) Implement a new more portable file format for cipher data. Some > >discussion has already begun on this. We need to continue the > >discussion and come to a conclusion on the final format. > > > These sound like projects that could be helpful for lots of people > working on classical cryptology. The first project was spawned out of laziness. I got annoyed by hand-encoding the sample bifid cipher included with ciphertool. :) As I might have mentioned before, the > cipher file format problem seems like an almost contrived example for > what xml is for. I've never used xml though, and I don't know if this > would be a sledgehammer vs. fly situation. Having worked a lot with XML, I think it would be a little bit of overkill for this situation. XML is much more suited for highly structured and hierarchical data. Here we just have a simple list of key/value pairs with no strong structure. The big problem with using XML, though, is the amount of work required to read/write it. XML parsers do exist for Tcl. But the API for using XML parsers in general tends to be somewhat verbose. And the use of XML would add another dependency on an external software package. If possible, I like to keep the number of external dependencies to a minimum. The Java property file syntax might be better suited for this data. The format for this file type is a set of key/value pairs separated by a single '=' character. Keys can only contain alphanumeric characters, including '.', '-', and '_', but not '='. Values can contain any character. A backslash '\' at the end of a line indicates that the value continues on to the next line. For example: type=aristocrat ciphertext=ab cde fgh ijklm plaintext=my dog \ has fleas key=abcde fleas title=Sample author=wart If we want to support multiple ciphers in a single file then we can prefix each key name with a unique, but arbitrary, cipher id: cipher1.type=aristocrat cipher1.ciphertext=ab cde efghi ... cipher2.type=vigenere cipher2.period=6 > type > period > plaintext > ciphertext > key > keyword > author > title > language I'll add to this: for aristocrat types: k1key fixedkey k2key for morse types (pollux, morbit, fractionated morse): morsetext for baconian types: bacontext for progressive types: progressionEncoding progressionIncrement > might all fit in well as attributes. Some of these could be forbidden > from use in certain cipher types (eg. period/aristocrat). Others could > be mandatory (eg. period/vigenere). Author and title could, for > example, always be optional regardless of cipher type. Instead of being forbidden, couldn't they just be ignored by the function that reads the file? For example, if an aristocrat is loaded, then the period field would just get ignored. All of these > conditions could be enforced by the xml DTD (document type definition) xml dtds (and xml schema) introduce a little more complexity. If you don't use a validating xml parser then the DTD and schema aren't used and are pretty much useless. If you use a validating xml parser when you read the files, then the DTD or schema must be made available to the parser. This means they have to be made available in a well-known location. This is all entirely possible, but I feel that it's a little bit of overkill for ciphertool. The property file syntax can also be validated, but the validation would have to be part of the function that reads the file. I don't think that's such a bad thing. I'm not sure that there's too much we need to validate anyway. The only real required field that I see is the 'ciphertext' field. I envision using the files to store everything from unidentified ciphertext (type is 'unknown' or missing), to half-solved ciphers (type is known, period is '0' or missing), to completed ciphers (keyword is known). In some cases a field might be required but not known (the period for an unsolved vigenere for example). On the other hand, having stricter validation of > Or it could all be in plain text files which might make more sense if > not many people are using it. I think the property file format would be a little better suited for our purpose. I could probably still be convinced to make more fields required or make more fields required only for certain cipher types (period, for example). It's getting late, I'll sleep on it. --Wart |
|
From: Alex G. <za...@za...> - 2004-03-31 04:43:52
|
>Major tasks: > >1) Add an "encode pt key" subcommand to all cipher types to make it easy >to encrypt plaintext using a given key. This will make it possible to >write scripts that encode the same plaintext or different plaintext >samples in a variety of ways to analyze the statistical characteristics >of the encryption methods. > >2) Implement a new more portable file format for cipher data. Some >discussion has already begun on this. We need to continue the >discussion and come to a conclusion on the final format. > These sound like projects that could be helpful for lots of people working on classical cryptology. As I might have mentioned before, the cipher file format problem seems like an almost contrived example for what xml is for. I've never used xml though, and I don't know if this would be a sledgehammer vs. fly situation. type period plaintext ciphertext key keyword author title language might all fit in well as attributes. Some of these could be forbidden from use in certain cipher types (eg. period/aristocrat). Others could be mandatory (eg. period/vigenere). Author and title could, for example, always be optional regardless of cipher type. All of these conditions could be enforced by the xml DTD (document type definition). Or it could all be in plain text files which might make more sense if not many people are using it. -Alex |
|
From: Wart <wa...@ko...> - 2004-03-31 01:23:39
|
Now that 1.6.0 is out, it's time to think about what should go into the next release. I've got a few ideas. Feel free to make suggestions to add more or remove some: Major tasks: 1) Add an "encode pt key" subcommand to all cipher types to make it easy to encrypt plaintext using a given key. This will make it possible to write scripts that encode the same plaintext or different plaintext samples in a variety of ways to analyze the statistical characteristics of the encryption methods. 2) Implement a new more portable file format for cipher data. Some discussion has already begun on this. We need to continue the discussion and come to a conclusion on the final format. Minor tasks: 1) Support the use of wordtree scoring methods on the command line. This just needs a simple procedure for loading a new wordtree, as we already do with 2,3,n-grams. 2) Add an example of a Tcl-based scoring method, with documentation on how it is done. The example should be a combo digram + wordtree. 3) Add "rpmopt" targets to the Makefile for generating cpu-optimized packges. --Wart |
|
From: Wart <wa...@ko...> - 2004-03-31 00:44:04
|
Get it while it's hot! http://sourceforge.net/project/showfiles.php?group_id=86325&package_id=89637&release_id=227571 Major improvements in this release: * New plaintext scoring system. It's now much easier to plug in custom plaintext scoring methods and to change the default scoring method for the various command line tools. The old "stat digram", "stat trigram", and "stat tetragram" commands have been removed in favor of the new "score" command. See the "score" command, the "Scoredata" package, and the "genscores" program documentation for instructions on using the new scoring system. * Lots of updates to the documentation. Almost all Tcl scripting commands are documented now. * New "lethist" program for generating histograms and contact charts. Thanks to Alex Griffing for all of his suggestions and help with creating the Windows installer. --Mike |
