PDA

View Full Version : Visible Obect Wish List



Garret Mott
17-Nov-2005, 10:28 PM
Hi All -

I'm tired of working on a project, so in the spirit of work avoidance, I
thought I'd toss out some things I'd like to see. Some of 'em (most?) may
have already been mentioned. I also know that some are available in 3rd
party packages, etc. but I'd like to see 'em all in "native" VDF.

This focuses on visual tools - not the studio, but what it contains. These
are in no particular order & I'm not asking for much here..................

I'm also hoping others will add to & comment on this list!


- Fonts throughout the studio: Use fonts & size + bold, italic, underline -
eliminate fontweight style i.e. have properties to set: Arial, 10, Bold -
like other languages & the RichEdit.


PictureContainer (i.e. BitmapContiner)

- allow all common types - jpg, gif, etc.


dbGrids

- Using Scrollbars should not set current record or take focus - should just
scroll the grid

- Easy to identify cells & rows (i.e. Get Value of Current_Cell, Get Value
of Current_Row Item 2, etc.)

- TextColor, Color, Fonts, etc. all set by cell, row or column or any
combination of 'em. Have cell setting override column or row.

- Checkbox, comboform & edit (including richedit - via a popup edit box) in
any cell: Set CellCheckBox Row 3 Col 3 to True

- Multiple row records

- Multi-Select of row, column or cells

- Simple export, addressing & deletion of above selection

- Picture support in cells - all formats, not just bitmaps

- Formattable headers - incl. font, colors, multi row & pictures

- Insert Row (as David Martinko recently did for current dbgrid), but set by
property (i.e. pbAllowInsert=True/False)

- Sort by clicking header - including Excel type - where just one column can
be changed (OK, this is pushing it;-)

- Expression Cells:
If (Towing.Vehicle_Freight="V") Set Value to Towing.Make
Else Set Value to Towing.Product

+ Calculated cells


Buttons

- Allow setting of Color & TextColor, Fonts, multiple lines


All Labels (forms, comboforms, groups etc.)

- Allow TextColor, Fonts, multiple lines


TextBoxes

- Allow TextColor, Fonts, multiple lines


ProgressBar

- Show Percentage and # done of # capability

Mark Rutherford
18-Nov-2005, 12:25 AM
Ditto!
If I say ditto more does it count as more votes? <grin>

I started using cWindowsEx to gain a lot more functionality, and
im sure the reasoning is that if cWindowsEx exists, they wont do it
because its there.

I think what your asking for exist in most other
languages/toolkits/widgetsets/classes, ect.

I have asked for some stuff like this before an I think, in all honesty
it falls on deaf ears sometimes.

The sad thing is that I read all too much that people are migrating off
VDF, and I think it has good potential.

What got me to like it, and not toss it out when I saw it:
The ability to drag fields onto a form...

This ability is like no other.... but it does not make up for the lack
of other functionality.

picturecontainer: would love it. I recall this question asked one year
in MMISL and I recall (I hope correectly) Stephen's response:
'Absolutely not'
If I recall, DAW .... LibPNG is open source.. :) jpg, gif .. well I can
see the snafu there.

This really cant be THAT hard to add. (png support)

I have asked for easier to get at rows/cells before in grids/dbgrids.


My request: how about threading? I cant stand the 'app locking up' look
when your doing something intensive.
this usually makes progress bars totally useless.

sockets would be nice, this way I dont have to write stupid DLLs to do
that task (admittedly sockets is a bit much :P)

Basically, I have the same gripes.
One thing to note, once people start using .net or delphi, or c, they
dont usually go back to VDF. once they are gone, you pretty much lose them.
There are people here that are dissapearing.

LAST THING: allow people to distribute the runtime with their app
without having to install it seperately. (meaning the DLLs)
its retarded but admittedly minor by comparison.


I WISH TOO, like Garret :)

