Is anyone useing aurelia-form,aurelia-api,aurelia-orm from spoonx?

1

Hello,

I am wondering if anyone was using aurelia-form,aurelia-api,aurelia-orm from spoonx ?
Those libraries are no longer developed by spoonx.
Is anyone interested in developing on it and migrate to aurelia 2 ?

2 Likes
2

I think all of those plugins are easy to port, if you are interested, maybe try one and post the questions you got a long the way here?

3

Okay thanks, i’ll try then.
Is there a new skeleton plugin for aurelia2 ? Which one can i use ?

1 Like
4

There’s not a skeleton plugin yet, as it’s relatively straightforward: everything is a registry in v2. A registry is an object with a property register, that is a function that take a container as first parameter. Like the following interface:

interface IRegistry {
  register(container: IContainer);
}

Some example hypothetical plugin scenarios:

  • export a single custom element: then you only need to export it, no need to do extra registration logic
  • export a group of custom elements/custom attributes: then you can do:
import { MyElement1 } from './my-element-1';
import { MyAttribute2 } from './my-element-1';

export const MyPlugin {
  register(container) {
    container.register(MyElement1, MyAttribute2);
  }
}

Anoher example here https://github.com/aurelia-ui-toolkits/aurelia-materialize-bridge/blob/v2/src/index.ts

1 Like
5

Hello,

Thanks for you help,
I have been able to create a basic plugin with this configuration (my first one with v2 !)
i’m moving on to migrate the spoonx plugins.

4 Likes
6

I have used aurelia-authentication: https://aurelia-authentication.spoonx.org/

3 Likes
7

Okay great, can you try porting the plugin to aurelia 2 ?

2 Likes
8

@bigopon i have been able to port 90% aurelia-form. But my brain hurt with the aurelia-view-manager. Can you help ? https://github.com/SpoonX/aurelia-view-manager

1 Like
9

View URL in v1 is a dynamic runtime concept, based on our loader. In v2, we no longer employ a loader, so it will be different, and you no longer have/need this.

And nice progress :+1:

10

Thanks ! But how can I load dynamic custom view for my model ? Is it possible yet in v2 ?

1 Like
11

In v1, you specify a string to load your vm, and that string will be used as module path. Same principle in v2, just the way we load it will be a bit different, and we haven’t decided yet, but probably the loader abstraction won’t be there so there won’t be any view to manage. If we do introduce some loader, it would be just for the compose (will be named au-compose, but you can have alias) specifically.
Dynamically composing different view + view model is possible, though a bit hairy for now. Will update here.

2 Likes
12

Hello @bigopon , is it yet possible to do dynamic custom view ?
good work !

1 Like
13

Hello, do you think it’s possible now ?

1 Like
14

I haven’t had a chance to look at this yet, been a bit busy with the alpha releases, maybe will do it sometime soon. Are you interested in porting them yourself?

15

yeah cause i am full relying on this for my app. I need a bit of guidance for porting it

1 Like
16

It seems the doc site is no longer there. Bringing the doc up maybe the first thing we need to do. Maybe let’s start with something you cannot live out the most? We can try in the following steps:

  • bringing up the doc
  • identify important bits
  • …start porting
17

:cry: seems like the company behind has closed. The domain is no longer available spoonx.org point to another company. :man_facepalming:

1 Like
18

I think the easiest i can start with is GitHub - SpoonX/aurelia-api: A simple convenience wrapper around aurelia-fetch-client.
It just wrapper to aurelia http library

1 Like
19

If it’s only wrapping the aurelia fetch client then we probably can start straight away, as the fetch client has been ported.

20

I might ask kinda dumb questions. What’s the difference beetwen IHttpClient and HttpClient ?

1 Like