Re: [Chicken-users] [ANN] sdl2, sdl2-image, sdl2-ttf eggs ported to CHICKEN 5

[Mario Domenech Goulart]

Hi John,

On Wed, 13 Feb 2019 19:46:34 -0600 John Croisant  wrote:

> sdl2 v0.3.0, sdl2-image v0.2.0, and sdl2-ttf v0.2.0 have been released.
>
> The main changes are compatibility with CHICKEN 5 (as well as CHICKEN
> 4), a more user-friendly installation process, and support for linking
> to frameworks on macOS. In most cases, the installer should now
> automatically detect the SDL2 compiler flags necessary for your system.
> Please let me know if you have any installation problems so I can fix them.
>
> Thanks to Christian Kellermann, Kristian Lein-Mathisen, Laughing Man,
> and Jonas whose bug reports and suggestions made the eggs better. Thanks
> also to Matt Welland whose email inspired me to finish porting to CHICKEN 5.
>
> - John Croisant
>
> P.S. Please add these URLs to the CHICKEN 5 coop:
>
>    
> https://gitlab.com/chicken-sdl2/chicken-sdl2/raw/master/sdl2.chicken-5.release-info
>    
> https://gitlab.com/chicken-sdl2/chicken-sdl2-image/raw/master/sdl2-image.chicken-5.release-info
>    
> https://gitlab.com/chicken-sdl2/chicken-sdl2-ttf/raw/master/sdl2-ttf.chicken-5.release-info

That's great.  Thanks.  I've aded them to the coop.  Please keep an eye
on tests.call-cc.org (specially on the non-cached machine) to see if
installation and tests are going to succeed.

All the best.
Mario
-- 
http://parenteses.org/mario

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Chicken-users] [ANN] sdl2, sdl2-image, sdl2-ttf eggs ported to CHICKEN 5

[John Croisant]

sdl2 v0.3.0, sdl2-image v0.2.0, and sdl2-ttf v0.2.0 have been released.

The main changes are compatibility with CHICKEN 5 (as well as CHICKEN
4), a more user-friendly installation process, and support for linking
to frameworks on macOS. In most cases, the installer should now
automatically detect the SDL2 compiler flags necessary for your system.
Please let me know if you have any installation problems so I can fix them.

Thanks to Christian Kellermann, Kristian Lein-Mathisen, Laughing Man,
and Jonas whose bug reports and suggestions made the eggs better. Thanks
also to Matt Welland whose email inspired me to finish porting to CHICKEN 5.

- John Croisant

P.S. Please add these URLs to the CHICKEN 5 coop:

   
https://gitlab.com/chicken-sdl2/chicken-sdl2/raw/master/sdl2.chicken-5.release-info
   
https://gitlab.com/chicken-sdl2/chicken-sdl2-image/raw/master/sdl2-image.chicken-5.release-info
   
https://gitlab.com/chicken-sdl2/chicken-sdl2-ttf/raw/master/sdl2-ttf.chicken-5.release-info



___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Chicken/Tk

[lundi]

Afaik the port was done by Peter Lane, who still maintains the 
non-Chicken version of pstk. He doesn't seem to keen on providing 
Chicken support nowadays, though. Perhaps a port to Chicken 5 could 
actually be based on his r7rs version, though.


Your version is still available on Sourceforge:
https://sourceforge.net/projects/pstk

As far as I can tell there are only minor differences between this, the 
Chicken egg version, and Peter Lane's version. All of them just had 
small tweaks post 2008.


Best wishes,
-Heinz


On 2/13/19 9:53 PM, Phil Bewig wrote:

I was once the maintainer of pstk. But I can tell you that I haven't
touched it in years, and it fell off of SourceForge in one of their
restructurings, so I have no intention of looking at it again.

Several years ago someone, I don't recall who, forked pstk for Chicken. I
was not involved in the fork, and I don't know what changes were made. I'm
pretty sure the Chicken version of pstk hasn't been maintained for a long
time, either.

I am not a regular user of Chicken and am not interested in being the
maintainer of Chicken pstk.



___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Chicken/Tk

[Phil Bewig]

I was once the maintainer of pstk. But I can tell you that I haven't
touched it in years, and it fell off of SourceForge in one of their
restructurings, so I have no intention of looking at it again.

Several years ago someone, I don't recall who, forked pstk for Chicken. I
was not involved in the fork, and I don't know what changes were made. I'm
pretty sure the Chicken version of pstk hasn't been maintained for a long
time, either.

I am not a regular user of Chicken and am not interested in being the
maintainer of Chicken pstk.

On Wed, Feb 13, 2019 at 1:51 PM lundi  wrote:

> Thank you Vasilij for the quick and detailed reply. That's pretty much
> all I needed to know.
>
> I was definately planning on using ttk widgets so pstk it is.
>
> As I only started coding in Scheme a few months ago I don't feel up to
> the task of maintaining the pstk egg at this point either. The code
> doesn't look too complicated though so I'll probably volunteer to do it
> once I have a bit more experience.
>
> Best wishes,
> -Heinz
>
> ___
> Chicken-users mailing list
> Chicken-users@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/chicken-users
>
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Chicken/Tk