Garret Mott wrote:
> Hi All -
>
> I'm tired of working on a project, so in the spirit of work avoidance, I
> thought I'd toss out some things I'd like to see. Some of 'em (most?) may
> have already been mentioned. I also know that some are available in 3rd
> party packages, etc. but I'd like to see 'em all in "native" VDF.
>
> This focuses on visual tools - not the studio, but what it contains. These
> are in no particular order & I'm not asking for much here..................
>
> I'm also hoping others will add to & comment on this list!
>
>
> - Fonts throughout the studio: Use fonts & size + bold, italic, underline -
> eliminate fontweight style i.e. have properties to set: Arial, 10, Bold -
> like other languages & the RichEdit.
>
>
> PictureContainer (i.e. BitmapContiner)
>
> - allow all common types - jpg, gif, etc.
>
>
> dbGrids
>
> - Using Scrollbars should not set current record or take focus - should just
> scroll the grid
>
> - Easy to identify cells & rows (i.e. Get Value of Current_Cell, Get Value
> of Current_Row Item 2, etc.)
>
> - TextColor, Color, Fonts, etc. all set by cell, row or column or any
> combination of 'em. Have cell setting override column or row.
>
> - Checkbox, comboform & edit (including richedit - via a popup edit box) in
> any cell: Set CellCheckBox Row 3 Col 3 to True
>
> - Multiple row records
>
> - Multi-Select of row, column or cells
>
> - Simple export, addressing & deletion of above selection
>
> - Picture support in cells - all formats, not just bitmaps
>
> - Formattable headers - incl. font, colors, multi row & pictures
>
> - Insert Row (as David Martinko recently did for current dbgrid), but set by
> property (i.e. pbAllowInsert=True/False)
>
> - Sort by clicking header - including Excel type - where just one column can
> be changed (OK, this is pushing it;-)
>
> - Expression Cells:
> If (Towing.Vehicle_Freight="V") Set Value to Towing.Make
> Else Set Value to Towing.Product
>
> + Calculated cells
>
>
> Buttons
>
> - Allow setting of Color & TextColor, Fonts, multiple lines
>
>
> All Labels (forms, comboforms, groups etc.)
>
> - Allow TextColor, Fonts, multiple lines
>
>
> TextBoxes
>
> - Allow TextColor, Fonts, multiple lines
>
>
> ProgressBar
>
> - Show Percentage and # done of # capability
>
>

Holger W.
18-Nov-2005, 02:24 AM
I think you are talking about VDF 27 or later versions (vbg) ???

regards
Holger

Mark Rutherford
18-Nov-2005, 09:20 AM
What is that? like .. 8 years or something? :D

Holger W. wrote:
> I think you are talking about VDF 27 or later versions (vbg) ???
>
> regards
> Holger
>
>

Garret Mott
18-Nov-2005, 09:36 AM
27-11=16, so I'm guessing 2021 or so. It'll be unlikely (as SWM said) that
I'll be terribly interested at that point!

<g>

"Mark Rutherford" <mark@maunzelectronics.com> wrote in message
news:m1zv5sE7FHA.2168@dacmail.dataaccess.com...
> What is that? like .. 8 years or something? :D
>
> Holger W. wrote:
>> I think you are talking about VDF 27 or later versions (vbg) ???
>>
>> regards
>> Holger
>>

Nick Wright
19-Nov-2005, 04:09 PM
Ditto Also,

