Hi Al I don't have any formal guidelines. Well I didn't until you asked:
1. The app/stack should show how LiveCode has been used to do something useful for the author or users. (This really rules out IDE plug-ins and Library stacks). 2. There should be a screenshot of the app. 3. Some notes about the app. Regards Peter http://LiveCode1001.blogspot.com On 25 May 2013, at 10:21, Alejandro Tejada wrote: > Hi Peter, > > > Peter W A Wood wrote >> If anybody else reading this message has any interesting that >> they've developed in LiveCode, I'd really appreciate being able >> to include it in 1001 things to do with LiveCode. > > Did you published the guidelines about the exact information > that you require to include reviews of stacks or applications > in the site 1001 things to do with LiveCode? > > A pdf download would be fine. :) > > Al > > > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/1001-things-to-do-with-LiveCode-tp4662960p4665420.html > Sent from the Revolution - User mailing list archive at Nabble.com. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