[lundi]

Thank you Vasilij for the quick and detailed reply. That's pretty much 
all I needed to know.


I was definately planning on using ttk widgets so pstk it is.

As I only started coding in Scheme a few months ago I don't feel up to 
the task of maintaining the pstk egg at this point either. The code 
doesn't look too complicated though so I'll probably volunteer to do it 
once I have a bit more experience.


Best wishes,
-Heinz

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Chicken-users] Call for Submissions: ICFP Student Research Competition

[Sam Tobin-Hochstadt]

 ICFP 2019 Student Research Competition
Call for Submissions

ICFP invites students to participate in the Student Research
Competition in order to present their research and get feedback from
prominent members of the programming language research
community. Please submit your extended abstracts through the
submission website.

### Important dates

Submissions due:14 Jun 2019 (Friday) 
https://icfp19src.hotcrp.com
Notification:   28 Jun 2019 (Friday)
Conference: 18 August (Sunday) - 23 August (Friday)


Each submission (referred to as "abstract" below) should include the
student author’s name and e-mail address; institutional affiliation;
research advisor’s name; ACM student member number; category
(undergraduate or graduate); research title; and an extended abstract
addressing the following:

* Problem and Motivation: Clearly state the problem being addressed and
  explain the reasons for seeking a solution to this problem.

* Background and Related Work: Describe the specialized (but
  pertinent) background necessary to appreciate the work in the
  context of ICFP areas of interest. Include references to the
  literature where appropriate, and briefly explain where your work
  departs from that done by others.

* Approach and Uniqueness: Describe your approach in addressing the
  problem and clearly state how your approach is novel.

* Results and Contributions: Clearly show how the results of your work
  contribute to programming language design and implementation in
  particular and to computer science in general; explain the
  significance of those results.

* Submissions must be original research that is not already published
  at ICFP or another conference or journal. One of the goals of the
  SRC is to give students feedback on ongoing, unpublished
  work. Furthermore, the abstract must be authored solely by the
  student. If the work is collaborative with others and*or part of a
  larger group project, the abstract should make clear what the
  student’s role was and should focus on that portion of the work.

* Formatting: Submissions must be in PDF format, printable in black
  and white on US Letter sized paper, and interpretable by common PDF
  tools. All submissions must adhere to the "ACM Small" template that
  is available (in both LaTeX and Word formats) from
  https://www.acm.org/publications/authors/submissions. For authors
  using LaTeX, a lighter-weight package, including only the essential
  files, is available from
  http://sigplan.org/Resources/Author/#acmart-format. The submission
  must not exceed 3 pages in PDF format. Reference lists do not count
  towards the 3-page limit.

Further information is available at the ICFP SRC website:
https://icfp19.sigplan.org/track/icfp-2019-Student-Research-Competition

ICFP Student Research Competition Chair:
  William J. Bowman (University of British Columbia)
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Chicken-users] Third Call for Papers: PACMPL issue ICFP 2019

[Sam Tobin-Hochstadt]

PACMPL Volume 3, Issue ICFP 2019
Call for Papers

accepted papers to be invited for presentation at
 The 24th ACM SIGPLAN International Conference on Functional Programming
 Berlin, Germany
   http://icfp19.sigplan.org/

### Important dates

Submissions due:1 March 2019 (Friday) Anywhere on Earth
https://icfp19.hotcrp.com
Author response:16 April (Tuesday) - 18 Apri (Friday) 14:00 UTC
Notification:   3 May (Friday)
Final copy due: 22 June (Saturday)
Conference: 18 August (Sunday) - 23 August (Friday)

### About PACMPL

Proceedings of the ACM on Programming Languages (PACMPL
) is a Gold Open Access journal publishing
research on all aspects of programming languages, from design to
implementation and from mathematical formalisms to empirical
studies. Each issue of the journal is devoted to a particular subject
area within programming languages and will be announced through
publicized Calls for Papers, like this one.

### Scope

