Send Beginners mailing list submissions to
        beginners@haskell.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
or, via email, send a message with subject or body 'help' to
        beginners-requ...@haskell.org

You can reach the person managing the list at
        beginners-ow...@haskell.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Beginners digest..."


Today's Topics:

   1.  [Call for Contributions] Haskell Communities and Activities
      Report, November 2017 edition (33rd edition) (Mihai Maruseac)
   2.  Automatically "deducing" of wrappers (Baa)
   3. Re:  Library for rendering text (Jona Ekenberg)


----------------------------------------------------------------------

Message: 1
Date: Thu, 5 Oct 2017 19:17:10 -0700
From: Mihai Maruseac <mihai.marus...@gmail.com>
To: haskell <haskell-c...@haskell.org>, Haskell Beginners
        <beginners@haskell.org>, Haskell <hask...@haskell.org>
Subject: [Haskell-beginners] [Call for Contributions] Haskell
        Communities and Activities Report, November 2017 edition (33rd
        edition)
Message-ID:
        <caomsumjcavvxmgrfrkh_zgscj8jjpxhq53jzpm2gvc9c-se...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Dear all,

We would like to collect contributions for the 33rd edition of the

============================================================
               Haskell Communities & Activities Report

http://www.haskell.org/haskellwiki/Haskell_Communities_and_Activities_Report

                Submission deadline: 5 November 2017

           (please send your contributions to hcar at haskell.org,
            in plain text or LaTeX format, both are equally accepted)
============================================================

This is the short story:

* If you are working on any project that is in some way related to
Haskell, please write a short entry and submit it. Even if the project
is very small or unfinished or you think it is not important enough
--- please reconsider and submit an entry anyway!

* If you are interested in an existing project related to Haskell that
has not previously been mentioned in the HCAR, please tell us, so that
we can contact the project leaders and ask them to submit an entry.

* If you are working on a project that is looking for contributors,
please write a short entry and submit it, mentioning that your are
looking for contributors.

* Feel free to pass on this call for contributions to others that
might be interested.

More detailed information:

The Haskell Communities & Activities Report is a bi-annual overview of
the state of Haskell as well as Haskell-related projects over the
last, and possibly the upcoming six months. If you have only recently
been exposed to Haskell, it might be a good idea to browse the
previous edition --- you will find interesting projects described as
well as several starting points and links that may provide answers to
many questions.

Contributions will be collected until the submission deadline. They
will then be compiled into a coherent report that is published online
as soon as it is ready. As always, this is a great opportunity to
update your webpages, make new releases, announce or even start new
projects, or to talk about developments you want every Haskeller to
know about!

Looking forward to your contributions,

Mihai Maruseac


FAQ:

Q: What format should I write in?

A: The usual format is a LaTeX source file, adhering to the template
that is available at:

     http://haskell.org/communities/11-2017/template.tex

There is also a LaTeX style file at

     http://haskell.org/communities/11-2017/hcar.sty

that you can use to preview your entry.

If you do not know LaTeX or don't want to use it or don't have time to
translate your entry into it, then please use plain text, it is better
to have an entry in plain-text which we will translate than not have
it at all.

If you modify an old entry that you have written for an earlier
edition of the report, you should soon receive your old entry as a
template (provided we have your valid email address). Please modify
that template, rather than using your own version of the old entry as
a template.

Q: Can I include Haskell code?

