1
votes

I've been trying to work with Codename One for years, but I still find errors that prevent me from releasing my apps.

Locally I can fix errors by I overshadowing erroneous classes. This works but for some reason it doesn't work when I send my apps to the build server.

If I could overshadow faulty classes would be good in many ways:

  1. I'd better get on with my work
  2. I could check how my corrections work on the different platforms
  3. I could contribute to the further development of Codename One

I suffer much from not being able to publish my apps because I see no way how I can fix basic problems.

I love iPhones and do not like the Mac. Therefore I do not own a Mac and prefer to work with Linux and use the Codename One build server.

What are the reasons for not supporting overloading classes like com.codename1.ui.Component? Can You see that it would be beneficial?

1

1 Answers

0
votes

This isn't the first time people asked for that but we won't deliver it. Doing this creates huge problems:

  • Developers don't file issues or submit fixes instead they make local fixes
  • Developers break things due to complex behaviors then try to get support and blame us for the issues

We have a process of submitting patches to Codename One, patches are always accepted quickly when they are valid. If something needs fixing that's what you need to do. If you need a hack then submit a patch that defines the extension point that you need. That's why we are open source...

In the past this might have been painful as you would need to wait until we updated the servers, but since changes go in every week in recent revisions this is no longer an issue. Don't think of it as "contributing", think of it as free code reviews where the entire community pulls together to improve your work...