Board index » delphi » Re: Delphi refocussing on .Net - good or bad?

2008-07-13 04:09:46 PM
delphi135
Hello,
for voting you should use the Win32 client available from the tools menu
but be sure to update it first. You can cast up to 10 votes for each QC
item then! Formerly one single QC user only had a total of 10 votes QC
wide...
I really hope they get that long promised QC web client overhaul out of
the door asap!
Greetings
Markus
 

Bob Dawson writes:
and Notepad++ (nice tool - it has Pascal highlighter and tons of
features) because I didn't figured out why 'sometimes' the 'New edit
window' makes a 2nd copy and 'sometimes' not. Thanks again for the clue.
--
m. th.
 

m. Th. writes:
showing code and design at the same time.
VS.Net can do that just fine. And not just since VS2005.
So it wasn't Winforms. And it still is around in the D2007, so what now?
The same goes for the "oh so difficult to implement Winforms designer".
 

Nick Hodges (Embarcadero) writes:
I hope you will listen to the delphi eco users also.
Can you confirm to what extend Eco 5 will be supported in the Tiburon
due this year end.
ECO team is planning for partial classes & partial methods in Eco V.
Will they be available in Tiburon or we will only have ECO IV in Tiburon
As Michael Swindell has admitted Delphi .net has found more favor with
asp.net & eco makes asp.net development really a breeze.
Hence having the latest eco features in delphi will add lot of value to
delphi .net.Else lot of developers will drift away to VS
venkatesh
 

"Dan Barclay" wrote
over/under, side by side, on different monitors, differently-sized, etc.
And of course I can have a half dozen dicuments tabbed in the additional
editor(s), all available for viewing without losing focus on the one I'm
primarily working on.
the docked view is not multieditor friendly unless you have multiple
monitors.
bobD
 

"Dan Barclay" wrote
uses NHibernate/Gentle/ECO, Log4Net, etc. etc.
The area of potential overlap is basically the area of the non-visual VCL.
Stuff which CG is unlikely to rework at this point.
bobD
 

"Robert Giesecke" wrote
show a winform form and code at the same time. I'd certainly be in your
debt.
soon-to-be-supplied evidence.
bobD
 

Bob Dawson writes:
It should create a new tab group. Now you should be able to see 2 documents at once.
VS.Net makes no difference between a design surface or a text editor. So you can see the designer and
either the user code, or the designer code, or both at the same time.
And sorry, didn't mean you (the not-believing part). You probably just repeated what you have heard by
someone from CG.
 

"Robert Giesecke" wrote
VS2008--either a vertical or horizontal split. Thanks!
I notice that it is not completely live (changes made visually to the form
don't show up in the code editor until you click on it and vice versa), but
I can live with that.
I can see this being very useful for those with super-wide monitors--i'd
still prefer moving an entire tab group to floating mode and over to my
second monitor over the embedded approach, but this is much better than I'd
found before ...
I stand corrected--and I appreciate it.
bobD
 

Bob Dawson writes:
of code at once.
I'd love to see a mixture of what VS can do (that cool splitting) and what CDS can do (new tabgroups)
It just *gotta* more intuitive than what you have to do in CDS to get a new tabgroup.
Dragging a document out of the main window should be sufficient to create a new tabgroup, or put it
into an existing one.
 

Nick Hodges (Embarcadero) writes:
thanks for listening. I use the Form and the code
beside each other to develop concurrently. While
writing code, the form tells me a lot about other
objects, their naming, their events and such.
I develop an application iteratively. With a rough
idea of the functionality in mind I start with a
few button and memos on a form and add functional
parts while testing them. Only of the trivial
components I know every detail. Of the more complex
and more seldom used ones I explore their
possibilities while developping the application.
The form is part of the process and cannot be
swapped away without loosing much overview.
My forms hardly ever exceed 600 pixels in square
and fit nicely on my 1600x1200 sceen together
with the rest of the IDE.
As to the embedded designer... what was
[considered] its advantage over the classical
Delphi IDE, beside being a Visual studio clone ?
Rene
--
Ing.Buero R.Tschaggelar - www.ibrtses.com
& commercial newsgroups - www.talkto.net
 

Bob Dawson writes:
where we use it <g>). But /why/ CG cannot implement such a thing? Also,
if one wants an 'embedded' designer, why should refactor the entire
architecture? Imho, something like the following code will give an
'embedded' designer while keeping the architecture unitary:
pnlDesigner.Visible:=True; //the 'docking' site
frmDesigner.Parent:=pnlDesigner;
{...here we'll have code to persist the original Left & Top coordinates,
perhaps in ExplicitLeft, ExplicitTop, in order to keep the original Left
& Top for RTM & for the case of 'undocked' }
//...and after this reset it in panel:
frmDesigner.Top:=0;
frmDesigner.Left:=0;
...or, if the want, they can implement a full fledged docking engine for
the designer (ie. having the designer as a docking panel etc. etc.).
...but perhaps I am missing something?
--
m. th.
 

Robert Giesecke writes:
give them a 'bona fide' in order to provide them an unbiased help. Imho,
this is much more constructive (and here I don't imply you necessary).
For me, as a humble outsider, a designer which targets VCL, WinForms,
QT, dfm, XAML etc. etc. it is a matter of form format generator. Well,
perhaps isn't everything straightforward, but with a plug-in/driver
architecture, imho, this is quite doable. Something like:
TFormGenerator = class(<whatever>)
//manyLOC
end;
TVCLGen = class(TFormGenerator)
//manyLoc
end;
TWinFormsGen = class(TFormGenerator)
//manyLoc
end;
TQTGen = class(TFormGenerator)
//manyLoc
end;
//...etc...
TFormDesigner = class(...)
...
function GenerateForm(aGenerator: TFormGenerator): TGenStatus;
...
end;
...where's the problem? (...and (un)fortunately I don't ask you Robert -
btw thanks for the clarifications)
AFAIS now, the main problem with supporting a gazillion of libs
shouldn't be the designer... even if, of course, the complexity grows.
But perhaps the wanted to leverage something already done from Microsoft
(I remember vaguely something about 'hardwired' things in Allen's
explanations about 'dropping WinForms support').
HTH,
--
m. th.
 

Robert Giesecke writes:
--
m. th.
 

"Robert Giesecke" wrote
drag a tab off the main form onto the desktop and it became a separate
window. And you could also drag it back where it would snap in as a tab
again. A lot of parentage/ownership issues to deal with, but definitely
do-able.
I don't find the context menu approach all that obscure, but then I do tend
to be a mouser, and given the number of people who don't seem to know it's
there ...
bobD