windows forms repeater

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

Im playing around with a little grid/repeater for windows forms
http://www.compona.com/repeateralpha1.zip

here is a short list of current features:

PanelRows , rows that behave like panels , where you can place controls
TableRows , like standard grid rows
TabRows , TabStrip container for child rows , each childrowtype will be
placed in a separate tab

ShowParentRows , feature to force parent rows to be visible for the first
visible row
this makes it possible to always see what data a row belongs to

no editing , selections , sorting or grouping is in place yet.

im currently working on xp and o2003 theme support.


need testers and feedback.
is it a good idea to be able to present data as the panelrows?
what features other than those listed would be good?

write to me at compona [at] gmail.com

//Roger
 
Since the source code was not included and your library was obfuscated I
didn't feel safe to run this piece of code.

I have no idea about how your code work right now, but I'll give you some
advice. If you are creating instances of a control for every data object then
you will run into a huge memory mess with more data. I recommend a grid
implementation. Where you can "plug in" your own custom renderers. Create an
instance of the control only if you are in edit mode. Take a look at
Syncfusion grid.
 
I am not creating multiple instances of each control ,
the entire control is rendered with gdi+
the controls are just used as templates in designtime and when editing

As for the safty of the code ,
its just as safe as for you to run our code as it is for you to run
syncfusions grid (and im sure they ofbuscate their code to).
we are a real company so privacy polices and more info can be found at
www.compona.com...

//Roger

Alex Korchemniy said:
Since the source code was not included and your library was obfuscated I
didn't feel safe to run this piece of code.

I have no idea about how your code work right now, but I'll give you some
advice. If you are creating instances of a control for every data object then
you will run into a huge memory mess with more data. I recommend a grid
implementation. Where you can "plug in" your own custom renderers. Create an
instance of the control only if you are in edit mode. Take a look at
Syncfusion grid.



Roger said:
Hi,

Im playing around with a little grid/repeater for windows forms
http://www.compona.com/repeateralpha1.zip

here is a short list of current features:

PanelRows , rows that behave like panels , where you can place controls
TableRows , like standard grid rows
TabRows , TabStrip container for child rows , each childrowtype will be
placed in a separate tab

ShowParentRows , feature to force parent rows to be visible for the first
visible row
this makes it possible to always see what data a row belongs to

no editing , selections , sorting or grouping is in place yet.

im currently working on xp and o2003 theme support.


need testers and feedback.
is it a good idea to be able to present data as the panelrows?
what features other than those listed would be good?

write to me at compona [at] gmail.com

//Roger
Click to expand...
Click to expand...
 
Its about trust. I can't just trust you just because you say that you're
trustworthy. You assembly isn't even strongly named.

Roger said:
I am not creating multiple instances of each control ,
the entire control is rendered with gdi+
the controls are just used as templates in designtime and when editing

As for the safty of the code ,
its just as safe as for you to run our code as it is for you to run
syncfusions grid (and im sure they ofbuscate their code to).
we are a real company so privacy polices and more info can be found at
www.compona.com...

//Roger

Alex Korchemniy said:
Since the source code was not included and your library was obfuscated I
didn't feel safe to run this piece of code.

I have no idea about how your code work right now, but I'll give you some
advice. If you are creating instances of a control for every data object then
you will run into a huge memory mess with more data. I recommend a grid
implementation. Where you can "plug in" your own custom renderers. Create an
instance of the control only if you are in edit mode. Take a look at
Syncfusion grid.



Roger said:
Hi,

Im playing around with a little grid/repeater for windows forms
http://www.compona.com/repeateralpha1.zip

here is a short list of current features:

PanelRows , rows that behave like panels , where you can place controls
TableRows , like standard grid rows
TabRows , TabStrip container for child rows , each childrowtype will be
placed in a separate tab

ShowParentRows , feature to force parent rows to be visible for the first
visible row
this makes it possible to always see what data a row belongs to

no editing , selections , sorting or grouping is in place yet.

im currently working on xp and o2003 theme support.


need testers and feedback.
is it a good idea to be able to present data as the panelrows?
what features other than those listed would be good?

write to me at compona [at] gmail.com

//Roger
Click to expand...
Click to expand...
Click to expand...
 
For those who might be interested in this kind of component but does not want
to run this untrusted code,
feel free to write to info [at] compona.com and verify that this post is valid
you can also visit componentsource.com to see that we are a real company and
not spreading harmful code and viruses...

so if this code was harmful in anyway , you know who to sue ;)

//Roger


Alex Korchemniy said:
Its about trust. I can't just trust you just because you say that you're
trustworthy. You assembly isn't even strongly named.

Roger said:
I am not creating multiple instances of each control ,
the entire control is rendered with gdi+
the controls are just used as templates in designtime and when editing

As for the safty of the code ,
its just as safe as for you to run our code as it is for you to run
syncfusions grid (and im sure they ofbuscate their code to).
we are a real company so privacy polices and more info can be found at
www.compona.com...

//Roger

Alex Korchemniy said:
Since the source code was not included and your library was obfuscated I
didn't feel safe to run this piece of code.

I have no idea about how your code work right now, but I'll give you some
advice. If you are creating instances of a control for every data object then
you will run into a huge memory mess with more data. I recommend a grid
implementation. Where you can "plug in" your own custom renderers. Create an
instance of the control only if you are in edit mode. Take a look at
Syncfusion grid.



:

Hi,

Im playing around with a little grid/repeater for windows forms
http://www.compona.com/repeateralpha1.zip

here is a short list of current features:

PanelRows , rows that behave like panels , where you can place controls
TableRows , like standard grid rows
TabRows , TabStrip container for child rows , each childrowtype will be
placed in a separate tab

ShowParentRows , feature to force parent rows to be visible for the first
visible row
this makes it possible to always see what data a row belongs to

no editing , selections , sorting or grouping is in place yet.

im currently working on xp and o2003 theme support.


need testers and feedback.
is it a good idea to be able to present data as the panelrows?
what features other than those listed would be good?

write to me at compona [at] gmail.com

//Roger
Click to expand...
Click to expand...
Click to expand...
 
Back
Top