[NTLK] Einstein "Workshop" extension

[Steven Frank]

The advantage to Workshop seems like it would be potentially much faster round-tripping packages through Einstein, shortening the edit/transfer/debug dev cycle...?  But NTX's compatibility with existing projects is important for software preservation.  So it feels like both are important.

Cross-platform is always such a huge challenge.  Einstein is really portable, although the Windows build has been broken for years and you get a nicer looking Monitor on a Mac.  On the other hand, native UIs are always superior to cross-platform frameworks.  The eternal dilemma.  :(

For my part, I'm always happy to help with Obj-C / Cocoa / Mac UI questions you may have.  That's the domain I have the most experience with.

Steven


> On Mar 3, 2017, at 7:03 AM, Matthias Melcher <mm at matthiasm.com> wrote:
> 
> 
>> On Mar 3, 2017, at 12:17 PM, Simon Bell <simonbell at me.com> wrote:
>> 
>> 
>>> On 2 Mar 2017, at 23:06, Matthias Melcher <mm at matthiasm.com> wrote:
>>> 
>>> I am in the process of adding a NewtonScript developer environment into Einstein.
>> 
>> You do know about NTX, right?  <https://www.newtonresearch.org/toolkit/>
> 
> Now that you mention it, I do remember. Hmmm, not sure if your NTX triggered my Workshop or if both our projects were triggered by the same need.
> 
> What I don;t like about either approach is the limitation of macOS X. I always tried to support Linux and MSWindows as well. Here, learning Cocoa and ObjectiveC is a huge pain ITA. Qt would be a different beast, and my old FLTK as a base GUI is quite outdated.
> 
> Either way, what do you suggest we do? Continue NTX, continue Workshop, continue both? Continue together? At least with serial port support on Einstein now, NTX would probably work with very little modification.
> 
> - Matthias
> ----------------------------------------------------------------------
> 
> http://newtontalk.net/
> http://twitter.com/newtontalk