Messaging system end-user node based building interface

Question

0.00/5 (No votes)

See more:

I am working on building a messaging system that will give the end-user the ability to create interfaces to send messages via text, web service, or simple FTP a message in a file. To attempt to build an intuitive interface for the end-user to create their own message interface I am leaning on using some kind of node system such as the function editor in Vue here ( http://www.e-onsoftware.com/wiki/Vue/index.php/File:Functioneditor-1.png[^] )

Or the nodes system in World machine http://www.world-machine.com/about.php?page=latest[^]

Do anyone know of a resource, source codem, examples I can be pointed to?

I thought about WPF and building the nodes in photoshop then displaying on a drag and drop toolbar to build a node linked list where each node has its own properties. I noticed unreal has a similar interface in developing games now called blueprints. ( http://www.youtube.com/watch?v=cRhWc2kAhqI&list=PLZlv_N0_O1gaCL2XjKluO7N2Pmmw9pvhE&index=24[^] )

Thanks of any assistance...

Posted 6-Oct-14 4:13am

Robert Wayne

Add a Solution

Comments

BillWoodruff 6-Oct-14 10:54am

Interesting idea, if vague. You might consider describing what a node might be in such a system, and how it might be used.

Sergey Alexandrovich Kryukov 6-Oct-14 12:33pm

Frankly, I personally see nothing but familiarity with some existing products and the itch to utilize them. Doesn't just one phrase, "about WPF and building the nodes in photoshop", tell the tale?

Also, I cannot see the understanding of separation of concerns. Data structure is one thing, its serialization is something different, other aspects are transport protocols, content-type, possibly the data container, and then some logic like event or data flow, push, pull, etc.

Note that the question is not about the particular message interfaces, but "the end-user the ability to create interfaces". That should come with description of the class of all possible interfaces, or at least with the representative example of a couple of different interfaces, to illustrate the prospective interface diversity.

I cannot say for sure OP does not have an interesting idea. He might have it, but nothing is expressed here. So far, this is a talking about nothing.

—SA

Robert Wayne 7-Oct-14 3:08am

Thanks for each of your insights and vague this may be. I was expecting you guru's to read my mind I suppose. I shall describe more of what I am looking for later today in the hope of receiving guidance to after I come off my hydrocodone and after I can think more clearly. Kidney stones no fun... :(

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KarstenK · Answer 1 · 2014-10-06T06:14:00

Solution 1

Your biggest problem is portability. Take a look at Xamarin which offers a developer solution which easily can prdouce software for many platform.

Use an internet standard service like sockets or ftp for transport, so it can get easily adopted.

Posted 6-Oct-14 6:14am

KarstenK

Comments

Sergey Alexandrovich Kryukov 6-Oct-14 12:37pm

I would understand it if you mentioned CLR. The implementation covering big part of it would be .NET + Mono + Xamarin. Xamarin only covers a limited set of platforms. Anyway, I cannot be sure that this all is relative, because the "question" is too vague. You way to address the platform compatibility issue, otherwise maybe very reasonable, just could not bring life to something so uncertain. Please see the comments to the question.
—SA

KarstenK 7-Oct-14 1:58am

You overlooked my second sentance :-O

Sergey Alexandrovich Kryukov 7-Oct-14 2:21am

Which one? "Take a look at Xamarin..."?
—SA

KarstenK 7-Oct-14 2:29am

Upps. It is the third :-O

Sergey Alexandrovich Kryukov 7-Oct-14 2:39am

No, I did not overlook it, and agree: a good point.
—SA