I think though that DAW is working on a new studio for version 12 - because
the most important thing for our Clients is that we as developers have some
fun tools to play with, the fact that we can't deliver to them things they
understand to be Standard these days is unimportant. (sorry to be so
flippant but I'm just working off some frustration)

I love working with vdf, and wish to continue to do so but when my boss
tells me to do something and I can't - not because of my own lack of
programming knowledge but rather because of some fundamental inner workings
of VDF which is based on a product model devised some twenty years ago - he
is simply going to tell me to find a solution, and I, like many others will
in find a solution in another language, and that's the thin end of the
wedge.

Let's face it VDF is a great tool to work with, we all use it because at
some point it filled a need and was the best solution to our problems, we
are all I think very loyal to vdf, but just lately I feel a shift in
attitudes. Maybe if DAW asked developers what are the most important
developer needs by way of a survey, then published the findings, then acted
on those findings we would not feel so kept-in-the-dark.

I'm not getting at DAW, despite what I have already said I think it is still
a great product with great potential, but I am also aware that without
subscriptions the resources will not be available to develop the product
further, without further development subscriptions will be lost (this is the
root of my frustration).

Can DAW give us some sort of roadmap of development? I see an earlier reply
to this post speculated on some 16 years before the little suggestions were
implemented, I know that was tongue-in-cheek, but it gives an honest
feeling.

Nick




"Mark Rutherford" <mark@freequest.net> wrote in message
news:kSmb3AA7FHA.4000@dacmail.dataaccess.com...
> Ditto!
> If I say ditto more does it count as more votes? <grin>
>
> I started using cWindowsEx to gain a lot more functionality, and
> im sure the reasoning is that if cWindowsEx exists, they wont do it
> because its there.
>
> I think what your asking for exist in most other
> languages/toolkits/widgetsets/classes, ect.
>
> I have asked for some stuff like this before an I think, in all honesty it
> falls on deaf ears sometimes.
>
> The sad thing is that I read all too much that people are migrating off
> VDF, and I think it has good potential.
>
> What got me to like it, and not toss it out when I saw it:
> The ability to drag fields onto a form...
>
> This ability is like no other.... but it does not make up for the lack of
> other functionality.
>
> picturecontainer: would love it. I recall this question asked one year in
> MMISL and I recall (I hope correectly) Stephen's response: 'Absolutely
> not'
> If I recall, DAW .... LibPNG is open source.. :) jpg, gif .. well I can
> see the snafu there.
>
> This really cant be THAT hard to add. (png support)
>
> I have asked for easier to get at rows/cells before in grids/dbgrids.
>
>
> My request: how about threading? I cant stand the 'app locking up' look
> when your doing something intensive.
> this usually makes progress bars totally useless.
>
> sockets would be nice, this way I dont have to write stupid DLLs to do
> that task (admittedly sockets is a bit much :P)
>
> Basically, I have the same gripes.
> One thing to note, once people start using .net or delphi, or c, they dont
> usually go back to VDF. once they are gone, you pretty much lose them.
> There are people here that are dissapearing.
>
> LAST THING: allow people to distribute the runtime with their app without
> having to install it seperately. (meaning the DLLs)
> its retarded but admittedly minor by comparison.
>
>
> I WISH TOO, like Garret :)
>
> Garret Mott wrote:
>> Hi All -
>>
>> I'm tired of working on a project, so in the spirit of work avoidance, I
>> thought I'd toss out some things I'd like to see. Some of 'em (most?)
>> may have already been mentioned. I also know that some are available in
>> 3rd party packages, etc. but I'd like to see 'em all in "native" VDF.
>>
>> This focuses on visual tools - not the studio, but what it contains.
>> These are in no particular order & I'm not asking for much
>> here..................
>>
>> I'm also hoping others will add to & comment on this list!
>>
>>
>> - Fonts throughout the studio: Use fonts & size + bold, italic,
>> underline - eliminate fontweight style i.e. have properties to set:
>> Arial, 10, Bold - like other languages & the RichEdit.
>>
>>
>> PictureContainer (i.e. BitmapContiner)
>>
>> - allow all common types - jpg, gif, etc.
>>
>>
>> dbGrids
>>
>> - Using Scrollbars should not set current record or take focus - should
>> just scroll the grid
>>
>> - Easy to identify cells & rows (i.e. Get Value of Current_Cell, Get
>> Value of Current_Row Item 2, etc.)
>>
>> - TextColor, Color, Fonts, etc. all set by cell, row or column or any
>> combination of 'em. Have cell setting override column or row.
>>
>> - Checkbox, comboform & edit (including richedit - via a popup edit box)
>> in any cell: Set CellCheckBox Row 3 Col 3 to True
>>
>> - Multiple row records
>>
>> - Multi-Select of row, column or cells
>>
>> - Simple export, addressing & deletion of above selection
>>
>> - Picture support in cells - all formats, not just bitmaps
>>
>> - Formattable headers - incl. font, colors, multi row & pictures
>>
>> - Insert Row (as David Martinko recently did for current dbgrid), but set
>> by property (i.e. pbAllowInsert=True/False)
>>
>> - Sort by clicking header - including Excel type - where just one column
>> can be changed (OK, this is pushing it;-)
>>
>> - Expression Cells:
>> If (Towing.Vehicle_Freight="V") Set Value to Towing.Make
>> Else Set Value to Towing.Product
>>
>> + Calculated cells
>>
>>
>> Buttons
>>
>> - Allow setting of Color & TextColor, Fonts, multiple lines
>>
>>
>> All Labels (forms, comboforms, groups etc.)
>>
>> - Allow TextColor, Fonts, multiple lines
>>
>>
>> TextBoxes
>>
>> - Allow TextColor, Fonts, multiple lines
>>
>>
>> ProgressBar
>>
>> - Show Percentage and # done of # capability
>>

Garret Mott
19-Nov-2005, 04:20 PM
Nicely put, Nick!

I'll add my ditto to this... Hmmm, we're starting to add up some dittos!

Best,

Garret


