> solution approach to project management so that I can have multiple
> projects open with shared common code between them all. This would be
> useful when creating different UIs for different devices especially if
> there was a facility that allowed a specific form to be chosen at
> application start based on device type.
>

Good thought. I usually have both the user and admin projects for any
solution. Along with conditional compiling with defines, that would be
good.

--
Matthew Jones

Pinch zoom on iPad

At the moment, when I scroll an EWB app on my mobile, at the end of the scroll, it stops immediately when in all other web pages, the scroll gradually slows down.

Could we have the same in our EWB apps please?

Thanks

Richard

And I have I think suggested before the ability to have "logical folders" in the project files tree. Essentially making them independent of the unit order (or perhaps done using a {$FOLDER Reports} comment in the file or something.

--

Matthew Jones

Rick,

<< I'm not sure if this qualifies as a small thing but I would like a solution approach to project management so that I can have multiple projects open with shared common code between them all. This would be useful when creating different UIs for different devices especially if there was a facility that allowed a specific form to be chosen at application start based on device type.

I guess something similar to solution management in Visual Studio. >>

No, that's not a small thing, but it's a good idea.  I think Xamarin forms does something similar.

Tim Young
Elevate Software
www.elevatesoft.com

Richard,

<< At the moment, when I scroll an EWB app on my mobile, at the end of the scroll, it stops immediately when in all other web pages, the scroll gradually slows down.

Could we have the same in our EWB apps please? >>

I will be addressing touch scrolling shortly by surfacing the ability to specify how touch should be handled on a per-UI element/control basis.  That will allow you to use the default touch scrolling where you want, and intercept the touch events where you want.

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<
I will be addressing touch scrolling shortly by surfacing the ability to specify how touch should be handled on a per-UI element/control basis.  That will allow you to use the default touch scrolling where you want, and intercept the touch events where you want.
>>

That sounds really good. Very important for mobile apps. Looking forward to that.

Uli

Uli,

<< That sounds really good. Very important for mobile apps. Looking forward to that.  >>

Just a quick caveat, though:  this will *only* apply to controls that can be scrolled using the natural scrolling in the browser.  It will *not* apply to grids, list boxes, or any other "virtual" control.  It *will* apply to the multi-line edit control, containers, forms, etc.

Tim Young
Elevate Software
www.elevatesoft.com

Tim.. latest update working fantastic, thanks. EWB footprint at Environment Canada continues to increase!

I know you mentioned 'no need to include them' (because they are already on the list), but I take the liberty to 'vote' on my "if I had to choose 2 things" list :

1. Code completion

.. makes it easier and faster for 'newbies' to explore a new language, but also for the veterans.. who start forgetting stuff. Using this since '95 (Delphi 1), we become spoiled, I suppose

2. SSL support on the EWB server

.. comfort for deploying secure applications to the outside world, avoids having to cobble together tunneling and the like

.. Bruno

Tim, you did a really great job.Thanks !

The only feature I'm missing is the code completion to work faster and get my beer sooner

Luk