|Why node + chrome rules the world...||Dennis Kane||9/1/12 5:11 AM|
When you go to the site, it "looks" like any plain-jane site, circa 1997. Not much to it in the visual department at the moment. But then you see things like close buttons on the major sections of the page. If you click one, that section will completely disappear from the page. Then you ask, "How do I get that section back?". Simple! If you just press the 'c' key, a "controller" menu will pop up. The closed sections appear in red. To bring it back up, just click on it! And to reorder how the sections appear on the page, just right click it in the controller menu, and use the up/down arrow keys. Then right click again to deselect it.
You can activate the major sections of the page by just clicking on them. It should change to a light red background when you do that. When you activate the "Journal" section, you can scroll through the entries with the right/left arrow keys. Holding down 'alt' at the same time will scroll according to the current "skip factor" and holding down 'ctrl+alt' will zoom it to the beginning or ending (this works on Macs... other operating systems will differ on how the arrow + meta key combinations work).
Okay... so that's not the really exciting part. Then fun only really begins when you press the 'd' key. I don't want to ruin the surprise... try it out for yourselves!
I developed the site primarily for Google Chrome, but of course any webkit based browser is going to work well.
On the backend, I just like to have a tight little server that just keeps the connection logic in order. I of course also need to save stuff, so I just use node-mysql for that. But as far as most tasks are concerned, I just like to offload as much work as I can onto the powerful little JS engine that is built into each Chrome browser. I use HTML5 Local Storage to save the state of the client.
|Re: Why node + chrome rules the world...||Dennis Kane||9/6/12 11:13 AM|
Hi! I've got a really slick Desktop GUI working that almost rivals my MacBook:) What I am creating is basically a browser based operating system that will allow you to plug in arbitrary application modules. I want the modules to be dynamically loadable, using node as the application server. So now that the "OS" is getting stabilized, I can really start to think about hardcore web-based application programming. I want to be able to load up the Video folder with youtube icons that you can double click to pop up a youtube video player. But really, I want to develop a crazy wicked HTML5 video player that can be used with "freeware" ogv video streams and such. That's just a "for instance" and there is obviously an unlimited number of things that can be done. Well, nobody has shown any real interest in this, so whoever wants to get together to hack away with me is very welcome! I am going to want people who are comfortable with both the node and the Chrome/DOM programming environments....
|Re: Why node + chrome rules the world...||Ket||9/6/12 9:47 PM|
Don't boast them much just yet they have taken down some cool MP4 video features. What do they think better video format than mp4 you guess.
Yes, I can use ogg but that is the case.
|Re: [nodejs] Re: Why node + chrome rules the world...||Karl Tiedt||9/6/12 10:30 PM|
Have you seen the Lucid Desktop project?
|Re: [nodejs] Re: Why node + chrome rules the world...||Dennis Kane||9/7/12 1:32 AM|
I think I have seen that site before... but the fact that I don't really remember is not a good thing! I guess the first red flag about that project is the fact that the last blog entry is dated September 30 2011. Also, I couldn't figure out how to jump through the hoops necessary to get the demo working. Mine is painfully simple to get working, though, and I am interested in working on it and blogging about it pretty much every day for the forseeable future! So I guess I'm just not very excited/worried about it.
|Re: [nodejs] Re: Why node + chrome rules the world...||Jorge||9/7/12 2:22 AM|
On 07/09/2012, at 10:32, Dennis Kane wrote:
>> On Thu, Sep 6, 2012 at 1:13 PM, Dennis Kane <dka...@gmail.com> wrote:
>> Have you seen the Lucid Desktop project?
> I think I have seen that site before... but the fact that I don't really remember is not a good thing! I guess the first red flag about that project is the fact that the last blog entry is dated September 30 2011. Also, I couldn't figure out how to jump through the hoops necessary to get the demo working. Mine is painfully simple to get working, though, and I am interested in working on it and blogging about it pretty much every day for the forseeable future! So I guess I'm just not very excited/worried about it.Yeah, that (lucid-desktop) seems to be a dead project...
Here's the pioneer of "web operating systems" (+6 years old) that's cool and awesome and still alive and kikin':
There's also Dan Ingalls' more academic experiment:
And WebShaka's (dead) attempt at it:
|Re: [nodejs] Re: Why node + chrome rules the world...||Dennis Kane||9/7/12 5:48 AM|
EyeOS might be technically wonderful, but it is a corporate/commercial/pay thing, so that makes it pretty much completely irrelevant to me. But... given the fact that when I clicked the "What's eyeOS" link under "About Us" at the bottom of the page only to be met with a "404 not found" page , I guess I'm just a tad skeptical about the whole venture :D The "academic" one, I dunno, it's just weird and sluggish. The dead one... well I guess that just speaks for itself.
Anyone know of any other contenders?
Anyone have any thoughts on mine?
|Re: [nodejs] Re: Why node + chrome rules the world...||Brandon Benvie||9/7/12 5:54 AM|
|Re: [nodejs] Re: Why node + chrome rules the world...||Karl Tiedt||9/7/12 6:35 AM|
Yeah, Lucid started years ago now, and it was very active, not sure
what happened with it, but it was pretty amazing at what it did for
its time.. If nothing else, it may be good for some ideas, I didnt
realize it has fell by the wayside :/
|Re: [nodejs] Re: Why node + chrome rules the world...||Dennis Kane||9/7/12 7:43 AM|
Well, the necessary technology didn't really exist years ago. I rely very heavily on node/socket.io/websockets for the server side and Chrome's constantly developing API in the client. Trying to implement my current site with older JS engines and HTTP servers along with AJAX would be next to impossible. So I'm pretty excited about what I'm doing... the GUI is pretty intuitive and the websocket connection is lightening quick!
|Re: [nodejs] Re: Why node + chrome rules the world...||Daniel Sousa||9/10/12 1:47 AM|
eyeOS used to be great on the 1.x versions, but in 2009 the eyOS Team abandoned the 1.x series and started developing eyeOS 2.0 almost secretly and since then eyeOS has been more a commercial software than an open source project. Currently their website doesn't even mention there's an open source project.
Lucid 2.0 was supposed to be developed on node.js, but there was basically just one person around it and he hasn't worked on it for a long time.
These desktops were a great idea 5 years ago when there weren't any web apps and the word "cloud" wasn't even used, now these small projects would have a hard time competing with Google Docs et al.
|Re: [nodejs] Re: Why node + chrome rules the world...||Dennis Kane||9/11/12 2:44 PM|
|Re: [nodejs] Re: Why node + chrome rules the world...||Tom Utley||9/11/12 8:53 PM|
You are insane! But in a good way. Keep up the good work
|Re: Why node + chrome rules the world...||Dennis Kane||9/14/12 7:31 PM|
When one person gives up, another one doubles down. It's the way of the world... yin and yang and all that happy crap. I've just added a youtube feature to my website/desktop thingy (http://luvluvluv.info). The info for the artists and videos are kept on the server, and are only downloaded via socket.io when you do some kind of mouse event. Hopefully I can start convincing summa you's that this new concept is worth a little of your time and energy! About the other crazy stuff I've been talking about recently, I realized that it's not really possible with the current state of my code (and the current state of my coding skills :) I need to refactor the hell out of this thing and approach it from a much higher level before I can start thinking about doing dynamic code insertion...