https://bugs.kde.org/show_bug.cgi?id=421065
--- Comment #3 from Nikita Sirgienko <warqu...@gmail.com> --- (In reply to avlas from comment #2) > (In reply to Nikita Sirgienko from comment #1) > > We have been considering improving the looks of Cantor worksheets, but there > > are some limitation here: language (C++) and graphical widget stack (Qt). > > So, i think, flexibility of Jupyter/Kaggle (with possibility to change view > > of, well, all existed elements via custom css). > > So, I don't think, that your request is fully possible. All of this > > castomizatio comes from flexibility of HTML+CSS, which used in Jupyter and > > Kaggle. > > > > I am not sure (we still considering using qt web engine in Cantor), but I > > think, that CSS Markdown styles don't possible in Cantor on this moment- > > this will work only with fully featured web browser. > > > > Converting worksheet to Markdown is theoretical possible feature, but this > > is a lot of work and I haven't seen a huge request for this feature, so I > > don't think, that we will implement this soon. > > > > On this moment, we more focused on improving user expirience, with > > supporting a good look of program. > > I see. Many thanks for the explanation. QtWebEngine seems like a drastic > move with pros (the flexibility you talked about) but also some significant > cons (security, privacy, "weight" and the effort involved in the transition). > > Why not just using nodejs instead? Would this help with the cons? > > Alternatively, I wonder if adding an interface in QML could help making it > more appealing. Perhaps that is what is needed and people from the design > team can help. > > Regarding Markdown, I guess you could take a look at projects such as > Typora. I think it uses nodejs to allow on-the-fly styling based on CSS > files. Nodejs no help in this situation at all, because the main limitation is that Cantor, without web engine, can't fully render (I mean, from text form to content, visible for user) HTML+CSS. You have been mentioned Typora, but key component of supporting css styles is that Typora application is actually a browser (chromium, to be more precisious, - Typora is based on Electron framework). And because of fully support of HTML+CSS - Typora can have css style for Markdown, and how it manage the styles - via javascript, or something else - is not very important in this situation. Also, I haven't been mistackend, QML can do only what Qt can do because it is just an another form of UI representation: one form is ordinary (for Qt apps) ui files (and ui files is just a XML) and another form is a more css styled QML markup. -- You are receiving this mail because: You are watching all bug changes.
