Why so many Common Libraries?

[sub]

All I can give you is a maybe on that one. In theory PVRUiPublic.dll could be opened, but admitedly I'm not super fond of the idea. I dont want to get in a position where some people make plugins depending on different versions of it etc. I also dont really want other developers making changes in there.

If we really need another class library, I'd probably prefer it to be an extra dll covering new stuff. I could help by distributing the current version with each release though.

[JavaWiz]

I am totally open to the idea of making my source available. I find that I don't have time to add features that others have requested, so the help would be appreciated. What I don't want are several custom versions of the WizTools that would complicate things more than they already are.

What I am not sure of is how to manage the 'official' version. I have not ever worked on a true open source community developed project, so I am unsure as to how you manage other developers contributions.

• Who becomes the official traffic cop that decides what features make it in a particular version?
  
• Where does the official source code reside?
  
• How do we manage release versions of the code so that new features are readily available to developers and users?
  
• Who is responsible for testing and providing patches when new code 'breaks' some plugin or feature, or is not backward compatible?
  

I am sure there are dozens of other issues related to managing code like this that is common to several other code bases.

That said, if we can agree upon a process that address these issues (and the others that I have not listed...), I will gladly publish any code that would be helpful for others. In fact I have shared much of my source with folks who have requested it already.

[McBainUK]

I think the CommonGBPVRUtilities and GbpvrUiElements were class libraries these developers made back in the old GBPVR.exe days because the app didnt provide these higher level classes for developers to use in their plugins. That changed with the advent of PVRX2.exe

True, these libraires should not be used for new development work, the base PVRX2 UI classes and JavaWiz's rather excellent extensions are all that's needed now.

Suggestion that Libraries are separeted into functions.
CommonUILibrary.dll - for UI related stuff
CommonMetadataLibrary.dll - for internet and metadata download stuff
CommonInterfaceLibrary.dll - for interfacing hardware stuff

This sounds good - although as JavaWiz has said managing it is the real issue. Anyone with any experiacne of using sourceforge or similar? As a side note the internet/metadata download dll would be a personal favourite as quite a few plugins could take advantage of it.

If we really need another class library, I'd probably prefer it to be an extra dll covering new stuff. I could help by distributing the current version with each release though.

Sounds good.

May I suggest the common dlls be based on JavaWiz's work? As most developers are using that unless they're rolling their own...

[psycik]

code.google.com is ok, just need to run an svn client. But I don't remember any approval process as part of that to do a final release.

[herrmannj]

totally agree the spirit of sharing the code. I also vote for JavaWiz dlls as base. (excellent work).

I'm not experienced in sourceforge but i recently started to use it for the my undergoing wikipedia plugin and I found it useful and (relative) easy to use. there is support for svn based source code management, so its possible for different people to work on the same source code without interfering each other. Also it is possible to roll back unwanted changes.

One advantage of the JavaWiz dlls - they are very well documented. So I suggest one part of the wiki dedicated to that new common dlls, well document and with sample code how to used it. (take for example php.net to show how I would like to see it).

the dll _MUST_ be backward compatible. (!)

I suggest that people before adding new things to the common dlls they should (have to) start a threat in the forum, telling what they want to do, why and how. So there can be a discussion in terms of quality, compatibility, design-points and future enhancements.

So there can be also an process of deciding if the new thing/feature/whatever should be added to the common dlls or if the developer should put it in its own stuff (because its to special or whatever).

And last but not least:
- I vote for an cover flow style ui element to be added there. (and I'm willing to help writing it)

Joerg

[MixMan]

I'm happy to see the positive response from smart guys.
So my suggestion of one popup with one button was not a good start project. Now I have another suggestion.
Start with a CommonInterfaceLibrary DLL, I think cooperation and documentation methods would be found along the way.
It took Bekken 4-5 re-writes and many hours before he got keyboard input showing on the PCH right. Why not start with sample code for a NumPad SMS function with freetext seach "field" that would work with the PCH. The sample code could be built from Subs "Tiles" sample. I will make a button template in Photoshop.
Perhaps that could be a start of a grid that would result in an OnScreen Keyboard the Reven had in his plugins.....long ago.

Wouldn't it also be possible to implement GLP Open Source classes in these DLLs, if somebody finds good Classes and Samples on Code Project or SouceForge?

[herrmannj]

the wiz dlls inculde a sms style text entry box, although without buttons and some issues with german keyboard layout in none sms mode.

[MixMan]

the wiz dlls inculde a sms style text entry box, although without buttons and some issues with german keyboard layout in none sms mode.

Yes, I know, but having code and sample that would work with PCH and MVP would be good for a new programmer.

Just for fun I started to break down a phone into a NumPad grid wth separate buttons and changable display background. Things like this I do in Paint.NET, an easy to use program for everyone.
You can have the graphics i a day or so....for a modified Tiles plugin.

[herrmannj]

<quote>Yes, I know, but having code and sample that would work with PCH and MVP would be good for a new programmer.</quote>

full ack, although the wiz skeleton plugin provides source.

[MixMan]

I have made a Photoshop template for NumPad images....my first contribution.
Backgrounds can be changes easily. A script generates the images.
Does anyone want it for a NumPad project?