"Nick Wright" <n.b.wright@btopenworld.com> wrote in message
news:$G0s11U7FHA.3872@dacmail.dataaccess.com...
> Ditto Also,
>
> I think though that DAW is working on a new studio for version 12 -
> because the most important thing for our Clients is that we as developers
> have some fun tools to play with, the fact that we can't deliver to them
> things they understand to be Standard these days is unimportant. (sorry to
> be so flippant but I'm just working off some frustration)
>
> I love working with vdf, and wish to continue to do so but when my boss
> tells me to do something and I can't - not because of my own lack of
> programming knowledge but rather because of some fundamental inner
> workings of VDF which is based on a product model devised some twenty
> years ago - he is simply going to tell me to find a solution, and I, like
> many others will in find a solution in another language, and that's the
> thin end of the wedge.
>
> Let's face it VDF is a great tool to work with, we all use it because at
> some point it filled a need and was the best solution to our problems, we
> are all I think very loyal to vdf, but just lately I feel a shift in
> attitudes. Maybe if DAW asked developers what are the most important
> developer needs by way of a survey, then published the findings, then
> acted on those findings we would not feel so kept-in-the-dark.
>
> I'm not getting at DAW, despite what I have already said I think it is
> still a great product with great potential, but I am also aware that
> without subscriptions the resources will not be available to develop the
> product further, without further development subscriptions will be lost
> (this is the root of my frustration).
>
> Can DAW give us some sort of roadmap of development? I see an earlier
> reply to this post speculated on some 16 years before the little
> suggestions were implemented, I know that was tongue-in-cheek, but it
> gives an honest feeling.
>
> Nick
>
>
>
>
> "Mark Rutherford" <mark@freequest.net> wrote in message
> news:kSmb3AA7FHA.4000@dacmail.dataaccess.com...
>> Ditto!
>> If I say ditto more does it count as more votes? <grin>
>>
>> I started using cWindowsEx to gain a lot more functionality, and
>> im sure the reasoning is that if cWindowsEx exists, they wont do it
>> because its there.
>>
>> I think what your asking for exist in most other
>> languages/toolkits/widgetsets/classes, ect.
>>
>> I have asked for some stuff like this before an I think, in all honesty
>> it falls on deaf ears sometimes.
>>
>> The sad thing is that I read all too much that people are migrating off
>> VDF, and I think it has good potential.
>>
>> What got me to like it, and not toss it out when I saw it:
>> The ability to drag fields onto a form...
>>
>> This ability is like no other.... but it does not make up for the lack of
>> other functionality.
>>
>> picturecontainer: would love it. I recall this question asked one year in
>> MMISL and I recall (I hope correectly) Stephen's response: 'Absolutely
>> not'
>> If I recall, DAW .... LibPNG is open source.. :) jpg, gif .. well I can
>> see the snafu there.
>>
>> This really cant be THAT hard to add. (png support)
>>
>> I have asked for easier to get at rows/cells before in grids/dbgrids.
>>
>>
>> My request: how about threading? I cant stand the 'app locking up' look
>> when your doing something intensive.
>> this usually makes progress bars totally useless.
>>
>> sockets would be nice, this way I dont have to write stupid DLLs to do
>> that task (admittedly sockets is a bit much :P)
>>
>> Basically, I have the same gripes.
>> One thing to note, once people start using .net or delphi, or c, they
>> dont usually go back to VDF. once they are gone, you pretty much lose
>> them.
>> There are people here that are dissapearing.
>>
>> LAST THING: allow people to distribute the runtime with their app without
>> having to install it seperately. (meaning the DLLs)
>> its retarded but admittedly minor by comparison.
>>
>>
>> I WISH TOO, like Garret :)
>>
>> Garret Mott wrote:
>>> Hi All -
>>>
>>> I'm tired of working on a project, so in the spirit of work avoidance, I
>>> thought I'd toss out some things I'd like to see. Some of 'em (most?)
>>> may have already been mentioned. I also know that some are available in
>>> 3rd party packages, etc. but I'd like to see 'em all in "native" VDF.
>>>
>>> This focuses on visual tools - not the studio, but what it contains.
>>> These are in no particular order & I'm not asking for much
>>> here..................
>>>
>>> I'm also hoping others will add to & comment on this list!
>>>
>>>
>>> - Fonts throughout the studio: Use fonts & size + bold, italic,
>>> underline - eliminate fontweight style i.e. have properties to set:
>>> Arial, 10, Bold - like other languages & the RichEdit.
>>>
>>>
>>> PictureContainer (i.e. BitmapContiner)
>>>
>>> - allow all common types - jpg, gif, etc.
>>>
>>>
>>> dbGrids
>>>
>>> - Using Scrollbars should not set current record or take focus - should
>>> just scroll the grid
>>>
>>> - Easy to identify cells & rows (i.e. Get Value of Current_Cell, Get
>>> Value of Current_Row Item 2, etc.)
>>>
>>> - TextColor, Color, Fonts, etc. all set by cell, row or column or any
>>> combination of 'em. Have cell setting override column or row.
>>>
>>> - Checkbox, comboform & edit (including richedit - via a popup edit box)
>>> in any cell: Set CellCheckBox Row 3 Col 3 to True
>>>
>>> - Multiple row records
>>>
>>> - Multi-Select of row, column or cells
>>>
>>> - Simple export, addressing & deletion of above selection
>>>
>>> - Picture support in cells - all formats, not just bitmaps
>>>
>>> - Formattable headers - incl. font, colors, multi row & pictures
>>>
>>> - Insert Row (as David Martinko recently did for current dbgrid), but
>>> set by property (i.e. pbAllowInsert=True/False)
>>>
>>> - Sort by clicking header - including Excel type - where just one column
>>> can be changed (OK, this is pushing it;-)
>>>
>>> - Expression Cells:
>>> If (Towing.Vehicle_Freight="V") Set Value to Towing.Make
>>> Else Set Value to Towing.Product
>>>
>>> + Calculated cells
>>>
>>>
>>> Buttons
>>>
>>> - Allow setting of Color & TextColor, Fonts, multiple lines
>>>
>>>
>>> All Labels (forms, comboforms, groups etc.)
>>>
>>> - Allow TextColor, Fonts, multiple lines
>>>
>>>
>>> TextBoxes
>>>
>>> - Allow TextColor, Fonts, multiple lines
>>>
>>>
>>> ProgressBar
>>>
>>> - Show Percentage and # done of # capability
>>>
>

