Build an Easy-to-Use and Powerful Attributed Label about nimbus

[rogchap]

Love the idea of using markdown. I'm sure (once we got going) we could add more markdown syntax features like lists, images etc.

Question: When supporting headings there are two types of syntax for headings; one is prefixing with a # and the other is "underlining" with = or -. I personally prefer the # syntax and I think this would be easier to parse.

How would we pass font information? We would need to know what point size for the headers were to be etc?

In what situation would we use -mutableAttributedStringFromLabel: ?

[rogchap]

Totally want to use NSDataDetector for links, but it is only in iOS 4.0 + :(

[jverkoey]

Support data detectors, just try to ensure that the label will still
build on iOS 3.

On 2011-08-04, at 7:56 AM, rogchap
[email protected]
wrote:

Totally want to use NSDataDetector for links, but it is only in iOS 4.0 + :(

Reply to this email directly or view it on GitHub:
#24 (comment)

[jverkoey]

We should try to support both header styles eventually, but for now
the ## format would be a good v1. As for the font info, perhaps we
should define a markdown stylesheet object of sorts?

@interface NIMarkdownStylesheet

@property (nonatomic, readwrite, retain) UIFont* header1Font;
Etc...

@end

[jverkoey]

We'd use mutableAttributedStringFromLabel when we want to create an
attributed label by defining the basic characteristics of a label and
then adding links, for example. An attributed label should probably be
a UILabel to make this easiest.

Sent from my iPad

On 2011-08-04, at 7:49 AM, rogchap
[email protected]
wrote:

Love the idea of using markdown. I'm sure (once we got going) we could add more markdown syntax features like lists, images etc.

Question: When supporting headings there are two types of syntax for headings; one is prefixing with a # and the other is "underlining" with = or -. I personally prefer the # syntax and I think this would be easier to parse.

How would we pass font information? We would need to know what point size for the headers were to be etc?

In what situation would we use -mutableAttributedStringFromLabel: ?

Reply to this email directly or view it on GitHub:
#24 (comment)

[rogchap]

Data Detectors for iOS 4 and I'll use a simple regex for iOS 3 etc

[rogchap]

I think markdown would have to have some sort of stylesheet. I think we can get the Label built first then address the markdown parser.... looks like I'm "grabbing" this one too!

[jverkoey]

Haha, try not to take on too many things without finishing some others :)

I'll be pushing out a new release later today by the way, 0.6. Notably in this change I'm doing away with independent projects for each feature and now have a single root project that contains separate targets for each feature. It's effectively the same thing, but now you can have on Xcode window open and access the entire Nimbus namespace of features. It's super handy for refactoring :)

[rogchap]

In terms of links within the label I was planning a delegate when the the link is hit. Not sure to either do a -(BOOL)shouldOpenLink: which if returned true would default to opening the URL in safari or -(void)didSelectLink: which would leave it completely up to the user. Either way would allow the user to intersept the URL and act appropriately. Any thoughts?

I guess most people would want to open the NIWebController, but obviously I don't want to tie to this dependency.

[jverkoey]

We definitely don't want to tie it to any controller. Once we get the navigator into Nimbus people might want to have the navigator open the URL, for example.

As for whether it should be shouldOpenLink or didSelectLink, I'm leaning towards the latter because I don't think the label would do anything interesting with the return value of shouldOpenLink.

[rogchap]

See #46

[rogchap]

This is is now in Nimbus < 0.8
Docs can be found here: http://jverkoey.github.com/nimbus/group___nimbus_attributed_label.html