Where should I write about the differences in behavior between amber and pharo?
Some of these will be bugs, others will be expected, but we 'd better write them somewhere. The developers could then look at them and if it is a bug that they fixed, erase it.
Maybe create a tag for these and put them as issues, But if they are not bugs, maybe before erasing them,put them in a wiki page?
-- Sincerely yours, Apostolis Xekoukoulotakis You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Hi! For things that you consider being bugs, you can add them to the issue tracker. For others, you can create a wiki page on github, and give us a link here? Nico Apostolis Xekoukoulotakis <[hidden email]> writes: > Where should I write about the differences in behavior between amber and > pharo? > > Some of these will be bugs, others will be expected, but we 'd better write > them somewhere. > > The developers could then look at them and if it is a bug that they fixed, > erase it. > > Maybe create a tag for these and put them as issues, > But if they are not bugs, maybe before erasing them,put them in a wiki > page? > > -- > > > Sincerely yours, > > Apostolis Xekoukoulotakis > > -- > You received this message because you are subscribed to the Google Groups "amber-lang" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- Nicolas Petton http://nicolas-petton.fr -- You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Ok after a few days programming, the issues I have are: a)the debugger is not working properly --> we'll have to wait for the new debugger i suppose.
b)inline problems (accessing smalltalk var from javascript and vice versa.) One needs to create accessors
c) Workspace requires to define the variables before using them. I thought the workspace was broken when I first used it.
I solved the last 2. For the one I have to wait.
One other thing. I created a new Branch in my repository in which I have written a two-way binding. An example of using it is something like this: a:=StyleAttrNumb selector:'img' attr:'height' unit:'px'. a is:1000.
a is:100+ 700.
a is:a+50.
The is: method automatically updates the DOM.
For changes of the dom affecting the varriables, I use mutationObservers. (under construction) In the long run, I want to have component based programming. So if a component is a child of a bigger component and the attributes of the bigger component affect the smaller, i need to propagate the changes
from the attributes of the one to the other. ex. a small box inside a bigger box where the height of the bigger box changes. If you have any remarks on its implementation, I ll be happy to hear them. 2013/2/11 Nicolas Petton <[hidden email]>
Sincerely yours, Apostolis Xekoukoulotakis-- You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Free forum by Nabble | Edit this page |