-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathbrowser_notes.txt
61 lines (35 loc) · 2.7 KB
/
browser_notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
Initial Prototype
=================
Date: March 16, 2009
A first test of rendering views and handling messages in another process.
Architecture:
-------------
Main Process:
Tranquility : BApplication
BrowserWindow : BWindow, just one to start
ProxyView : BView, one taking up all the frame of the BrowserWindow, draws the BBitmap rendered in the render process, forwards needed BMessages to the render process. This view is simply a canvas that the render process will draw on.
Render Process:
RenderBoy : BApplication
RenderLooper : BLooper, receives messages from the main process and sends them to RenderView. Embeds the RenderView into a BBitmap, sends the bitmap to the main process.
RenderView : draws and handle events.
Date: May 16, 2009
It has been two months and I finally have a somewhat working version of the above, minus major event handling and there is no RenderLooper yet. It may not be needed.
Ideas
=====
From http://news.ycombinator.com/item?id=518449:
QUOTE>>
5 points by andreyf 3 hours ago | link
I'm actually moving away from what you describe - a little less than a year ago, I had just finished school, my wife had a baby, and I started a demanding coding job at a startup. For about 6 months, I couldn't code outside of work for my life - I'd doze off to news.yc, RSS feed, even reddit at times.
In those 6 months, though, two ideas have been snowballing - (1) that (Greasemonkey) + (code repository with dependency resolution) + (some other stuff) would be a revolutionary piece of software, and (2) that the great thing about Lisp is vaguely similar to "Dependency Injection" and "Inversion of Control" - macros (reader and otherwise) are dependencies which are injected into the reader and compiler. If I was to figure out an elegant way of doing this in JS, I can piggyback on the buzz of DI and IoC to help people think deeper about programming.
Couple that with the frustration of "people don't get it unless you show them code", and I've been spending more and more nights coding away again. So my recommendation would be:
1) Get excited about something
2) Realize that you're very fortunate to have the resources to be excited about something 99% of the world does not
3) Socially commit by telling people about it (even if they don't get it)
>>ENDQUOTE
The idea I like is the Greasemonkey idea. This could in some ways be used to replace many Firefox add-ons.
-------
The Chrome extension API proposal is also interesting: http://dev.chromium.org/developers/design-documents/extensions
-------
DNS prefetching seems like a good idea: http://dev.chromium.org/developers/design-documents/dns-prefetching
It depends on how Haiku handles DNS resolution and whether or not there is a DNS cache.
-------