pbroadbery / aldor-idea-plugin Goto Github PK

An easy way would be to open an issue, say 'Screenshot', cut & paste a .png screenshot in the description filler, use the code in the issue filler to add it to the README.md file and close the issue. For GUI things it's always informative I think.

We've got makefiles, let's use them...

Add abbrevs index
Ideally sort first in Goto Class

rep/per

• show documentation; some free text, then the type
• Use 'Goto Related' [ctrl-alt-home] to jump to representation
  See RelatedItemLineMarkerProvider.

mod, case, exquo, etc should look similar to 'for', 'while', 'return', etc

Error:aldor compiler: IO Error on build: Cannot run program "make" (in directory "/home/pab/IdeaProjects/aldor-codebase/home/pab/IdeaProjects/aldor-codebase/tmp"): error=2, No such file or directory

Need to figure out what to do with these; how they interact with .abn files, etc.

Grammar is a bit of a mess - parse tree should come out nicely.

Constraints

• must accept same language as aldor and spad.
• tree amenable to analysis, Macro expansion and formatting.

Allow building with gradle

Want the following to work:

ctrl-alt-shift-n shows list of symbols declared in domains

• [Fn] determinant (in MatrixCategory X) ... matrix.spad

ctrl-q shows documentation

• determinant: % -> R (in SquareMatrix X)
  determinant(m) returns the determinant of the matrix m. Error: if the matrix is not square.
  -- hyperlink (if possible) to fricas.github.io

Up/Down should move between matches (this works out of the box)

Should be able to add external libraries to a module

External library should have link to source & can index that.. or export able file containing symbols.

First phase is an SDK for each of the following modes:

• Spad files
• Aldor standalone library
• Fricas development
• Aldor development

• Empty Spad/Aldor (Done)
• -Simple Aldor- (Done)
• Github Spad
• GitHub Aldor
• Aldor Library for Fricas
  (add note in v1 re no doc links).
• aldor lib with tests and runnable.. (nb no doc links again)

Macros should be highlighted.. doc could show expansion.. analysis should look through.

• The "Exports == Implementation" idiom needs a bit of thought.

constants (ok)
binary ops - check
implicit ops
lambda vars (ok)

Find bugs..

Identify and fix any issues

Mostly aldor.

First version just needs to echo the doc strings as is.

Currently we have 3 types of aldor level tests:

1. ALDORTEST sections in library files (fairly thorough, not many)
2. Test suite files (lots of these, but limited value - old bugs, not validating, very dependent on compile)
3. aldor/test directory.

• Won't be difficult, index is in place, might want to try to add some location decoration around

Should resolve to declaration, not I'd.

Need some text settings to avoid massive tab damage.

.. sort of works (via .abn file) in aldor, ought to work ok in spad

Need per theme scheme

additionalTextAttributes scheme="Default" file="colorSchemes/GLSLDefault.xml"
colorSettingsPage implementation="glslplugin.GLSLColorAndFontsPage"

A light version and a dark will be enough.

Was disabled.. needs to work.

The "Create Aldor File" is way too simplistic.

Extras:

• Should show the destination directory for the file
• Should populate with some kind of template
• Should amend Makefile.in (if present) so that new file is in build (checkbox-optional).

1. RelatedElement thing to go from defn to declaration and back (if ambiguous, show all)
2. Dig out related documentation, and link which jumps to defn.

Show type of identifiers on ctrl-hover.

Should use Travis to check commits

See Ctrl-Hover in java mode

Currently using the aldor codebase will give errors for the java classes in the lib directory.
Would be nice to create java subprojects for dealing with these.

.. handy feature sometimes

Need a big flag somewhere

A bunch of tests - mostly around parsing - don't work correctly at the moment.
Rather than marking them as @ Ignore, I prefer to have them run locally and fail.
Under travis, I'm happy if they don't run as that is more for spotting regressions.

Looks like

 I ==> with
      ...
 E ==> ....

Is parsed incorrectly - probably a missing EOL marker somewhere.

Should be runnable as "Run test..."..

Can of worms here...
Version 1 will do the doc strings with minimal preprocessing.

Ideally,

• links should work
• maths should be pre processed
• domains should be substituted if appropriate.

Needs a bit of thought, but would be good.