[PACMPL](https://pacmpl.acm.org/) issue ICFP 2019 seeks original
papers on the art and science of functional programming. Submissions
are invited on all topics from principles to practice, from
foundations to features, and from abstraction to application. The
scope includes all languages that encourage functional programming,
including both purely applicative and imperative languages, as well as
languages with objects, concurrency, or parallelism. Topics of
interest include (but are not limited to):

  * *Language Design*: concurrency, parallelism, and distribution;
 modules; components and composition; metaprogramming; type
 systems; interoperability; domain-specific languages; and
 relations to imperative, object-oriented, or logic programming.

  * *Implementation*: abstract machines; virtual machines;
 interpretation; compilation; compile-time and run-time
 optimization; garbage collection and memory management;
 multi-threading; exploiting parallel hardware; interfaces to
 foreign functions, services, components, or low-level machine
 resources.

  * *Software-Development Techniques*: algorithms and data structures;
 design patterns; specification; verification; validation; proof
 assistants; debugging; testing; tracing; profiling.

  * *Foundations*: formal semantics; lambda calculus; rewriting; type
 theory; monads; continuations; control; state; effects; program
 verification; dependent types.

  * *Analysis and Transformation*: control-flow; data-flow; abstract
 interpretation; partial evaluation; program calculation.

  * *Applications*: symbolic computing; formal-methods tools;
 artificial intelligence; systems programming; distributed-systems
 and web programming; hardware design; databases; XML processing;
 scientific and numerical computing; graphical user interfaces;
 multimedia and 3D graphics programming; scripting; system
 administration; security.

  * *Education*: teaching introductory programming; parallel
 programming; mathematical proof; algebra.

Submissions will be evaluated according to their relevance,
correctness, significance, originality, and clarity. Each submission
should explain its contributions in both general and technical terms,
clearly identifying what has been accomplished, explaining why it is
significant, and comparing it with previous work. The technical
content should be accessible to a broad audience.

PACMPL issue ICFP 2019 also welcomes submissions in two separate
categories  Functional Pearls and Experience Reports 
that must be marked as such at the time of submission and that need
not report original research results.  Detailed guidelines on both
categories are given at the end of this call.

Please contact the principal editor if you have questions or are
concerned about the appropriateness of a topic.

### Preparation of submissions

**Deadline**: The deadline for submissions is **Friday, March 1, 2019**,
Anywhere on Earth ().
This deadline will be strictly enforced.

**Formatting**: Submissions must be in PDF format, printable in black
and white on US Letter sized paper, and interpretable by common PDF
tools. All submissions must adhere to the "ACM Small" template that is
available (in both LaTeX and Word formats) from
.  For authors
using LaTeX, a lighter-weight package, including only the essential
files, is available from
.

There is a limit of **25 pages for a full paper or Functional Pearl**
and **12 pages for an Experience Report**; in either case, the
bibliography will not be counted against these limits. Submissions
that exceed the page limits or, for other reasons, do not meet the
requirements for formatting, will be summarily 

Re: [Chicken-users] Chicken/Tk

[Vasilij Schneidermann]

Hello Heinz,

I've looked into the state of GUI eggs for some time and even
contributed a few of my own, way before the release of C5.

> I'm planning on using Tk in a project, and was wondering what's the current
> status of Tk support in Chicken. So Chicken 4 has two eggs, pstk and tk. Of
> these, pstk is listed under "Unsupported or redundant". What's the reason
> for that? I thought pstk was essentially an enhanced version of Wolf-Dieter
> Busch's Chicken/Tk.

You're correct, pstk is an enhanced version of tk with extra commands
(most notably for the ttk extension which allows limited theming) and a
more agreeable license.  Back then I've asked Felix Winkelmann the same
question about its status, the result of that discussion was that he
didn't know either, but agreed to swap both (so that tk would be
obsoleted and pstk in the GUI section) provided that a new maintainer
steps up.  I didn't consider myself good enough for the task back then,
so nothing happened.

> Also, is anybody working on porting either of these eggs to Chicken 5? I'll
> probably stick to Chicken 4 for my project for the time being, since a
> number of distros don't ship C5 yet. I'd volunteer to port the egg myself at
> some point in the future though, once I do transition to 5.

I've worked on porting a number of eggs to ensure everything popular can
be used with C5, but stopped in favor of other projects I'm working on.
Porting the pstk egg shouldn't be hard though, the most challenging bit
would be finding a maintainer.

> On a side note, a while ago I was in contact with Mr. Busch and asked if he
> would relicense the tk egg under BSD terms, to which he agreed. As far as I
> can tell he hasn't actually taken any steps to do so, however. In any case,
> afaik the "Bremer License" is not applicable here, because it specifically
> and exclusively covers the OSCI library, of which Chicken/Tk is not a
> component. So in it's current state, Chicken/Tk is not free software,
> strictly speaking.

This is lamentable, but not the end of the world.  If a maintainer steps
up for pstk, it would supersede the tk egg and no licensing issues will
arise from it.

Vasilij


signature.asc
Description: PGP signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Chicken-users] Chicken/Tk

[lundi]

Hi,

I'm planning on using Tk in a project, and was wondering what's the 
current status of Tk support in Chicken. So Chicken 4 has two eggs, pstk 
and tk. Of these, pstk is listed under "Unsupported or redundant". 
What's the reason for that? I thought pstk was essentially an enhanced 
version of Wolf-Dieter Busch's Chicken/Tk.


Also, is anybody working on porting either of these eggs to Chicken 5? 
I'll probably stick to Chicken 4 for my project for the time being, 
since a number of distros don't ship C5 yet. I'd volunteer to port the 
egg myself at some point in the future though, once I do transition to 5.


On a side note, a while ago I was in contact with Mr. Busch and asked if 
he would relicense the tk egg under BSD terms, to which he agreed. As 
far as I can tell he hasn't actually taken any steps to do so, however. 
In any case, afaik the "Bremer License" is not applicable here, because 
it specifically and exclusively covers the OSCI library, of which 
Chicken/Tk is not a component. So in it's current state, Chicken/Tk is 
not free software, strictly speaking.


Best wishes,
-Heinz

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users