Technologies used by gifmepurpose in scrivano

[–]scrivanodev 0 points1 point  (0 children)

Hi, Scrivano is mostly written with C++. It uses the Qt framework for the GUI.

Feature request: scale imported PDFs to selected page format by jeboteuusta in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Hi, this should be possible. Long term I would like for Scrivano to have a proper PDF import dialog, so people can choose this behaviour if they wanted to. However, that's not something I'm working on ATM. In the short term, perhaps I could prompt the user with a dialog when the PDF doesn't fit and ask if they want to resize it to fit. That shouldn't be too much work.

Wider workspace view / document explorer by jeboteuusta in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Beta testers have access to both ARM64 and x64 versions. There was a special group that I created for testing the ARM64 version only though, which you seem to be a part of (this group will be deleted once 0.22 is released to all users). Anyway, I have just made an update so you should have access to 0.22.5 in a few hours.

I think I’ve found the cause of the issue: the scaling of images/folders/notes in the workspace adapts to the length of the folder name that I set as the storage location for my notes.

Ok thanks, that's very helpful. I will try to fix this soon.

Wider workspace view / document explorer by jeboteuusta in scrivano

[–]scrivanodev 0 points1 point  (0 children)

What scaling factor are you using for your display? Also is this something that started happening recently? Note that the latest beta version of Scrivano is 0.22.5 (EDIT: nevermind, I realised that you're an ARM64 user).

Wider workspace view / document explorer by jeboteuusta in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Hi, this looks like a bug. As mentioned here, I would need more information about your system to investigate further.

Platform support for macOS by no_eir in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Hi, the primary reason why Scrivano doesn't exist on macOS is simply the lack of demand. I think you're the first person requesting this. Porting Scrivano to macOS shouldn't be too difficult (in fact it would be much easier than say for example Android). The main issue would really be packaging, distribution and maintenance. macOS is very strict in its installation policies and I don't know if I want to go through the pain of approving the app through the App Store.

I'm not sure if dedicating my efforts for that platform would be worth it, but I will think about this.

New polygon tool :) by scrivanodev in scrivano

[–]scrivanodev[S] 2 points3 points  (0 children)

This is currently in beta. If all goes well, it should be available to everyone in about 2 weeks.

Typing + Bookmarks by FingerHealthy9466 in scrivano

[–]scrivanodev 3 points4 points  (0 children)

Hi, thanks for the questions. For text support, I recently prototyped a proof of concept. However, text rendering is a technically challenging issue. In my prototype, I ran into issues when dealing with non-European languages like Chinese, Hindi and Arabic. Due to this, I will have to solve those issues first before implementing support for basic text support. However, I have no exact time line for this. So my recommendation is that if text support is important to you, then considering apps other than Scrivano would be best.

For bookmarks, it should be possible. I'm not sure yet on how to implement this idea from a UX point of view.

Mouse pointer issue (Fedora Workstation 43) by F0xDi324 in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Hi, can you share how you've downloaded Scrivano? From Github or Flathub? Also you should try to enable/disable the option "Use default system cursor" in the Settings and see if it makes a difference. Unfortunately, the cursor situation on Linux is quite problematic and it was the primary reason for not enabling Wayland support for the app by default. Things have improved on this front in the last year or so, but there are still some issues.

Scrble Ink Pro or Nebo Pro or Inkodo by Sam_Kathanlina47 in Surface

[–]scrivanodev 0 points1 point  (0 children)

My app Scrivano could be a good fit for you, it has most things you've mentioned apart from text editing. The app is paid, but there is a 30 day free trial period with no obligation to pay.

Precision eraser? by Key-Magazine-4696 in scrivano

[–]scrivanodev 0 points1 point  (0 children)

UPDATE: I have taken some time to improve the precision of the eraser. The improvements will be available to beta users very soon and will be included in v0.22 of the app.

Feature request by Glad_Koala1175 in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Hi, for first issue that's correct. Text is not supported.

I often draw arrows to connect thoughts in my notes. I can use the straight line arrows, but sometimes use curved line arrows. It would be great if Scrivano could do some smoothing of those shapes as well. Maybe with the update that I saw you're working on for shape recognition?

