On 28-Feb-08, at 20:41 , Mike Schrag wrote:
>>>
>>> 7) WOLips: Some recent email mentioned we could put //VALID next
>>> to some bindings in the wod to prevent warnings from being
>>> displayed. Is there some similar tag that can be used when using
>>> inline notation.
>>
>> Not that I know of.
> Actually, yes -- But ONLY if you use Wonder's inline bindings (this
> does not with with WO 5.4). You can put a // VALID at the end of
> your binding value and it will be considered valid. For instance;
>
> <wo:str value = "$someBrokenBinding // VALID"/>
that's the notation I'm using but it's not working for me. But i'll
further investigate.
>
>>> 10) Eclipse/WOLips: same question about protecting some portions
>>> of a .wo file against reformatting.
>>
>> Huah. File a feature request. But I doubt that this will get a high
>> priority.
> It will get near zero priority :) But if you want to submit a
> patch, even better ... No lie, formatting is some of the hardest
> code I've worked on in WOLips. Nobody would ever imagine. It's all
> crazy hueristics to try to do what most people think is "right" when
> it comes to laying out HTML.
I'm convinced it's quite touchy to code to write and since everybody
has different taste in format/structure, it gets unwieldy. I'm quite
happy with the way wolips format the .wo file except that sometimes I
manually edit some lines to make them more compact vertically
(typically when layout some table). Instead of trying to teach wolips
tons of formats useful in too specific circumstances, simply having it
ignore some section might be an easier alternative. But I agree, it's
not worth much precious time.
>
>>> 12) WOLips: In trying to get clickToOpen to work as recently
>>> demonstrated by Mike, All I got were crashes saying the
>>> "WOLToolbar class/component could not be found" (from memory) I
>>> checked build path, I whecked that WOLips framework was in cluded,
>>> everything extends ERXComponents. I finally got it to go further
>>> by adding "import er.wolips.components.*;"
>>> to my Page wrapper.
>>
>> So, if it works now, where is the problem? ;-) Haven't used that,
>> so somebody else will have to answer that.
> That import would 100% not have any effect on whatever your problem
> was. That's a red herring. I have no idea what your problem was,
> but I can tell you that isn't it. You haven't used it Guido?
> That's my crowning lifetime achievement :)
When I click "open" in the woltoolbar and click some section of the
page, the browsers just stalls trying to load the page and eclipse
does not open any document. The WOApp does not crash, I can interrupt
the browser and navigate the application. My intuition is that the
communication between the woapp and eclipse/wolips server is stalling.
I'll try ot get more info.
>>
>> Other tip: I always start in Debug mode, not in Run. Then when I
>> change things that can't be "hot-fixed" Eclipse shows a dialog
>> whether to terminate or restart the application or just to ignore it.
> 100% yes and 300% yes.
seems nicer indeed. I always assume debug mode is slower than just
running the apps. but it really isn't that different.
Louis Demers eng.
www.obzerv.com
This archive was generated by hypermail 2.0.0 : Thu Feb 28 2008 - 21:22:01 EST