A: Yes. Please use lhs2tex syntax
(http://www.andres-loeh.de/lhs2tex/). The report is compiled in mode
polycode.fmt.

Q: Can I include images?

A: Yes, you are even encouraged to do so. Please use .jpg or .png
format, then. PNG is preferred for simplicity.

Q: Should I send files in .zip archives or similar?

A: No, plain file attachments are the way.

Q: How much should I write?

A: Authors are asked to limit entries to about one column of text. A
general introduction is helpful. Apart from that, you should focus on
recent or upcoming developments. Pointers to online content can be
given for more comprehensive or "historic" overviews of a project.
Images do not count towards the length limit, so you may want to use
this opportunity to pep up entries. There is no minimum length of an
entry! The report aims for being as complete as possible, so please
consider writing an entry, even if it is only a few lines long.

Q: Which topics are relevant?

A: All topics which are related to Haskell in some way are relevant.
We usually had reports from users of Haskell (private, academic, or
commercial), from authors or contributors to projects related to
Haskell, from people working on the Haskell language, libraries, on
language extensions or variants. We also like reports about
distributions of Haskell software, Haskell infrastructure, books and
tutorials on Haskell. Reports on past and upcoming events related to
Haskell are also relevant. Finally, there might be new topics we do
not even think about. As a rule of thumb: if in doubt, then it
probably is relevant and has a place in the HCAR. You can also simply
ask us.

Q: Is unfinished work relevant? Are ideas for projects relevant?

A: Yes! You can use the HCAR to talk about projects you are currently
working on. You can use it to look for other developers that might
help you. You can use HCAR to ask for more contributors to your
project, it is a good way to gain visibility and traction.

Q: If I do not update my entry, but want to keep it in the report,
what should I do?

A: Tell us that there are no changes. The old entry will typically be
reused in this case, but it might be dropped if it is older than a
year, to give more room and more attention to projects that change a
lot. Do not resend complete entries if you have not changed them.

Q: Will I get confirmation if I send an entry? How do I know whether
my email has even reached its destination, and not ended up in a spam
folder?

A: Prior to publication of the final report, we will send a draft to
all contributors, for possible corrections. So if you do not hear from
us within two weeks after the deadline, it is safer to send another
mail and check whether your first one was received.

-- 
Mihai Maruseac (MM)
"If you can't solve a problem, then there's an easier problem you can
solve: find it." -- George Polya


------------------------------

Message: 2
Date: Fri, 6 Oct 2017 10:51:49 +0300
From: Baa <aqua...@gmail.com>
To: Haskell Beginners <beginners@haskell.org>
Subject: [Haskell-beginners] Automatically "deducing" of wrappers
Message-ID: <20171006105149.328cb041@Pavel>
Content-Type: text/plain; charset=US-ASCII

Hello, List! This is a little bit theoretical question but not only...
Let's suppose I have a lot of functions like:

  llfunc :: A -> B -> C -> D -> C

and I have types C and HLC and "constructor" of HLC from C:

  makeHLC :: C -> Maybe HLC    -- or Either String HLC

and I want to create "automatically" (i.e. with minimal coding!)
functions like:

  hlfunc :: A -> B -> HLC -> D -> HLC   -- see llfunc

i.e. for each ll* (low-level) to create hl* (high-level). For example,
I can have even HLC -> C function. I may have a lot of llfunc's. Idea
is to replace a coding of hlfunc's with some automatically or
semi-automatically deduce/creating of them. For example, C may be
`FilePath`, HLC may be some kind of `Path a` (wrapper for paths). And I
have a lot of FilePath-based legacy functions.

I suppose it's possible to solve such problem in D language (I made
somthing similar several years ago). And possible it's easy in Nim
(Nimrod) because of them: a) types exist b) meta-programming features.
IMHO should be a way to do similar in Haskell, but it does not look
easy. IMHO I can code arguments + return types with Generic, and next
step may be type class with custom methods C -> HLC/HLC -> C and default
method like `perform` which will get Generic and automatically makes
instance of this type class or... And how will it look like?

Is it even possible in Haskell?


===
Best regards, Paul


------------------------------

Message: 3
Date: Fri, 6 Oct 2017 11:35:24 +0200
From: Jona Ekenberg <saik...@gmail.com>
To: The Haskell-Beginners Mailing List - Discussion of primarily
        beginner-level topics related to Haskell <beginners@haskell.org>
Subject: Re: [Haskell-beginners] Library for rendering text
Message-ID:
        <CALvEEUfpPvf9yKEUcOno8zUGjH=z2ie0uvnkagzjebmp8jg...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Thanks, I will try these out.

2017-10-04 15:32 GMT+02:00 Stefan Risberg <steffeno...@gmail.com>:

> You have Cairo and gi-cairo, I think that gi-cairo are autogenerated and
> from my experience a bit of a pain to set up.
>
> It also depends on if you use stack, cabal or nix of course for your
> project. But I think both are mostly equal
>
> On 4 Oct 2017 13:46, "Jona Ekenberg" <saik...@gmail.com> wrote:
>
>> Thanks for your reply Stefan.
>>
>> When I look for cairo bindings for Haskell I find several different ones.
>> Is there any one considered "the best" or most current? It does seem like a
>> suitable combination.
>>
>> Den 4 okt. 2017 12:49 em skrev "Stefan Risberg" <steffeno...@gmail.com>:
>>
>> Wouldn't pango with Cairo be good combination?
>>
>> On 4 Oct 2017 10:53 AM, "Jona Ekenberg" <saik...@gmail.com> wrote:
>>
>>> Dear mailing list,
>>>
>>> I want to create a text editor, preferably using open gl to render text.
>>> Are there any easy to use libraries for this? I like the gloss library, but
>>> the functions for rendering text seems quite basic. I could add upon this,
>>> but I figured I should ask here first; are there any existing libraries
>>> suitable for rendering text?
>>>
>>> Kind regards,
>>> Jona
>>>
>>> _______________________________________________
>>> Beginners mailing list
>>> Beginners@haskell.org
>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
>>>
>>>
>> _______________________________________________
>> Beginners mailing list
>> Beginners@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
>>
>>
>>
>> _______________________________________________
>> Beginners mailing list
>> Beginners@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
>>
>>
> _______________________________________________
> Beginners mailing list
> Beginners@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.haskell.org/pipermail/beginners/attachments/20171006/0de5dfbd/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
Beginners mailing list
Beginners@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners


------------------------------

End of Beginners Digest, Vol 112, Issue 8
*****************************************

Reply via email to