Chris Spencer
19-Nov-2005, 10:26 PM
Nick

Can you give some indication of what type of things are considered "standard
these days"?
Also what things have been asked of you by the boss that you haven't been
able to comply with?
Just curious.

Chris Spencer
TUFware Systems

"Nick Wright" <n.b.wright@btopenworld.com> wrote in message
news:$G0s11U7FHA.3872@dacmail.dataaccess.com...
> Ditto Also,
>
> I think though that DAW is working on a new studio for version 12 -
> because the most important thing for our Clients is that we as developers
> have some fun tools to play with, the fact that we can't deliver to them
> things they understand to be Standard these days is unimportant. (sorry to
> be so flippant but I'm just working off some frustration)
>
> I love working with vdf, and wish to continue to do so but when my boss
> tells me to do something and I can't - not because of my own lack of
> programming knowledge but rather because of some fundamental inner
> workings of VDF which is based on a product model devised some twenty
> years ago - he is simply going to tell me to find a solution, and I, like
> many others will in find a solution in another language, and that's the
> thin end of the wedge.
>
> Let's face it VDF is a great tool to work with, we all use it because at
> some point it filled a need and was the best solution to our problems, we
> are all I think very loyal to vdf, but just lately I feel a shift in
> attitudes. Maybe if DAW asked developers what are the most important
> developer needs by way of a survey, then published the findings, then
> acted on those findings we would not feel so kept-in-the-dark.
>
> I'm not getting at DAW, despite what I have already said I think it is
> still a great product with great potential, but I am also aware that
> without subscriptions the resources will not be available to develop the
> product further, without further development subscriptions will be lost
> (this is the root of my frustration).
>
> Can DAW give us some sort of roadmap of development? I see an earlier
> reply to this post speculated on some 16 years before the little
> suggestions were implemented, I know that was tongue-in-cheek, but it
> gives an honest feeling.
>
> Nick
>
>
>
>
> "Mark Rutherford" <mark@freequest.net> wrote in message
> news:kSmb3AA7FHA.4000@dacmail.dataaccess.com...
>> Ditto!
>> If I say ditto more does it count as more votes? <grin>
>>
>> I started using cWindowsEx to gain a lot more functionality, and
>> im sure the reasoning is that if cWindowsEx exists, they wont do it
>> because its there.
>>
>> I think what your asking for exist in most other
>> languages/toolkits/widgetsets/classes, ect.
>>
>> I have asked for some stuff like this before an I think, in all honesty
>> it falls on deaf ears sometimes.
>>
>> The sad thing is that I read all too much that people are migrating off
>> VDF, and I think it has good potential.
>>
>> What got me to like it, and not toss it out when I saw it:
>> The ability to drag fields onto a form...
>>
>> This ability is like no other.... but it does not make up for the lack of
>> other functionality.
>>
>> picturecontainer: would love it. I recall this question asked one year in
>> MMISL and I recall (I hope correectly) Stephen's response: 'Absolutely
>> not'
>> If I recall, DAW .... LibPNG is open source.. :) jpg, gif .. well I can
>> see the snafu there.
>>
>> This really cant be THAT hard to add. (png support)
>>
>> I have asked for easier to get at rows/cells before in grids/dbgrids.
>>
>>
>> My request: how about threading? I cant stand the 'app locking up' look
>> when your doing something intensive.
>> this usually makes progress bars totally useless.
>>
>> sockets would be nice, this way I dont have to write stupid DLLs to do
>> that task (admittedly sockets is a bit much :P)
>>
>> Basically, I have the same gripes.
>> One thing to note, once people start using .net or delphi, or c, they
>> dont usually go back to VDF. once they are gone, you pretty much lose
>> them.
>> There are people here that are dissapearing.
>>
>> LAST THING: allow people to distribute the runtime with their app without
>> having to install it seperately. (meaning the DLLs)
>> its retarded but admittedly minor by comparison.
>>
>>
>> I WISH TOO, like Garret :)
>>
>> Garret Mott wrote:
>>> Hi All -
>>>
>>> I'm tired of working on a project, so in the spirit of work avoidance, I
>>> thought I'd toss out some things I'd like to see. Some of 'em (most?)
>>> may have already been mentioned. I also know that some are available in
>>> 3rd party packages, etc. but I'd like to see 'em all in "native" VDF.
>>>
>>> This focuses on visual tools - not the studio, but what it contains.
>>> These are in no particular order & I'm not asking for much
>>> here..................
>>>
>>> I'm also hoping others will add to & comment on this list!
>>>
>>>
>>> - Fonts throughout the studio: Use fonts & size + bold, italic,
>>> underline - eliminate fontweight style i.e. have properties to set:
>>> Arial, 10, Bold - like other languages & the RichEdit.
>>>
>>>
>>> PictureContainer (i.e. BitmapContiner)
>>>
>>> - allow all common types - jpg, gif, etc.
>>>
>>>
>>> dbGrids
>>>
>>> - Using Scrollbars should not set current record or take focus - should
>>> just scroll the grid
>>>
>>> - Easy to identify cells & rows (i.e. Get Value of Current_Cell, Get
>>> Value of Current_Row Item 2, etc.)
>>>
>>> - TextColor, Color, Fonts, etc. all set by cell, row or column or any
>>> combination of 'em. Have cell setting override column or row.
>>>
>>> - Checkbox, comboform & edit (including richedit - via a popup edit box)
>>> in any cell: Set CellCheckBox Row 3 Col 3 to True
>>>
>>> - Multiple row records
>>>
>>> - Multi-Select of row, column or cells
>>>
>>> - Simple export, addressing & deletion of above selection
>>>
>>> - Picture support in cells - all formats, not just bitmaps
>>>
>>> - Formattable headers - incl. font, colors, multi row & pictures
>>>
>>> - Insert Row (as David Martinko recently did for current dbgrid), but
>>> set by property (i.e. pbAllowInsert=True/False)
>>>
>>> - Sort by clicking header - including Excel type - where just one column
>>> can be changed (OK, this is pushing it;-)
>>>
>>> - Expression Cells:
>>> If (Towing.Vehicle_Freight="V") Set Value to Towing.Make
>>> Else Set Value to Towing.Product
>>>
>>> + Calculated cells
>>>
>>>
>>> Buttons
>>>
>>> - Allow setting of Color & TextColor, Fonts, multiple lines
>>>
>>>
>>> All Labels (forms, comboforms, groups etc.)
>>>
>>> - Allow TextColor, Fonts, multiple lines
>>>
>>>
>>> TextBoxes
>>>
>>> - Allow TextColor, Fonts, multiple lines
>>>
>>>
>>> ProgressBar
>>>
>>> - Show Percentage and # done of # capability
>>>
>