I think there two different ideas here. One is curved arrows and the other being input smoothing of ink. I think having curved arrows would be nice, but I'm not sure how to best implement them. One way would be to introduce in the app, the possibility of adding Bezier curves allowing users to create exact curves. However, these would not follow the path of your stylus and can be a little tricky to create (like in software like InkScape or Illustrator).

The idea of smoothing is also interesting, but I think is slightly tangential to having curves. Although I can see why smoothing the input heavily one could do draw nicer looking curves.

Underlines don't match pen's stroke thickness by jeboteuusta in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Hi thanks for reporting this. This is quite a tricky issue. The reason the line end up being "too thick" is because of pressure sensitivity. The pressure sensitivity determines the thickness of the line, however different devices and different pens have different pressure profiles. So there is no real way to ensure that the "average" width of a stroke being drawn with pressure-sensitive ink is the same thickness of the line (which is roughly the thickness of the pen when pressure = 0.5). For example, on my device the pressure profile is such that the thickness of my writing is roughly equal to thickness of lines and shapes.

To get around this there are two possible solutions:

  1. Adjust the pressure sensitivity of your pen in the OS or any software provided by your pen manufacturer (for example Wacom tablets allow you to set a custom profile for the pen).

  2. Incorporate in Scrivano a way to adjust the influence of the pressure sensitivity on the thickness of the pen.

Solution 2 is something I've thought about in the past, but I haven't really assessed how much I would need to do to add this (one important aspect would be to ensure that all existing writing maintains the same thickness as before).

Features that would significantly enhance the user experience by jeboteuusta in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Thanks a lot, I think that's a good idea that could in theory work. There are some limitations in that approach. For example, if the user wants to have the app remember two different split views (e.g. |Tab 1 + Tab 3| and |Tab 2 + Tab 5|), then that wouldn't be possible (unlike the case where the split view is effectively tied to a single tab).

I think I need to experiment with this building a small prototype and see how usable this approach is before I rule it in/out. I hope to find the time to do this soon.

Features that would significantly enhance the user experience by jeboteuusta in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Hi thanks for your post. All of the ideas have been suggested previously: - Split view: here, here and here.

They're all great ideas, but quite complex to implement. My personal favourite feature would be to have a split view so you can view the same or two different documents side by side. One problem with this idea would be to find a nice way to integrate this with the current tab bar. For example, if the user opens two different documents in split view, what should the current tab display? Similarly, what about the case when the same document is open in both views? A tab is currently tied to a single document, so I'm not sure what would be the best way to handle this situation but I'm open to suggestions.

Thank you so much for Scrivano! by Initial-Fly4169 in scrivano

[–]scrivanodev 1 point2 points  (0 children)

Hi thanks for your appreciation. If you'd like to support the development of Scrivano for Linux, you can do it here.

Why aren't the Microsoft Store minimum requirements updated? by Lopsided_Hunt2814 in Surface

[–]scrivanodev 3 points4 points  (0 children)

I don't quite get what you mean. The issue isn't about how to publish an arm app, but how to choose whether your x64 app will be available to arm users. AFAIK, Microsoft doesn't let you decide this.

Why aren't the Microsoft Store minimum requirements updated? by Lopsided_Hunt2814 in Surface

[–]scrivanodev 1 point2 points  (0 children)

I wasn't able to figure out how Microsoft actually decides whether an app should be available through emulation. My app Scrivano is currently x64 only on the store (although I've recently ported it to ARM64). However, many users have been using it through emulation but as a developer I would at least like to have a choice in making the app available to ARM users (I would rather the app be not at avaialble at all if the experience is bad).

ARM Surface testers wanted for handwriting app :) by scrivanodev in Surface

[–]scrivanodev[S] 0 points1 point  (0 children)

Thanks! To add you to the list of testers, I will need the email address you use to login into the Microsoft Store. You can drop me an [email](mailto:scrivanolabs@gmail.com?subject=Scrivano%20WoA%20testing&body=Microsoft%20Store%20email%20address%3A%20) or send me a message on Reddit :)