Category:Development - Revision history

Yuhjyechang: /* Questions? */

2011-03-25T01:38:22Z

‎Questions?

Sambaker at 13:25, 14 March 2011

2011-03-14T13:25:40Z

Ablainey: /* General Feature Requests/Discussion */

2011-03-01T21:14:04Z

‎General Feature Requests/Discussion

Sambaker at 15:17, 1 March 2011

2011-03-01T15:17:02Z

Ablainey: /* GUI */

2011-03-01T11:10:48Z

‎GUI

Ablainey: /* Module Request */

2011-03-01T11:07:57Z

‎Module Request

Ablainey: /* General Feature Requests/Discussion */

2011-03-01T11:05:22Z

‎General Feature Requests/Discussion

Ablainey: /* General Feature Requests/Discussion */

2011-03-01T11:02:45Z

‎General Feature Requests/Discussion

Johannsen: /* Existing Feature Change/Improve */

2011-03-01T03:59:25Z

‎Existing Feature Change/Improve

Johannsen: /* Module Request */

2011-03-01T03:54:33Z

‎Module Request

← Older revision		Revision as of 01:38, 25 March 2011
Line 60:		Line 60:
	===Questions?===		===Questions?===
	*Joh, Yuh-Jye: Speaking of the cross-platform development, could you talk a little about the Java version of [[History \| Neat Software]], specifically what security restrictions prompted Java to be abandoned in favor of C++ and whether that reasoning would still applies to a future version of NeatTools? --[[User:Sambaker\|Sambaker]] 17:08, 27 February 2011 (PST)		*Joh, Yuh-Jye: Speaking of the cross-platform development, could you talk a little about the Java version of [[History \| Neat Software]], specifically what security restrictions prompted Java to be abandoned in favor of C++ and whether that reasoning would still applies to a future version of NeatTools? --[[User:Sambaker\|Sambaker]] 17:08, 27 February 2011 (PST)
		+	I will let JoJo to answer this question for you. But, according to my understanding, at least the mouse/keyboard handler that intercept the global mouse/keyboard events was not possible in Java unless JNI Native C code is used. Once JNI is used, then the Java code will build on dependency on this piece of native code and become non-cross platform. [[User:Yuhjyechang\|Yuhjyechang]] 18:38, 24 March 2011 (PDT)

@@ Line 5: / Line 5: @@
 How do you sign a comment? -- PDG
 Type four (4) tildes "~" in a row or press the signature button (second from the right) --[[User:Sambaker|Sambaker]] 08:32, 19 February 2011 (PST)
 ===General Dev. Discussion===
@@ Line 17: / Line 16: @@
 **I already make communication between nrattools too complicated by make it ack the on be half of receiving side. So the sender and receiving side can negotiate a rate that is acceptable for both of them. Now there is one more thing to make it even more complicated, that is communicate the data type or aggregate data structure between them... Let user create new data type out of aggregate data structure is one thing that is missing in NeatTools. We really need to include it in the next version.--[[User:Yuhjyechang|Yuhjyechang]]
 ===General Feature Requests/Discussion===

@@ Line 29: / Line 29: @@
 *More control over links! like the ability to make specific links un-editable to stop accidental deletion, rather than all editable on/off. [[User:Ablainey|Ablainey]] 03:02, 1 March 2011 (PST)
 *Can't believe I forgot this one: and undo button.[[User:Sambaker|Sambaker]] 07:17, 1 March 2011 (PST)
 ===Module Request===

@@ Line 27: / Line 27: @@
 **For text representation of NTL, there's only two things to represent: links between modules and module properties. "instance output => instance input" and "instance property = value" Anything else? --[[User:Johannsen|Johannsen]]
 ***That sounds about right. However, don't the linkages have to specify which input or output they are connected to? Links might need properties too (color, type, etc.).--[[User:Pdgelling|Pdgelling]]
