|
From: Jarek C. <jar...@po...> - 2012-01-10 20:32:41
|
I inserted an example section. The problem is that I am too fresh to know the pitfalls, but I believe there are things one should do with special care, not to get in troubles. I hope that if someone discovers such a thing, especially if it is not well documented, he will mention it in wiki. I know it's easy to meet troubles if one doesn't appropriately handle threading issues. Is it correct what I put in wiki? Make corrections if you wish, as always with wiki contents. I put a watch on all articles and will get notification emails on contents change. Jarek W dniu 01/10/2012 12:30 PM, Shlomy Reinstein pisze: > Can you provide an explanation / example of what you mean by "api > common pitfalls"? It would be useful to start with something (maybe > just fill in one or two items) > > Thanks, > Shlomy > > On Tue, Jan 10, 2012 at 9:57 AM, Jarek Czekalski > <jar...@po... <mailto:jar...@po...>> wrote: > > If you know about any, please update our wiki article: > https://sourceforge.net/apps/mediawiki/jedit/index.php?title=JEdit_api_common_pitfalls > > At this time it is empty and only admins have access to edit the wiki. > If someone else is interested in writing, please let me know. > > By the way: creating a "broken" link and following it is the best > way to > create a new wiki article. > > Jarek > > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. > Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. > appdeveloper.intel.com/join <http://appdeveloper.intel.com/join> > http://p.sf.net/sfu/intel-appdev > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > <mailto:jEd...@li...> > https://lists.sourceforge.net/lists/listinfo/jedit-devel > > |