CintaNotes Forum

Hi again,

I think the program should include rich text format (bold, italics, colors, etc). And spellcheck.

Have a look at the roadmap item #154. Formatting support is planned for the commercial version.

These suggestions are already on the roadmap and can be voted for:

http://cintanotes.userecho.com/feedback ... monospace/
http://cintanotes.userecho.com/feedback/3362-seach/

to CintaNotes Developer: will you plan to move to rtf completely or user could choose between plain text and rtf ?

This feature hasn't been planned in detail yet, it is open to discussion.

i personally against rtf, because i think that it will slow all operations with database and will increase the database size

but i whant to suggest a customizable sintax coloring
(like in vim - users can write a cfg's for different coloring. for example i want that all text between " " became red or i want that all numbers in text became green)
what do you think about this idea?

I am rather partial to markdown, text2tags and wikicreole as ways to embed formatting information in text only files...

hlop4ik wrote:to CintaNotes Developer: will you plan to move to rtf completely or user could choose between plain text and rtf ?

Well, CintaNotes already uses RichEdit control as text editor, so it shouldn't get slower just from using the styles.
I tend to make plain text the default, and display the styling toolbar on demand. But the styling shortcuts like Ctrl+I or Ctrl+B will be always available.

The note preview is quite another story. Using the styles there will get software much slower because of the dimension calculations (total height, line breaking). So for the starters note preview won't display styled text.

@Midas: the selection of the markup used is still up to discussion. I was thinking that simple WYSIWYG would be much easier to work with (don't have to split the note into to views - source markup and final design). Underneath it can just use a subset of HTML.
But I guess the FTS tokenizer will need to be rewritten again to skip the tags..

CintaNotes Developer wrote:@Midas: the selection of the markup used is still up to discussion. I was thinking that simple WYSIWYG would be much easier to work with (don't have to split the note into to views - source markup and final design). Underneath it can just use a subset of HTML.
But I guess the FTS tokenizer will need to be rewritten again to skip the tags..

Of course WYSIWYG will always be sexier... I realize now that a big part of the infrastructure is already in place, so this is no time for radical shifts of paradigm. But, from my layman point of view, between the two mentioned and I'd rather have HTML than RTF -- it maybe not as powerful, but it is a wider standard and the code remains mostly human readable, which is one of my concerns. And the default windows HTML renderer could be used for display like in many other apps.

I agree that rtf would be overkill... but would using some text based syntax make formatted clipping very complicated?

Anyway, I use Zim for alot of notekeeping and am quite fond of their syntax which you can use inline or using the format buttons
http://zim-wiki.org/manual/Help/Wiki_Syntax.html

But, from my layman point of view, between the two mentioned and I'd rather have HTML than RTF -- it maybe not as powerful, but it is a wider standard and the code remains mostly human readable, which is one of my concerns. And the default windows HTML renderer could be used for display like in many other apps.

I totally agree here on that it should be HTML (actually XHTML) subset. No RTF.

Brian wrote:I agree that rtf would be overkill... but would using some text based syntax make formatted clipping very complicated?

Anyway, I use Zim for alot of notekeeping and am quite fond of their syntax which you can use inline or using the format buttons
http://zim-wiki.org/manual/Help/Wiki_Syntax.html

Thanks for the info, Brian. I don't know if CN will support any wiki syntax, it's definitely an option to be considered - but only after basic standard WISYWYG formatting support is in place.