Nick Wright
20-Nov-2005, 05:33 AM
Chris,

Things they understand to be Standard these days :

Unicode
multi-threading - so it doesn't look like your app just crashed when it's in
a tight loop.
Picture compatibility other than Bitmap (I know you can use an OCX or DLL).
proper xp theme application.

to name a few.

Having companies in 11 different countries with about 5 different languages
mostly using two-byte characters from one central database tends to make
Unicode a pretty high priority.

Nick


"Chris Spencer" <nomail@nomail.com> wrote in message
news:RI4pLHY7FHA.3872@dacmail.dataaccess.com...
> Nick
>
> Can you give some indication of what type of things are considered
> "standard these days"?
> Also what things have been asked of you by the boss that you haven't been
> able to comply with?
> Just curious.
>
> Chris Spencer
> TUFware Systems
>
> "Nick Wright" <n.b.wright@btopenworld.com> wrote in message
> news:$G0s11U7FHA.3872@dacmail.dataaccess.com...
>> Ditto Also,
>>
>> I think though that DAW is working on a new studio for version 12 -
>> because the most important thing for our Clients is that we as developers
>> have some fun tools to play with, the fact that we can't deliver to them
>> things they understand to be Standard these days is unimportant. (sorry
>> to be so flippant but I'm just working off some frustration)
>>
>> I love working with vdf, and wish to continue to do so but when my boss
>> tells me to do something and I can't - not because of my own lack of
>> programming knowledge but rather because of some fundamental inner
>> workings of VDF which is based on a product model devised some twenty
>> years ago - he is simply going to tell me to find a solution, and I, like
>> many others will in find a solution in another language, and that's the
>> thin end of the wedge.
>>
>> Let's face it VDF is a great tool to work with, we all use it because at
>> some point it filled a need and was the best solution to our problems, we
>> are all I think very loyal to vdf, but just lately I feel a shift in
>> attitudes. Maybe if DAW asked developers what are the most important
>> developer needs by way of a survey, then published the findings, then
>> acted on those findings we would not feel so kept-in-the-dark.
>>
>> I'm not getting at DAW, despite what I have already said I think it is
>> still a great product with great potential, but I am also aware that
>> without subscriptions the resources will not be available to develop the
>> product further, without further development subscriptions will be lost
>> (this is the root of my frustration).
>>
>> Can DAW give us some sort of roadmap of development? I see an earlier
>> reply to this post speculated on some 16 years before the little
>> suggestions were implemented, I know that was tongue-in-cheek, but it
>> gives an honest feeling.
>>
>> Nick
>>
>>
>>
>>
>> "Mark Rutherford" <mark@freequest.net> wrote in message
>> news:kSmb3AA7FHA.4000@dacmail.dataaccess.com...
>>> Ditto!
>>> If I say ditto more does it count as more votes? <grin>
>>>
>>> I started using cWindowsEx to gain a lot more functionality, and
>>> im sure the reasoning is that if cWindowsEx exists, they wont do it
>>> because its there.
>>>
>>> I think what your asking for exist in most other
>>> languages/toolkits/widgetsets/classes, ect.
>>>
>>> I have asked for some stuff like this before an I think, in all honesty
>>> it falls on deaf ears sometimes.
>>>
>>> The sad thing is that I read all too much that people are migrating off
>>> VDF, and I think it has good potential.
>>>
>>> What got me to like it, and not toss it out when I saw it:
>>> The ability to drag fields onto a form...
>>>
>>> This ability is like no other.... but it does not make up for the lack
>>> of other functionality.
>>>
>>> picturecontainer: would love it. I recall this question asked one year
>>> in MMISL and I recall (I hope correectly) Stephen's response:
>>> 'Absolutely not'
>>> If I recall, DAW .... LibPNG is open source.. :) jpg, gif .. well I can
>>> see the snafu there.
>>>
>>> This really cant be THAT hard to add. (png support)
>>>
>>> I have asked for easier to get at rows/cells before in grids/dbgrids.
>>>
>>>
>>> My request: how about threading? I cant stand the 'app locking up' look
>>> when your doing something intensive.
>>> this usually makes progress bars totally useless.
>>>
>>> sockets would be nice, this way I dont have to write stupid DLLs to do
>>> that task (admittedly sockets is a bit much :P)
>>>
>>> Basically, I have the same gripes.
>>> One thing to note, once people start using .net or delphi, or c, they
>>> dont usually go back to VDF. once they are gone, you pretty much lose
>>> them.
>>> There are people here that are dissapearing.
>>>
>>> LAST THING: allow people to distribute the runtime with their app
>>> without having to install it seperately. (meaning the DLLs)
>>> its retarded but admittedly minor by comparison.
>>>
>>>
>>> I WISH TOO, like Garret :)
>>>
>>> Garret Mott wrote:
>>>> Hi All -
>>>>
>>>> I'm tired of working on a project, so in the spirit of work avoidance,
>>>> I thought I'd toss out some things I'd like to see. Some of 'em
>>>> (most?) may have already been mentioned. I also know that some are
>>>> available in 3rd party packages, etc. but I'd like to see 'em all in
>>>> "native" VDF.
>>>>
>>>> This focuses on visual tools - not the studio, but what it contains.
>>>> These are in no particular order & I'm not asking for much
>>>> here..................
>>>>
>>>> I'm also hoping others will add to & comment on this list!
>>>>
>>>>
>>>> - Fonts throughout the studio: Use fonts & size + bold, italic,
>>>> underline - eliminate fontweight style i.e. have properties to set:
>>>> Arial, 10, Bold - like other languages & the RichEdit.
>>>>
>>>>
>>>> PictureContainer (i.e. BitmapContiner)
>>>>
>>>> - allow all common types - jpg, gif, etc.
>>>>
>>>>
>>>> dbGrids
>>>>
>>>> - Using Scrollbars should not set current record or take focus - should
>>>> just scroll the grid
>>>>
>>>> - Easy to identify cells & rows (i.e. Get Value of Current_Cell, Get
>>>> Value of Current_Row Item 2, etc.)
>>>>
>>>> - TextColor, Color, Fonts, etc. all set by cell, row or column or any
>>>> combination of 'em. Have cell setting override column or row.
>>>>
>>>> - Checkbox, comboform & edit (including richedit - via a popup edit
>>>> box) in any cell: Set CellCheckBox Row 3 Col 3 to True
>>>>
>>>> - Multiple row records
>>>>
>>>> - Multi-Select of row, column or cells
>>>>
>>>> - Simple export, addressing & deletion of above selection
>>>>
>>>> - Picture support in cells - all formats, not just bitmaps
>>>>
>>>> - Formattable headers - incl. font, colors, multi row & pictures
>>>>
>>>> - Insert Row (as David Martinko recently did for current dbgrid), but
>>>> set by property (i.e. pbAllowInsert=True/False)
>>>>
>>>> - Sort by clicking header - including Excel type - where just one
>>>> column can be changed (OK, this is pushing it;-)
>>>>
>>>> - Expression Cells:
>>>> If (Towing.Vehicle_Freight="V") Set Value to Towing.Make
>>>> Else Set Value to Towing.Product
>>>>
>>>> + Calculated cells
>>>>
>>>>
>>>> Buttons
>>>>
>>>> - Allow setting of Color & TextColor, Fonts, multiple lines
>>>>
>>>>
>>>> All Labels (forms, comboforms, groups etc.)
>>>>
>>>> - Allow TextColor, Fonts, multiple lines
>>>>
>>>>
>>>> TextBoxes
>>>>
>>>> - Allow TextColor, Fonts, multiple lines
>>>>
>>>>
>>>> ProgressBar
>>>>
>>>> - Show Percentage and # done of # capability
>>>>
>>
>
>

Torkild U. Resheim
20-Nov-2005, 05:50 PM
Nick Wright wrote:

> Chris,
>
> Things they understand to be Standard these days :
>
> Unicode
YES!
> multi-threading - so it doesn't look like your app just crashed when it's
> in a tight loop.
Yes, but it's not really a big issue. If we could have two threads; One for
the UI and one for the rest I'd be happy (for a while ;-)
> Picture compatibility other than Bitmap (I know you can use an OCX or
> DLL).
Yes. And proper handling of these images; Transparency et cetera.
> proper xp theme application.
Yes, that would be nice.
>
> to name a few.
I would also like to see the language cleaned up a bit (i.e. make the parser
disallow code that is not per specification), and of course a more detailed
specification. For instance, which characters are allowed in names where.
Why allow ICODE in userspace code etc.
>
> Having companies in 11 different countries with about 5 different
> languages mostly using two-byte characters from one central database tends
> to make Unicode a pretty high priority.
I understand your sentiment. We're having enough trouble with only one
language.
>
> Nick
>
[snip]

Regards,
Torkild.