You’re the best, thank you Ramsey :-) > On Dec 8, 2024, at 6:30 PM, Ramsey Gurley <ramseygur...@gmail.com> wrote: > > Oh, I see, it's a new issue. This is why I haven't merged to master yet :) I > assumed it would take some time for issues to be reported. I can verify you > are right, it works on WOLips master branch but not WOLips5. I'll see if I > can hunt down the problem and fix it. I've started a ticket for it, > > https://github.com/wocommunity/wolips/issues/185 > > On 12/9/24 12:37 AM, Aaron Rosenzweig wrote: >> Yes I noticed this too, that dynamic elements like <wo:if and <wo:str don’t >> do auto-complete anymore. A minor issue. Everything else seems great :-) The >> entity modeler and component editor work in all other respects. >> >> It’s really nice to have WOLips on the latest Eclipse. Thank you Ramsey :-) >> >>> On Dec 7, 2024, at 6:43 AM, Ramsey Gurley via Webobjects-dev >>> <webobjects-dev@lists.apple.com> wrote: >>> >>> If I have to hazard a guess, it is that WOString is not a WOComponent but a >>> WODynamicElement. It doesn't have an API file. ERXBooleanSelector is a >>> component and does have an API file. There could also be some weirdness >>> because WOString is replaced by ERXWOString in wonder, but that would be my >>> first hunch. All the examples you named are dynamic elements unless I'm >>> mistaken. It makes sense that dynamic elements should autocomplete equally >>> well as components if that is the cause. >>> >>> On 12/7/24 7:28 PM, Martino Limido wrote: >>>> Hi Ramsey, >>>> >>>> First, let me express my gratitude for the hard work and dedication to >>>> updating WOLips. The new version (5) installs smoothly on both Eclipse >>>> 2024-09 and Eclipse 2024-12, and I truly appreciate the improvements. >>>> >>>> However, I am experiencing an issue with the WOComponent Editor when using >>>> the latest WOLips version. Specifically, the autocomplete for binding >>>> names does not work for standard WebObjects components (e.g., WOString, >>>> WOConditional, WOTextField). This issue occurs both when using the inline >>>> syntax and when editing the bindings in the .woo file. >>>> >>>> Interestingly, the autocomplete works perfectly for components from >>>> Project WOnder or custom components from internal frameworks or the >>>> current project. >>>> >>>> To better illustrate the problem, you can access the following link: >>>> https://poodoo.xplants.net/test-wolips.mp4. >>>> >>>> I am unsure if this is an issue specific to my environment or a broader >>>> problem. Any guidance or suggestions would be greatly appreciated. >>>> >>>> Best regards, >>>> Martino >>>> >>>>> Il giorno 27 nov 2024, alle ore 21:00, >>>>> webobjects-dev-requ...@lists.apple.com ha scritto: >>>>> >>>>> Hi again everyone. >>>>> >>>>> I just finished setting up a build of WOLips5 with Github actions. That >>>>> means you no longer need to build it locally to install it. The new >>>>> update site url is, >>>>> >>>>> https://wocommunity.github.io/wolips/repository/ >>>>> >>>>> There is currently no index.html so if you go there in a browser, it >>>>> will give you a 404. It will work as an update site url however. It will >>>>> build a fresh update for every push to the wolips5 branch. Maybe we can >>>>> put a nice index.html in there sooner or later :) >>>>> >>>>> Ramsey >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com >>> >>> This email sent to aa...@chatnbike.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
