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?
- Queries
- All Stories
- Search
- Advanced Search
Feed Advanced Search
Advanced Search
Advanced Search
Sep 7 2018
Sep 7 2018
filipesaraiva moved T9565: Port Julia backend to KSyntaxHighlighting from To-Do to Done on the Cantor board.
Thanks @sirgienko. It is an important feature to be added to Cantor.
filipesaraiva committed R55:3798dfc44d82: Port the syntax highlighting for Sage backend to KSyntaxHighlighting… (authored by filipesaraiva).
Port the syntax highlighting for Sage backend to KSyntaxHighlighting…
filipesaraiva closed T9564: Port Sage backend to KSyntaxHighlighting, a subtask of T5382: Port worksheet syntax highlighting to KSyntaxHighlighting, as Resolved.
filipesaraiva moved T9564: Port Sage backend to KSyntaxHighlighting from Work in Progress to Done on the Cantor board.
filipesaraiva moved T9564: Port Sage backend to KSyntaxHighlighting from To-Do to Work in Progress on the Cantor board.
filipesaraiva moved T9563: Port Lua backend to KSyntaxHighlighting from To-Do to Done on the Cantor board.
Sep 4 2018
Sep 4 2018
Removed after R55:22fd4479ab02.
filipesaraiva committed R55:22fd4479ab02: Remove 'PythonKeywords::instance()->addVariable' because it put the variable to… (authored by filipesaraiva).
Remove 'PythonKeywords::instance()->addVariable' because it put the variable to…
Thanks @sirgienko. When I ported to KSyntaxHighlighting the tab completion stopped to work for variables.
filipesaraiva committed R55:96f5ded806fb: Port Python 2 and Python 3 syntax highlighting to KSyntaxHighlighting (authored by filipesaraiva).
Port Python 2 and Python 3 syntax highlighting to KSyntaxHighlighting
filipesaraiva closed T9511: Port Python 2 backend to KSyntaxHighlighting, a subtask of T5382: Port worksheet syntax highlighting to KSyntaxHighlighting, as Resolved.
filipesaraiva closed T9512: Port Python 3 backend to KSyntaxHighlighting, a subtask of T5382: Port worksheet syntax highlighting to KSyntaxHighlighting, as Resolved.
filipesaraiva moved T9512: Port Python 3 backend to KSyntaxHighlighting from Work in Progress to Done on the Cantor board.
filipesaraiva moved T9511: Port Python 2 backend to KSyntaxHighlighting from Work in Progress to Done on the Cantor board.
filipesaraiva moved T9566: Port R backend to KSyntaxHighlighting from To-Do to Done on the Cantor board.
Sep 1 2018
Sep 1 2018
Aug 31 2018
Aug 31 2018
filipesaraiva moved T9563: Port Lua backend to KSyntaxHighlighting from Backlog to To-Do on the Cantor board.
filipesaraiva moved T9564: Port Sage backend to KSyntaxHighlighting from Backlog to To-Do on the Cantor board.
filipesaraiva moved T9565: Port Julia backend to KSyntaxHighlighting from Backlog to To-Do on the Cantor board.
filipesaraiva moved T9566: Port R backend to KSyntaxHighlighting from Backlog to To-Do on the Cantor board.
filipesaraiva moved T9513: Port Scilab backend to KSyntaxHighlighting from To-Do to Done on the Cantor board.
I looked if cmake 3 was available in some stable Linux distribution and it is, so there is no problem for building Cantor for them.
Aug 30 2018
Aug 30 2018
filipesaraiva added a comment to T6895: Making KDE software the #1 choice for research and academia.
In T6895#157200, @helderc wrote:@filipesaraiva Are you still here in USP/Sao Carlos? I'm PhD student here...
Aug 29 2018
Aug 29 2018
In D14738#316508, @sirgienko wrote:Hi, @kqwyf, as I see, your GitHub account name is kqwyf, right?
As I see, Github don't connect your commit with your github account, so author this patch on Github is 1160300905.
Should we try to fix this injustice :) and connect your github account with commit author via github support?
Aug 26 2018
Aug 26 2018
filipesaraiva committed R55:0dc2e3a36b3d: Change the evaluate worksheet icon at worksheet entry from view-refresh to… (authored by filipesaraiva).
Change the evaluate worksheet icon at worksheet entry from view-refresh to…
filipesaraiva added a comment to D15012: Change the evaluate worksheet icon at worksheet entry from view-refresh to system-run.
In D15012#315802, @asemke wrote:Should we use system-run for "evaluate worksheet", build-run for "insert command entry" and media-playback-start for "evaluate entry"?
filipesaraiva updated the diff for D15012: Change the evaluate worksheet icon at worksheet entry from view-refresh to system-run.
Change the "view-refresh" icon in command entry to "media-playback-start"
Nice, it fix the problem while we don't delivery T9513.
filipesaraiva added a comment to D15012: Change the evaluate worksheet icon at worksheet entry from view-refresh to system-run.
In D15012#315092, @asemke wrote:@filipesaraiva in 6b722430ec6120acef7b99c54a0ed5c607c56bae I set the icon for the "Insert Command Entry" item in the context menu to "run-build". Should we use the same icon, either system-run or run-build, in the context menu to insert an entry and in the action bar to execute it?
filipesaraiva moved T9511: Port Python 2 backend to KSyntaxHighlighting from Backlog to To-Do on the Cantor board.
filipesaraiva moved T9512: Port Python 3 backend to KSyntaxHighlighting from Backlog to To-Do on the Cantor board.
filipesaraiva moved T9514: Port Octave backend to KSyntaxHighlighting from Backlog to To-Do on the Cantor board.
filipesaraiva moved T9513: Port Scilab backend to KSyntaxHighlighting from Backlog to To-Do on the Cantor board.
The commit R55:9bb6049e4670b3fa2dd0fdedf9802851a2cf01db ported Maxima backend to KSyntaxHighlighting.
filipesaraiva moved T5382: Port worksheet syntax highlighting to KSyntaxHighlighting from Backlog to Work in Progress on the Cantor board.
A bit late but: thanks @asemke. :)
Aug 24 2018
Aug 24 2018
filipesaraiva committed R55:b6243d6e60d5: Merge branch 'arcpatch-D14738' (authored by filipesaraiva).
Merge branch 'arcpatch-D14738'
Add the markdown entry
filipesaraiva closed T9108: Add support for markdown as Resolved by committing R55:ea6b09e9e5c9: Add the markdown entry.
filipesaraiva moved T9108: Add support for markdown from Work in Progress to Done on the Cantor board.
Aug 23 2018
Aug 23 2018
filipesaraiva added a comment to T5242: Display user information so that others can land/amend a patch.
I had this same problem recently - land a commit from a different user but the authorsihp was changed. I reverted the commit. :(
Thank you again @kqwyf, the markdown support is a very wished feature and you did a good job!
In D12504#314000, @sirgienko wrote:Hi, @filipesaraiva, I completely forgot about this patch.
@sirgienko thanks, it fix the current problem with Scilab backend (I could to reproduce it). I think while we don't implement T5382, we need to fix the problem with this backend.
Aug 22 2018
Aug 22 2018
+1
filipesaraiva committed R916:48f2423a7fb9: Add news about Cantor 18.08 release (authored by filipesaraiva).
Add news about Cantor 18.08 release
filipesaraiva committed R916:4ab2f82cf699: Add news about Cantor 18.04 release (authored by filipesaraiva).
Add news about Cantor 18.04 release
filipesaraiva committed R916:d38148cf057f: Increment Cantor version to 18.04 (authored by filipesaraiva).
Increment Cantor version to 18.04
Aug 20 2018
Aug 20 2018
Well, I really don't like the behaviour of Cantor processing LaTeX and text together in a same text entry. For me it is a very confuse behaviour, mainly for now when we have Markdown options for rendering too.
Nice, thanks again!
Thanks @arojas, do you know if this change break the compatibility with previous versions of Sage?
Aug 16 2018
Aug 16 2018
In D14738#310008, @kqwyf wrote:So the behavior should be:
- If the user focus on a markdown entry, the rendered content will remains there.
- If the user double click on it, the plain markdown code will replace the rendered content in the entry, and the user can edit and re-evaluate it.
Is that right?
In D14738#309642, @sirgienko wrote:Nitpick: Maybe, then user without Discount edit rendered markdown entry from loaded worksheet, we should drop rendered result? So, users don't forget reevaluate this edited entry later.
Aug 15 2018
Aug 15 2018
In D14738#309526, @filipesaraiva wrote:In D14738#309525, @pino wrote:In D14738#309519, @filipesaraiva wrote:Can I change the authorship of the commit and push now? Do you know @pino?
You definitely cannot change already pushed commits...
- revert the commit, because of wrong authorship, and unfixed issues still there
filipesaraiva added a reverting change for R55:6d70bfac748c: Add the markdown entry: R55:cfc9324d30dd: Revert "Add the markdown entry".
filipesaraiva committed R55:cfc9324d30dd: Revert "Add the markdown entry" (authored by filipesaraiva).
Revert "Add the markdown entry"
In D14738#309525, @pino wrote:In D14738#309519, @filipesaraiva wrote:Can I change the authorship of the commit and push now? Do you know @pino?
You definitely cannot change already pushed commits...
- revert the commit, because of wrong authorship, and unfixed issues still there
- wait for @kqwyf to fix the issues
- once it is done, ask him/her for name and email (since silly phabricator cannot provide this info for commits sent with arc)
- take the patch, amend it fixing the authorship, and push
Oh no, sorry. I thought the authorship was maintained... when I answer:
Add the markdown entry
Aug 14 2018
Aug 14 2018
Thank you for your contribution @kqwyf. I built with Discount and it is working fine. I built without Discount, I could run Cantor correctly and the options to insert Markdown entries continues to show, but it is a problem with others entries options like LaTeX. Maybe it is time to some refactoring in this part.
Review in progress at D14738.
filipesaraiva moved T9108: Add support for markdown from Backlog to Work in Progress on the Cantor board.
In D14780#308005, @sirgienko wrote:@filipesaraiva, after 90b001d1b01556cc5d5b60791e9b43e6dfcff0b4, do you still have build errors?
Aug 13 2018
Aug 13 2018
In D14780#307590, @asemke wrote:There is no jl_string_ptr in Julia 0.4.7. Are you using older includes with newer libraries?
Hello @kqwyf, are you from that course in a Chinese university about open source contribution?
filipesaraiva added a reviewer for D14780: Fix Julia backend build for Julia minor version > 5: sirgienko.
filipesaraiva added a project to D14780: Fix Julia backend build for Julia minor version > 5: Cantor.
Aug 10 2018
Aug 10 2018
In D14680#306377, @sirgienko wrote:Hi @filipesaraiva, in this moment Python 3 use dbus for communication with server. And Python 2 don't use server, so we have bug 363606. In this commit I apply python server code from Python 3 also for Python 2. In future we plan remove dbus code and use QProcess (or KProcess) for this.
Hi @sirgienko, what about the support for this backend in other OS? In past we throught about drop dbus because it is unfortunately not supported in Windows and OS X.