Nice news ! Thanks ASiegel !

"Requirement : PowerMac G5 or faster"

What is this hardware faster than a G5 ?

[ Edité par Papiosaur activé 5/11/2020 9:34 ]

Looks really good! Well done!

This is great. Do you plan to add some boolean operations on SVG paths? Or quick transform options for shapes (like mirror horizontally or vertically)?

Maybe it's not Inkscape, but definitely a long awaited app. Thanks a lot!

Quote:


[ Edited by takemehomegrandma On 2020/11/5 12:10 ]

@Papiosaur
Quote:
Thanks for the donation.

Well, in terms of officially supported machines, X5000 owners will likely notice a performance boost thanks to the faster PCI-Express bus, especially in higher resolutions and with large application window sizes.

Also, for those who will not read the included documentation, a PowerMac G5-class machine is by no means "required", it is merely "recommended" for optimal performance (in particular when dealing with more complex designs).

I personally use VectorInk on a G4 machine and it is quite snappy for many uses.

Nice to have a tool like this. Why did you change the name from https://github.com/methodofaction/Method-Draw to VectorInk?
And it is JavaScript together with WebKit in a MUI surface. Was it much more difficult to use https://github.com/SVG-Edit/svgedit insetad? svgedit has many more functions.

@koszer

Quote:
"Mirroring" sounds like a good idea.

I would agree that boolean operations for merging or subtracting shapes would generally be desirable but this would require quite some effort (which is why the feature is not already there).

@connor

Quote:
Because while it is based on the same engine, they are not the same thing. VectorInk features MorphOS-specific changes that will never find their way into the official MethodDraw code base.

It is common practice to come up with a new name for project forks. In fact, it is the polite and morally right thing to do. Imagine someone forks a project, adds a ton of bugs and makes it harder to use but insists on using the original name, thus ruining the reputation of the original project...

That said, if you think Method Draw is the same thing. Feel free to use it instead. But do not be surprised if it crashes your MorphOS machine sooner or later.

Quote:
Have you actually tried it? SVG-Edit is substantially slower on MorphOS-compatible hardware.

That said, Method Draw and subsequently VectorInk are derived from SVG-Edit so they are certainly related.

Great news!

I have been hoping for more drawing tools on MorphOS, and hope that someday we will get a basic architectural CAD program, nothing too complex or 3D enabled, just 2D and able to import and modify a few of the most common CAD file formats.

I know that VectorInk isn't what I'm hoping for, but it is still good to see new software for MorphOS. If we want to get more users, new software development is how it will happen, and since the Dev Team seems to have done a great job at adding features to the core of MorphOS that help developers with more modern tools, I think we will see more new software in the near future.

Great job ASiegel!

[ Edited by amigadave On 2020/11/6 11:55 ]

As i am untalented, i downloaded an example from wikipedia. Maybe include some files with the next version?

9k2Qxsh

Some remarks:
i find it weird that the tool buttons scrolling out of view instead of the canvas only.
The canvas' scrollview doesn't shrink to the size of the picture if possible.
There is no bubblehelp(yet) for the gadgets?
The documents name should be visible in the window title.

[ Edited by amifrog On 2020/11/6 21:05 ]

@amifrog

Quote:
It does include a "shape" tool that allows to quickly populate the canvas with various ready-to-use design elements.

The picture you downloaded is not fully editable in VectorInk unless you use the built-in SVG code editor. As the news announcement explains, this is really about offering MorphOS users a convenient option for designing and editing SVG icon graphics, which they have not had before although MorphOS 3.10 first introduced OS-level support for vector graphics two and a half years ago.

Quote:
Well, the application is currently set to require a minimum window width of 1100 pixels and a minimum height of 600 pixels. These seemed like a reasonable default as most MorphOS users use higher screen resolutions.

It is possible to make the top toolbar flow icons into a second row. Also, the sidebar on the right could be hidden in smaller window sizes and only be made to appear (overlapping the canvas) when a user clicks a button.

That said, I prefer the approach of the UI scrolling out of view as opposed to making the canvas so small that it becomes unusable. Plus, showing these scrollbars should also be more user-friendly than preventing users from going below a certain window size altogether.

Quote:
Zooming in or out can affect the speed of the software by a fair amount so there is an argument to be made that the user should be left in control. In fact, I am considering to add a small indicator that informs if performance may be hampered by the chosen zoom level.

Quote:
Not at this time.

Quote:
This would require changes to the Kite runtime. File names are not being passed to VectorInk at this time.

[ Edited by ASiegel On 2020/11/7 9:53 ]

Thanx for your response. i understand its not a fully fledged app yet and just wanted to suggest some bits.
The required screen size would be a problem once one started to open multiple documents to compare/copy&paste etc. so workflow would get increasingly difficult. but we are not there yet.
Looking forward to the next version.👍

@amifrog

This is really supposed to be more of a "single window" app. GPU memory is limited on MorphOS hardware and every new window eats up a lot so it is important to be vigilant about this.

It would probably make sense to add "tabs" in the future in order to optimize use of GPU memory so multiple documents can be handled via a single window.

For users with small screen solutions, I had already added a "Fullscreen" mode to the first release that maximizes the surface area of the program window. It is the icon on the far right of the top toolbar.

That said, I just added what I described above and made the UI work a bit better on smaller resolutions. The changes should be included in a future update.

Really not nitpicking your explanations, but, when you make a single window app you might consider making it a single screen app at all per default and remove the ability to resize the main window in the process. Like Kais PowerGoo, anyone remembers? Once you add multiple documents you are in UI hell, choose wisely.

@amifrog

People have had no issues with Odyssey of Wayfarer offering multiple tabs even though both applications allow to freely resize their windows.

If you prefer to run the app on its own screen, you can easily move it to one or - as I stated earlier - just use its convenient "fullscreen" mode.

That issue got lost in translation, probably on my part. No harm, please continue.😉

On startup it asks for "system:" which will be a nonissue for people not changing drive names after a clean install but is still bad practice.

"SYS:" would be the right way to go.

@Kronos

Thanks. This had already been fixed.

I just uploaded version 1.1 with the following changes:

1. Enabled compact UI mode that allows to use the application in screen resolutions as low as 800x600 (as suggested by amifrog).

2. Fixed absolute paths that referenced the default system partition name rather than the generic "SYS" (as reported by Geit/jPV).

3. Added additional styling to node-related tool buttons for a more coherent appearance.

4. Disabled leftover debug window that was triggered by clicking the fullscreen mode button.

Thank you ! Impressive piece of work indeed !

Quote:

I always wondered if any attempt was made to obtain and update the wonderful DrawStudio software. I used it for YEARS on Amithlon but it never ran quite right on MorphOS.

I currently use Gravit Designer on ChromeOS and have to say much of the program is overkill for my uses.

Thank you so much for this. However, I'm wondering where to get the Kite Hybrid-App Runtime that is needed for running the application? Any help would be appreciated.

> where to get the Kite Hybrid-App Runtime that is needed for running the application?

Kite is integral part of the VectorInk package.