Small improvments (change else if to else)
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Oct 30 2018
Added cyclic moving for tabs
Oct 27 2018
Some code improvments
Oct 23 2018
Remove entry cursor reseting (on master already)
Oct 21 2018
- Allow double click in readonly mode
- Fix bug with existing assistant, when we load read-only worksheet from empty worksheet with existing backend
- Fix bug with existing entry cursor, when we load read-only worksheet from empty worksheet with existing backend
Another improvments
Fix bug with load
Oct 20 2018
Add availability check for default session
Some improvements
Oct 19 2018
Improve subprompt handling
Oct 16 2018
Oct 15 2018
Oct 14 2018
Rewrite the patch according new @asemke changes
Oct 13 2018
Replaced setResult by addResult in PythonExpression::imageChanged().
Oct 11 2018
Oct 5 2018
This resulting code looks ugly, so @asemke, @filipesaraiva I am open to suggestions.
Oct 4 2018
Comment's changes and some small text fixes
Oct 3 2018
In 610f8c8ec70b4b52a3f4487c3348b87b66a0b85f I have added autocompletion by native Python autocompletion.
It's work for variables, functions, modules, even for class methods and fields.
Oct 2 2018
Add support for latex typesetting
Sep 29 2018
Sep 15 2018
well done!
Sep 13 2018
Don't start prompt animation, if user disable animations at all.
Sep 7 2018
In T5382#159464, @filipesaraiva wrote:For now it is not possible, so that is ok. Maybe we can to open some tasks in backlog column while there are not syntax definitions for it in KSyntaxHighlight.
Or we could create syntax datafile and send pull request. A think, we should mention this option in the tasks. I have spended some time on testing highlighting in this backends - they in good condition, so I think rewriting them on KSyntaxHighlighting is not very priority task (and not very easy: qalqulate use own block highlighting function and kalgebra use highlighter from analitza gui). So, wishlist priority, maybe.
In T5382#159457, @sirgienko wrote:Well, good job, guys!
In T9564#159462, @filipesaraiva wrote:In T9564#159448, @sirgienko wrote:Sage support also another languages, not Python only, as I know. Should we add them highlighting too, or it's impossible?
Hi @sirgienko, I think it is possible because Sage uses R and Maxima (among others) as well, but I don't know if it uses the entire set of keywords/functions/etc of these languages or just a small subset.
Do you have any knowledge about this topic? In fact I am not a Sage user.
In T9564#159448, @sirgienko wrote:Sage support also another languages, not Python only, as I know. Should we add them highlighting too, or it's impossible?
Well, good job, guys!
But, that we will do with Qalculate and Kalgebra backends? They haven't syntax file, as I see (but we don's support this backends very well, so maybe we could leave it as it is.
And another question: Are we will use KSyntaxHighlighting for the highlighting?
For example, we could use AbstractHighlighter::highlightLine from KSyntaxHighlighting inside DefaultHighlighter, especially in our DefaultHighlighter::highlightBlock function. In this case, hgihtlighting code supported from KSyntaxHighlighting team and we also fix one of our highlighting problem: we can't highlight multiline elements, like multiline strings, comments, etc. (actually, some backends highlighter do multiline hightlighting (MaximaHighlighter::highlightBlock, ScilabHighlighter::highlightBlock, some others backends), but DefaultHighlighter can't do it)
Hi, @filipesaraiva. I have checked your commit(R55:3798dfc44d824b8437bbfd91d047978a833f24ec) and found, that SageHighlighter uses Python keywords.
Sage support also another languages, not Python only, as I know. Should we add them highlighting too, or it's impossible?
Sep 6 2018
Sep 4 2018
@filipesaraiva, GSoC'2017 ended, but this task is still important, so maybe better remove info about GSoC and use the describtion from GSoC task (The main aim of this project...)?
Hi @filipesaraiva
As I see, python backends in this moment works on Python C API (pythonserver.cpp).
So, as I see, this task is duplicate of T6114, isn't it?
Finish this task by c44304870127ffea8f6191b44699bccbfce5a90c
But maybe more simple way is using native autocompletion tools from Python itself. Like we do it in Octave (octavecompletionobject.cpp::35).
As variant, we could use variable model: it alreay stored variable names, unique for each session, and we have api to acess to it from Cantor::Session.
Removed after R55:22fd4479ab02.
Thanks @sirgienko. When I ported to KSyntaxHighlighting the tab completion stopped to work for variables.
Hi, @fililesaraiva.
PythonKeywords::instance()->addVariable(variable); }
don't good idea, because in this case we store all variables from all Python session in singliton PythonKeywords.
I think, keywords classes should store only session independent data, in our case, from KSyntaxHigligting
Sep 3 2018
R syntax file in (r.xml) in KSyntaxHighlighter not very big, but now we use data from it.
Sep 1 2018
Aug 31 2018
Change member name from isInternal to internal
Highlighting for user-defined variables don't work now, but the realization of this highlighting was wrong (highlighting shared between session). I investigate good way to implement this, and I don't think, that this is related with this task, so I mark this task as "Resolved".