-****More control over links! like the ability to make specific links un-editable to stop accidental deletion, rather than all editable on/off. [[User:Ablainey|Ablainey]] 03:02, 1 March 2011 (PST)
+*More control over links! like the ability to make specific links un-editable to stop accidental deletion, rather than all editable on/off. [[User:Ablainey|Ablainey]] 03:02, 1 March 2011 (PST)
 ===Module Request===
 *A scripted module, that would allow in-program customization of a module's function with javascript or python. --[[User:Sambaker|Sambaker]] 08:36, 19 February 2011 (PST)
 **Suppose there were a module that allowed this, where you could connect some inputs (say, X and Y), and and there was an output (say Z).  The scripted module really should have the inputs and outputs available as variables.  So, for example, you could have the module code just be Z = X + Y.  Sounds simple, but with neattools, you'd also have to decide when to execute this.  I'm not so clear on that.  It seems that the "when to execute" needs to be specified independent of the code and inputs and outputs.  --[[User:Johannsen|Johannsen]] 19:54, 28 February 2011 (PST)
 *this module I want sounds really really stupid, which is usually a good sign. Its a module that does absolutely nothing, it has minimal properties that would probably be in module base class (like name), and it takes any number of inputs and outputs. Here's what it would be good for: requires extension points to be useful,is a specification, allows the abstract nodes to be be isolated for a test specification (the "test space")--[[User:Johannsen|Johannsen]]
 **Hmm... I don't quite get what you mean. But, there is one container module in NeatTools that does nothing and can have any number of input and output. Is that what you are thinking about, or its something else?--[[User:Yuhjyechang|Yuhjyechang]]
 ***That might be the one I'll check it out. I'm looking at from point of view of making neattools more like an IDE, so it would support new module definition within IDE and the extension would be very limited. For example being able to define a "plus" module by drawing two inputs, one output, and limiting extension code to implementing an interface. Being able to define test data before implementing would be a really nice feature.--[[User:Johannsen|Johannsen]]
 *Video module would be nice. Supporting different common filetypes.[[User:Ablainey|Ablainey]] 03:07, 1 March 2011 (PST)
@@ Line 40: / Line 43: @@
 *The socket modules on the current NeatTools have been the biggest impediment to integrating with Flash. Flash's potential as a visualization tool (including 3D) as well as GUI/Front End is something I'd really like to explore more. [[User:Sambaker|Sambaker]] 17:08, 27 February 2011 (PST)
 **Sam, what are some good examples of external programs feeding data into Flash?--[[User:Johannsen|Johannsen]] 19:59, 28 February 2011 (PST)
 **I agree with Sam. In the new NeatTools, we should provide the socket as dumb pipe. On top of that, we can build up the notion of Channels, Objects, or encryption layer.--[[User:Yuhjyechang|Yuhjyechang]]
 **The previous NeatTools design over the socket is that: In order to address the issue of matching the speed between the consumer and producer when dealing with Audio/Video or other type of packet of data that need feedback acknowledgment to adjust the rate of communication in both ends. The protocol become too complicate and confusing for simple communication with regular event with object data. In stead of making it the default protocol, we should just separate it into an protocol object cascade with socket object to handle this special case. --[[User:Yuhjyechang|Yuhjyechang]]

@@ Line 49: / Line 49: @@
 **I think that its possible to create a 3D interface using multi-touch that is immersive and intuitive. But, its not automatic. We probably need to put some thoughts on that front. For mouse and keyboard, I think its very hard to make it intuitive. What do you think?--[[User:Yuhjyechang|Yuhjyechang]]
 **It seems to me that the 3D aspect of NeatTools needs to serve a purpose, either making something easier to use or easier to visualize, but be optional, or at least limited if so desired. For example, a "legacy mode" which while still 3D would be more like 2.5D, basically it would look and function similarly to the current NeatTools for systems where 3D would be more cumbersome.[[User:Sambaker|Sambaker]] 17:08, 27 February 2011 (PST)
 ===Questions?===
 *Joh, Yuh-Jye: Speaking of the cross-platform development, could you talk a little about the Java version of [[History | Neat Software]], specifically what security restrictions prompted Java to be abandoned in favor of C++ and whether that reasoning would still applies to a future version of NeatTools? --[[User:Sambaker|Sambaker]] 17:08, 27 February 2011 (PST)