[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orekit Developers] Roadmap for releasing Orekit 9.0?
- To: orekit-developers@orekit.org
- Subject: Re: [Orekit Developers] Roadmap for releasing Orekit 9.0?
- From: Hank Grabowski <hank@applieddefense.com>
- Date: Mon, 12 Dec 2016 15:51:29 -0500
- Authentication-results: kepler.orekit.org; dkim=pass reason="2048-bit key; insecure key" header.d=applieddefense-com.20150623.gappssmtp.com header.i=@applieddefense-com.20150623.gappssmtp.com header.b=Jb05VE6U; dkim-adsp=none (insecure policy); dkim-atps=neutral
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=applieddefense-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=zggeOyk1OltkeePAO6Pt5mFBo2RL8vVl9isvuuJqeKY=; b=Jb05VE6U2mUeNAeBBhWcxel0/jQc1zpkoRRcmGf3RUzwnS3uhAmiAoKrpfjw0BO5e8 goFjUYTG17DX8CiNXkDGeFpELxNq0mGr4GimPyVVHT9cNw89JmL+9sQDqBzuTjPQOQz7 mTsvKc/4+hORjoZKvvQhTQPnr52Kxj5lAL5af+6HxVijfiAKh2lHaBf0YoiXPlyy/nns ZCUyR3ztk/u8V+P2d2MCbVgnJZP+31Gooi/rrulJJ0uZuEsL1qwy9OqGPX1dbaB7TX9u WBy424sZ5UwUzPBsB8WlXN/gf0EHg7WwA7VQnSoHZuXpQDok5d830AOxpVTbryPRN+Pu j1oQ==
- In-reply-to: <CAP2my4YMBRe=169e_5M3HTeJ=uop60TC9L4AONUGAMLLnfY5CQ@mail.gmail.com>
- References: <20161125160342.Horde.WSIzKnqS8b5VYMeXY0MFKw1@messagerie.c-s.fr> <8e78c19c-e7d5-9f55-054f-66a551f5872b@nrl.navy.mil> <CAP2my4Y2y0CxDcm06GXmp0+K=RPLuJRYTuQ6wmcPOEdGunds5Q@mail.gmail.com> <CAP2my4Z5bsYecwEZjhdvf8Rzo41=1GjYqvMcPX52vgdUuMXRQg@mail.gmail.com> <20161209102028.Horde.rMUiOj9m1mQdbtVitypxTQ2@messagerie.c-s.fr> <CAP2my4YMBRe=169e_5M3HTeJ=uop60TC9L4AONUGAMLLnfY5CQ@mail.gmail.com>
I've reviewed the implemented interfaces. I would say a short term plausible objective for me by the end of year is to implement the OEM parser. I had originally thought there would be a writer as well as a parser interface. Are people interested in that? If so I'll emulate the parser interface for a writer and implement an OEM writer as well.