Originally Posted by simon.hain
libraries are kind of like the accumulated knowledge of a developer. thus there will be no code here. some kind of open source library would sure make developing a lot easier, but i really doubt my company would pay me for it.
there are two approaches to create such a library:
- have a library (an extra jar/cod) that is installed seperately. i use this for my modified ksoap2, for example.
- have a seperate project and add the classes you need to your current project. i use this for my ui components, don't have to pay attention to backward compatibility this way, and no need to install an extra cod on the devices.
some components are really easy to develop, like a bitmapfield that acts like a button, and you can reuse them a lot.
there are also quite some non-ui things that reoccur in every second application, like network connectivity, webservices or certain options. develop modular and reuse.
thanks for ur suggestions, but what I am looking for is the suggestions of having an architecture of all the UI components i.e. our custom UiApplication extended class that is capable of using all our custom elements packaged with other utility custom elements.
Each of this element will be having its own controllers. e.g. lets say in terms of layouts, we build a complete architecture of all possible layout structures we might be needing like a table layout which is not present in JDE 4.2.1.
I dont want to use each custom control separately as that will be more like patching things up.
Any guesses how we can proceed with such an architecture.