What do you want to contribute?

[Mike Kerner]

I can think of a pile of things:
1) Script editor (for those of us keeping score, there are at least three
other script editors for LC, so hopefully Jerry will be involved).  All of
them improve various things in LC.  Here are some things I think should be
done:
     a) Version Control
     b) Code Blocks
     c) Custom color schemes
     d) Code Collapse
     e) More breakpoint modes
2) Puny but so, so annoying:  built-in method to switch between the run and
edit modes - remember command-tab?  I know that's not an option but...
3) Parser improvement and compiler directives - I LOVE the dynamic typing
and the like - compilers should adapt to us, not the other way around, BUT
sometimes, there are typos and it would be nice to be able to find them
more easily.  Sometimes some datatype and scope enforcement would be good,
too - if nothing else we should be able to do reporting to see what's going
on.
4) NATIVE CONTROLS ON MOBILE and an easier way to do cross-platform mobile
development
5) A language committee.  There are things in the language that should be
addressed, and there are going to be times when the language needs to be
expanded.
6) Better properties palettes and editors.
7) Built-in externals store - I need something, it should be trivial to
find it and buy it.  I really don't care if some add-on costs me more
money.  That's fine.  I would like it to be a lot simpler to find it.
8) More bootstrapping - If the IDE is all written in LC, awesome - it makes
perfect sense for a tool to be written in the language that the developers
that use the tool use.  More is better.  The kernel, for lack of a better
word, can be in something lower-level, but the things we use every day
would be way better if they were all open and we as a group could make them
better.

That's my first list of things I would want to work on.

It might also go without saying, but some sort of list like that as a base
promise would be far more interesting to me than the diagrams I've seen of
re-engineering the code as I've seen it so far.  Perhaps I don't understand
the underlying architecture, or, maybe it hasn't been laid out for all of
us well enough, yet.


On Wed, Feb 13, 2013 at 3:38 PM, Monte Goulding <monte at sweattechnologies.com
> wrote:

> One of the things I thought might get people excited about LiveCode going
> open source is a thread about what different people are keen to contribute
> to the engine. There isn't a heap of low level language developers using
> LiveCode but there are enough that I think we could come up with a decent
> list for the engine. But also the IDE will be GPL too so what do you want
> to contribute there. None of us knows the feasibility of these things right
> now so consider it a pre-feasabilty hit list:
>
> Planned Open Source Contributions
> - Mobile sockets - engine (Monte)
> - Nested behaviors so you can set the behavior of a behavior (Monte)
> - Getting the long id of an icon/pattern given the context of the object
> it's applied to (Monte)
> - VCS integration into the IDE most likely focussed on git & mercurial
> (Monte)
>
> Please respond with the whole list so we can keep track. You can add your
> name to someone else's thing if you want to help them.
>
> --
> Monte Goulding
>
> M E R Goulding - software development services
> mergExt - There's an external for that!
>
>
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."