RE: [Rainbowportal-devel] Break in Development?

[Mark A. G. <mgr...@gt...>]

Debugging modules that are not in the core.
We do this all the time, none of our modules are in the core.

Open the module in .Net
Open rainbow in IE

In .Net go debug->processes
Select aspnet process

Set breakpoint in your code
Do something in ie and you will get to breakpoint

Mark


-----Original Message-----
From: HolonCom Support [mailto:su...@ho...]=20
Sent: Thursday, 24 February 2005 8:35 PM
To: rai...@li...
Subject: Re: [Rainbowportal-devel] Break in Development?

Some feedback on my part: What is holding me back of some basic
debugging:

Debugging of modules is a pain since there are split from the core.
Mainly because I don't succeed in running a module in debug mode even=20
with specifying the Start URL in the properties of the project of a=20
module. Breakpoint just get ignored.

Apart from that I discovered (and posted) some bugs that are too=20
complicated for me to resolve.

Last but not least I more and more get irritated by the fact that still=20
many design properties are hardcoded.
widths, heights, colors, ...  I don't dare to remove them from cvs=20
because this could break compatibility of existing designs/layouts.=20
However, this makes it more and more difficult for me to keep in sync=20
with the cvs.
I strongly plead that in version 1.6 all hardcoded design properties=20
would be removed (with only one exception: the table cellspacing=3D0=20
cellpadding=3D0 border=3D0 - because overriding these with css is
problematic )

Basicly, I'm waiting for Bill to release first draft of v1.6.

Rob


on 24/02/2005 8:52 Ed Daniel said the following:

>Thanks for the update John.  Indeed all of us have been consumed by
work
>responsibilities.
>
>Is there any possibility that we might re-ignite those regular online
team
>meetings, they did help synergise - 30 minutes each week for team leads
and
>for each team lead if they could also hold 15-30 minute meetings as
well
>with their teams?
>
>Those meetings were and I hope should be to discuss what has been done
that
>week, what will be done next week and what is stopping us progressing
(a la
>Scrum).  Issues raised in meetings are then taken outside for further
>discussion / resolution - i.e. the meeting is not to resolve issues but
to
>identify them - then each team can address these afterwardsb- team
leads are
>responsible for removing obstacles to progression.
>
>Ed
> =20
>





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Rainbowportal-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel