| Article: |
BYOB: Build Your Own Browser | |
| Subject: | RE: XCode please | |
| Date: | 2004-01-25 17:23:26 | |
| From: | derrick | |
|
Response to: RE: XCode please
|
||
|
Alright, well let's get back on track. First item, thanks iopossum for your note. No hard feelings :)
|
||
Showing messages 1 through 4 of 4.
-
RE: XCode please
2004-01-25 21:28:40 Andrew Anderson | [Reply | View]
-
RE: XCode please
2004-01-31 11:19:30 jbakse [Reply | View]
Hello,
I originally took a look at this tutorial thinking there was a small chance there might be a little information I could apply towards creating an javascript aware environment.
I know that this is something that probably wouldn't fit in the next article that well, but I thought this was as good a place as any to get in a request. I'd love to see an article about embedding a javascript environment.
-justin -
RE: XCode please
2004-01-28 18:38:23 keath [Reply | View]
Thanks Andrew,
I would just like to see you follow up with what you outlined at the end of the article. For example, updating the URL line.
I saw the 'Mac OS X State of the Union' video at ADC. Towards the end, it was demonstrated how to set up a browswer using WebKit very quickly. Using XCode, it was easy to set up the outlets from the UI elements to the WebView; but I don't understand how the new controller mechanism was used to do the reverse: update the UI from WebKit.
It would be great if you could explain not only WebKit, but something about how this new tool works. -
RE: XCode please
2006-01-31 07:02:02 speth [Reply | View]
i've posted some code at http://end.com/BionicDOM that does something like this. it is a framework with an Interface Builder palette that lets you use Cocoa Bindings to access values in the WebView. the sample.nib file included implements a live CSS inspector panel entirely with bindings. (try running sample.nib in the Interface Builder simulator)




I understand that the first article was a little basic and that it was not the most novel concept. the thing is the goal for this topic was always two articles: part one with the basics, part two with more meat. i felt it would be confusing to readers to jump right into the intracies of webkit without having a backgroud article for readers to refer to.
that being said, if there is anything that anyone is specifically looking for in part 2, let me know and I will try my best to include it in the article. i need specifics though, not something like "more technical details of webkit".
as derrick said, it's a team effort, i can't deliver what you want in an article unless i know what it that is.
andrew