Skip to main content

Browse GamesGame JamsUpload GameAutumn SaleDeveloper LogsCommunity
On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
billiam3 years ago (1 edit) (+1)

Thank you for the feedback and kind words!

Some of these are (obviously) easier than others, but I can see why they’d be useful.

Syntax obfuscation

This one is a lot of work! I understand the desire, but it does mean adding lot of wysiwyg toolbars, or having displaying your text as markdown when your cursor moves near it. I find that behavior really distracting, and makes cursor movement really unpredictable.

It’s probably the only way to make a markdown editor useful to non-markdown folks though.

Markdown engine

Like most editors, Deepdwn uses a superset of markdown. What features are you expecting from MultiMarkdown’s implementation that don’t exist in Deepdwn?

Web publication

API integration is out of scope for Deepdwn right now. I’m trying to make it as independent from third party services as possible, mostly for maintenance reasons.

Similarly, a built-in FTP client is not currently planned.

Image previewing

Showing all images in the explorer would be nice, but obviously the UI isn’t set up for it (at all) currently. It might be possible in the future if that changes. I’ll keep it in mind.

Image paths

I agree. This is a limitation in exporting right now. I’d like to improve it for sure, but I think it will require pretty complicated UI to do it right, for example having some kind of path export preferences on a per-folder basis. :(

Demo

I’ve thought about this a lot, but haven’t settled on a good way of doing it. If Deepdwn was subscription based, it would be easier, but selling a DRM-free application adds some challenges. Stripping features is no fun.

A no save/no load version might work, but would be easy to circumvent, and wouldn’t be a great experience for users who are interested.

Export format

  • Textbundle - great idea
  • Zip - Sure, though I guess you could zip these yourself. I think the problem here is if you refer to images in relative paths above the markdown file. I could rewrite those paths, but that can cause collisions with other files… it’s tricky :D
  • epub - Would be nice, but would require Deepdwn to act as a full featured document publisher. I think this will be better left to dedicated tools.
  • Jpeg - Already planned!

I really appreciate the feedback, and I hope that I can get you at least some of these in the future :D

Reply
Manukineko3 years ago

thanks for your answer :D

Syntax Obfuscation

I totally understand it !
So what about styling ? It's similar to how Deepdwn handle it now : color-coded line per syntax types. The improvement would be to add font and size styling to sintax tag elements, like for example, H1 tag with a bigger size than H2 size or simpler, a lighter color than the line the tag apply to (purple for the title, light purple for the tag). Something like this ?

Markdown engine

Oh, let me stress test that when I'll be home.
Actually, mat be not that much XD

Web Publication

I can totally hear it, and that was just a QoL feature anyway.
And it's not like it's difficult to use any FTP client.

Image preview

To be precise, I though of a thumbnail next to the name.
But well that means generating thumbnails AND caching them somewhere.

Maybe to "just" have Deepdown to grab the images filename and list them in the explorer like they are regular text file, and then double-clicking it to display a preview window would be enough for the time being ?


Image Path

Yeah, it fall down to have a kind of a hidden internal database of some sort, to store that kind of data.
I was more on the per-file kind of system, though and it would be relevant only if the image preview window is implemented because you could set this alternate path with it (two bird, one stone).


Export Format

Textbundle is a kind of zip is I'm not mistaken.
Regarding zip itself, I'll go the simple way : create a dedicate root folder for images (e.g assets), create a hierarchy of folders base on each images path, rewrite links in the exported file to point to their new location.
Like :
I have "../dogs/dog.jpg" and "cats/black/cat.jpg" in my file.
At export, I would have this hierarchy created inside the zip :
- file.md
- assets
    |_ dogs
    |    |_ dog.jpg
    |_ cats
        |_ white
            |_ cat.jpg

and in the file, link rewrote as "assets/dogs/dog.jpg"
"assets/cats/white/cat.jog"

Of course, if the image path feature would make it, the user could overwrite the default rewriting which would use the alternate path/url the user has provided for each images.

epub - Oh didn't though about that. You're right.


Anyway, please, don't stress yourself, you clearly know what you are doing, in my opinion.

Deepdwn is already plenty useful for my usecase.

Reply
AboutFAQBlogContact us
Copyright © 2024 itch corp · Directory · Terms · Privacy · Cookies