ExtJS Component for ACE

333 views
Skip to first unread message

Christoph Dorn

unread,
Mar 14, 2011, 9:01:07 PM3/14/11
to ace-in...@googlegroups.com
Hi All,

I am pleased to announce a cleaned-up version of my ExtJS component that
wraps ACE for embedding in ExtJS applications.

https://github.com/cadorn/ace-extjs

I will be maintaining this component as I am using it as part of my
tools [1].

The TODO list is as follows:

* Toolbar for editor component
* Footer for editor component (line wrapping, caret position, read
only, charset, ...)
* Persist editor styling to survive reload
* Document API
* Configurable/automatic worker path (cadorn)
* ExtJS 4 support/demo (cadorn)
* Bundeling for production loading (cadorn)

Once I complete the items assigned to me (target is this week) the
component will be usable in production applications via an optimized
release build containing static JS files only loadable via SCRIPT tags.

I am looking for contributors to complete the other items.

The project is facilitated by my PINF JavaScript Loader [2] which
includes a development server, downloads various projects and bootstraps
them together to provide a consistent dev environment to work on the
component.

Looking forward to feedback.

Christoph

[1] - http://www.ChristophDorn.com/Tools/
[2] - https://github.com/pinf/loader-js

Christoph Dorn

unread,
Mar 16, 2011, 7:53:36 PM3/16/11
to ace-in...@googlegroups.com
I just pushed an update to the PINF JS Loader and ace-ext project to
support load contexts. See here [1].

This allows the server to combine multiple client ASYNC load cycles into
one and provides the info needed to exclude already loaded modules for
subsequent ASYNC load requests when themes are loaded for example.

This functionality has already sped up the loading time during
development and will be further optimized in future.

The last aspect outstanding to make the ace-ext component usable in
projects is the building of a release containing static files only. I
expect this to be done by early next week.

HELP: There is one issue with the worker code that needs fixing. See
"Status" -> "TODO" here [2].

The worker code loads but I don't think communicates properly with the
editor as the alert icon for the JavaScript demo does not show up in the
gutter.

The PINF loader does not expect any special treatment but enforces
proper ASYNC load boundaries that the code must work around. Fixing this
should make the ACE editor more portable and reliable in general and the
fix should work with RequireJS as well.

I am hoping that someone can take a look at this. If you need more info
you can post to this thread or contact me on skype: christophdorn

Christoph

[1] -
https://github.com/cadorn/ace-extjs/blob/c942b48c1198208582052c6e070a15f271616a30/programs/ace/program.json#L3-19
[2] -
https://github.com/pinf/loader-js/tree/74a3cf47b81f2c68175ce87fd36912639959ba27/demos/ACE

Fabian Jakobs

unread,
Mar 21, 2011, 7:22:22 AM3/21/11
to ace-in...@googlegroups.com
Hi Christoph,

this looks really cool. I'm going to add a link to the homepage.

Best,
Fabian

> --
> You received this message because you are subscribed to the Google Groups
> "Ace Internals Dev" group.
> To post to this group, send email to ace-in...@googlegroups.com.
> To unsubscribe from this group, send email to
> ace-internal...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/ace-internals?hl=en.
>
>

Christoph Dorn

unread,
Mar 21, 2011, 9:17:50 PM3/21/11
to ace-in...@googlegroups.com

I just pushed an update to the PINF JS Loader and ace-ext project to add
support for static builds. See "Production" heading here:

https://github.com/cadorn/ace-extjs

The build is done via a script

https://github.com/cadorn/ace-extjs/blob/master/lib/build.js

which creates a mock program server and spiders all ASYNC load URIs
based on the defined contexts.

You can inspect the static files here:

https://github.com/cadorn/ace-extjs/tree/master/build/extjs3-ace

This completes my initial featureset for the PINF JS loader and I will
now shift focus to refining what is there and fixing bugs as more
use-cases are tested.

HELP: The worker init code still needs fixing as outlined in my previous
post.

Looking forward to feedback.

Christoph

--
http://www.ChristophDorn.com/Tools/

Reply all
Reply to author
Forward
0 new messages