I'm pondering some improvements to my application, and they will
involve some components that might be useful to others, and perhaps
others could improve and share their improvements. I wonder therefore
if putting some components on somewhere like BitBucket or Github would
make sense, but it raises some issues that need to be discussed with
others, and one for Tim.

First off, I am pondering a "tab" control, which is exactly the same as
the page control but doesn't have pages. And then a "mini-tab" control
which is designed to be minimally sized tabs. But the obvious way for
me to make it would be to take the EWB library code and hack it to fit,
rather like I have with a "FormList" control. The key then is if it is
okay to "publish" this source for others to use, given the derived
nature of it. I think that every component I make would be based on an
EWB one, and modified to varying degrees. Is Elevate Software okay with
this?

Assuming it is okay, I then wonder whether one big repository of
components is the right way to go, or one repo per component. And I
sort of assume that each component would definitely go in a separate
directory, so if you wanted the tab component you could add it without
using the mini-tab, formlist, and bananawidget that I might come up
with. The Library option appears to be okay with multiple paths, so one
per component. It might at some point be handy to have an "include
subdirectories" option, so all could be included in a single path.

The whole purpose of this is to make it easier not only to share (which
we have done by posting zips here), but to share fixes. I'm sort of new
to Git, so never done a pull request, but it seems that EWB is mature
enough that components will become more popular.

Thoughts? Things I missed?

It's a great idea. One repository to share and improve components for EWB.
This way we'll have some examples of components to learn from too.
This will make EWB even more popular I think.

Looking forward to see the first component(s).

"Matthew Jones" wrote:

I'm pondering some improvements to my application, and they will
involve some components that might be useful to others, and perhaps
others could improve and share their improvements. I wonder therefore
if putting some components on somewhere like BitBucket or Github would
make sense, but it raises some issues that need to be discussed with
others, and one for Tim.

First off, I am pondering a "tab" control, which is exactly the same as
the page control but doesn't have pages. And then a "mini-tab" control
which is designed to be minimally sized tabs. But the obvious way for
me to make it would be to take the EWB library code and hack it to fit,
rather like I have with a "FormList" control. The key then is if it is
okay to "publish" this source for others to use, given the derived
nature of it. I think that every component I make would be based on an
EWB one, and modified to varying degrees. Is Elevate Software okay with
this?

Assuming it is okay, I then wonder whether one big repository of
components is the right way to go, or one repo per component. And I
sort of assume that each component would definitely go in a separate
directory, so if you wanted the tab component you could add it without
using the mini-tab, formlist, and bananawidget that I might come up
with. The Library option appears to be okay with multiple paths, so one
per component. It might at some point be handy to have an "include
subdirectories" option, so all could be included in a single path.

The whole purpose of this is to make it easier not only to share (which
we have done by posting zips here), but to share fixes. I'm sort of new
to Git, so never done a pull request, but it seems that EWB is mature
enough that components will become more popular.

Thoughts? Things I missed?

Matthew,

<< Is Elevate Software okay with this? >>

Absolutely.  We would love to see more 3rd party controls/components, especially since that was one of the primary motivations for the rewrite from EWB 1.x to EWB 2.x, and you're always welcome to use our source code as the template for further enhancements/changes.  Just try to report changes that require modifications to the base source code (TControl, for instance) back to me so that I can try to integrate them into the base source.  I can't say that I will implement 100% of all requested changes, but I'll try to do so as long as the don't violate the intended design or cause other problems.

Tim Young
Elevate Software
www.elevatesoft.com

This is much needed me thinks. I have done a desktop app to manage datsets and a component that I am sure is lost in the forum.

A more central way and listing would be perfect and certainly improve the EWB ecosystem for sure!

Any news on this project ?

Luk wrote:

> Any news on this project ?

Not from me - I'm swamped and late on the project I'm doing. Things are
a little in flux too, but that shouldn't stop anyone kicking things off
somehow.

Luk wrote:
<< Any news on this project ? >>

https://github.com/pascalnetwork/L27ButtonComboBox

Moments ago I created a GitHub repository for the following component.

Free EWB Component: L27ButtonComboBox
------------------------------------------------------------------
Description:
A data enabled ButtonComboBox component for use in Elevate Web Builder 2

This demo creates a sample DataSet at Run-Time in the FormCreate event.

You would normally create it at Design-Time by dropping a dataset from the DataSet Manager and define the component properties there.

Enjoy!