corinthia-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jan i <>
Subject Re: Developer Discussions
Date Sun, 28 Dec 2014 20:11:48 GMT
On Sunday, December 28, 2014, Dennis E. Hamilton <>

> Can we please have these discussions about development direction and what
> goes where on this list?
> I am in the uncomfortable position of having to second-guess you two
> and/or retreading matters that you are privately in accord with.

sorry I completely agree with you. And just to be sure, peter and I have no
discussions offlist anymore, but we have a history which I referred to. I
should have been clear in my statement.

No, however small decisions shall be made offlist !  we are ONE community.

that being said, if I have a development problem I sometimes call peter on
skype, simply because its faster....but you can see that eg. code writing
standards go through the list.

Sorry I referenced the history without writing it clearly, but very
important if you disagree, then we discuss in here until we have consensus,
history do NOT overwrite this list.

jan i

>  - Dennis
> -- replying below to --
> From: jan i [ <javascript:;>]
> Sent: Sunday, December 28, 2014 10:13
> To: <javascript:;>
> Subject: Re: MiniZIp/tidy-html Dependency (was RE: External libraries on
> windows)
> On 28 December 2014 at 19:03, Dennis E. Hamilton <
> <javascript:;>>
> wrote:
> [ ... ]
> I am moving in the direction of not needing sources for external libraries.
> Upgrades are so much easier to handle if all we need to do is download a
> new lib.
> We have the same problem with maintenance in case of minizip that is based
> on zlib. So for minizip, we have our own implementation (DFZipfile.c) a
> modified version of minizip and an external library....that seems overkill.
> Both peter and I have discussed the use of external libraries, and we both
> want to isolate them in platform, so that we can replace them if needed,
> without having to change a world of sources.
> Peter thinks we should write our own HTML parser to replace w3c, I tend to
> agree with him, even though I think we need a discussion first how we
> internally represent documents.
> [ ... ]

Sent from My iPad, sorry for any misspellings.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message