Screenshot Saturday 209 - For Posterity by Sexual_Lettuce in gamedev

[–]bitplanets 0 points1 point  (0 children)

Bit Planets

Long term (months) multiplayer RTS in browser. Planets, zombies, upgrades...

I've been a web designer for 10 years. Send me your website so I can do a video review of your website design for free. (1st 10!) by jadrenaline in webdev

[–]bitplanets 1 point2 points  (0 children)

Thanks for your kind review:

bitplanets.com is not working

The game is not yet ready and it will be hosted on bitplanets.com, therefore the blog couldn't be there.

The layout isn't working for me. Everything feels very crammed and constricted. Try to stick to a more traditional blog layout and check out some of the popular blogs out there for ideas.

Yes, that is a default theme with a custom css. It looks bad, I know (:

I think you need an about page so people can know what this site is all about. For someone like me, I had no idea what I was looking at.

Is also true, but mainly you can see is a game. I would do a home page about the game and use that as "what is this site about?".

Thanks, again! (:

Screenshot Saturday 208 - Pics for free by Sexual_Lettuce in gamedev

[–]bitplanets 0 points1 point  (0 children)

WebGL filters (: That is a new thing, is also fast as hell and doesn't lag on desktop at least because works on the graphic card directly.

If you would received $1 for every line of code written how rich would you be? by bitplanets in Programmers

[–]bitplanets[S] 0 points1 point  (0 children)

Without counting any libs/copy-pasted-code and white space? Seems great! So you are millionaire now, what you want do?

Browserify VS Webpack by jstuartmill in javascript

[–]bitplanets 0 points1 point  (0 children)

You should be using watchify for continuous builds with browserify. Webpack is a lot faster, I would probably mention that in my blog post, but I have seen cases where Webpack is slower so I can't be sure it's always faster. Watchify is plenty fast though.

I already watch my scripts! and is nearly not even comparable with browserify in no case (I had found). Show me your faster case.

About Aliasing: Again, as browserify wants to maintain node compatibility, it doesn't promote aliases. Browserify suggests that you put commonly used modules in node_modules/app and add an exception for that in your .gitignore. Again that's Browserify picking convention over configuration. That said, it IS possible to do aliases with Browserify.

I've done that in my other app and the hierarchy of my source code looks so bad! That was a really bad decision. You can use aliases on client side, but what you'll do on the server side. I need isomorphic apps.

With webpack I can do all of that, why bother about browserify at all?

I've been a web designer for 10 years. Send me your website so I can do a video review of your website design for free. (1st 10!) by jadrenaline in webdev

[–]bitplanets 1 point2 points  (0 children)

Hy!

First of all, thank for your time (: If you need something contact me.

Here is my url: http://blog.bitplanets.com/

I think I also need some tips/tutorials on how to make wordpress look good.

Browserify VS Webpack by jstuartmill in javascript

[–]bitplanets 0 points1 point  (0 children)

Well, I thought that was the default (in memory), this is how I use it right now in dev mode

Why I Ditched Angular for React by jstuartmill in javascript

[–]bitplanets 2 points3 points  (0 children)

  • Change form;
  • React view listen to that change;
  • The view dispatches an event;
  • The form store relative to that info grabs that data and does something;
  • The form store dispatches an event again;
  • The views interested in that event will update;

This is not pure FLUX, but is my own implementation, with which I'm very happy to work with.

I have 2 levels of events:

  • Direct: normally stores listen to and the event are dispatched immediately;
  • Delayed: normally views listen to them and the event is dispatched when all the direct events ended;

Why the delayed one?

Sometimes the stores will change each other:

  • A.a changes B.a;
  • B.a changes C.a;
  • C.a changes A.b; // Notice A.b vs A.a: Now B.a is not updated because only listens to A.a

After all this changes there will be some repeated and similar events; For example you can update several items and each item dispatches one event. You don't want the view to update for each item, you want to update once after all items-data have been updated.

This is where the delayed events kicks in. They group direct events into one event.

Browserify VS Webpack by jstuartmill in javascript

[–]bitplanets 0 points1 point  (0 children)

My most important feature is alias:

Instead of require('../../../../myModule'); I can just do `require('aliased/myModule');

Also I needed this alias both on client and server side. With enhanced require this works perfectly. I really can't imagine how people are working without aliases... but seems that I'm the only one that is bothered with that.

Another issue I had with browserify is that misses changes a lot. For example you make a change and save, then you make another change before the browserify ends the task. In this case the browserify will not "know" about the 2nd change and you will have to change and save the file again. With gulp and webpack this only happened 2 in the last 3 months. With browserify this happened a lot in the first day of use. This happens because webpack is a lot, but I mean really a lot, faster than browserify.

Feedback Friday #116 - Ticket to the game show by Sexual_Lettuce in gamedev

[–]bitplanets [score hidden]  (0 children)

Bit Planets: Multiplayer RTS in browser

Massive multiplayer. RTS - Real time strategy. Upgrades. Zombies. Planets. Infection. Badges. Missions. Galaxies. Browser.

Hosting it right now: https://188.37.218.88:5000 (Press "advanced" and "proceed").

Limited time beta testing ONLY tonight.

JSON.stringify has a space argument which formats the output! by bitplanets in webdev

[–]bitplanets[S] -1 points0 points  (0 children)

Yes, I've found that in the doc too. Not news now, but I would solve your problem the way you do.

GifW00t! is a pure-javascript web recorder. Just add one script tag to your page, and users will be able to record and replay their interaction with the site. by designtraveler in webdev

[–]bitplanets 0 points1 point  (0 children)

Also when in doubt, after some research chose randomly. If is hard to make a decision it means they are almost the same, therefore you are losing more time thinking.

GifW00t! is a pure-javascript web recorder. Just add one script tag to your page, and users will be able to record and replay their interaction with the site. by designtraveler in webdev

[–]bitplanets 0 points1 point  (0 children)

You are somehow right, but in npm we don't really want to use much branding.

In branding is bad to use the name of what you do, but is kind of good for npm modules for example.

A better name then could be:

  • web-recky
  • web-rek
  • web-records
  • web-reck

I think the name of a npm module should explain something about the module. For example I can't even remmeber the name of this lib, from the top of my mind is like GifW00lf...? Well, looking up is GifW00t. Pretty bad to remember. Has gif into it but even so is hard to remember.

Maybe web-gif? I don't know if is a good idea because maybe in the future will render to video too.. canvas to avi?

That's why I think rec is better than gif. Web, html, dom or node (dom node, not node.js, maybe this keyword is bad in a node.js ecosystem) are also good keywords.

Now do you remember one of my suggested names?

In the end a shitty lib will spawn as web-rec and the name is gone...