shadow_7283 wrote:
(That's odd... the forums keep changing it to lowercase)
Caps filter. To avoid it, add
[b][/b]
at the end.
Offline
Is Snap going to used prototype base inheritance like BYOB or is it going to use classes?
Offline
Oops, *use , * based
Offline
@roijac saying "
Jens wrote:
We'll use prototypical inheritance for Snap, just like in BYOB
which i never got "
Have a look at the following link:
http://www.xleroy.net/ByobTuto
where are given examples of OOP instructions.
Start from the 52th project (Tutonew)
Last edited by xly (2012-08-27 10:58:52)
Offline
roijac wrote:
which i never got
I take it you do understand class/instance objects?
Class/instance has two different mechanisms that, if you think about it, are both aspects of specialization:
1. Instantiation, in which a new object is created that shares the properties of a class except for specialization of its instance variables.
2. Class inheritance, in which a new object is created that shares the properties of a class except for specialization of some methods.
Well, aren't those almost the same? Especially once you understand that procedures are data (i.e., first class procedures)! Both of these are specialization in which a new object shares the characteristics of an old one, except for exceptions.
So, doesn't it make sense to simplify away this unnecessary distinction and just understand inheritance as creating a new object as a specialization of an old one?
Offline
For some reason when i try to open projects from a URL not one I've saved, it just shows a blank canvas
Offline
joefarebrother wrote:
For some reason when i try to open projects from a URL not one I've saved, it just shows a blank canvas
Right, until we get back end and/or standalone local Snap! done, Save works using JS Localstore, which can only be read in the same browser and from the same URL.
Instead, use Export, and then save the resulting browser tab to an .xml file locally.
Offline
But if I click on a link to a snap project, it won't open.
Last edited by joefarebrother (2012-08-27 17:54:25)
Offline
Suggestion.: I think you should be able to make cap blocks. For example, Throw should be a cap block, and in my nondeterminism project, fail should also be a cap block.
Offline
joefarebrother wrote:
Suggestion.: I think you should be able to make cap blocks.
That's a reasonable idea, but of course it doesn't hurt anything to have the little tab at the bottom of the block. (BTW "cap block" is a terrible name for these, given that there is a completely different thing called a "hat block"! I'd never heard "cap block" before and it took me a while to figure out what you meant.)
Offline
MathWizz wrote:
Question... Why did you go with XML instead of JSON?
We actually went back and forth on this, but afaik there's no terribly compelling reason either way. It's just aesthetic taste. Do you think differently?
Offline
I vote JSON if it's not too late to change.
Offline
bharvey wrote:
Do you think differently?
I didn't mean, "which would you vote for?" I meant, "do you think there's a serious technical reason, not just taste, to prefer one over another?" So you have to explain why your preference is more than a mere preference.
Offline
bharvey wrote:
bharvey wrote:
Do you think differently?
I didn't mean, "which would you vote for?" I meant, "do you think there's a serious technical reason, not just taste, to prefer one over another?" So you have to explain why your preference is more than a mere preference.
faster parsing!
http://www.navioo.com/ajax/ajax_json_xm … arking.php
Offline
bharvey wrote:
bharvey wrote:
Do you think differently?
I didn't mean, "which would you vote for?" I meant, "do you think there's a serious technical reason, not just taste, to prefer one over another?" So you have to explain why your preference is more than a mere preference.
It is also smaller. Not that any textual format can be very small though...
Offline
You're writing Snap! in JS. JS uses JSON to represent data structures. Therefore...
Offline
MathWizz wrote:
bharvey wrote:
bharvey wrote:
Do you think differently?
I didn't mean, "which would you vote for?" I meant, "do you think there's a serious technical reason, not just taste, to prefer one over another?" So you have to explain why your preference is more than a mere preference.
It is also smaller. Not that any textual format can be very small though...
at least not serializing the list viewers xD
Offline