Now that the Apache Daffodil™ Extension for VSCode v1.3.1 has been
officially released, it's time to plan the features for v1.4.0. Here is
what the development team is considering:
Data Editor:
•Ability to represent data where MSB or LSB bit can be the first bit
displayed
•Provide a viewports f
+1 (binding)
v1.3.1 is solid and is a big improvement over v1.3.0. Mike B. gave RC1
a +1 and the difference between RC1 and RC2 is just fixing the handling of
null bytes in the Data Editor.
On Fri, Sep 8, 2023 at 2:45 PM Steve Lawrence wrote:
> +1 (binding)
>
> Checks I marked as MINOR and I'm
+1 from me. To help inform the discussion, here are some draft
release notes for the possible v1.3.1-RC1 release:
Data Editor
· Add support for large file editing and "infinite" scrolling
· Added support for editing in several Data Editor simultaneously
· Implement Incremental
ngle file in a fairly transparent manner.
> There's very little conceptual difference between a file of binary records,
> and a directory of files each containing 1 binary record, so a data editing
> environment should treat these as roughly equivalent. So searching for a
> par
In v1.3.1 we've added support for editing large files, but it has
exposed some other challenges related to search, replace, and data
profiling. I outline the problems and possible solutions to these problems
in a discussion thread here (
https://github.com/ctc-oss/daffodil-vscode/discussions/122).
+1 on the ".dar" SBT plugin.
Once a Daffodil Archive format is established, an SBT plugin enables
developers to easily create Daffodil Archives and further enforce
consistency.
On Mon, Jul 24, 2023 at 9:10 AM Davin Shearer wrote:
> +1 on the ".dar" idea.
>
> The
+1 on the ".dar" idea.
The Daffodil Archive ".dar" idea Steve introduced and the parallels with
the Apache NiFi ecosystem is exciting. The idea of bunding the serialized
parser, the runtime dependencies, and a README is a great non-intrusive
solution to both the tunables and classpath problems.
Greetings Daffodil developers and users!
As v1.3.0 of the Apache Daffodil Extension for VS Code has been officially
released, it’s time to plan the next release.
Since v1.3.0 was a huge feature release compared to v1.2.0, I propose that
we do a smaller (e.g., v1.3.1) release *before *we jump
+1
The Data Editor, while not perfect, is functional for small files (under
1MB), and it's much more functional than the experimental Data Editor in
1.2.0. DFDL Intellisense is more robust and complete over 1.2.0. The user
documentation for 1.3.0 (on the wiki) has also improved. The VSIX was ea
Excellent, I'm glad it's not a JRE version problem since we're on Java 8 to
maximize compatibility across our supported platforms. Also agree with
dropping the JRE bundling for 1.3.0 at least.
Environment isolation and configuration validation updates ought to be
straightforward PRs to review and
issues that bundling solves? Mike said that
> it requires Java 11, but it's not clear what Java 11 only features the
> debugger uses. I image there is an alternative to these features that
> works on all versions of Java (for a reasonable definition of all).
>
>
>
> On 2
lution of that bug is to me
>
> - Steve
>
>
> On 2023-06-05 12:21 PM, Davin Shearer wrote:
> > Hi Mike,
> >
> > The answer is useful. It allows the VS Code user to select the version
> of
> > Java they wish to use and it will attempt to locate a compatible JV
Hi Mike,
The answer is useful. It allows the VS Code user to select the version of
Java they wish to use and it will attempt to locate a compatible JVM
through various means. Sounds really useful for Java _development_ but not
so much for other extensions to leverage for their JVM dependencies u
Thanks for the detailed update and your patience Mike. This is
definitely not the user experience we're hoping for. Are these regressions
that have occurred since the v1.2.0 release?
I'm a big fan of compartmentalization and technologies like docker and
python's venv (virtual environment) among
}
>
> Now I get to the first stop on the schema root.
>
>
>
> On Fri, Apr 28, 2023 at 12:23 PM Mike Beckerle
> wrote:
>
> > Operating system is Ubuntu 20.04.
> >
> > I have changed that to 4712, and that also fails same way.
> >
> >
> > On Fri, Apr 28, 2
Hi Mike,
So it appears that the daffodil debugger server is not able to start and
listen on TCP port 4711 given the error message in your email. The
daffodil debugger server is different from the server that is used by the
data editor that comes up by default on port 9000 that you've configured
n
fferent from the releases page here:
> https://daffodil.apache.org/vscode/ . In fact one might have the releases
> page serve mulitple purposes: link to the release, and link to the doc for
> the release.
>
>
> On Mon, Apr 17, 2023 at 3:08 PM Davin Shearer wrote:
>
> >
Hello Developers,
Currently the Daffodil extension for VS Code documentation is on the GItHub
wiki (https://github.com/apache/daffodil-vscode/wiki). Daffodil itself is
documented on the https://daffodil.apache.org/ site. I'm thinking
extension documentation should also be in the same site, also
Hi Steve,
As a developer, I like to script things that I need to do repeatedly, to
the extent possible, and regularly use wget and curl. I'm on board with
whatever can be done to make it simple for developers to script fetching
these artifacts with minimal frustration.
+1 for me.
-Davin
On Thu
t; +1 because I keep on reading it as competition … “Apache Daffodil versus
> Code Extension” ;-)
> >
> > Chris
> >
> > From: Davin Shearer
> > Date: Wednesday, 30. November 2022 at 17:37
> > To: dev@daffodil.apache.org
> > Subject: Propose name change fro
I'm working through getting our wiki documentation (
https://github.com/apache/daffodil-vscode/wiki) refreshed to coincide with
our upcoming 1.2.0 release of the extension, and in the course of updating
the material, I came across this guide (https://code.visualstudio.com/brand)
on proper ways to n
I really like this idea of centralizing a test framework for DFDL schemas
for all the reasons you mentioned. It would also serve to help structure
DFDL repositories, reduce burden on schema authors, and institute best
practices.
On Wed, Nov 30, 2022 at 9:48 AM Mike Beckerle wrote:
> I never got
Greetings!
I vote -1 (binding) on this.
I downloaded the .vsix, checked the SHA 512, and verified the signature
matches with gpg imported KEYS file. Installation went smoothly and
according to the documentation. I opened up an DFDL schema, set the syntax
from XML to dfdl, then tried to edit it
23 matches
Mail list logo
